Free v3.11.1 with geocoding providers usability improvements and bugfixes is available

Posted on 04 November, 2016

Category:

Free-Version Releases
Attention: this is not the changelog for the latest stable version 4.29.1 (see related release notes)

With v3.11.1 we fixed several bugs and also optimized the usability of the new geocoding provider feature.

Please also have a look at our new blog post about our new partnership with Mapzen – our the new default geocoding provider for Leaflet Maps Marker.

Pro v2.8.1 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 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 v3.11.1:

geocoding provider usability optimizations and bugfixes

  • do not clear (existing) geocoding search results if (no more additional) results are found anymore
  • show 10 instead of 5 geocoding search results for Mapzen, Algolia and Photon@MapsMarker
  • do not switch to alternative geocoding provider if Google Geocoding returns no results
  • show detailed error message if MapQuest Geocoding failed 
  • loading indicator for geocoding search was not shown on marker edit pages  
  • PHP warnings if Photon@MapsMarker for APIs or importer is used and an empty address is given 
  • Google Geocoding initialization could be broken (hotfixed on 30/10/2016)

https is now also required on iOS/Safari 10+ for geolocation to work properly

Please be aware that since Apple release iOS 10, https for your website is now also required on Safari 10+ if you want to offer the geolocation feature to your visitors. See this post for more details.

broken (OSM based) maps on retina devices on highest zoom level

With v3.11 we increased the maximum zoom level for OpenStreetMap and Stamen maps – this resulted in no map tiles being shown on retina devices when using the highest zoom level.

With this version we added a temporary workaround by automatically disabling retina device detection on mobiles. We will remove this workaround again after updating leaflet.js in Leaflet Maps Marker to v0.7.7, which we have on our roadmap for the near future.

FYI: Maps Marker Pro is not affected from this bug and no workaround has been included there, as leaflet.js version 0.7.7 is already used there.

Other changes and optimizations

  • removed MemCached support for importer and Stiphle rate limiting due to compatibility issues reported
  • auto-select marker/layername, mapwidth, mapheight & zoom input values on backend on input focus 
  • new compatibility setting “maxZoom compatibility mode”

Other bugfixes

  • bulk actions on “list all markers page” could be broken since v3.11 (thx reeser!)
  • “add marker link” for layer center icon was broken after geocoding search result was selected on layer pages
  • fatal error on activation if another plugin also utilizes WP_Session_Utils-class (thx Jan-Willem!)
  • unneeded checked=”checked” output on import pages on backend 
  • openpopup-links in list of markers after search did not work since v2.8 (thx Takeo!)

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 80%, the translator receives a free 25 licenses pack worth €249 as a compensation for completing the translation to 100%.

Outlook – plans for the next release

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.

Full changelog

blog post about our new partnership with Mapzen – the new default geocoding provider for Leaflet Maps Marker
new compatibility setting “maxZoom compatibility mode” for themes conflicts where markers on (Google) maps are not displayed properly 
do not clear (existing) geocoding search results if (no more additional) results are found anymore
show 10 instead of 5 geocoding search results for Mapzen, Algolia and Photon@MapsMarker 
do not switch to alternative geocoding provider if Google Geocoding returns no results 
removed MemCached support for importer and Stiphle rate limiting due to compatibility issues reported 
auto-select marker/layername, mapwidth, mapheight & zoom input values on backend on input focus
show detailed error message if MapQuest Geocoding failed  
broken (OSM based) maps on retina devices on highest zoom level (disabled retina detection by default as workaround) 
bulk actions on “list all markers page” could be broken since v3.11 (thx reeser!) 
“add marker link” for layer center icon was broken after geocoding search result was selected on layer pages 
Google Geocoding initialization could be broken (hotfixed on 30/10/2016)
fatal error on activation if another plugin also utilizes WP_Session_Utils-class (thx Jan-Willem!)
PHP warnings if Photon@MapsMarker for APIs or importer is used and an empty address is given
unneeded checked=”checked” output on import pages on backend
loading indicator for geocoding search was not shown on marker edit pages
Translation updates
In case you want to help with translations, please visit the web-based translation plattform
updated German translation
updated Russian translation thanks to Ekaterina Golubina (supported by Teplitsa of Social Technologies – http://te-st.ru) and Vyacheslav Strenadko, http://slavblog.ru 

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”. Alternatively you can also download the current version here, unzip the package and overwrite the plugin´s files on your webserver.