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.

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.

Enable Pages Setting WordPress SLP Power add-on

Included in WPSLP Power only  NOT available with MYSLP

Find it under Store Locator Plus | General | Server

 

Enable Pages turns on the Store Pages (“Pages” or “SEO Pages”) functionality of Store Locator Plus.     Once enabled a new Pages tab will appear under Store Locator Plus Admin Panel menu and the Store Locator Plus | Locations | List will have new entries under bulk actions.

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.

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.

CSV Import Zip / Postal Codes

When creating a CSV import file make sure the zip / postal code column is properly formatted as text so you do not lose leading zeros.

The column header for postal/zip codes is zip or sl_zip.

In the United States many northeastern postal codes start with zero.   Many sheets, Microsoft Excel in particular, LOVE to lead off the leading zero if you enter a zip code as 03907 and save as CSV.

Invalid Postal Codes
Invalid Postal Codes

In Excel, and many other apps, you can force a field where you are typing in numbers to be text by starting your entry with an apostrophe (‘).  Type ‘03907 when entering the data NOT 03907.

A good test is to open your CSV file in Google Sheets and see what it looks like.  Does it look like the sheet above missing a zero?  The data is likely wrong.

Another indicator that this column is set to a numeric type and not an text type is the data is on the RIGHT SIDE of the cell.  Text is left-justified (like sl_state) and numbers are right-justified.

Note:

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.

 

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

CSV File Import Header

All Store Locator Plus CSV files must start with a file import header that indicates what data is in each column.

The  first row of the Store Locator Plus import file should look like this, you do not need the (sl in front of the header name for the basic import function to work):

Please see the Example CSV files post for a sample base file with a header.

To speed up imports you should NOT include columns that have no data.

For imports that did NOT start out as a CSV export from the SAME SITE you should NOT have an sl_id column.

For geocoding, assigning a latitude and longitude, to work during import you need to have at least one of the address fields in your file and preferably these main fields:

  • sl_address
  • sl_city
  • sl_state
  • sl_zip

All field names can drop the leading “sl_” for readability.   For example sl_address can become address. The field names usually match the field label, for example the Experience add on can have “Featured” and “Rank” as import columns.

To import files you must have the Power add on for WordPress plugins or be using the Professional, or Enterprise level of service for MySLP.

Curly Quotes In WordPress Shortcodes

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.

Straight versus curly quotes when pasted into a page.

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.

The fix?

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.