v3.9.3 focusing on bugfixes and refinements is available

Posted on 10 October, 2014

Category:

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

This release is dedicated to Pippin from pippinsplugins.com who wrote the inspiring post “Refinement: the greatly unappreciated aspect of project releases” 🙂

I also believe that in the long run fixing bugs and adding optimizations for existing features is more important than just adding new features – so v1.9.1 includes lots of bugfixes and refinements which you will probably not notice, but which are important for a smooth overall usability – read below for detailed changes.

For even more features and optimizations (see the comparision page), please use the integrated pro upgrader to start a free 30-day-trial of Maps Marker Pro (Pro v1.9.1 has also been released today).


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.

I 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 v3.9.3:

support for accent folding for API and importer geocoding calls 

The MapsMarker API now also supports accent folding for addresses, which means special chars are better supported when sending an address to Google for fetching gelocation data.

Other changes and optimizations

  • compatibility check for Sucuri Security plugin which breaks maps if option “Restrict wp-content access” is active
  • MapsMarker API: use “MapsMarker API” as createdby & updatedby attribute if not set

Bugfixes

  • leaflet-min.css was not properly loaded on RTL themes (thx Nic!)
  • custom default marker icon was not saved when creating a new marker map (thx Oleg!)
  • custom panel background for marker maps was taken from layer map settings (thx Bernd!)
  • Google+Bing language localizations could be broken since WordPress 4.0 as constant WPLANG has been depreciated
  • Bing culture parameter was ignored and fallback set to en-US when constant WPLANG with hypen was used
  • RSS & Atom feeds for marker and layer maps did not validate with http://validator.w3.org
  • remove slashes before single apostrophes (Arc d\’airain) in addresses for new maps / on map updates (thx Guffroy!)
  • sort order on “list all markers” page was broken on page 2+ if custom sort order was selected (thx kluong!)

Translations updates

Thanks to many motivated contributors, this release comes with 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 gets a free 25 licenses pack worth €149 as a compensation for completing the translation to 100%.

Outlook – my 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

support for accent folding for API and importer geocoding calls (to better support special chars)
compatibility check for Sucuri Security plugin which breaks maps if option “Restrict wp-content access” is active
MapsMarker API: use “MapsMarker API” as createdby & updatedby attribute if not set
leaflet-min.css was not properly loaded on RTL themes (thx Nic!)
custom default marker icon was not saved when creating a new marker map (thx Oleg!)
custom panel background for marker maps was taken from layer map settings (thx Bernd!)
Google+Bing language localizations could be broken since WordPress 4.0 as constant WPLANG has been depreciated
Bing culture parameter was ignored and fallback set to en-US when constant WPLANG with hypen was used
RSS & Atom feeds for marker and layer maps did not validate with http://validator.w3.org
remove slashes before single apostrophes (Arc d\’airain) in addresses for new maps / on map updates (thx Guffroy!)
sort order on “list all markers” page was broken on page 2+ if custom sort order was selected (thx kluong!)
Translation updates
In case you want to help with translations, please visit the web-based translation plattform
updated Danish translation thanks to Mads Dyrmann Larsen and Peter Erfurt, http://24-7news.dk
updated Dutch translation thanks to Patrick Ruers, http://www.stationskwartiersittard.nl
updated French translation thanks to Vincèn Pujol, http://www.skivr.com and Rodolphe Quiedeville, http://rodolphe.quiedeville.org, Fx Benard, http://wp-translator.com, cazal cédric, http://www.cedric-cazal.com and Fabian Hurelle, http://hurelle.fr
updated German translation
updated Polish translation thanks to Pawel Wyszyński, http://injit.pl, Tomasz Rudnicki, and Robert Pawlak
updated Spanish translation thanks to Alvaro Lara, http://www.alvarolara.com, Victor Guevara, http://1sistemas.net, Ricardo Viteri, http://www.labviteri.com and Juan Valdes
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://20x.se and Anton Andreasson, http://andreasson.org/

show previous 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.