| 开发者 | tijmensmit |
|---|---|
| 更新时间 | 2026年9月25日 13:07 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
[wpsl] shortcode or block on a page, and visitors can search by address, postcode, city or their current position, filter by category and get directions.
Why WP Store Locator 3
[wpsl] for the full locator, with attributes for categories, filters, map style, markers, shapes, region and distance unit.[wpsl_map] for a map with one or more locations.[wpsl_address] and [wpsl_hours] to show the address, contact details or opening hours of a single location anywhere.[wpsl] shortcode to a page.Please take a look at the documentation before making a support request.
wp-store-locator folder to the /wp-content/plugins/ directory, or install it from the Plugins screen.[wpsl] shortcode to a page.No. Choose OpenStreetMap (Leaflet) as the map service and the store locator runs without any API key. A key is only needed for Google Maps, Mapbox and Stadia Maps, or if you want routes drawn on the map with OpenStreetMap (free Openrouteservice key).
Yes. The map service is a single setting under Store Locator > Settings > API. Your locations, coordinates, categories, custom fields, markers and settings stay the same.
Add the Store Locator block, or the shortcode [wpsl], to the page where you want to display the store locator.
Yes. Go to Store Locator > Settings > Fields Manager, create a group and add your fields. Then use the Section Editor to place them in the results list or info window. It can generate the template code for you, so no coding is required.
Yes. Design markers in the Marker Studio, then assign them to categories or to single locations. You can also set a separate marker for the active location.
They were migrated automatically. Some sections moved: Google Maps API is now API, Permalink is now Local Pages, and sizing, templates and map styling moved to the Appearance page. If the migration did not complete, use Retry migration under Store Locator > Settings > Tools.
3.0 requires version 2.0 or later of the CSV Manager, Statistics and Search Widget add-ons. Older versions are disabled automatically until you update them.
This is a Google Maps error. Set a valid browser key under Store Locator > Settings > API and click Validate API key to see the exact reason Google returns.
This is most likely caused by a caching plugin that minifies the HTML output on the store locator page. Exclude the store locator page from minification in the settings of your caching plugin.
Make sure you have defined a start location under Store Locator > Settings > Map. If the locator looks broken after upgrading to 3.0, try Disable v3 theme rules under Settings > Tools.
If you use a caching plugin, or a service like Cloudflare, then make sure to flush the cache.
Version 3.0 requests Google Maps directions through the Routes API instead of the legacy Directions API that version 2 used. It is a separate product in your Google Cloud project, so open the Routes API page, select the project that holds your API keys and click Enable. If the browser key has API restrictions, also add the Routes API to the allowed APIs under Credentials. Until then the map keeps working, but clicking Directions shows a notice instead of the route.
Some location names exist in more than one country. Set the correct Bias country under Store Locator > Settings > API, or restrict results to specific countries.
This is most likely caused by your theme using ajax navigation ( the loading of content without reloading the page ), or a conflict with another plugin. Try to disable the ajax navigation in the theme settings, or deactivate plugins one by one to find the conflict. If you find a plugin or theme that causes a conflict, please report it on the support page.
Please report security bugs found in the source code of the WP Store Locator plugin through the Patchstack Vulnerability Disclosure Program. The Patchstack team will assist you with verification, CVE assignment, and notify the developers of this plugin.
You can find the full documentation here.
init.is_plugin_active is available before calling it.wpsl_create_meta_filter() now calls the correct service.$wpsl_settings now gets the active template's height, instead of always 450.<strong> (default true) so single store pages match the search results list. Set to false to restore the v2 unbolded output, or override via the 'wpsl_address_shortcode_defaults' filter.