外掛標籤
開發者團隊
原文外掛簡介
MRZ Maps Exp is a generic, minimalist plugin to display any custom post type on a Google Map. Coordinates are read from an ACF Google Map field declared on each post. Everything is configured from the WordPress admin — no theme code required: source post type, filters, pagination, HTML templates, custom markers, responsive layout.
Features
Multiple maps via a dedicated Custom Post Type — each map has its own configuration.
Filters by taxonomy and by ACF field, in dropdown / radio / checkbox mode, with OR / AND logic.
Hybrid search in a single field: Google Places address suggestions and posts whose title matches the input.
Optional URL filter synchronization — share a pre-filtered link.
Customizable markers: default icon, or per-term taxonomy icon.
100% custom tooltip via OverlayView (not the native InfoWindow), fully overridable in CSS.
Configurable HTML templates for the tooltip and the list, with ACF / taxonomy placeholders.
Front pagination, automatic fit bounds after filtering, recenter on the current post in single template.
Overlapping marker spiderfier (OverlappingMarkerSpiderfier).
Snazzy Maps: paste a JSON to style the map.
Responsive layout — filters above, left or right; detachable full-width search field; collapsible filters on mobile.
Shortcode with optional forced filter: [mrz_maps_exp id="X" filter_taxonomy="genre" filter_term="42"].
Translation-ready (text-domain mrz-maps-exp, .pot file provided).
Requirements
WordPress 6.3 or later, PHP 7.4 or later.
Advanced Custom Fields (Pro recommended) — for the Google Map field.
A Google Maps API key with the “Maps JavaScript”, “Places” and “Geocoding” APIs enabled. The key must be declared in the theme’s functions.php via the mrz_maps_exp_api_key filter or the MRZ_MAPS_EXP_API_KEY constant (the plugin deliberately does not expose an admin field for the key — it is a secret that has no place in the database).
Privacy / external calls
MRZ Maps Exp loads the Google Maps JavaScript library in the end user’s browser, like any mapping plugin. No data is sent to Morez.co or any third-party service; no telemetry is collected. The Google Maps API key supplied by the site administrator is exposed on the client side (required to call Google’s JS API) — it is recommended to restrict it by HTTP referrer in the Google Cloud Console.
Source code and contributions
Development happens publicly on GitHub: https://github.com/m0r3z/mrz-maps-exp
Issues, pull requests and forks welcome.
External services
This plugin relies on the Google Maps JavaScript API to display the interactive map, geocode addresses entered in the search field, and provide place autocomplete suggestions. The Google Maps API key is supplied by the site administrator (via the mrz_maps_exp_api_key filter or MRZ_MAPS_EXP_API_KEY constant in the theme); the plugin itself does not bundle any key.
What is sent and when
When a page containing the [mrz_maps_exp] shortcode is loaded, the visitor’s browser loads the Google Maps JavaScript library from https://maps.googleapis.com/maps/api/js, including the places library. The Google Maps API key is appended as a query parameter.
When the visitor types in the search field, each keystroke (debounced) sends the current query string to Google’s Places Autocomplete service to retrieve address suggestions. If the visitor picks a suggestion, Google’s Places Details service is then called to obtain the coordinates for that place.
The visitor’s IP address is transmitted to Google as part of these HTTP requests, as it is for any third-party request initiated by their browser.
No data is sent to Google when the plugin is only installed or activated in the admin — only when a public page containing the shortcode is loaded.
The plugin does not send any data to Morez.co or to any other third-party service. No telemetry is collected.
Provider and legal links
Service: Google Maps Platform (Google LLC).
Terms of Service: https://cloud.google.com/maps-platform/terms
Privacy Policy: https://policies.google.com/privacy
It is the responsibility of site administrators to obtain a valid Google Maps API key, accept Google’s Terms of Service for the project that key belongs to, and disclose the use of Google Maps in their own site’s privacy policy where required.
