Can you provide a bit more information, what in the plugin doesn’t work when caching is activated, can you give us some expamples.
Would it be possible to see your site?
Hello 👋.
I’m a maintainer of the ActivityPub plugin, maybe I can help.
ActivityPub (the specification) uses the profile pages (author pages in WordPress) as the end user representation and API endpoint, using content negotiation. The classic Accept header of the browser still returns the HTML and with Accept: application/activity+json the plugin returns the JSON version.
Since we are talking about the problems in the interaction of both plugins, I assume that WP-Optimize does not include the Accept header in the caching logic, i.e. the first request wins. If the first request is via the browser, HTML is in the cache and ActivityPub does not work, if the first request is via ActivityPub, JSON is in the cache and the site visitor gets to see JSON instead of the website.
I hope this helps and happy holidays!
Thanks @pfefferle, this’ll help a lot.
@xizor, we’ve taken a note of this issue and will investigate based on the information we have so far. If we need more information, we’ll let you know. Thanks for reporting this issue.
There are no visual problems that you describe, though I know of what you speak, @pfefferle.
@kowsar89 ,
These are my Observances:
- HTML is always correctly shown. No JSON displayed 👍🏽.
- Fully Built Cache + Newly Published Post = ActivityPub will not federate this newly published post.
- The newly published post empties the cache.
- All following published posts will federate via ActivityPub until the cache finishes auto-preloading itself.
- When Cache exists again – ActivityPub stops federating.
Thanks for providing additional information. Since I’ve already included this investigation in the queue, I’ll mark this thread as resolved for the time being. If we require further information, I’ll make another post here.
