If you have the Power add-on and are using the import function , 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
Premier Subscription Licenses must be validated on the primary site of a multi-site install. This is typically the FIRST site in your site list, but can be changed via wp-config. If you are using multi site you should know which site is the primary Blog ID. Adding your Premier id and your license on your sub sites will not validate the WPSLP Premier license. (This information only applies to WordPress SLP and not MYSLP.
Communication with the SLP license server is required for any licenses to be validated. You can check if standard web requests are working between your WordPress install and SLP. This can be tested from within your PHP environment with a simple PHP script that uses a ‘curl’ or ‘file get contents ‘operation.
You can also click on the Store Locator Plus / info tab in the back end of the plug-in. If you are seeing “Latest News” with fairly current dates then the problem is most likely not a blocked communications via a firewall. In those cases the issue is most likely an incorrectly typed subscription ID or you have entered the info on the wrong site of a multi-site install.
The ability to change results layout is included in the Experience add on.
The default format for the results string uses the numerical encoding for the various data elements that can be rendered. This default string format is present in the base Store Locator Plus plugin. You can reset to the default at any time by deleting the entry in the Results Layout field under Settings/Results/Appearance and saving the settings.
Load locations does not replace the csv file import functionality available to the Professional or Enterprise level plan subscribers but it can be used to load basic location data from your WordPress Store Locator Plugin (such as WP Store Locator Plus®,) into your MYSLP account. It will not load category tables.
This functionality can be found from the MYSLP account, the SLP sidebar tab and under Locations as shown in the screenshot below.
The loader supports loading locations from WordPress sites running the WordPress Store Locator Plus plugin. If you are using a locator or directory plugin other than Store Locator Plus, please contact us to discuss the possibility of beta testing if it does not load.
Our MYSLPEnterprise level users or WPSLP Premier subscribers will find several additional map controls to enable or disable built-in Google Map elements. A simple checkbox allows users to turn the Full Screen and zoom controls on or off in addition to the previously-available Hide “Stick Man” , scale, and type controls.
This option is also available to WordPress plugin users with an active Premier subscription.
Changes as of June 11, 2018 will effect the WordPress Store Locator Plus (DIY) community. Google requires all sites using map services to have an API key with a billing account attached. See Google Developers console.
The Browser key is used to display the map and handle user-input addresses during a location search. The Geocoding API is used on your WordPress server to geocode locations you’ve entered via the Google “Places” box and APIs. You do not need the additional geocoding “key” unless you have added restrictions. You do however, need to have the geocoding API enabled in your Google projects library.
Google’s push for all websites to be HTTPS has been a game changer over the past few years with many companies switching from HTTP to HTTPS with some hiccups along the way. Some of the site transfer mishaps are minor, but if done incorrectly can cause your plug-ins to misbehave , and often is the case, after the transition team has left the building.
Mixed Content Warnings – Loading Assets Over HTTP
Site Migrations Vary
Occasionally we see comments from customers that Store locator Plus broke their site or is not working. When asked if they recently migrated their site they often state nothing has changed. On further investigation , or by inspecting their console we often see the “Mixed Content warnings” quite often for images or icons from older versions of Store Locator Plus. This is a sure fire clue that there was indeed a “site migration”. They started out with their site when the SLP plug-in was originally installed as HTTP and now , at least part of their site, is HTTPS. This is known as a protocol migration. If you migrate your site from HTTP to HTTPS, Google treats this as a site move with a URL change. That means you may need to obtain a new Google API key for SLP to work properly. With version SLP 4.9.15 you are allowed to add HTTP referrers now as long as you also obtain a geocode key. See info about those changes under news
A site migration is a great opportunity to address legacy issues. If you have outdated legacy add-ons this is a good time to invest in your future by planning for and including any update expenses in your overall budget. Including these costs in the project scope is the most cost-effective method to ensure your site stays relevant and on-track. When you consider that issues that may arise after going live will require additional time , resources and, yes, may even create downtime and loss of traffic to your site it is worth including the new versions in your budget. Contact support if you have made a recent purchase or check our What to Buy guide for options.
There are settings under the General tab for Admin , User Interface, Server, and Data. This documentation has been updated to reflect the Google API changes
The Admin tab is where your SLP Premier subscription Accounts ID , Enable WP debug , and other info is located. There is also a Reset Manage Locations button available for use to reset the back end Manage Locations display page to the default view (10 locations per page view). This feature was previously only available with the free SLP Janitor Add-on.
The label that will be displayed in front of the Search form box on your locator page can be changed under Settings/Search in the Appearance section Label. If none are set, a blank box will appear on your site. The “Address” Label you enter will appear in front of the search box. The “radius” information indicates to the site visitor that this is the radius (whatever radii you entered in the search form for radii options.
Consider this label as a help text tool for the site visitor to assist them as to what to enter in the box. Label Examples: zip code, city, street, or a combination such as address / zip code. The more detailed the better. We find address and zip code to be the most useful hint. If you leave this label blank nothing will appear in front of the search form box and your site visitors will be guessing what to enter as keywords to search (the same as any other search boxes). They can type in anything that comes to mind and end up with no results.
The second search box is the drop down menu for your distance units. We find the words “Within” useful. If you prefer to enter another language for the labels that appear on the front end , that is your option as well.
Additional Search settings are available with MYSLP Professional or Enterprise level or the WPSLP self managed with the Experience or Premier add-ons.
The location limit feature is available exclusively to our Store Locator Plus Premier/Enterprise customers.
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.
Example: Client has 250 results to return by default but when the site via a URL link loaded they only wanted 5 to come back.
Location Limit functionality supersedes the initial default limit.