A map block for Gutenberg using OpenStreetMap and Leaflet that needs no API keys and works out of the box. Or should we say, ...Out of the Block?
A map block for Gutenberg which uses OpenStreetMap and Leaflet.js. It needs no API keys and works out of the box (or, out of the Block, if you prefer). Benefiting from Gutenberg’s potential, the plugin tries a different take on how to add your locations on the map and rethinks a few things, UX-wise.
Instead of manually adding coordinates for each one of your markers, just click-and-drop them directly on the map. You want to adjust their position? Just drag them wherever you want. And instead of filling-in custom fields to set each marker’s popup content, just open that popup and start writing in it, the Gutenberg way (it supports WYSIWYG editing, with links, images, and all). It even stores the map’s zoom level as you use it so that you don’t have to set it by hand.
Dead-simple interface. Don’t search for coordinates and don’t get overwhelmed by too many fields when using multiple markers. Just point and click on the map to add your marker where you want it and edit it’s popup content directly from there.
Remembers the zoom that you set when adding the markers and stores it so that you don’t set it by hand (which you can do anyway if you prefer).
OpenAI integration which allows you to add markers by using commands in natural language. Just say “please” to activate (e.g. “Please, show me where GOT was filmed”). Requires an OpenAI API key. Read more.
Query Maps: Supports creating a map out of maps added on other posts or post types. This can be quite powerful when, for example, you have a custom post type for “Places” with each place having its own map, and you want to dynamically gather-up all the places on a single map.
Shortcode support: You can use the shortcode [ootb_query] as an alternative way to use the aforementioned Query Maps feature (see the FAQ for more info).
Support for a location custom field, which can be used to store a post’s or post type’s location, following the Geodata guidelines. Read more in the v.2.8.0 release notes.
Adjust the map height.
Change the default marker icon with a custom one.
Enable or disable map dragging.
Enable or disable touch zoom.
Enable or disable double-click zoom.
Enable or disable scroll wheel zoom.
Set a minimum and maximum limit that the user can zoom on the frontend. Setting the same value to both fields will lock the zoom at that level.
Support for other Layer Providers: MapBox (using your own API key) and Stamen.
Option to export locations in a JSON file
Option to import locations from a JSON file
Installation
Upload the plugin to your WordPress plugins directory and activate it.
That’s it. You can go to a post/page that supports the Gutenberg editor and start using the block called “Out of the Block: OpenStreetMap”
Screenshots
Adding markers and rich content
Using the place search to throw multiple markers in a row by typing keyword and double+enter (no mouse)
The map editing screen
Map behavior options
Adding a marker
Using custom markers
Place search
Plugin settings page
Adding a polygon
Adding a polyline
Export and import locations
Demonstrating the OpenAI integration
FAQ
Do I need an API key, like with Google Maps?
No.
That’s the point, actually. Just install the plugin and start adding maps. Keep in mind, though, that as stated on the OpenStreetMap Tile Usage Policy, OSM’s own servers are run entirely on donated resources and they have strictly limited capacity. Using them on a site with low traffic will probably be fine. Nevertheless, you are advised to create an account to MapBox and get a free API Key.
How can I add a custom Mapbox style?
You can find the style URL on Mapbox Studio. There, use the “Share” button, and under “Developer resources”, copy the “Style URL”. It should look like that: mapbox://styles/username/style-id. You can declare a global style on the plugin’s settings, to be used as a default for all the maps, or you can set a custom style for each map, by using the block’s settings panel.
How do I add a new location?
To add a location, left-click on the map for a while, until you see the prompt saying “Release to drop a marker here”. On browsers that support it, the cursor transforms from hand to crosshair, to make it even more apparent. As long as the prompt is visible, it means that releasing the click will drop the marker at that spot. That slight delay has been added to prevent you from accidentally adding markers all over the place with every click.
Alternatively, you can use the map’s place search functionality.
How do I remove a location?
Click on the marker to open up its popup. There, you will see the “Remove” button.
I can’t find some of the options like disable dragging, setting zoom levels etc
Check under the “Map behavior” section, at the blocks’ settings at the sidebar on the right. It’s toggled off by default, that’s probably why you missed it.
How does the OpenAI integration work?
First of all, you will need to create an account to OpenAI and get an API key. Then, go to the plugin’s settings page and paste your key there. After that, you can start adding markers by using commands in natural language. Just say “please” to activate (e.g. “Please, show me where GOT was filmed”). Please keep in mind, though, that it’s like asking ChatGPT: the answers you get might not always be 100% reliable, and you should always double-check to confirm their accuracy. Read more.
How can I query maps from other posts or post types?
On the block’s side panel, Select the “Map data” panel and click on the “Fetch locations” button. This will automatically retrieve on the frontend all the markers from your posts (you can also select a specific post type from the dropdown). The block will be locked from editing, as the markers will be dynamically retrieved from the selected posts. If you don’t want that, there is a “Stop syncing” button that will unlock the block, drop the markers on the map and allow you to edit.
How can I use the shortcode?
To see the available shortcodes and the parameters that you can pass, go here.
I want more control. Are there any hooks that I could use?
Glad you asked! There are a few hooks that you can use to further customize the plugin’s behavior. You can find them here.
Changelog
2.8.2
[NEW] Adds the ootb_cf_modal_content and ootb_cf_marker_icon hooks, which allow you to change the content of the modal that appears when you query posts based on their “Location” custom fields, as well as the marker icon. For more info, check the plugin’s FAQ section.
2.8.0
[NEW] Adds an option to enable a location custom field, which can be used to store a post’s or post type’s location, following the Geodata guidelines.
[NEW] Adds a new block (a Block Variation, to be precise), to display a map that retrieves markers from posts or post types including the location custom field.
[FIX] Fixes a bug which caused an editor crash (see the report).
[FIX] Fixes an issue where the plugin was triggering unnecessary post updates.
[MAINTENANCE] Updates the build scripts and the plugin’s assets.
2.7.0
[NEW] Adds an option to set custom Mapbox styles using Mapbox Studio.
2.6.0
[NEW] Adds option to query maps, which allows you to create a map out of maps added on other posts or post types. This can be quite powerful when, for example, you have a custom post type for “Places” with each place having its own map, and you want to dynamically gather-up all the places on a single map.
[NEW] Adds shortcode support. You can use the shortcode [ootb_query] to retrieve the aforementioned Query Maps feature (see the FAQ for more info).
2.5.0
[New] Adds OpenAI integration which allows you to add markers by using commands in natural language. Just say “please” to activate (e.g. “Please, show me where GOT was filmed”). Requires an OpenAI API key. Read more.
2.4.1
Updates the build scripts.
Updates compatibility with WordPress 6.4.
Fixes a bug where the marker’s delete button would remove the wrong marker.
2.4.0
[New] Adds an option to prevent the default map scroll/touch behaviours.
2.3.0
[New] Adds support for different icons per marker.
Updates the react-leaflet script to v.4.2.1.
Updates compatibility with WordPress 6.2.
2.2.0
[New] Adds option to export locations to a JSON file
[New] Adds option to import locations from a previously exported JSON file
2.1.0
[New] Adds support for polygon shapes
[New] Adds support for polyline shapes
[Fix] Improves the drag and drop of markers
Updates the react-leaflet script to v.4.2.0
Updates the plugin’s assets and documentation
2.0.2
Replaces str_contains with strpos, for better backwards compatibility with older versions of PHP / WordPress.
2.0.1
Fixes a bug which broke the admin on WordPress versions prior to 5.9.
2.0.0
Refactors the build scripts to use the official @wordpress/create-block instead of create-guten-block, which isn’t supported anymore.
Updates Leaflet and react-leaflet to their latest versions (Leaflet 1.9.3 and react-leaflet 4.1.0).
Adds a new option to set the default coordinates when you add a new block. The plugin will try to guess the default location based on the site’s timezone.
1.3.5
Fixes a PHP warning in the widgets area of the admin
Updates translations
1.3.4
Fixes a PHP warning (more info: https://wordpress.org/support/topic/error-under-php8-2/)
1.3.3
Fixes a bug where the block’s scripts didn’t load if the block is used in a Widget
1.3.2
Fixes a bug where the block’s scripts didn’t load when used as a reusable block
1.3
Added Stamen as a Tile Provider
Fixed a bug with map centering when there is only one location