Legacy Add-ons not compatible with SLP version 4.8

Pro Pack, Tagalong, Pages, Directory Builder (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 years due to security patches, coding changes, WP updates, 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, remember, 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,  you may also need to rollback WordPress.  Due to the security patches required by  WPSLP , there may be an issue.  Before attempting to roll back or downgrade, make sure you have a recent back-up of your site. Do not attempt 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, not to mention, you will miss  important security patches.     If you are confident that you know what is entailed and are willing to take the risk;  absolutely 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.  There are  also import options under  MYSLP SAAS

 

Upgrading from Legacy add-ons to Power add-on

Return customers who have upgraded to the newer add-ons will notice a change in the location of some of the functionality/features  that were part of the separate legacy add-ons ,  now available in the Power add-on. (see Legacy to feature add-ons)

Legacy Add-on Tagalong = Categories on the header tab in the Store Locator Plus User Interface.

Legacy Pages = General / Data /Enable Pages.  To use the SEO Pages you must first “enable Pages” under this setting.

Legacy Contact Extender = General/Data/Enable Contact fields.

Legacy ProPack = Various fields and functions

  •  Import Under Locations/Import
  •  Location sensor checkbox is located under the General/User Interface tab.

 

 

 

Map display options

Map Display

The Experience add-on for the WP Store Locator Plus or the MySLP/Professional Plan  allows you to customize your Map display.

With the WPSLP Experience add-on installed and activated  go to Settings/Map.

  • Show Map (default)
  • Hide map until search
  • Image until search

Appearance

Additional options  are available to change your  Map layout and appearance    with the WPSLP Experience Add-on.   If you do not have the Add-on or a corresponding MySLP plan,  the  optional settings will  NOT appear.   (Note: There is a sidebar menu with MySLP/Professional under Advanced Options. See Adjust Locator styling for more information)

The additional options with the above mentioned plans or add-ons allows you to  hide the map , change the map layout, change the map bubble display, and/or  hide the map info bubble.  The Plugin Style under View (WPSLP) may supersede these settings. Choose one that  will compliment your theme or utilizes the add-on features available to you.

Locator Data – The Field Names

Store Locator Plus includes a default set of data fields that is included with every installation as well as extended fields provided by add-on packs.

For  data fields, including those added with the Extended Data Manager, you can output the data in the map info bubble or results layout,  by using the following shortcode:

[slp_location data.<field_slug>]

For example:

[slp_location data.contact]

[slp_location data.facebook_custom_url] (for someone that added a field named Facebook Custom URL).

Both the default data and extended data can be displayed in the search results, (for SEO Pages some fields will be [storepage field=contact] for SEO-friendly details pages. Most of the tools provided by the various add-on packs work best when using the field slug. The slug is a unique name for the field that is similar-to, but not exactly the same as, the field name.

The slugs are used in the add-on packs such as the layout strings from the Experience Add On in as well as the column headers for CSV Import in the Power Add On.

Default Location Fields

ID

Name

Address

Address Line 2

City

State

Zip

Country

Latitude

Longitude

Tags

The Pro Pack tags field. Requires Pro Pack for full functionality.

Description

Email

Website

Hours

Phone

Fax

Image

An fully qualified image URL, http:: with a full domain.

Private

May be used in the future as a 1|0 value to determine if a location is to only appear on the admin interface and not front end searches.

Neat Title

May be used in the future as an alternate store name or subtitle.

Linked Post ID

The ID of the related store_page entry where extra taxonomy data and other location data is stored. Used with Store Pages and Tagalong. Should not be modified.

Pages URL

The relative URL for the Store Pages linked post ID. Provides a processing shortcut for the Store Pages add-on pack.

Pages On

Used with Store Pages to determine which locations have been populated with Store Pages template content.

Option Value

A serialized JSON data object which can store extra location data. Slower and less direct than extended data fields.

Last Updated

A date and time MySQL timestamp indicating the last time the main data for the location was updated.

Initial Distance

The initial distance calculated between your center map latitude/longitude and the location.

Add On Pack Import Fields

These fields appear in the extended data table, slp_extendo. The field metadata, used to manage the slp_extendo table, is store din the slp_extendo_meta table.

Power Add On : Contacts Enabled

Identifier a unique location identifier from an external database that can be used to update existing locations in Store Locator Plus

Contact

First Name

Last Name

Title

Department

Training

Facility Type

Office Phone

Mobile Phone

Contact Fax

Contact Email

Office Hours – long formatted text

Contact Address – long formatted text

Notes – long formatted text

Featured – valid values are “1” for featured and “0” (zero).

Rank – an integer from 1 (highest rank/top of list) to 999999. 0 = no rank.

Power Add On : Categories Data

Power categories utilize the built-in WordPress custom taxonomy system. Standard WordPress category IDs are kept in the term_relationships and term_taxonomy tables. The relationship between locations and categories is managed via the slp_tagalong table that maps the Store Locator Plus id field to the WordPress Taxonomy term_id.

 

Import remote file retrieval

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)

Power 4.6 import back end

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.

Additional Import Data field headers

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.

Facility::Showroom.

Results Settings and interaction

Additional Results Interaction features  are available with the MySLP/Enterprise or   WPSLP Premier Add On.  The results interaction set of features provides a variety of visual cues on the location map to indicate the location a user has clicked  when viewing a list of locations., providing a variety of additional options beyond the standard Info Bubble that Store Locator Plus displays when a location is clicked.

Use the Experience add-on to completely disable the Info Bubble under the map and only use these interactive result indicators. When a visitor to your site clicks on the results marker they will see additional information such as description you have entered for that location, in addition to the fields that are populated for the location.

Info bubble turned off, marker clicked shows the additional info for that location

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.