Dylan Kuhn

That error indicates the WordPress database user has insufficient permissions. Usually that would be the same user that created the table, and so should have full permissions on it. It’s surprising that this error is intermittent, because on most WordPress installations only one database user is configured to connect to the database for everything WordPress does. Might be some kind of issue with your host.

Something is redirecting map URLs (like https://dombai.org/?geo_mashup_content=render-map&map_data_key=8165ac3b4bd20872bf62a8ef33c85a9c&map_content=global&name=gm-map-1&object_id=53) to the home page. This could be the theme, another plugin, or even the hosting service. I would try deactivating plugins to see if you can identify the cause that way first.

I think deleting the plugin is supposed to remove the options and tables, but it does look like this may not be working. I made an issue to fix that:

https://github.com/cyberhobo/wordpress-geo-mashup/issues/920

That said, it seems like your issue might be something else. If you can link to a page with the issue I may have more ideas.

Global maps show all post types by default. You can use the map_post_type parameter to limit it to the post types you want.

I do have an issue to look at bundling OpenLayers.

It might work to deregister the ‘openlayers’ script and register a different one as a workaround in custom code.

Hi Pietro,

Could you include a full log entry with the warning? That should include the file and line number that raises the warning.

It would also be helpful to paste the information from Tools / Site Health / Info / Copy site info to clipboard.

Thanks!

Geo Mashup only handles location for posts, users, and comments. So locating terms isn’t really a choice. The performance cost of including taxonomies enables filtering of located posts by term, but not mapping terms themselves.

A lot of people publish on a different date than when the topic of the post actually happened, and having a different geo date accommodates this. It probably would be possible to add a setting to sync it with the publish date.

Thanks for letting me know about the date picker, I made an issue to address that.

Check the Geo Date for that post in the location editor and make sure it’s earlier than the newer posts.

Ha, I thought maybe I was the only user left! I must have made that update myself at some point, but the plugin is so old I’ve almost forgotten how to do a release. It would be amusing to do one after 9 years.

The instructions were wrong, the filename in the custom plugin folder should just be search-results.php. I’ve fixed that, sorry for the confusion.

Thank you, version 1.13.9 should fix that.

Well, I managed to screw that one up, look for 1.13.8.

I released version 1.13.7 with your suggestion. It may be a glitch with the CDN that the version we were using stopped working, but I made another issue to research alternatives.

Thanks for reporting that. I’ve made a GitHub issue to address it: https://github.com/cyberhobo/wordpress-geo-mashup/issues/900