Disciple.Tools - What3Words
Adds support for `///word.word.word` locations from What3Words
by cairocoder01 · github.com/cairocoder01/dt-what3words · website
Install
No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:
wp plugin install https://github.com/cairocoder01/dt-what3words/archive/refs/heads/master.zipDeclares an update source (https://github.com/cairocoder01/dt-what3words), so updates arrive through the plugin's own updater.
Readme

Disciple.Tools - What3Words
Adds What3Words geocoding support to Disciple.Tools location fields.
Purpose
Disciple.Tools location fields geocode through Mapbox (default) and Google. This plugin lets users
enter and display a What3Words ///word.word.word address that resolves to real coordinates and a
location grid value, complementing the existing location field without replacing place-name search
or the base map.
It registers a What3Words geocoding handler that the location field uses when present, falling back to the built-in Mapbox/Google behavior when What3Words returns no result. The What3Words API key is stored in the plugin settings and all What3Words calls are proxied server-side so the key is never exposed to the browser.
Usage
Will Do
- Add a What3Words API key setting in the Disciple.Tools admin area.
- Proxy What3Words
convert-to-coordinates,convert-to-3wa, andautosuggestcalls server-side. - Resolve a
///word.word.wordaddress into a location on contacts, groups, and other location-enabled records.
Will Not Do
- Replace the base map tile layer (Mapbox is still used for map tiles).
- Geocode non-interactive flows (IP geocoding, bulk upgrades), which continue to use Mapbox/Google.
Requirements
- Disciple.Tools Theme installed on a WordPress server.
- A What3Words API key (developer.what3words.com).
Installing
- Install as a standard Disciple.Tools/WordPress plugin in the system Admin/Plugins area.
- Requires the user role of Administrator.
Contribution
Contributions welcome. You can report issues and bugs in the Issues section of the repo. You can present ideas in the Discussions section of the repo. And code contributions are welcome using the Pull Request system for git. For more details on contribution see the contribution guidelines.