Import using WordPress Store Locator Plus Power add-on

This page /information does not apply to SLP SaaS. This information is provided for the SLP do it yourself plug-in only

WPSLP   Power add-on  uses the built-in file up-loader provided by WordPress Core instead of a custom file import script.   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

Legacy Add-ons not compatible with SLP version 4.8 and higher

 Legacy Add-ons

If you want to keep the legacy add-ons, do not upgrade the base plug-in to version 4.7 or above.   All individual legacy add-ons have been phased out and replaced over the past 2  plus years due to security patches, coding changes, WP updates, maintenance overhead and inefficiencies that were no longer viable to support.  To find the match to your Legacy Add-ons,  see FAQ: Legacy versus featured add-on

Please follow the SLP news feeds for important information about updates.

Even if you received a notice in your WordPress admin panel that an update to your base plug-in is available, you do not need to click the update button.  All version updates to SLP are optional.  We do not auto-update like WordPress does.

If  you already updated (most likely if you are reading this) and now try to roll back SLP to earlier version to o retain the Legacy add-on compatibility.

Note:  Due to the security patches required by Word Press  you may also need to rollback WordPress.  Before attempting to roll back or downgrade WordPress or any plugins , make sure you have a recent back-up of your site.  Do not attempt this on a live site.

The SLP author does not recommend rolling back versions of any software or WP.   This is time consuming and messy, requires technical savvy,  and you will miss  important security patches.     If you are confident that you know what is entailed and are willing to take the risk;  it is still recommended to use a back-up service such as  Vault Press or Jet Pack. 

P.S. If you do not want the headache of maintaining back-ups , updating, obtaining a new Google API, you may want to consider moving over to a My SLP plan.   See  MYSLP SAAS

 

Q. Why am I seeing a message that I do not have sufficient permissions when I am trying to manage my locations?

You Do Not Have Sufficient Permissions

If you are getting the message “you do not have sufficient permissions to access this page” when trying to access the “Manage Locations” or “Map Settings” page, but “Add Locations ” is working it is because another plugin is interfering with the submenu management module in WordPress. You will likely find that any plugin that has a separate sidebar menu with multiple entries underneath will only work on the first entry. There is little we can do to remedy the situation without risking breaking other plugins. We suggest deactivating other plugins, one-at-a-time, until you find the plugin causing problems then ask them to rewrite their menu and submenu process and admin panel filters to ensure the basic menu system remains intact.

Gray map or blank map and/or search does not work

JavaScript Problems:

Note: Major Updates to WordPress versions 5.0 and 5.5 may effect more plug-ins and cause additional errors. We advise updating on a staging site or test site first.

Many times we hear that an update to SLP broke “everything” Upon asking  for clarification  we find out that they also updated WP and/or  other plugins or that they didn’t update other plugins to work with the current version of WP.  WordPress explains how to  use your browser to diagnose javascript error

Issues with the JavaScript part of the plugin usually manifest themselves by showing the search form but either a blank map, a map that is all gray, or a map that appears but search does not work. To identify what is causing your issue use the Firebug add-on with Firefox or any Browser developer tools (see above how to diagnose with browser).

The WordPress Store Locator Plus map rendering is managed by the slp.js JavaScript file.  It sets up the communication with the built-in WordPress AJAX handler, admin-ajax.   Your server must be setup to allow the built-in WordPress AJAX handler to execute.  Additionally, ANY PLUGIN or THEME that is breaking javascript will break SLP functionality. This is rarely an issue with the SLP plugin.

Common errors or issues:

The PHP JavaScript connector did not load

We have come across this error on several installations. The short answer to this problem is that something in the WordPress installation prevented the Store Locator Plus JavaScript component from loading. This means that the map system cannot communicate with Google. This prevents the map from appearing and search results from working properly on your locations page.

Here are some issues we’ve come across that cause this to happen:

    • PHP version is < 5.3, this generates an error message that you will not see in the browser. Any error message will prevent the JavaScript PHP file from loading. SLP will not work with versions lower then PHP 5.3.
    • PHP Error Reporting Enabled, if PHP error reporting is enabled and ANY PLUGIN has bugs, uses deprecated WordPress functions, or uses deprecated PHP functions they will generate an error message. This error message can be hidden in the browser if the error happens in something that is creating page header information. This will also break the page loading process and prevent the JavaScript PHP from loading.
    • Plugin Errors, any plugin that does not load properly and does ANYTHING with page header output will break and thus cause a domino effect prevent the Store Locator Plus PHP JavaScript component from loading.

In many cases the cause of the maps not loading is because our PHP JavaScript file could not load. We can often detect this and pop-up the “PHP JavaScript connector did not load” warning. However we cannot catch all errors. Why good Javascript is critical.

One of the best tools for searching for errors in the HTML page headers is to use Firefox with the Firebug plugin or any browser developer tool. Turn on the console and check the responses tab under console for any errors. We have resolved many client installation and map problems with this plugin. More often than not we are finding errors in other plugins, themes, or server/site  configuration settings.

The PHP JavaScript page header is a critical part of a working Store Locator Plus installation. Since it loads very late in the page creation process it is susceptible to failures from almost anything else you may be loading on the page or your WordPress site. The the map is not loading and you are receiving this message get some page debugging/tracking tools like Firebug and isolate any plugins that are generating coding/output errors.

IF YOU Update your WordPress environment , BE SURE TO  review  the WordPress VERSION changes  as they have changed.

Review the WordPress suggested requirements

  • Update PhP to 7 or higher
  • Update MySQL to 5.6 or higher
  • Site move to HTTPS 

2017 was  the year  WordPress was requiring   hosts to have HTTPS available. Just as JavaScript is a  necessity for smoother user experiences ,  updated PHP versions are critical for performance,  and SSL just makes sense as the next hurdle  users are going to face.   Note: Google also weighs SSL as a search engine ranking factor and have begun flagging unencrypted sites in Chrome.

Search and results not loading

AJAX Blocked

It is common for web hosts and system administrators to disable the built-in WordPress AJAX processing.   Store Locator Plus requires AJAX to be enabled.   This typically manifests itself with the AJAX call to the admin-ajax.php script not executing.

You can test this by directly surfing to the admin-ajax script on your server with a URL similar to this:

/wp-admin/admin-ajax.php?action=csl_ajax_onload&addressInput=&ignore_radius=1

This should return a JSON response showing curly braces that start with {“success”:true,…

If it comes back with nothing, or a warning/error about being blocked, your AJAX security is not set properly.  Check you web server log files and talk to your system admin for assistance on configuring access to WordPress AJAX scripts.

Forceload Javascript Warning

Store Locator Plus has a checkbox under the General /User Interface tab called Force Load Javascript

Having this checked forces the JavaScript for Store Locator Plus to load in the header of EVERY page on your site. This can slow down your site and will disable various Store Locator Plus features. If you need to do this to make SLP work you should ask your theme author to add proper wp_footer() support to their code, or switch to a theme that behaves properly.

WordPress White Screen

The “White Screen” in WordPress is one way that a WordPress site will show bugs in the underlying PHP code or system configuration.   In geek-speak this is known as a fatal error.    It can be a bug in PHP code or an incompatibility between the code and the server configuration.

The most common cause is a bug in the PHP code itself.  Plugins, themes, and WordPress can be the source of the problem.    If you have upgraded more than one item on your site prior to noticing a white screen, any of the updated items is suspect.

Note: You should ALWAYS back-up your site before upgrading to new versions of WP or any plugins. We suggest using JetPack . BAck-up your Word Press site

Here are some ways to track down the source of a “white screen” and recover from it quickly.

Debugging With Debug Log

With WordPress it is very easy to debug the activation process of a plugin and get a detailed log file of exactly what is going on.

Often there are hidden warnings or errors. Sometimes they are generated by the plugin. Many times they are generated by OTHER plugins or your custom WordPress theme. The first stage of debugging is to turn on the built-in WordPress debugging messages and debug log.

Troubleshooting Large scale Exports/Imports

Issue: Exports/Imports Incomplete

Multiple large-scale exports (export function is available with Power Add-on ) have been tested on the Store Locator Plus dev sites. 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  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.

Map Not Showing

You activated the Store Locator Plus base plug-in and followed all the instructions but when you visit your locator page no map is there.

Here are some common reasons why the map will not appear:

Did you obtain a Google MAP API key?

As of June 22, 2016 Google requires all new domains, sites to obtain a key.  There are many options based on how often your locations are queried. There are instructions in the SLP documentation site , in the SLP User Interface under INFO.  See Getting Started Guide.  More recently, 2018, Google has introduced security measures requiring SSL certification (HTTPS)  for sites that may want the search to locate their customers location. (Location Sensor)