First automated SVN deployment. No code change.<\/p>","1.0.6":"
Readme description translated to English (wordpress.org requirement) and GitHub repository made public so the Plugin URI resolves. No code change.<\/p>","1.0.5":"
Plugin Name shortened to "MRZ Maps Exp" to match the existing slug Updated readme Pre-submission polish for wordpress.org. No functional change, safe upgrade.<\/p>","1.0.1":" Small post-rebrand fixes: admin menu label ("GMaps" \u2192 "MRZ Maps"), uninstall cleanup targeting the right prefixes. Recommended upgrade.<\/p>","1.0.0":" First public release as "MRZ Maps Exp" (Morez.co). Full rebrand from the internal "GMaps-AA" codebase \u2014 namespaces, prefixes, slug and CPT all changed. Sites previously running the internal "GMaps-AA" build must reconfigure their maps after upgrade.<\/p>"},"ratings":[],"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":3565514,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3565514,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.6","1.0.7"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3565514,"resolution":"1","location":"assets","locale":"","width":1940,"height":838},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3565514,"resolution":"2","location":"assets","locale":"","width":1942,"height":1178},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3565514,"resolution":"3","location":"assets","locale":"","width":1942,"height":1362},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3565514,"resolution":"4","location":"assets","locale":"","width":1942,"height":1312}},"screenshots":{"1":"Source data<\/strong> metabox: choose the source post type, the ACF coordinates field, and an optional load limit.","2":"HTML templates<\/strong> metabox: customizable templates for the tooltip and for the list items, with ACF and taxonomy placeholders.","3":"Cosmetic<\/strong> metabox: default marker, size, Spiderfier toggle, and per-term taxonomy markers.","4":"Filters<\/strong> metabox: configure taxonomy and ACF field filters (dropdown \/ radio \/ checkbox mode, OR \/ AND logic)."}},"plugin_section":[],"plugin_tags":[2211,1794,1571,2909,91],"plugin_category":[49,57,59],"plugin_contributors":[266282],"plugin_business_model":[],"class_list":["post-322908","plugin","type-plugin","status-publish","hentry","plugin_tags-acf","plugin_tags-custom-post-type","plugin_tags-google-maps","plugin_tags-map","plugin_tags-taxonomy","plugin_category-maps-and-location","plugin_category-taxonomy","plugin_category-utilities-and-tools","plugin_contributors-mrzxp","plugin_committers-mrzxp"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/mrz-maps-exp\/assets\/icon-256x256.png?rev=3565514","icon_2x":"https:\/\/ps.w.org\/mrz-maps-exp\/assets\/icon-256x256.png?rev=3565514","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/mrz-maps-exp\/assets\/screenshot-1.png?rev=3565514","caption":"Source data<\/strong> metabox: choose the source post type, the ACF coordinates field, and an optional load limit."},{"src":"https:\/\/ps.w.org\/mrz-maps-exp\/assets\/screenshot-2.png?rev=3565514","caption":"HTML templates<\/strong> metabox: customizable templates for the tooltip and for the list items, with ACF and taxonomy placeholders."},{"src":"https:\/\/ps.w.org\/mrz-maps-exp\/assets\/screenshot-3.png?rev=3565514","caption":"Cosmetic<\/strong> metabox: default marker, size, Spiderfier toggle, and per-term taxonomy markers."},{"src":"https:\/\/ps.w.org\/mrz-maps-exp\/assets\/screenshot-4.png?rev=3565514","caption":"Filters<\/strong> metabox: configure taxonomy and ACF field filters (dropdown \/ radio \/ checkbox mode, OR \/ AND logic)."}],"raw_content":"\n 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 \u2014 no theme code required: source post type, filters, pagination, HTML templates, custom markers, responsive layout.<\/p>\n\n 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) \u2014 it is recommended to restrict it by HTTP referrer in the Google Cloud Console.<\/p>\n\n Development happens publicly on GitHub: https:\/\/github.com\/m0r3z\/mrz-maps-exp\nIssues, pull requests and forks welcome.<\/p>\n\n 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 The plugin does not send any data to Morez.co or to any other third-party service. No telemetry is collected.<\/p>\n\n 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.<\/p>\n\n\n Yes. MRZ Maps Exp relies on ACF Google Map fields to retrieve each post's latitude, longitude and address. The plugin is built to integrate with ACF rather than duplicate a custom coordinates system. The free version of ACF is enough; ACF Pro is only required if you use Pro features such as the repeater field.<\/p><\/dd>\n This is a deliberate choice. An API key is a secret that has no place in the database: it could be exfiltrated via a DB export, an unencrypted backup, or a compromised admin account. The key must be declared in the theme code via the Yes. MRZ Maps Exp detects whether Google Maps JS is already loaded by another plugin (e.g. Salient via In the map's \"HTML templates\" metabox, free-form HTML templates are configurable with placeholders: mrz-maps-exp<\/code>. No data migration needed \u2014 all internal identifiers and data are unchanged.<\/p>","1.0.3":"Contributors:<\/code> to the actual wp.org account (mrzxp<\/code>). Cosmetic only.<\/p>","1.0.2":"Features<\/h4>\n\n
\n
[mrz_maps_exp id=\"X\" filter_taxonomy=\"genre\" filter_term=\"42\"]<\/code>.<\/li>\nmrz-maps-exp<\/code>, .pot file provided).<\/li>\n<\/ul>\n\nRequirements<\/h4>\n\n
\n
functions.php<\/code> via the mrz_maps_exp_api_key<\/code> filter or the MRZ_MAPS_EXP_API_KEY<\/code> constant (the plugin deliberately does not expose an admin field for the key \u2014 it is a secret that has no place in the database).<\/li>\n<\/ul>\n\nPrivacy \/ external calls<\/h4>\n\n
Source code and contributions<\/h4>\n\n
External services<\/h3>\n\n
mrz_maps_exp_api_key<\/code> filter or MRZ_MAPS_EXP_API_KEY<\/code> constant in the theme); the plugin itself does not bundle any key.<\/p>\n\nWhat is sent and when<\/h4>\n\n
\n
[mrz_maps_exp]<\/code> shortcode is loaded, the visitor's browser loads the Google Maps JavaScript library from https:\/\/maps.googleapis.com\/maps\/api\/js<\/code>, including the places<\/code> library. The Google Maps API key is appended as a query parameter.<\/li>\nProvider and legal links<\/h4>\n\n
\n
\n
functions.php<\/code>:\n add_filter( 'mrz_maps_exp_api_key', function () { return 'YOUR_API_KEY'; } );<\/li>\n[mrz_maps_exp id=\"X\"]<\/code>.<\/li>\n<\/ol>\n\n\n\n
Is ACF really required?<\/h3><\/dt>\n
Why is the Google Maps API key not configurable from the admin?<\/h3><\/dt>\n
mrz_maps_exp_api_key<\/code> filter or the MRZ_MAPS_EXP_API_KEY<\/code> constant. This is also the recommended pattern for key rotation.<\/p><\/dd>\nIs the plugin compatible with the Salient theme or with other mapping plugins?<\/h3><\/dt>\n
salient-core<\/code> \/ nectar_gmap<\/code>) and does not re-enqueue it in that case. A mrz_maps_exp_skip_gmaps_enqueue<\/code> filter lets you override the behavior if needed.<\/p><\/dd>\nHow do I add content inside the tooltip or list items?<\/h3><\/dt>\n
{post_title}<\/code>, {post_url}<\/code>, {post_excerpt}<\/code>, {post_thumbnail}<\/code>, {post_thumbnail_url}<\/code>, {%acf_field_name%}<\/code>, {taxonomy:slug}<\/code>, {taxonomy:slug:first}<\/code>. Conditional blocks {#if %field%}\u2026{\/if}<\/code> are supported so that an area is only rendered if the field is filled.<\/p><\/dd>\n