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 year as announced in our news posts, blogs 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:
SLP 4.9 with the Power add-on now uses the built-in file uploader 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 uploader.
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.
The Power Add-on Import allows the administrator to schedule your Import process from a remote file retrieval to provide more control over recurring imports from a full url where you CSV file resides and allows flexibility for scheduling the time for daily imports. WordPress cron is not exact, it executes the next time a visitor comes to your site. WordPress times are UTC/GMT time NOT local time. Set to none and leave the URL blank to clear the cron job. Example: 14:25. (Default: empty = do not run daily cron)
Checking your server, PHP and MySQL to ensure the character set is correct will go a long way toward importing special characters like registration characters.
If you have the Power add-on you will have the ability to import data fields via a properly formatted csv file. All columns MUST have a header row with the field name. All fields are short text fields, up to 255 characters, unless otherwise noted. The header text is NOT case sensitive.
If you are using the category (aka tagalong) functionality of Power you may want to import and assign a category slug on the fly. The header field name is:
category (or plural categories).
If you wish to import and assign more than one category per location , you will need to use a comma-separated list for the data field (category). Example: My location has more than one category associated with it, I want to indicate it is a hotel,restaurant, and has music. Category for that location would show under the column with the header row “category”…. hotel,restaurant,music
Alternatively, to define parent/child relationships , i.e. hierarchical categories , use a double colon as the separator Example the Parent is Facility, the child is showroom.
If checked , use the faster MySQL Load Data method of file processing. Only base plugin data can be loaded, see the approved field name list.
This feature uses the MySQL Load Data command and is much faster than WordPress / PHP CSV file parsing, with the typical Google Geocoding limitations on performance and record counts (if you are not supplying, filling in the latitude/longitude data fields). This feature will only import basic location data. It does not import extended data fields or (Tagalong) category data. If you use this along with pre-entered latitude and longitude values you can import 100,000 locations in less than 10 minutes on a basic web server. The column headers must be included in the file and must match the basic fields. You do NOT need to include all columns.
The same 9 places with full address and latitude and longitude. Including latitude and longitude gets the locations online and active on the site faster. This was created from an Export CSV of the above Full Address file when we stripped the sl_id column and all the blank columns at the end, relabelled the header row to be user friendly.
Location Imports are handled via a CSV file for users that signed up for the MySLP Power service or are using the WPSLP Power Add On.
CSV Import Format
Getting the proper CSV format can be a challenge when using spreadsheet apps like Excel or Numbers. Here are some tips to getting a valid CSV format out of a spreadsheet app:
Make sure you always have a header row. That tells the import process what data is in each column. The column headers have meaning, so be precise.
When a cell is a text field that STARTS WITH A LEADING ZERO, make sure you explicitly mark the cell as text. The easiest way to do this is to type a single apostrophe then the number when adding data to the cell as in ‘01886 for the zip code 01886.
Always export with UTF-8 support enabled.
Export to a CSV format. Comma delimited not tab delimited and quoted strings if given the option.