This release focuses on the Google API changes which are in effect since January 22nd 2016 and helps fixing related potential issues.
Pro v2.7.3 has also been released today – upgrade today for more features and optimizations.
An update to the latest version is – as always – highly recommended.
Let me know what you think about this new release by submitting a review!
If you want to keep up to date with the latest Maps Marker development, please follow @MapsMarker on twitter (= most current updates), on Facebook, Google+ or subscribe to news via RSS or via RSS/email.
We would also like to invite you to join our affiliate program which offers commissions up to 50%. If you are interested in becoming a reseller, please visit https://www.mapsmarker.com/reseller
Now let´s get to the highlights of pro v3.10.6:
Google has changed the Google Maps API on June 22nd 2016, requiring a mandatory Google API key for all sites, which call the Google Maps API services for the first time after June 22nd 2016 – full details here.
If this is true for your site/domain, you need to register a free API key to be able to continue using Google services on your site. v2.7.3 assists you in verifying this and helping you through this process – in addition to our updated tutorial on how to register a Google Maps API key at https://mapsmarker.com/google-maps-api-key.
We discovered that this change could also lead to issues, if another plugin or theme also enqueues the Google Maps API – in particular if that implementation does not take your Google Maps API key in account or does not load all libraries needed for Leaflet Maps Marker. As a result maps or address search may not be working anymore.
So in order to prevent this, we added a new compatibility check. If this is true for your site, you will see the following admin notice:
To fix this, you can either manually remove the additional Google Maps API calls from third party plugin or themes or – as we would recommend – enable the new compatibility option “Deregister Google Maps API scripts enqueued by third parties”:
This will call the wp_dequeue_script()-function for all Google Maps API call from third party plugins or themes – preventing them from being loaded.
Thanks to many motivated contributors, this release includes the following updated translations:
If you want to contribute to translations (new Hindi translators would be appreciated!), please visit https://translate.mapsmarker.com/projects/lmm for more information.
Please note that translators are also compensated for their contribution – for example if a translation is finished less than 50%, the translator receives a free 25 licenses pack worth €149 as a compensation for completing the translation to 100%.
Please see the roadmap for a rough schedule for planned features of the pro version and please subscribe to this blog (via RSS or Email) or follow @MapsMarker on twitter (= most current updates) if you want to stay up to date with the latest development news.
 |
compatibility check and option to deregister Google Maps API scripts added by 3rd party themes or plugins |
|
compatibility check for “Page Builder by SiteOrigin” & “Yoast SEO” where a special settings combination is causing maps to break |
 |
enhanced Google Maps API key support which is mandatory since June 22nd 2016 |
 |
compatibility check for Autoptimize plugin was broken as plugin was updated |
|
“improve map” and “ToS” links on layer maps with Google as basemaps were not clickable |
| Translation updates In case you want to help with translations, please visit the web-based translation plattform |
|
 |
German |
|
Russian thanks to Ekaterina Golubina (supported by Teplitsa of Social Technologies – http://te-st.ru) and Vyacheslav Strenadko, http://slavblog.ru |
How to download / update
The easiest way to update is to use the WordPress update process: login with an user who has admin privileges, navigate to Dashboard / Updates, select plugins to update and press the button “Update Plugins”. Alternatively you can also download the current version here, unzip the package and overwrite the plugin´s files on your webserver.