Giorgos Sarigiannidis

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.

Hi!

I’m not sure why this is failing on your case. Perhaps there is a conflict on the OpenAI model, because when this feature was implemented, it supported a specific model. In any case, version 2.8.6 added more flexibility on that, and you can go to the plugin settings and set a specific API provider and AI Model.

I did some digging, and I think that OpenAI doesn’t have a free tier anymore, so it might be the case. On your OpenAI account, do you have a credit card set up?

In any case, I’m preparing an update to the plugin, to allow the users adding their own provider URL and model, so that it is not necessary to be tied to OpenAI.

Hi. I’ve tested this locally, and it works as expected. I get a “Something went wrong” error if I put a wrong API key. Could this be the issue in your case? Did you check that the API key is working?

Hi,

This is a 3 step process:

1. First, you need to enable the custom field via?Settings → OOTB OpenStreetMap → Custom Fields
2. Then, you should see the field in the posts. You should assign a location to at least one post.
3. Finally, you can go to another post or page and use the shortcode, to retrieve a map with the posts that have a location.

Instructions with screenshots can be found here (about the custom field) and here (about the shortcode).

Let me know if it works for you.

Thanks!

Thanks for your kind words.

btw, if the custom field works for what you intend to do, then perhaps you can take a look at the [ootb_query] shortcode. For example, something like the below would output the locations of all posts with locations:

[ootb_query source="geodata"]

If you would want to put it anywhere in your PHP files instead of the post editor, you could use do_shortcode, like:

<?php echo do_shortcode('[ootb_query source="geodata"]'); ?>

For all the available options, you can check the plugin’s readme.

• This reply was modified 7 months ago by Giorgos Sarigiannidis.

I don’t think that this plugin can help much as what you describe sounds like something that requires a custom implementation. You might be able to utilize the Custom field support, if you want to have a map on specific posts as a custom field instead of a block, but you would still have to implement the logic to fetch the data and manipulate according to your needs in order to display the locations in a different way.

Hello,

Right now, there isn’t (I didn’t know about this service). I can look in to it and perhaps include it in a future update.

Hello and sorry for the delayed response. I’m not sure that I understand the request. Are you referring to the new Block-based Widges Editor, or the Classic Widgets?

Hello, and thanks for reporting this with such clean steps to reproduce. Version 2.8.1 should fix this issue. Also, your report made me look at some more stability and performance improvements. For more details on what else is included in this release, you can see the?release notes of v.2.8.0.

Hello, and thanks for your patience on this one. Version 2.8.1 should fix this issue. For more details on what else is included in this release, you can see the release notes of v.2.8.0.

Hi and thanks for reporting this.

A fix for it will be included in the next update.

So, v.2.6.0 adds shortcode support, which essentially allows you to query the markers from existing posts. More info: https://github.com/gsarig/ootb-openstreetmap/releases/tag/2.6.0

Hi and thanks for the suggestions. I try to not divert from what Leaflet supports, especially when it comes to usability. I like the suggestion about the fullscreen mode, though, and added it to the plugin’s backlog.

Hi and thank you both for reporting this. It seems that the core Button element had some change in the markup on some recent update, causing this regression. Version 2.4.1 should fix that, so please update and let me know if it worked for you.

Thanks!