Category Archives: Third Party Add Ons

Third Party Add Ons

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 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

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

Adding Locations with additional features

If you have any of the Store Locator Plus featured Add-ons such as Power, Experience, or Premier add-ons you will see additional sections when Adding (or managing) a Location.

You can opt to fill in all the rows and info that determine the Location and geocoding and hit Add button if you are done entering information. Or you can opt to continue to the next section, whether it be featured, tags, categories, territories, or other functions that are in separate sections on the Location Add Tab.Click the “Add button” at the bottom of the next section instead.

For example, I want to add a location that also is going to have a category assigned to it. I have the latest version of the Power Add-on activated. After adding all the Location information, I do not click on the Add button under the location information but continue on down to the next section called “Power” and add whatever pertinent information I wish to add there. Once I am satisfied and have no additional data to add, I click on the Add Button under the Power section of the Locations Panel to create the location that I have just added.

The category or other additional data you just associated will appear when you review the Locations Page.When to click the add buttonaddlocationa nd acategories

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

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.

EDM 4.5 Add Field

EDM 4.5 Add Field

 

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.

EDM 4.5 Manage Fields

EDM 4.5 Manage Fields