Google Map Domains supported in SLP

Google Map Domains

The following countries are currently supported in the Store Locator Plus plugin.  These countries determine the default center starting point for location searches and determine which Google locations engine is used when searching for an address.   This influences, but does not restrict, which results are returned.   Regardless of what country you select as the default, any location in your location database can be returned by the search regardless of the country in which that location resides. This does not effect the zip codes necessarily. Some country postal codes are  unique, others are not.  Google search engines may revert back to an “international” search engine as they are constantly updating.  If your country postal codes are not unique in the world, the Google Map API algorithms will use their international map search and search worldwide. This can be frustrating if all your locations are in a different part of the world.  You can override this by using a shortocde  (included with the experience add-on ), such as append only with =”country” available with the Experience add-on.

  • United States
  • Algeria
  • American Samoa
  • Andorra
  • Angola
  • Antigua and Barbuda
  • Argentina
  • Australia
  • Austria
  • Bahamas
  • Bahrain
  • Bangladesh
  • Belgium
  • Belize
  • Benin
  • Bolivia
  • Botswana
  • Brazil
  • Bulgaria
  • Burundi
  • Canada
  • Chile
  • China
  • Congo
  • Czech Republic
  • Democratic Republic of Congo
  • Denmark
  • Djibouti
  • Ecuador
  • Estonia
  • Ethiopia
  • Finland
  • France
  • Gabon
  • Gambia
  • Germany
  • Ghana
  • Greece
  • Guatemala
  • Guyana
  • Hong Kong
  • Hungary
  • India
  • Indonesia
  • Israel
  • Italy
  • Japan
  • Kenya
  • Lesotho
  • Liechtenstein
  • Lithuania
  • Macedonia
  • Madagascar
  • Malawi
  • Malaysia
  • Mauritius
  • Mexico
  • Mozambique
  • Namibia
  • Netherlands
  • New Zealand
  • Nigeria
  • Norway
  • Paraguay
  • Peru
  • Philippines
  • Poland
  • Portugal
  • Republic of Ireland
  • Romania
  • Russia
  • Rwanda
  • Sao Tome and Principe
  • Senegal
  • Serbia
  • Seychelles
  • Sierra Leone
  • Singapore
  • South Africa
  • South Korea
  • Spain
  • Sri Lanka
  • Sweden
  • Switzerland
  • Taiwan
  • Tanzania
  • Thailand
  • Togo
  • Uganda
  • United Arab Emirates
  • United Kingdom
  • Uruguay
  • Venezuela
  • Zambia
  • Zimbabwe

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”

Using Store Locator Plus On Multilingual Sites

Unlike single-language websites where all of the site content and administrative interfaces are operating under a single language, multilingual sites allow visitors to pick their language while viewing the website.

WPML

The most popular plugin for WordPress multilingual sites at the time of this writing is WPML.

Store Locator Plus has begun the journey into supporting multilingual sites with WPML.    Changes to WPML in late 2015 will require further revisions to the WPML compatibility layers.

Since version 4.3.06 Store Locator Plus added features that will help the plugin and add-on packs communicate with WPML for user-configurable translation strings.  While the entire fixed-text portion of Store Locator Plus uses gettext, a common language translation utility, there are many strings that appear as user-configurable settings.  Options such as search and results labels fall into this category.
Continue reading “Using Store Locator Plus On Multilingual Sites”

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”