As a result of these changes the Enhanced Search Legacy add-onwill no longer be supported and will not work with SLP v. 4.7.4
Pro Pack MUST be updated to 4.6.5
Experience add-on Must be updated to v 4.7.4
With the upgrade of SLP, the Pro Pack legacy add-on will be deactivated. Follow the How to install / update add-on instructions. Download add-on from your account. Delete the old version from the WP Plugin admin panel. Install and activate the newest version.
2016 , bye bye bye… Here’s to you 2017! : We are looking forward to a productive and prosperous year. Last of the year updates for the WordPress Store Locator Plus plug-in as well as updated versions for the featured Power, and Experience add-ons as well as new Premier functionality and features.
Before updating the add-ons, you will be required to update the base Store Locator Plus plugin to 4.7 or higher. Note: If you have bookmarks and/or “auto- form fill” to your WordPress Store Locator Plus account you will need to change the WP-SLP url to the new url .
You can review the WordPress Store Locator Plus change log here.
In case you haven’t noticed, your Store Locator Plus and My Store Locator Plus apps may be working a little different during the last few weeks of 2016. You didn’t change ANYTHING but suddenly things are not exactly like they were before.
It is a special Christmas gift from Google to all of us.
Sometime in late 2016 Google updated their Google Maps API. We are not sure how many changes went into this release. I must have missed the call from Larry and Sergey this time. However we do know a few things that changed that impact customers.
#1 – Geocoding Requires Accurate Addresses
You better make sure your addresses that are sent to Google are darn-near perfectly formed. No more hiding meta in that address 2 field. If a business does not have a suite named “Attn: Customer Service” as part of their official address don’t put it on there. It very likely will not geocode.
Looks like Google is turning the screws a little more on their attempt to squash as much competition in the maps market as possible. Over the past few months they have tweaked their Google Geocoding API algorithms. Each change is going to make it just a little more difficult to get your addresses to return a correct latitude and longitude. It is definitely having an effect on locations people are entering into Store Locator Plus but the truly concerning issue is not with addresses you can fix but how it is going to impact all the odd variations of addresses your customers type in during a search.
As is typical from the Google Maps people, the results from their in-house applications including Google Maps The Website is very different from what non-insiders get. Any application using the Google Maps Geocoding service, whether a $20,000/year OEM license or a few-dollar-or-less-per-month Pay-As-You-Go API key, will see different results. The sad part is that what worked perfectly fine “yesterday” no longer works today.
Several known addresses that were designed to “test the system” suddenly started failing our internal testing over the past few days. After rolling back our software and servers to older releases to ensure we did not introduce a problem we’ve discovered that the change is almost 100% guaranteed to be a change in Google’s Geocoding API algorithms.
Diane Blackwelder CFP ®, Charleston Financial Advisors LLC, 4 N Atlantic Wharf, Charleston SC 29401 USA
Last spring that geocoded perfectly fine. Today it comes back “ZERO_RESULTS” which is Google-speak for “bad address”.
This does not work either:
Diane Blackwelder, Charleston Financial Advisors LLC, 4 N Atlantic Wharf, Charleston SC 29401 USA
Only the 100% proper address works:
Diane Blackwelder c/o Charleston Financial Advisors LLC, 4 N Atlantic Wharf, Charleston SC 29401 USA
Yet on Google Maps ALL 3 of these variations come back with the correct address.
This happens with a number of other addresses as well including this example using Google Maps in Germany with the same type of results:
Hotel Berlin Märkischer, Hof am Tacheles, Linienstraße, 133 Berlin 10115 Germany
While this only impacts a very small percentage of addresses people enter into Store Locator Plus, or just about any other mapping service using Google besides internal Google services like their Places (think Adwords but far more costly), it is still very clear what Google’s long term plans are for businesses using their map services.
Granted, Google can always fall back on the “well, that is technically not the right address” argument but the fact-of-the-matter is that these addresses worked perfectly well before. The same addresses work perfectly well in Google-owned properties TODAY. The addresses do NOT work for any third party applications because someone at Google decided they shouldn’t. Not nice, Google. Not nice. It is increasingly clear that Google intends to slowly strangle all third party mapping-software providers so they can collect all the customers that end up being left behind and throw them into their pay-per-request services.
Looks like we are once again having to seriously consider introducing alternative Geocoding and map image technology solutions. We have been investigating Open Street Map for some time. It looks like 2017 is finally going to see that option come online. It is almost a certainty for our MySLP SaaS service and may be integrated into one of our planned live-service options for our Premier Subscribers.
When people ask why we spent so much time and money building a SaaS service for maps, this is one reason why. It is much easier for us to help our customers have a superior experience for their end users when we can setup, testing and activate alternatives in one step. With per-website installations of Store Locator Plus on 20,000+ servers in 128 different countries providing the same type of pro-active response is impossible. We don’t have any control over what those webmaster are doing and not all of them are tech-savvy.
Sure, buy-and-own options like Store Locator Plus can be cost effective but if you’re business relies on your locator having a managed service makes a lot more sense.
Store Locator Plus version 4.6.4 fixed the zoom settings, the plug-in tabs “save changes” and the back-end UI.
The change in the back end user interface will not be noticeable to most users. The naming of sections and tabs and settings now will use programmatic slugs instead of the plain text names. This allows the settings translations in different languages to remain intact even if language files have not been updated. This means future updates to Store Locator Plus, Power, Experience, and Premier add-ons will no longer lose their settings tabs. Another behind the scenes development is populating the plug-in and add-ons with “smart options” settings. To learn more please watch the developer’s brief You Tube.
You will notice a new look in your admin panel of Store Locator Plus in Version 4.6.2 . Featuring a new sidebar on the admin pages for the settings tabs and the locations tab.
Important fixes: SLP version 4.6.2 fixes the “white screen” error on sites running the older version of WordPress 4.4 and/or Multi-site users running WordPress 4.6.
Show admin help settings in a new sidebar to make it easier to see what each setting does.
Show location details preview in right sidebar on manage locations page.
Added links to direct documentation pages for various settings.
Implement a new slp_get_text_string filter for add-ons to manage text strings.
Additional hard-coded gettext strings accessible to the text manager.
Don’t load the SLP overhead on the WordPress admin heartbeat since SLP doesn’t require “heartbeat” processing. Wouldn’t it be nice if all plugins did that?
Multisite installs – upgrading SLP fixes “not an array” error that would cause white screen on upgrade for sites using WP 4.6+
Fix stripslashes_from_strings_only() undefined function for sites running old WordPress (you really should update to WordPress 4.4+ for security reasons if nothing else).
Recalculate initial distance for all locations on global center map at change.
Performance update: Drop adminUI create_InputElement() method. (Note : This may break pre-4.2 Legacy Add Ons, you must upgrade to the Legacy add-on latest version release. 4.3 or higher or downgrade SLP to earlier version)
Experience will need to be updated to 4.6.2 when updating SLP to 4.6.2
Power Add-on Users reported some glitches with version 4.5.12 imports. The duplicate handling updates has been fixed. Note: In order for the Duplicate Handling Update location to function, either the sl_id or the Contacts field Identifier MUST be present and match what is stored in the location data field. To see the sl_id number you can hover over to the left of the location name under manage locations. Exporting the locations file to a csv file will also show the sl_id. This id is assigned automatically when a user adds a location in SLP for the first time and is not the one you assign as an identifier with contact extender. The specific contact identifier field can be used instead of the sl_id and takes precedence.
Surprise! He did it again…..our world traveler and developer supreme fixed a bug (..truth be told..he probably introduced the !oops! by muddling around with making a good thing great) that was discovered by one of our loyal customers who upgraded to the Power Add-on and shared it with us in the Store Locator Plus Support forum.
We also would like to thank the many new Power users and Premier Members who took advantage of the latest sales campaign to upgrade their Legacy add-ons. Although our summer sales event is alas coming to a close, you die hard Legacy add-on users can still request a coupon to upgrade to the new and improved Power add-on (with faster than ever importing functions, ) Experience Add-on group or our platinum Premier. The coupon value will be determined as shown under the relevant Product Descriptions.
SLP was updated to version 4.5.09 to allow for compatibility with those users who have a lower PHP of 5.5 or lower. WordPress recommends PHP 5.6 but we realize not everyone can get their host to upgrade. WP does provide verbiage (click on the link) to send to your provider host if you are interested in helping put the pressure on. When you upgraded the base plug-in to 4.5.09 and if you had a lower version of ProPack installed, you will see a notice that disabled 4.5 version of Pro Pack. You still have access to it and can upload the latest version (4.5.07). All you need to do is log into your account and download the latest version from there as noted in an earlier blog.
Pro Pack, Tagalong, Pages = Power
As many of you have noticed there have been changes that affect some of our most popular add-ons. The latest updates to these add-ons were made for compatibility reasons as Store Locator Plus continues to evolve on its way to become lighter, more efficient and will use less of your overhead. Pro Pack and Tagalong have joined the ranks of LEGACY add-ons and will not be updated further since the functionality and features have been moved or added to the newer Power add-on. Legacy add-ons will continue to work with the SLP version in use at the time the add-on was purchased Continue reading Store Locator Plus 4.5.09, Premier 4.5.09 and Add-on updates
Store Locator Plus 4.5.08 was released today with several notable updates.
Disabled Add Ons
One of the most prominent “features” users are noticing is that their older add ons are being automatically disabled if they are not compatible with the latest Store Locator Plus release. Having your add on disabled is preferable, at least for most site admins, than crashing your WordPress site. So far in ALL cases the disabled add on has a NEWER VERSION available. Login to your account at StoreLocatorPlus.com to download the latest version of your add on.
You can find the list of versions on the StoreLocatorPlus.com website.
Data I/O Performance
Changes in the extended data manager reduces the data I/O requests through WordPress by at least one, if not a few, data reads for every page load. For sites with heavy traffic this can be a notable performance improvement on page load times.
Complex Data Query Support
Version 4.5.08 of the location query engine has been updated to allow “stacked” queries. Stacked queries make it possible to perform complex location inquiries that were not possible with a single data request. For example “show all locations with no territory assigned that are within X miles of a user PLUS all locations with a territory that covers the user’s location”. This change will allow future Store Locator Plus releases and the forthcoming My Store Locator Plus service to perform very creative location searches in real time.
There are some new Google changes that we anticipated nearly a year ago and is not specific to Store Locator Plus.
Effectively Immediately, all new websites that come online as of June 22, 2016 will require a Google Map API key. This is no longer optional. Store Locator Plus has had the ability to set a Google API key since version 4. Go to the General / Server tab and enter your Google API Server Key.
Any users running Chrome including those using Android based web browsers will no longer be able to auto-detect their location using the location sensor unless the source site is running https. That means that your website must have a valid SSL certificate. If your site URL does not load when you use https:// as the starting part of your web address the location sensor provided by the Power Add On will not work.
The Store Locator Plus developer and team have been busy in the past months updating the base plugin and add-ons to version 4.5 or higher. These include updates to add-on packs, Experience, ProPack, Premier, Power (in pre-release), and some of the more popular third party add-ons (User Managed Locations, Extended Data Manager, Event Location Manager, Social Media Extender, Gravity Forms Locations and Integration) to work with SLP 4.5 and WordPress v 4.5 or higher. If an add-on has not been updated to 4.5, that indicates it is either considered a legacy pack and/or included in a new Add-on.
As mentioned in the developers previous blog, WP 4.5 updated jquery which revealed many errors with themes and plugins that were not using latest versions or blocked/forced jquery versions. SLP uses the recommended jquery version 1.12 or higher.
New feature: an Edit icon will appear in the [[slp]] results list on the front-end for only those locations the logged on user has access to. Clicking the Edit icon will lead to the manage page on the admin section so you would only need to allow the user access to that page. By adding the text “[slp_location uml_buttons]” to the results layout, (changes to layout is available as part of the Experience add-on) you can control the location where the Edit icon appears.
On a separate note, when Store Locator Plus released v 4.5.01 , a new set of issues were introduced on the sites using the Network Active Multisite for WP. Store Locator Plus version 4.5.05 fixed those issues as noted in the release notes and the video. This revealed how many sites were using the SLP add-ons but not purchasing for each site they were running for their customers. This was contrary to the rules of business licensing that had been requested from the start. Therefore, an active Premier Subscription is requested for any sites running network-activated Store Locator Plus with paid add ons. For further information see the below videos.
Ever since WordPress 4.5 rolled off the press there have been numerous complaints about websites breaking. Numerous reports are coming into our Store Locator Plus forums and support email telling us “our map broke when they updated our website”. The problem? jQuery. To be more specific the problem is not jQuery but how some plugins and themes implement jQuery in WordPress.