Pro Pack Legacy Add-on not compatible with SLP version 4.8

Pro Pack Features

If you want to keep the legacy add-on, ProPack,  do not upgrade the base plug-in to version 4.8.   All individual $30-$50 legacy add-ons have been phased out over the past 2 years. Please follow the SLP news feeds for important information.

 

Remember, upgrades are optional.  We do not auto-update the way WordPress has in the past.  When you purchased the Pro Pack from Charleston Software Associates you purchased a product that does A,B, and C for $X.    Those features do not go away and will work with the version of the core plug-in that was available at the time of your purchase.   Remember updating to  SLP version 4.8.  is optional. If you already updated, you can downgrade the base plug-in to an earlier version (see documentation about downgrading and the steps you should take beforehand)  or upgrade to the Power add-on.

You do not need to update the base plug-in unless you want the smart options capability in the newer add-ons using current technology that is more efficient and will use less of your server overhead.   If there is a bug or a security patch needed  those will be made as part of the regular service.  The last stable version of ProPack worked with SLP version 4.7.11 but we could not continue to update ProPack without re-wrtiting a major piece of code, alternatively, those ProPack features (and more) already exist within the Power add-on.   It was not efficient to continue to maintain two separate blocks of code to do the same job.  Compatibility with other plug-ins, or with newer versions of the base plug-in,  or your theme are not  guaranteed in “perpetuity”. We endeavor to keep the plug-in and add-ons relevant and working smoothly, updates are needed occasionally.

As a side note: Website Developers who are providing a service to customers often tell us their customers upgraded without checking with them first.

Please remind your customers to read warnings, news  posts, release specifications, change logs, and upgrade notes BEFORE hitting the update now button.    Upgrading just for the sake of upgrading is not really a great idea on a production server.  In fact it is a very bad idea!  Production servers are meant to be stable.   Ask them to stop upgrading their live production servers and require them to use a back-up service such as  Vault Press or Jet Pack.  You might  mention they should hire an experienced  site administrator if they want a stable and secure site.

Alternatively, take the worry out of updating with a MySLP plan.  Check out the Power and import options under   MYSLP SAAS

 

Q. Geocoding stopped working suddenly , why?

A. Most likely reasons;

  • You are over your daily query limit see Google API information. If you are on a shared Host this can impact those limits.
  • You moved your site or changed the domain name and did not change your Google Map API key. See Getting Started
  • If you imported and your csv file is incorrect, or your header rows are not accurate or have wrong field names, the columns may be misaligned and data field for an address could not import. Check your import message log
  • Google does not recognize an address. See FAQ post

Q. How do I remove or delete multiple tags that are associated with the locations?

A.  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”

Bulk Action with Power allows you to remove tags

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.

Q. I see a gray map or blank map and search does not work

JavaScript Problems

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 debug these issues use the Firebug add-on with Firefox as noted above.

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.

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.2, this generates an error message that you will not see in the browser. Any error message will prevent the JavaScript PHP file from loading.
    • 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.

One of the best tools for searching for errors in the HTML page headers is to use Firefox with the Firebug plugin. Turn on the console and check the responses tab 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 configuration settings on the servers. No, our plugin is not perfect and is not 100% bug free (we wish it were) but we are no longer finding bugs in our plugin as the primary culprit in broke installations.

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.

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 turned on 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.
Continue reading “Forceload Javascript Warning”

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.
Continue reading “WordPress White Screen”

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.
Continue reading “Debugging With Debug Log”

Troubleshooting Large scale Exports/Imports

Issue: Exports are Incomplete

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.
Continue reading “Troubleshooting Large scale Exports/Imports”