I’m developing a small Onebox plugin and testing it in my production install.
It appears that Discourse is caching the Oneboxes: When I paste a link I once saw oneboxed into a new post, the preview is still looking as if it was generated by an older version of the plugin, while newer links appear as they should. All this is happening in the preview, I’m not actually posting the link.
In the redis cli, you can also delete individual keys without flushing the entire redis cache:
# ./launcher enter app
# redis-cli
> keys *CACHE:onebox*example.com*
1) `"default: CACHE:onebox__https://example.com/"`
> del "default: CACHE:onebox__https://example.com/"
(integer) 1
> keys *CACHE:onebox*example.com*
(empty list or set)
I expect that this key schema is unlikely to change often, but if it does, you can just use keys *onebox*url* or even keys *url* to look for the cached key to delete…
I can confirm that I successfully deleted cached oneboxes and rebuilt HTML for posts affected by cached broken data using this method.