Posted from

Hi Thorsten,

Do you mean, you do not have any Text elements being updated for new posts or no elements are there for existing posts.
If the latter is the case, that is as expected, since the hook for updating the texts is only fired when a blogpost is updated or created. In all other cases, it seems like a bug and I am happy to investigate it.

Please give me an update in regards to this.

Best regards,
Yann

Hi Yann,

It does not matter if I write a new article or change an existing article. There is no text entry, after “Posted in”

Hi Thorsten,

sorry, it took a while to set up a clean install to figure out what you mean. Now I got your point and will chase the bug ??

…it looks like the ?reverse geocoding“ feature is broken, i.e., there is no adress generated from your long and lat.

Hi Yann,

thanks for your response.

But what i have to?

Best regards Thorsten

I was able to fix the issue, i.e., there is a new bugfix release 0.4.1 available now.
Keep in mind to activate “Maps JavaScript API” for the pure map functionality and “Geocoding API” for enabling reverse geocoding functionality. The later is needed in order to derive the location name from the post’s longitude and latitude.

I have installed the fixed version but have still this error, at Google both map and geocoding apis are enabled. What can I do?

Does this error occur for new posts or for existing posts?
The reason behind my question is that the reverse geocoding is only called when updating or creating a post but not for old posts.

If requested, I could think of an ex-Post update function…

Hi, I tested it with no restriction in the google api, that works! I had restricted it to the current website with https://subdomain.domain.tld/*, that don’t work. Better to have this restriction, can you take a look at that?
And yes, a function ex-Post would be great!
Thanks and kind regards

addendon: I tested the restriction with other sites and map function and uses now https://*.domain.tld/*, that should work, but it doesn’t, please take a look at that. Because of the new Google payment regulation I may not let the api without restriction.
Thanks, kind regards