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.
T_PAAMAYIM_NEKUDOTAYIM is the scope resolution operator. In most languages it is the double-colon (::).
Most people that are looking for this odd-looking word are probably running into an issue with a PHP program. For as often as it comes up, there is very little information on what is causing the problem.
With PHP it typically means the application has a syntax error. The PHP interpreter cannot figure out how to compile your code properly and crashes with the Unexpected T_PAAMAYIM_NEKUDOTAYIM error message. Often it is due to a class name or static method reference that PHP cannot handle. Either the class name is entered incorrectly OR your PHP version is so old it cannot process variable names before the double-colon operator.
For Store Locator Plus™ users that are still using the WordPress plugins it most likely means the version of PHP you are running on your web server is very outdated. Upgrade PHP to a newer version, preferably something that is supported in the past 5 years like PHP 7.
User that chose the fully managed Store Locator Plus™ service don’t have to worry about things like this.
Because there is not template specified it will display the “full” (entire/complete) SEO page. Login to the WP site and go to Store Pages as admin, click on any page. What you see there is what you’ll get on the page list output.
That means when we add descriptions to SEO pages (either manually editing the SEO page OR with some new description magic in development today) the ENTIRE page will show up.
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 , Add-on packs User info , and Update Notices are 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.
There is also a Locations management option to Highlight the locations that are not geo-coded on the Panel that displays your entered locations.
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 two years as announced in news posts, blogs , changelogs, mail campaigns 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:
WPSLP 4.9.x or above Power add-on uses the built-in file up-loader 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 up-loader.
NOTE: As of July 2018, if you are using the WPSLP “do it yourself” plugin with Power add-on and you have not included the latitude and longitude and require geocoding , make sure you have a Google API account and have checked off the Maps and Geocoding APIs in your library.
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.