Feature Request: Periodic cleanup of corrupt caches

Thats a great idea!

Ill try to add that feature as soon as i have time….

Awesome!

Please post an update when this is added.

Thanks!

I’ve been researching the WordPress oEmbed features (wrote an article on it today https://stallion-theme.co.uk/understanding-wordpress-oembed-and-unknown-postmeta-entries/) and the unknown entries aren’t corrupt caches per se.

If a plain text URL is to a page that doesn’t provide oEmbed formatted data, WordPress can’t cache any oEmbed data, so it adds an unknown entry so WordPress doesn’t keep hitting the URL with get requests etc…

It’s not ideal, but the alternative is add nothing to the database and check the URL over and over again every page load!

Just had a quick look at the command you linked to and if I understand it correctly it doesn’t clear the unknown entries, I think it’s looking for entries which don’t end in >

I guess some cached embed code is messed up and doesn’t result in correctly formatted HTML code.

Back to my research, trying to figure out when the oEmbed cache is recached by WordPress.

David Law

Sorry. Just now saw this comment after still trying to find a solution!

I think it would still work to check for the unknowns and clear them. Because I am assuming whenever oembed is used that most of the time the ideal response is to have some kind of embed. And even if it were returning an unknown because of what you mentioned (to a page that doesn’t provide oEmbed data), then it would just have “unknown” as the value again and be cached. No big deal.

But I am assuming if something is being cached in the oembed, that an “unknown” value in the database is not the desired response. So a periodic cleanup of those values would be great.

Thanks!