Giorgos Sarigiannidis

Hi Ralf,

Before diving into Mapbox-specific debugging, it’s worth confirming that the map works with the default
OpenStreetMap provider. If you see a grey map there too, the issue is unrelated to Mapbox (could be a JavaScript conflict, a caching plugin, or a theme issue).

Assuming the default provider works fine, a grey map with Mapbox usually comes down to one of three things:

1. Style URL format
   The plugin expects the Mapbox protocol URL, not the browser URL. In Mapbox Studio, click “Share” on your style and copy the Style URL. it should look like this:
   mapbox://styles/your-username/your-style-id
   If you copied the page URL from your browser (starting with https://), that won’t work.
2. Access token
   Make sure you’re using a public token (starts with pk.), not a secret one. You can find and create tokens at mapbox.com/account/access-tokens. The default public token on your account works fine for this.
3. Selecting Mapbox as the provider in the block
   The API key and style URL in the plugin settings are the global defaults, but each block still needs to have Mapbox explicitly selected as its provider. Open the block in the editor, go to the block settings in the sidebar, and make sure “MapBox” is selected as the map provider. If it’s still set to OpenStreetMap, it will ignore the Mapbox settings entirely. If none of the above helps, open your browser’s developer console (F12 → Network tab) and reload the page. Look for failing tile requests. The error message there will tell you exactly what’s wrong (invalid token, wrong URL format, billing issue, etc.), and that would be the thing to take to Mapbox support if needed.

Hope that helps!

Hi,

I’m not sure that I understand exactly what you have in mind. The plugin doesn’t have any backed-in functionality to search or filter the results. Since version 2.8.0 it supports custom fields, though, so you could utilize it to implement some filtering functionality in your theme. I’m not familiar with FacetWP so I don’t know exactly how it works, but since its just standard WordPress custom fields, it might be relatively straightforward.

Hi

This has been deployed with version 2.8.8.

Thanks for reporting it!

In that case, you would need to adjust the code to this:

foreach ( $attrs->markers as $marker ) {
	if ( isset( $marker->text ) ) {
		$marker->text = wp_kses_post( apply_filters( 'ootb_block_marker_text', $marker->text, $current_post_id) );
	}
}

(notice the $current_post_id parameter that has been added)

Then, you can use the filter like that:

add_filter('ootb_block_marker_text', 'customize_marker_text', 10, 2);

function customize_marker_text($text, $post_id) {
    return $text . ' whatever additional info you want, plus the post id:' . $current_post_id;
}

• This reply was modified 11 months, 2 weeks ago by Giorgos Sarigiannidis.

Simply changing the extension wouldn’t work, because the plugin expects a very specific structure. Example:

[
  {
	"lat": "37.9839412",
	"lng": "23.7283052",
	"text": "<p>Athens, Municipality of Athens, Regional Unit of Central Athens, Attica, 104 31, Greece</p>",
	"id": 1673647730152
  },
  {
	"lat": "40.7127281",
	"lng": "-74.0060152",
	"text": "<p>New York, United States</p>",
	"id": 1673647735921
  },
  {
	"lat": "41.3828939",
	"lng": "2.1774322",
	"text": "<p>Barcelona, Barcelonès, Barcelona, Catalonia, 08001, Spain</p>",
	"id": 1673647741383
  },
  {
	"lat": "51.5073219",
	"lng": "-0.1276474",
	"text": "<p>London, Greater London, England, United Kingdom</p>",
	"id": 1673647744636
  }
]

So, you ‘d have to go for example to ChatGPT, give it the contents of the .geojson and ask it to convert it to the specific format. Then, save the contents as a .json file and try to import. In theory, this should work.

Great! Than’s again for flagging the issue!

Hi,

Thanks for reporting this. I’ve identified the issue and working on a fix, which should be available later today. I will let you know when it’s ready.

Hi,

Can you temporarily disable Complianz to see if that’s what’s blocking it? If that’s the case, another user reported something similar in the past (see the link), and posted the way that he solved it.