Load locations does not replace the csv file import functionality available to the Professional or Enterprise level plan subscribers but it can be used to load basic location data from your WordPress Store Locator Plugin (such as WP Store Locator Plus®,) into your MYSLP account. It will not load category tables.
This functionality can be found from the MYSLP account, the SLP sidebar tab and under Locations as shown in the screenshot below.
The loader supports loading locations from WordPress sites running the WordPress Store Locator Plus plugin. If you are using a locator or directory plugin other than Store Locator Plus, please contact us to discuss the possibility of beta testing if it does not load.
The WPSLP Power Add On or MySLP/Professional plan allows you to import CSV files with several options. View the information under SLP/Locations/Import . You have various options to consider when determining how to update locations that match your pre-existing locations.
Options available on how to handle duplicates: Choose to Add, Skip, and /or Update.
Please check your versions on our Home site to ensure you are using the latest versions of the plug-in and add-ons. A lot has changed since release 4.9.2. See our News channel for latest information regarding WordPress, SLP, and Google changes. Changes to the terms for Google API use went into effect or or about June 11, 2018. This effected every plug-in that utilized Google APIs. Newer Versions of WPSLP added fields for Google API key placement. This means, if you had been using older versions in order to keep legacy add-ons, and never added your Google MAP API key to SLP, your map will not display correctly. See News for current information
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.
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
With the Power add-on you will find additional Bulk Actions under the Locations/Manage panel. There is a drop down menu under the Bulk actions tab that can be utilized to remove many, some or all tags associated with the location data. Check off which locations you want to remove the tags from, or you may check off all and select the filter to “Apply to all”
Multiple large-scale exports (export function is available with Power Add-on ) have been tested on the Store Locator Plus dev site. On a relatively small server, a virtual machine with 2GB RAM running CentOS 6, we have been able to export 10,000 locations within 15 minutes with no issues. Special characters and extended data have also exported without issue.
If you are experiencing issues there are several things to check that can cause problems during an export:
Web Server Process Limits
Apache, and nginx as far as I are aware, have per-process limits. This is built into the web server to prevent “runaway” processes that eat up all of the CPU and memory on the server over time. On shared servers this limit is very low and typically allows 30 seconds to 2 minutes of processing time. Large data sets can use up to 5 minutes or more of processing time. Make sure your server has a high enough limit to allow the entire data export to complete execution.