If you have questions that are not answered here please use the contact form.
PHP 5.6+, MySQL 5+ and WordPress 4.1+. Using the latest version of WordPress is highly recommended. Support requests from customers on older versions of the requirements listed above will be very limited and/or not supported.
If nothing is displaying after adding the shortcode to a page or post and you’ve added at least one location, try deactivating and reactivating the plugin to clear the location data transient.
No, according to Google’s TOS: “The Geocoding API may only be used in conjunction with a Google map; geocoding results without displaying them on a map is prohibited.” The Geocoding API is used in this plugin to get the latitude and logitude of the address or zip code entered in the input field by a user.
Yes, if you’re adding or updating a location using the built-in locations custom post type or another custom post type specified in the plugin settings, Cardinal Store Locator will attempt to automatically geocode the location if you’re connected to the internet. You can check the post’s custom fields for “bh_storelocator_location_lat” and “bh_storelocator_location_lng” to see if the geocoding request was successful.
No, if you have existing location data with locations that haven’t been geocoded and are importing to a custom post type or are using KML, XML or JSON the locations need to be geocoded prior to being used with the plugin. A background geocoding task will potentially be added in a future version.
Yes, import functionality is included since version 1.5.0 of Cardinal with support for importing a CSV file via a custom WP-CLI command. If you have a data set you need imported and are not familiar with WP-CLI please send an email for further information. Assistance will be provided to license holders and a WordPress import file can potentially be generated for you depending on the current format of the location data.
Alternatively, because Cardinal Store Locator can pull data from WordPress custom post types you can use an existing WordPress import tool such as WP All Import.
Yes, the plugin checks for the existence of a cardinal-locator directory within the site’s active theme and checks for infowindow-description.html and location-list-description.html to override the defaults. If you’re using KML location data you should use kml-infowindow-description.html and kml-location-list-description.html instead. If you’re using a custom post types a list of available data attributes available can be found in the plugin documentation. If you’re using XML or JSON the Handlebars expression just has to match the attribute in your data.
By default all the location data is saved as a WordPress transient. If your imported locations aren’t showing up in the locator you may need to delete this transient. This can be done by deactivating and reactivating the plugin or by using the Transients Manager plugin. The transient is named bh_sl_locations.
By default, the plugin stores all locations in a WordPress transient. If you have more than 1,000 locations there is a setting under the Primary Settings tab that enables a different technique for searching. It works by setting up a custom, indexed database table of all the location coordinates along with the related location post ID. The data is inserted when a new location post is added or updated and there’s also a method that hooks into the WordPress Importer plugin if you’re setting up a custom XML import and have the latitude and longitude meta keys set up.
Yes, if the coordinates that Google returns aren’t accurate enough for one or more of your locations the latitude and longitude can be overridden with custom fields. Use ‘latitude’ as the meta key name for the latitude and ‘longitude’ for the meta key name for the longitude.
By default, the plugin registers a custom post type named ‘bh_sl_locations’ so if you’re wanting to create a custom single template for locations, for example, you’d want to name the single template file single-bh_sl_locations.php
If the automatic update is failing first try deactivating and reactivating the license key and running the update again. This is especially true if your domain has changed. If it’s still not working you can download the plugin by logging into your account. Email firstname.lastname@example.org if you don’t have an account or need your credentials reset.
There are a couple of things to be aware of when using Cardinal Store Locator with other plugins and pre-built themes.
- Themify themes handle 404s in a method that’s different form WordPress core. If you’re seeing 404s on every page when using Cardinal Store Locator and a Themify theme, please add at least one location and the issue should go away.
- The Toolset Views/Google Maps plugins enqueue Google Maps with the same handle as Cardinal Store Locator. If you’re using both plugins make sure you include the Google Maps API key in the Toolset settings.
- CForm Builder seems to override all Google Maps includes so be sure to add your Google Maps API Key under CForm Builder > Global Options.
Yes, on a case by case basis direct purchases from these types of organizations are eligible for a discounted license price. Please email email@example.com for more information.
Yes, if you’re not satisfied for any reason or run into an issue that’s not solvable via a support request within a reasonable amount of time, a refund is available within the first 30 days from the original purchase date. Refunds are only available for the original purchase license and not renewals. Please refer to the Terms and Conditions for more details.