| 开发者 | lewisburgess79 |
|---|---|
| 更新时间 | 2026年10月20日 00:29 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
route-finder folder to the /wp-content/plugins/ directoryYou can use the plugin with OpenStreetMap tiles and Nominatim geocoding without any API keys. However, for additional features like weather forecasts, Google Places search, or premium map tiles, you'll need to obtain API keys from the respective service providers.
Route Finder supports GPX, KML, TCX, and FIT file formats for route uploads.
Upload GPX files (each creates a route, with distance, ascent and other details extracted automatically). To move routes and settings between sites, use the plugin's Export / Import tool, which exports and imports all plugin configuration and route data as a file you download and upload yourself - no external service is involved.
Yes, Route Finder is fully translation-ready with all strings properly internationalised.
You can use the Gutenberg blocks or shortcodes provided by the plugin. The main shortcodes are:
[route_card id="123"] - Display a single route card[filtered_routes] - Display a filterable list of routesYes, individual routes can be password-protected or hidden from search results entirely.
A PHP session is only started when it's actually needed: when a visitor is on (or navigating within) a page that can render route content and password protection is switched on for the site, or when they already hold an unlock cookie from a previous visit. It is never started at all if you haven't enabled password protection under Protection settings, and never on pages that can't show a route anyway. Starting a session makes that specific page uncacheable by server-side full-page caches (Varnish, Nginx FastCGI cache, etc.), since a unique session cookie is issued - so once password protection is enabled, expect route pages specifically to be served uncached by such caches.