Google Server (Browser) Key for WPSLP

Get A Google API Key

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.

Before you get started you will need to get a Google Maps Javascript API Key.

Please note, there are some misleading instructions in the Google developer console telling you to  create a browser-restricted API key when you move your site to production. You do not need to do that but if you do then you will also need a second unique key to add in the second field under the SLP/General settings the Geocoding API key.  Either way you must “enable” both the Maps  and Geocoding APIs.  When you create your project , obtain  your Maps Javascript API you will see selections under the Maps Javascript API for more options.   One of those options is Geocoding API.  Check to see that is also enabled for your project. View the support documents under google for more information. They have added many different APIs. The ones you need for WPSLP to work properly are the two in the screenshot below, referred to as Maps Javascript and geocoding (not to be confused with geolocation). The Geocoding API  converts addresses into geographic coordinates (geocoding), which you can use to place markers or position the map. This API also allows you to convert geographic coordinates into an address (reverse geocoding).

Step 1: Go To the Google Developer Site

CSV Import Duplicates Handling

The WPSLP Power Add On  or MySLP/Professional plan   allows you to import CSV files with several options.     Under SLP/Locations/Import  options.  You select which option you wish to use when determining how to update  locations  that match pre-existing locations.

There are several options available for duplicates handling. They are  Add, Skip, and Update.

T_PAAMAYIM_NEKUDOTAYIM

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.

How Store Pages Templates and [slp_pages] Work

Available In: WordPress Store Locator Plus™ with the Power add on.
Not yet available Coming Soon (ETA 2019): Fully Managed Store Locator Plus™ (MySLP) service.

Showing A List Of Pages — Full Content

[slp_pages style=”full” no_map=”1″ pages_directory_entry_css_class=”slp_page location_details col-xs-12″]
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 Aware

The Location Sensor capability is a Power feature in WPSLP or Professional feature in MYSLP.

Location sensor feature can be  turned on/off with a simple check box under the SLP/General/User Interface tab.

MYSLP Power Level or higher Plan
WPSLP Power add-on General 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.

Google  returns a “No results found” if you do NOT have an HTTPS site and will stop the javascript from loading. An update to SLP with the Power add-on will negate Location sensor settings entirely if you do not have https://  so that your page continues to load.   If you require the location sensor functionality to work properly you must have  a valid SSL certification.

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.

Google Geocoding and Browser keys

This article effects the WordPress StoreLocatorPlus  users “Do it yourself “

MAP Service and API Keys

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 Maos Javascript API. You do not need the geocoding “key” added to the back end of SLP  unless you have added referrer restrictions.  You do however, need to have the geocoding API enabled in your Google projects library.

General Settings

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

Admin

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.
2016general-admin
There is also a Locations management option  to Highlight the locations that are not geo-coded on the Panel that displays your entered locations.

Store Locator Plus INFO Plug-in Environment

Plug-in environment

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.

 

Plugin environment example

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.

 

Store Locator Plus 4.8 and above updates will disable Legacy add-ons

Legacy Add-ons

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-onPower 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:

Store locator Plus  updates and retired add-ons

 

Import process using WordPress Store Locator Plus Power add-on

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 .

WP CRON can be found under Forms WP environment

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.

Click on the file to see the file size and meta data