wp_options table with lots of “leaflet_osm_” rows

I think yes. These are entries from geocoder.
[leaflet-map address="..."]

Yes, but are they actively used or was this an old version that left them? We have 280 on our main site and they’re all set to autoload => true!

Please advise if these can be purged?

Thank you.

Oliver

https://github.com/bozdoz/wp-plugin-leaflet-map/issues/213

I don’t think that’s related.

But there is another option leaflet_geocoded_locations which is also set to autoload => true and is massive (13Kb) which I think should also not be there and I think that’s what your link above relates to.

I would like to know if the leaflet_osm_ options can be deleted? Thank you.

Oliver

Warum einfach, wenn es auch umst?ndlich geht. ??
Why make it easy when it can be done in a roundabout way?

In Leaflet Map Settings is a button “Clear Geocoder Cache”.

Ah ??

OK, so it’s a cache … but unless users know that the data is permanently stored!

In that case surely the plugin should use the WordPress Transients API rather than the options API?

That would negate the requirement for the “Clear Geocoder Cache” button and allow old data to be forgotten.

I would appreciate if this could be considered.

Thank you.

Oliver

I think Oliver is right, this is IMHO a case for the transient API. The way it is done right now will eventually overload the options table on sites with dynamic map usage. This is something that should at least be documented in the admin screen where the delete option is placed. Or a warning could be placed there if the amount of entries is higher than , say, 100 or so … they are counted anyway in the option leaflet_geocoded_locations ( which creates an additional huge option table entry …)

Maybe https://github.com/bozdoz/wp-plugin-leaflet-map/issues/213 is a better place to discuss it, since bozdoz himself has opened this issue .

Thanks @ulicgn, I’ve updated the ticket and referenced back to this thread.

Oliver