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 of Maps Marker Pro – read below for detailed changes.
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.
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 pro v1.9.1:
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.
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%.
For pro v2.0 I plan to add support for Google Streetview.
Please understand that I am not being able to promise any release dates for new features. The roadmap for major new features gives you an idea where Maps Marker Pro is heading – anyway I just would want to keep the flexibility to add optimizations and bugfixes with rather unplanned minor releases resulting mostly from users feedback.
Please also see the roadmap for a rough schedule for planned features 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.
 |
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!) |
|
potential CSS conflict resulting in geolocate icon not being shown (thx Christopher!) |
|
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!) |
|
API delete action for markers was broken (thx Jason!) |
|
“Delete all markers from all layers” function on tools page did not delete cached QR code images |
|
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 |
|
MapsMarker API search action did not work as designed if popuptext or address was empty (thx Jason!) |
|
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/ |
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 12 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”:
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.
No additional action on plugin update required.