Is it normal behavior for this module to be caching/storing the full HTML content of shared URLs? I just checked into the cache_opengraph_filter table in my DB, and for all the shared URLs, there is a BLOB containing the full page markup of any shared URL, many of which are as big as 100KB.
Is that just the way this module needs to work? Can't it just cache the <head> or just the requested metatags?
Comments
Comment #1
amaisano commentedComment #2
frans commentedJup, This is as designed.
The idea is that we can fetch images (or other content, like first paragraph) form the body copy when no image is given in the tags. That comes at the cost of diskspace, but imho that is cheap.
Comment #3
amaisano commentedThanks for clarifying. I get the idea, for sure.
Would it be an option to ditch the cache once the text and image(s) have been found, and just retain only what is displayed?
Comment #4
frans commentedThe cache is already split up in tags (parsed content) and content (html). The html cache could be removed but it is not very high on the priority list. Thing is that I don't see what the problem is with a little bit of space extra. It doesn't eat bread, does it?
I am not saying that the cache will be removed, but once this module matures, it could be an option. Big advantage with the cache in is that you can extract other stuff (all links for example). I am using that on a site, in a custom module.. it is just easy.
Comment #5
loon commentedComment #6
loon commentedD7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.
Thanks!