Pro v2.9 with support for WPML multilingual maps is available

Creating multilingual maps has never been easier, thanks to full WPML support added with this release. In addition we fixed some nasty bugs regarding geocoding and several issues reported by our users – thanks a lot for this valuable feedback! 

An update to the latest version is – as always – highly recommended. For more details about this release please see below.


Let us know what you think about this new release by submitting a review or leaving a comment below!

If you want to keep up to date with the latest Maps Marker Pro development, please follow @MapsMarker on twitter (= most current updates), on FacebookGoogle+ 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

uncle-sam-mmp
We want YOU for Maps Marker Pro!
Join our team as a freelance developer and apply now!
https://www.mapsmarker.com/join-the-team


Now let´s get to the highlights of pro v2.9:

WPML translation support for multilingual maps

Based on many requests by our users, we finally added support for displaying all map content in different languages by adding full WPML support.

For details on how to translate your map content, please see the new WPML tutorial.

New products for renewing your access to updates and support

If you want to make sure to profit from new features, optimizations and bugfixes, you need to have an active access to updates and support for Maps Marker Pro.

As we value long term relationships, we are now also offering the possibility to renew your access to updates and support for 3 and 5 years – with 10% respectively 15% discount.

For more details please click here.

Enhanced Javascript Events API for LeafletJS

In order to make Maps Marker Pro more flexible for developers, we added the new function getAllMarkers(), allowing you to better customise Maps Marker Pro according to your needs.

See related API docs for more details and an usage example.

Other changes and optimizations

  • automatically trigger geocoding search after fallback geocoding is activated
  • update leaflet-locatecontrol from v0.49 to v0.58 (includes new options & bugfixes, full changelog)
  • disabled geolocation control by default for new installations only (as this feature will only work with modern browsers if map is accessed via https)
  • updated compatibility check if plugin “WP External Link” is active, which can cause layer maps to break
  • if compatibility option “Deregister Google Maps API scripts enqueued by third parties” is enabled, scripts from maps.googleapis.com/maps/api/js are now dequeued too
  • temporarily disabled SQLite & SQLite3 caching method for importer due to conflicts with PHP 5.6.29+ (thx Frederic!)

Bugfixes

  • Latitude and longitude values were swapped when using Mapzen Search for importer or APIs (thx David!)
  • MapQuest Geocoding did not deliver correct results for importer and APIs
  • custom MapQuest Geocoding errors were not shown for importer and APIs
  • list of markers CSS conflicts with twentyfifteen themes (thx Verena!)
  • geocoding provider selection for Mapquest Geocoding and Google Geocoding was broken for importer (thx Resi!)
  • trim bing maps API key to prevent issues caused by spaces on input
  • opening popups from links in list of markers could result in javascript error on layer maps with clustering enabled
  • “duplicate layer and assigned markers” button did not duplicate layer controlbox status correctly (thx Thorsten!)
  • selecting geocoded address was broken on marker edit pages if direction link was not added to popuptext automatically (thx Thorsten!)
  • action bar search for list of markers was broken for multi-layer-map with “display all markers” option enabled (thx jacob!)
  • importer: links to show the detailed error message for each row did not work properly

Known issues

Geolocation feature does not work anymore with Google Chrome 50+ and Safari 10+ unless your site is securely accessible via https

With Chrome 50 (and Safari 10) significant changes to the geolocation support were introduced by the related browser vendors: all applications requesting the current position of the user (not just for Maps Marker Pro´s geolocation feature) are only allowed anymore to retrieve the current position of the user if the site is setup to be delivered securely via https – users will see the following or a similar warning instead:

geolocation-error-info

See more details about this decision by Google at https://developers.google.com/web/updates/2016/04/geolocation-on-secure-contexts-only. Geolocation will still work on non-https sites if the users access the site via alternative browsers like Firefox, Safari or Internet Explorer – anyway it could be likely that those browsers will also add a similar security restriction in the future.

Update November 2016: since iOS 10 also Safari 10+ now requires https to support geolocation. The implementation is even more strict than with Google Chrome – geolocation will not work for example if there are mixed-content warnings on your site.

So if you need the Maps Marker Pro geolocation featue on your site, it is highly recommended to migrate your site to https. Some hosters already provide free https certificates from letsencrypt.org for example. For configurations needed within your WordPress site in order to configure it to support https, please have a look at tutorials like https://css-tricks.com/moving-to-https-on-wordpress/.

As https has more advantages for your site than just geolocation working again with Google Chrome 50+ and Safari 10+ (like securing the data integrity, sender authentication and user privacy as well as higher Google ranking as https is used as ranking signal), we strongly advise to switch your site to https only if you haven´t done so yet.

If you switched your site to https and still get a geolocation error (like “Geolocation error: user denied geolocation”), please check your device´s location settings if it is allowed for apps/web sites to retrieve the geolocation.

Translations updates

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 €249 as a compensation for completing the translation to 100%.

Outlook – plans for the next releases

Please understand that we are not able to promise any release dates for new features. We are dynamically aligning our roadmap based on feedback from our users. Anyway we keep the flexibility to add optimizations and bugfixes with rather unplanned minor releases resulting mostly from users feedback.

For Maps Marker Pro v3.0 we plan to upgrade leaflet.js from v0.7.7 to v1.0.2.

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.

Full changelog

WPML translation support for multilingual maps
renewal for access to updates and support is now also available for 3 and 5 years – with 10% respectively 15% discount (details)
Javascript Events API for LeafletJS: add getAllMarkers() function
automatically trigger geocoding search after fallback geocoding is activated
update leaflet-locatecontrol from v0.49 to v0.58 (includes new options & bugfixes, full changelog)
disabled geolocation control by default for new installations only (as this feature will only work with modern browsers if map is accessed via https)
updated compatibility check if plugin “WP External Link” is active, which can cause layer maps to break
if compatibility option “Deregister Google Maps API scripts enqueued by third parties” is enabled, scripts from maps.googleapis.com/maps/api/js are now dequeued too
temporarily disabled SQLite & SQLite3 caching method for importer due to conflicts with PHP 5.6.29+ (thx Frederic!)
Latitude and longitude values were swapped when using Mapzen Search for importer or APIs (thx David!)
MapQuest Geocoding did not deliver correct results for importer and APIs
custom MapQuest Geocoding errors were not shown for importer and APIs
list of markers CSS conflicts with twentyfifteen themes (thx Verena!)
geocoding provider selection for Mapquest Geocoding and Google Geocoding was broken for importer (thx Resi!)
trim bing maps API key to prevent issues caused by spaces on input
opening popups from links in list of markers could result in javascript error on layer maps with clustering enabled
“duplicate layer and assigned markers” button did not duplicate layer controlbox status correctly (thx Thorsten!)
selecting geocoded address was broken on marker edit pages if direction link was not added to popuptext automatically (thx Thorsten!)
action bar search for list of markers was broken for multi-layer-map with “display all markers” option enabled (thx jacob!)
importer: links to show the detailed error message for each row did not work properly
Geolocation feature does not work anymore with Google Chrome 50+ & iOS/Safari 10+ unless your site is securely accessible via https (details)
Translation updates
In case you want to help with translations, please visit the web-based translation plattform
updated Catalan translation thanks to Efraim Bayarri, http://replicantsfactory.com, Vicent Cubells, http://vcubells.net and Marta Espinalt, http://www.martika.es
updated Dutch translation thanks to Marijke Metz – http://www.mergenmetz.nl, Patrick Ruers, http://www.stationskwartiersittard.nl, Fokko van der Leest – http://wandelenrondroden.nl and Hans Temming – http://www.wonderline.nl
updated German translation
updated Greek translation thanks to Philios Sazeides – http://www.mapdow.com, Evangelos Athanasiadis – http://www.wpmania.gr and Vardis Vavoulakis – http://avakon.com
updated Italian translation thanks to Luca Barbetti, http://twitter.com/okibone and Angelo Giammarresi – http://www.wocmultimedia.biz
updated Lithuanian translation thanks to Donatas Liaudaitis – http://www.transleta.co.uk and Ovidijus – http://www.manokarkle.lt
updated Russian translation thanks to Ekaterina Golubina (supported by Teplitsa of Social Technologies – http://te-st.ru) and Vyacheslav Strenadko, http://slavblog.ru
updated Spanish translation thanks to David Ramí­rez, http://www.hiperterminal.com, Alvaro Lara, http://www.alvarolara.com, Victor Guevara, http://1sistemas.net, Ricardo Viteri, http://www.labviteri.com, Juan Valdes and Marta Espinalt, http://www.martika.es
updated Swedish translation thanks to Olof Odier http://www.historiskastadsvandringar.se, Tedy Warsitha http://codeorig.in/, Dan Paulsson http://www.paulsson.eu, Elger Lindgren, http://bilddigital.se, Anton Andreasson, http://andreasson.org/ and Tony Lygnersjö – https://www.dumsnal.se/

show all available changelogs

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”. The pro plugin checks every 24 hours if a new version is available. You can also manually trigger the update check by going to Plugins and clicking on the link “Manually check for updates” next to “Maps Marker Pro”:

manual-update-check

If you do not see the link “Check for updates” and are using a version below 1.7, please update manually once by downloading the current package from https://www.mapsmarker.com/download-pro and overwritting the existing plugin files on your server via FTP. This might be needed on several hosts, which use outdated SSL libraries, which prevent Maps Marker Pro from making a secure connection to retrieve the update package from mapsmarker.com. Pro v1.7 includes a workaround for those kind of servers and the following updates should work again as usual. If you are affected and need help, please open a support ticket.

How to verify the integrity of the plugin package

SHA-256 hash value:

A44241DA87C20B83799B69D96FA68E9A2D4F45DB497D954FAF9A7A406AC43A96

Click here for a tutorial on how to verify the integrity of the plugin package (recommended if the plugin package for a new installation was not downloaded from https://www.mapsmarker.com – verification is not needed though if the automatic update process is used)

Additional update notes for beta tester

No additional actions on plugin update from beta to final version are required.

Leave a Reply

Your email address will not be published. Required fields are marked *