v2.7.2 is a compatibility and bugfix release which focuses on increasing the overall usability on frontend and backend. I would especially like to thank all users reporting issues and plugin conflicts which could also be solved with this release.
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 Facebook, Google+ or subscribe to news via RSS or via RSS/email.
Now let´s get to the highlights of pro v2.7.2:
On the layer edit pages you now can delete assigned markers from the table in bulk:
Thank Chris for that valuable feedback!
Maps Marker Pro already supports displaying maps properly in tabs created with jQuery UI tabs and bootstrap tabs. What caused us some headaches so far were proprietary tab solutions or maps being loaded in hidden divs and shown by click on demand – this could result in maps not being fully loaded.
So with v2.7.2 we now added a new general compatibility settings at Settings / Misc / General Settings:
Please enable this setting only if you are experiencing issues with maps in proprietary tab solutions or hidden divs which are displayed on demand.
The fact that markers cannot be assigned to multi-layer-maps directly, but only to layers which are used in multi-layer-maps, might not be intuitive – especially to new users. With v2.7.2 we tried to improve this by showing an alert info with related information if a user tries to assign a marker to a multi-layer-map:
With Chrome 50 Google made a significant change to the geolocation support of its browser: 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 warning instead:
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.
So if you need the Maps Marker Pro geolocation featue on your site (which with v2.7 even gets more usable as you can sort the list of markers based on the current position of the user), it is strongly advised 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+ (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.
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%.
Please understand that we are not 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 want to keep the flexibility to add optimizations and bugfixes with rather unplanned minor releases resulting mostly from users feedback.
|new bulk action to delete assigned markers on layer edit page (thx Chris!)
|add compatibility setting for maps to load correctly in proprietary tab solutions and hidden divs
|show error message if users tries to assign a marker directly to a multi-layer-map
|“change layer ID” feature on tools page now also updates layer ID used in multi-layer-maps (thx Coen!)
|removed icon width option for widgets (as icon got distorted)
|updated minimum recommended PHP version for built-in PHP check to 5.6 – supporting wpupdatephp.com
|compatibility for ContactForm7 forms in popuptexts on layer maps
|upscaling for MapQuest OSM basemaps to zoom level 18+ was broken (thx Michael!)
|layer maps could be broken if a special settings combination for list of markers was used (thx Lynn!)
|recent marker widget: show separator lines-, show popuptext- and show icons-options did not work as designed (thx Harald!)
|recent marker widget: option to set color value for separator line was broken
|control characters like tabs in marker name could break layer maps with enabled list of markers (thx Peter!)
|REST API error “The specified user already has API keys or the specified user does not exist.”
|compatibility check for WP external links plugin did not work anymore since v2.0 (thx Oleg!)
|trial period independent-access to frontend maps on localhost installations was broken
|layer(s) assignment-dropdown was not ordered by layer ID on marker edit- and tools-page (thx Coen!)
|“change layer ID” feature on tools page did not update assigned markers since v2.4 (thx Coen!)
|“list of markers” table on layer edit pages for multi-layer-map with all markers assigned was not displayed correctly
|Geolocation feature does not work anymore with Google Chrome 50+ unless your site is securely accessible via https (details)
In case you want to help with translations, please visit the web-based translation plattform
|updated German translation
|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
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.
SHA-256 hash value:
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 steps are required if you are updating from a beta version.