News

Store Locator Loading Indicator

The loading indicator, a graphical indicator that is shows up as a spinning circle when locations are loading, has been patched in the November update of My Store Locator Plus®.

Loading Indicator
Loading Indicator

Enterprise users that enabled this feature may have had had an issue where the map would not display when this feature was enabled.    The problem has been ongoing since its introduction earlier this summer but was not brought to our attention until recently.   The patch to address the issue is now online.

The Loading Indicator settings are under Store Locator Plus® | Settings | Results for Enterprise level users.

Location Map and Directory Listing Improvements

Several changes have made it into the October 2018 release of My Store Locator Plus®.  The updates include features users of the mapping and directory service have been asking for since the start of the summer.

Faster map loads

Users that generate embed codes for their Weebly, Wix, Squarespace or other sites will notice a small change to the code — we now serve up a minified JavasScript snippet.  The compressed code will load faster and take up less memory on your site.   Mobile users visiting your site will like that.

Users that have already embedded the map may want to grab the new embed code by logging into MySLP and copying the code from Generate Embed.

Store Locator Plus updates and Patches

With so many changes in the wind these days about APIs and the speed  in which the Google MAP API  terms of service  in their “cloud” platform have been happening , we are always thankful when our customers point out changes that have occurred in the WPSLP functionality.  Thank you to our forum poster, Paul , for pointing  us in the right direction by deactivating Power and exposing the zoom  issue.  If you discover something isn’t working the way it used to, check for updates.  Posting in the WordPress Store Locator Plus  forums is the best way to bring issues to our attention.  Providing your Plugin environment , as Paul did, helps us the most. The more people who post the issue with a screenshot of their plug-in environment, the more likely we are to believe it really might be a bug in SLP.