We aim at offering a sustainable service as well as stable and secure products to all of our users. As a result we were focusing on improving backend services and infrastructure as well as operational processes during the last 2 months and had to delay the regular developments as a consequence.
Nevertheless v2.3 is now finished and includes not only compatibility fixes but also new features regarding geolocation and enhancements especially for developers and integrators.
An update to the latest version is – as always – highly recommended. Please read below for more details.
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 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 v2.3:
Within Settings / Map defaults / “Geolocate Settings” you will find a new option called Autostart:
By default this setting is set to false. If set this option to true, geolocation will automatically start on all maps. If you only want to start geolocation on selected maps, please proceed to the next highlight of v2.3:
With v2.3 the new javascript variables mapid_js and mapname_js were added to the source code of each maps. This eases the re-usage of javascript-function from outside Map Marker Pro´s framework.
Let´s say for example you want to start geolocation for all maps displayed within your blog archive only. In order to achieve this, you have to add the following javascript code to your template file (usually archives.php, but this may be different based on the theme you are using):
<script type=”text/javascript”>
eval(‘locatecontrol_’+mapname_js).start();
</script>
This change gives you also the flexibility to more easily call direct leaflet.js API commands from outside the plugin framework, e.g. adding a button within your theme which changes the zoom level.
The full reference of the leaflet API can be found here.
With MapTiler you can turn images into interactive map layers that can be displayed with Maps Marker Pro by configuring them as custom basemap or custom overlay.
Matthew Sangster now created a tutorial on how to create custom basemaps using MapTiler – many thanks for that!
The guys & ladies from cgi-branding.com created a new 3D logo for Maps Marker, which is now also used in all our products and services:
many thanks for the great work!
Thanks to Anna Dukan, http://www.unisci24.com/blog/ Slovenian has been added as available translation number 36.
If you also want to contribute to translations (in exchange for a pro license), please visit https://translate.mapsmarker.com/projects/lmm for more information.
Thanks to many motivated contributors, this release includes updates to the following 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%.
Unfortunately there is currently one issue that cannot be resolved directly within Maps Marker Pro:
With WordPress 4.2, Emoji support was added. Unfortunately there is an open bug (details) which can result in frozen maps or crashes on Internet Explorer – so WordPress 4.2, 4.2.1 and 4.2.2 are affected. According to the related trac ticket, a fix is already available and will hopefully be deployed soon with WordPress 4.2.3.
As workaround until WordPress 4.2.3 is available you can only disable Emojis at the moment for maps to also work properly in Internet Explorer.
We am really sorry for this issue, but this is beyond our influence – we already contacted the guys & ladies at WordPress and hope that the fix for the Emoji/SVG bug will be available soon.
Please understand that we 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 we just would want to keep the flexibility to add optimizations and bugfixes with rather unplanned minor releases resulting mostly from users feedback.
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.
 |
new option to automatically start geolocation globally on all maps (see changelog on how to start geolocation for selected maps only) |
|
added javascript variables mapid_js and mapname_js to ease the re-usage of javascript-function from outside the plugin |
|
new tutorial: how to create custom basemaps using MapTiler |
|
new 3d logo for Maps Marker Pro 🙂 |
 |
use CSS classes instead of inline-styles for recent marker widgets to better support overrides (thx Patrick!) |
|
updated customer area on mapsmarker.com as well as switching to PHP 5.6 – please report any issues! |
 |
GPX tracks using UTF8 with BOM encoding do not show up in Google Chrome (thx José!) |
|
SiteOrigin fixed a plugin conflict by releasing Page Builder v2.1 |
|
Removed unset() for validate_local_key() as it could cause the second validation of the local key after refresh to fail |
|
issues with license API calls on servers where SSLVerifyClient directive is set to “required” (thx Ron!) |
|
custom default icon was not saved after “add new marker”-link was used a second time (thx Cyrille!) |
|
custom PHP separator settings for floatval() could result in broken maps (thx Tamas!) |
|
broken layer edit link on marker edit pages after publish- or update-button has been clicked |
|
check for PHP Suhosin patch led to whitescreens on special server configurations if phpinfo() was blocked |
| Translation updates In case you want to help with translations, please visit the web-based translation plattform |
|
|
Slovenian (sl_SL) translation thanks to Anna Dukan, http://www.unisci24.com/blog/ |
 |
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, Fabian Hurelle, http://hurelle.fr and Thomas Guignard,http://news.timtom.ch |
|
updated German translation |
|
updated Latvian translation thanks to Juris Orlovs, http://lbpa.lv and Eriks Remess http://geekli.st/Eriks |
|
updated Norwegian (Bokmål) translation thanks to Inge Tang, http://drommemila.no |
|
updated Romanian translation thanks to Arian, http://administrare-cantine.ro, Daniel Codrea, http://www.inadcod.com and Flo Bejgu, http://www.inboxtranslation.com |
|
updated Russian translation thanks to Ekaterina Golubina (supported by Teplitsa of Social Technologies – http://te-st.ru) and Vyacheslav Strenadko, http://poi-gorod.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 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/ |
|
updated Vietnamese (vi) translation thanks to Hoai Thu, http://bizover.net |
| Known issues | |
 |
Internet Explorer can crash with WordPress 4.2 to 4.2.2 due to Emoji conflict (details) – planned to be fixed with WordPress 4.2.3, workaround until WordPress 4.2.3 is available: disable Emojis |
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 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.
How to verify the integrity of the plugin package
SHA-256 hash value:
238F109F0057EBBACBE0984B01AFFBA2C52E81B93C767F53A28668CFB7F7EFA5
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)
No additional action on plugin update required.