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.

 

Continue reading “Locator Data – The Field Names”

Gravity Forms Integration vs GF Locations

Gravity Forms Locations (Free) vs. Integration (Paid)

The Gravity Forms add-ons are available to purchase at  Store Locator Plus.

Gravity Forms Locations”  by De-Baat  (free) is available from the WordPress Plugin Directory and works with Store Locator Plus. The paid version, Gravity Forms Integration  is available as a paid add-on , available at the Store Locator Plus home page under Third Party Add-ons  and provides extended capabilities.

Continue reading “Gravity Forms Integration vs GF Locations”

Gravity Form Locations Add-on for SLP

Gravity Forms Locations is an add-on pack for Store Locator Plus and Gravity Forms that allows you to setup a Gravity Form generated form and have it add locations to Store Locator Plus.

You will need the Store Locator Plus base plugin, the Gravity Forms Locations add on, the Gravity Forms Integration add on, and a licensed copy of Gravity Forms installed.
Continue reading “Gravity Form Locations Add-on for SLP”

Store Locator Plus Featured Add-ons versus Legacy Add-ons

Q:    Can you help me identify the Store locator Plus add-ons that replace the add-ons now described as Legacy?

A:  Power Add-on  will deactivate and replace the following:
Continue reading “Store Locator Plus Featured Add-ons versus Legacy Add-ons”

Using Language Files To Help WPML With Gettext

The following findings are current as of WPML 3.4.0 and SLP 4.5.07.

GetText Strings

The short version:  When using WPML to switch languages you will want to make sure your alternate language files are up-to-date and installed in the Store Locator Plus languages folder.   You can use Loco Translate to sync and generate updated .po/.mo files.  You may want to check out the WordPress Translate for Store Locator Plus site and download the latest .po and .mo files from there.

The WPML String Translations set manually via the user in the admin panel is NOT used when for the plugin when a gettext string is used.  Developer’s Note: WPML String Translations appear to only be used when employing the wpml_translate_string or wpml_translate_single_string filters.

Store Locator Plus sets most of the default text in the Text Manager class using gettext functions.     When a page implements the [slplus] shortcode the string presented in various locations, the default Find Button label, for example, is NOT loaded in the alternate language despite using the WPML String Translation plugin.

SLP Text String Management Class
SLP Text String Management Class

Manually setting the translation via the WPML String Translation admin interface does not seem to to be used by default despite WPML Multilingual CMS, WPML String Translation, and WPML Translation Management being installed and active.

WPML String Translations Ignored
WPML String Translations Ignored
 String Translations Ignored - UI
String Translations Ignored – UI

 

 

Using Loco Translate To Help WPML

By using Loco Translate to sync and save an updated .po/.mo language file to the SLP languages directory, the WPML language switcher will now pick up the proper translation.  The process I used to get the Italian translation for “Find Locations” to show up when I select the Italian version of the page:

  1. Install and Active Loco Translate
  2. Go To Manage Translations in Loco Translate
  3. Select the existing it_IT translation file next to Store Locator Plus.
  4. Click sync to load in the latest gettext() calls that need translation.
  5. Add the missing “Find Locations” text in Italian.
  6. Save the file.

Now my Italian version of the English “Locations” page shows the proper text on the Find Locations button when I switch from the English page to the Italian page.

WPML Using Language Files To Set Text
WPML Using Language Files To Set Text

wpml-config.xml

This file resides in the root directory of the plugin.

The file is only loaded on admin pages.

The admin-texts node is only used for changing the text on the admin options, serial or singular, only.

The user’s language on the admin page is based on the language selected in their PROFILE, not via the language selector on the admin bar.

Related Articles

WPML.org : Translating wp_options Entries

WPML.org: The wpml-config.xml File

Countries and Languages

Plugin Text

The Store Locator Plus plugin is now part of the WordPress Translate project.  You can get the current status of the Store Locator Plus translations on the WordPress Translation website.  If you would like to see the plugin fully translated into your language, please send a request to be added to the WordPress translate team for your language.  As soon as a language reaches 100% completion for the stable release of the Store Locator Plus plugin, the custom language files will be removed from Store Locator Plus and be replaced by the more-efficient Translate system.
Continue reading “Countries and Languages”

Extended Data Manager

The Extended Data Manager feature allows additional data fields to be added to your locations and allows you to add new elements.

Works best with Experience Add On.

Note: If you want the extended data to appear in your results and it is not already there via the SLP style you are using, you may add to the Results layout the shortcode: [slp_location data.<slug>] where <slug> matches the field slug noted in the Extended Data Manager admin interface.

Adding Custom Fields

Go to the General / Data tab.   Add a new custom field to your locations via the Add Extended Data Element group.

Managing Extended And Custom Fields

You can manage which fields are shown, hidden, their data types, and other attributes of extended location data element via the Manage Extended Data Elements group under the General / Data tab.

Bulk Actions

 

Translating Store Locator Plus

Store Locator Plus uses the built-in WordPress internationalization and localization tools to translate the interface text into various languages.  Starting in October 2015, Store Locator Plus has become part of the WordPress Translate project.  You can contribute translations for the base plugin at the Store Locator Plus directory at WordPress Translate.

If you do not see the base plugin in your language, check the SLP Translate report for the latest Stable Release and make sure your language is at 100%.  The Translate system will not create a language export for partial translations.  If you want to help with the translation, send a request to be added to the WordPress PolyGlots project.

Learn About Translate.WordPress.Org.
Continue reading “Translating Store Locator Plus”