We often have questions posted from users asking why something is or is not working. The information needed to be able to assist them properly and efficiently is shown under the SLP/INFO tab. It is called the Plugin environment.
What is meant by the Plugin Environment.
The plugin environment shows the versions of Store Locator Plus, and any active SLP add-ons you have installed, as well as the WordPress version, php version, MYSQL , the domain name and other useful data specific to the WPSLP environment.
This information is required when posting in forums. You can also find the latest release versions under your account Downloads List, and/or review the Versions under the Support tab on the WordPress Store Locator Plus home site to see if you have the most recent version of Store Locator Plus and the various add-on packs.
The auto-update of WordPress v 4.8.2 and above required a major update to the WP Store Locator Plus free base plug-in resulting in the end of compatibility with the popular Pro Pack , Tagalong and other Legacy add-ons. The Legacy add-ons are no longer supported nor maintained and have been retired over the past year as announced in our news posts, blogs and social media. If you are not sure if your add-on is considered Legacy, see the FAQ comparison featured to Legacy add-ons
Time to invest in your future
Some of our customers were surprised by the change and retirement of the Legacy Add-ons. We tried to give as much of a heads up as possible using news blogs, content news to the home site and reached out using a Mail Chimp campaign for those most likely effected. Ultimately, there is no sure fire method to reach the thousands of customers who may have had these older add-ons installed. If there is one thing we know, change in the technical genre is inevitable. The SLP support team will always endeavor to help our customers transition to the new age. We pledge they will see real value-added from updating their site and software . Please take a moment to review the multiple benefits of utilizing the newer Experience add-on, Power add-on.
Although downgrading to an earlier version of SLP is an option, you may note that changes to the WordPress code and their security patches may disable features. Before making any changes to your site you should ensure you are backing up your site WP database and files. It is very important to take this step before you have issues or worse, site crashes. WordPress security has become more robust over the years.
For more information please see this important message from the author:
SLP 4.9 with the Power add-on now uses the built-in file uploader provided by WordPress Core instead of a custom file import script. If you were able to import and now do not see that process working, look in the Media Library in WordPress. Make sure your install has not disabled the default WordPress media uploader.
What to look for when importing
Do you see the CSV file you just imported? If not then your site has disabled the WordPress media uploader.
If your file IS in the media library but never gets past the offset “0” setting check to make sure your server has not disabled the WordPress Cron .
Check to see if your server is preventing the wp-cron.php from being triggered.
Check your import file in the media library by clicking on it. It should show what the file size is and the current offset. The offset is where the background process is shown while importing the file. If it is shown as “zero” then your WordPress Uploads directory for the media library has been set to non-standard restricted access meaning the background location import process is not allowed to open the file after it was uploaded.
If you want to keep the legacy add-ons, do not upgrade the base plug-in to version 4.7 or above. All individual legacy add-ons have been phased out and replaced over the past 2 plus years due to security patches, coding changes, WP updates, maintenance overhead and inefficiencies that were no longer viable to support. To find the match to your Legacy Add-ons, see FAQ: Legacy versus featured add-on
Please follow the SLP news feeds for important information about updates.
Even if you received a notice in your WordPress admin panel that an update to your base plug-in is available, you do not need to click the update button. All version updates to SLP are optional. We do not auto-update like WordPress does.
If you already updated (most likely if you are reading this) and now try to roll back SLP to earlier version to o retain the Legacy add-on compatibility.
Note: Due to the security patches required by Word Press you may also need to rollback WordPress. Before attempting to roll back or downgrade WordPress or any plugins , make sure you have a recent back-up of your site. Do not attempt this on a live site.
The SLP author does not recommend rolling back versions of any software or WP.This is time consuming and messy, requires technical savvy, and you will miss important security patches. If you are confident that you know what is entailed and are willing to take the risk; it is still recommended to use a back-up service such as Vault Press or Jet Pack.
P.S. If you do not want the headache of maintaining back-ups , updating, obtaining a new Google API, you may want to consider moving over to a My SLP plan. See MYSLP SAAS
WordPress blog posts likes to use curly quotes instead of straight quotes whenever you write an article. Our documentation site is built on WordPress which means many of our articles are replaced any quotes we type in an article with curly quotes.
The problem is that the WordPress shortcode processor does NOT like curly quotes. If you use curly quotes in a shortcode attribute such as [slp_directory by=”city”] and those quotes are “curly”, WordPress treats the quotes as a plain-old alphabetic character just like the C-I-T or Y in “city”. In other words WordPress things you mean “by quote-city-quote” not “by city”.
Why is that an issue?
If you copy-and-paste most examples from this documentation site WordPress will copy the “pretty curly quotes” into your shortcode. If you paste that into your WordPress page it breaks.
An example of how this can impact Store Locator Plus can be seen from my example where I pasted the slp_directory shortcode directly from the docs site into my test site. I get an invalid data query because WordPress added curly-quotes to my data field name. The SLP database does not have a field name quotesl_storequote but does have a field named sl_store.
Make sure you re-type each quote manually. Typing the ” in your blog instead of copy-and-paste will ensure you are getting “straight quotes” in your shortcode attributes not curly quotes.
This is how the example looks now that the curly quotes have been replaced with straight quotes.
Return customers who have upgraded to the newer add-ons will notice a change in the location of some of the functionality/features that were part of the separate legacy add-ons , now available in the Power add-on. (see Legacy to feature add-ons)
Legacy Add-on Tagalong = Categories on the header tab in the Store Locator Plus User Interface.
Legacy Pages = General / Data /Enable Pages. To use the SEO Pages you must first “enable Pages” under this setting.
When the URL Control module is active you can enable location ID passing by turning on “Location Selection” under the General / User Interface tab.
When this is enabled you can pass in a location ID by adding ?location=<id> to the end of the page address where your locator map is deployed with the [slplus] shortcode.
When the location ID is present and the settings is enabled the specified location will be activated on the location map as if a user had clicked the marker on the map. This will show the info bubble by default.
Note:If cluster map markers are enabled they will be turned off for the initial page load. Subsequent input or searches by the user will re-activate the cluster map markers.
Note: When passing in a location ID via a URL the location latitude/longitude will become the center point for the map display. The location that is shown will be at the top of the result listing if sort by distance (default) is in place.
When the URL Control module is active you can enable location ID passing by turning on “Location Limit” under the General / User Interface tab.
When this is enabled you can pass in a limit for the number of locations to be returned when the map initially loads and when a search is performed by adding ?limit=<id> to the end of the page address where your locator map is deployed with the [slplus] shortcode.
Filter By Tag
When the URL Control module is active you can filter locations to show only this matching the tag(s) by turning on “Filter By Tag” under the General / User Interface tab.
This setting will require the Power Add On to be installed and active.
This setting will also require the following shortcode to be present in the Results Layout. The shortcode is standard in most Store Locator Plus provided Style Gallery Styles. It can be removed or changed if you have the Experience Add On active.
An example of a Results Layout where locations are assigned a single tag. With multiple tags the entire list will be hyperlinked and will not likely perform as expected. Note the [slp_location data.sl_tags] takes the place of the [slp_location pro_tags] shortcode that is set by default on most Style Gallery styles.
If you have the Power add-on using the import function and your csv file is incorrect, or your header rows are not accurate, or they have wrong field names, the columns may be misaligned and the data field for an address could not import and/or does not geocode. Check your import message log.
Google does not recognize an address. See FAQ post
With the Power add-on you will find additional Bulk Actions under the Locations/Manage panel. There is a drop down menu under the Bulk actions tab that can be utilized to remove many, some or all tags associated with the location data. Check off which locations you want to remove the tags from, or you may check off all and select the filter to “Apply to all”