This section pertains to the WordPress Store Locator Plus plug-in which is the free base plugin for those WordPress administrators who are controlling the plugin and updates. If you are a subscriber to MySLP, our fully managed locator SaaS service, you can ignore this page, we’ve got that covered!
Location sensor feature can be turned on/off with a simple check box under the SLP/General/User Interface tab.
When the box is checked and a visitor to your site performs a search , SLP queries the browser and requests their current location. If the browser allows location queries it will return their geographic location which will be used to set the default search location.
Note: This will only work with most browsers if you have a secure site or if your site visitor “allows” there location to be visible to you. Google Chrome has had restrictions since Chrome version 50 (released in 2016) that they will only return locations using location sensor if the request is generated within the url of a valid secured site (https://). See the Google developers console for more information.
Location Aware Browsing
Accuracy varies greatly from location to location. In some places, service providers may be able to provide a location to within a few meters. All locations returned by service providers are estimates only and we do not guarantee the accuracy of the locations provided. Your SLP settings also determine the number of locations shown nearest the site visitor. Settings for radius, number of results to return and center of map all interact to show locations nearest to the site visitor.
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 referrer restrictions. You do however, need to have the geocoding API enabled in your Google projects library.
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 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.
Note: In order to enable these settings you must enter your Premier Subscription user ID and Subscription ID under the General / Admin tab. When entered correctly the notice under “Add On Packs , Subscription Accounts” will tell you your subscription is validated. This feature is only functional while your subscription is active.
When your subscription has been validated you will see new options available to you under several Store Locator Plus tabs. The new Security settings will appear under the General tab, Server subtab as shown below.
Block Requests Limit
This is the maximum number of location searches a user can perform within the Block Requests Time Span before their IP address is blocked from all locator requests.
This should be set to an integer value greater than 0.
The first page load request from an IP address is always allowed, even if this setting is 0.
If this is set to “2” and the Block Request Time Span is set to “Hour” the system will allow 2 location searches before the IP address is blocked.
The initial loading of the locator page will count as a “search” if you have the default “show locations at startup” enabled.
Changing this parameter will not release already-blocked IP addresses.
Block Requests Time Span
This setting determines over which period of time the locator request limit is checked. A user that has more than the Block Requests Limit number of locator searches performed in this time period will cause their IP address to be blocked from future location searches until their IP is “released” from the block list.
Setting this value to Never will disable the IP blocking system.
Changing this parameter will not release already-blocked IP addresses.
Release IP After
This is the maximum amount of time a request is “remembered” for a given IP address. Once this amount of time has passed since the most recent location request that triggered the block the IP address is “released” and once again free to perform location searches.
A list of IP addresses that will not be tracked by the blocker. This allows unlimited location lookups from these IP addresses.
Keep in mind that an IP address is not a unique “user” or “computer”. Many locations share an IP address such as a hotel or your local Starbucks. The limitations will apply to the entire group of users from the same shared IP address.
Once an IP address has been blocked, subsequent location requests are not tracked until the block has been released. This design lessens the server load in both volume of data stored and data I/O requests. It helps alleviate issues from possible denial-of-service type attacks where a bot loading requests in rapid succession could overwhelm the data storage and/or database I/O processing.
Blocking Locator Requests was added in the Premier Plugin version 4.7.11.
Store Locator Plus . Premier subscription holders with active subscriptions for WordPress Store Locator Plus or are Enterprise level subscribers for MySLP have a module that adds URL control functionality.
Upgraded Premium Features
The application separates functionality into different application modules. This will ensure that extra overhead is not incurred for features not being deployed in your environment. The interface for turning modules on and off is found under the General | Server tab in the Web App Settings section.
The WordPress plugin includes a module for building SEO friendly web pages based on location data. The option is a checkbox to enable the Pages module . This can be found under the General | Server | Web App Settings section.
Enterprise / Premier Users
Enabling the Territory Bounds module was moved from the General | Data tab to the General | Server | Web App Settings section.
A URL Control module was been added to the application for Enterprise or premier subscribers. Enabling this module will turn on the interface to allow additional data to be presented in a web page URL to impact how the locator behaves.
URL Control : Allow Location In URL
The first URL Control option is to pass a location ID in via a URL. Adding ?location=<id> to the end of a web page address that hosts the locator will cause the page to load with the specified location being highlighted as if the map marker was clicked. The default behavior is to show the info bubble for that location.
Return customers who have upgraded to the newer add-ons will notice a change in the menu 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.
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