What’s the fix: Page Cache: Processed content filter

Hello

Thank you for reaching out and I am happy to help!
You can check all the details about this fix in this GitHub pull request.

Can you please also elaborate what is the issue you are reffering to?

Thanks!

OK, thanks. This seems different from what I’m fighting against.

The issue I’m facing has been described here.

• This reply was modified 7 months, 1 week ago by T4ng.

Hello @schwipps

The problem is that we are unable to replicate the issue you are reffering to, and therefore we are unable to determine why this is happening, and also, there are no other reports like this at all.

I’ll have another chat with the team about this and let you know if we can figure somehting out.

Thanks!

Hi,

Thanks for your reply, and for trying to investigate this a bit further.

If I can add details, we face this error almost systematically right after proceeding to a deployment, even though it purges all W3TC caches from the CLI, and the opcache. In such cace, most, if not all the pages including a nested Elementor template miss the related CSS.

Last precision, we face this issue on 2 different environments, staging and live, which both exploit the same deployment process, for the same WordPress code. It’s very painful to solve, since at that time, purging the whole website manually won’t help, and we have to spot all the broken pages to purge them manually.

Later on though -out from a deployment- I can purge all the caches, and the issue won’t occur.

The error only seems to occurs right after the deployments.

Hi,

Did you get to discuss this internally?

We’ve just published our monthly update. As usual, after clearing cache, some of our main pages (always the same, mentionned above) were broken. Clearing all the cache resolve the issue, for these page (sometimes, or only partially with some elements still broken…), then that’s other pages that do not display properly.

It’s a nightmare to deal with this, for each deployment

• This reply was modified 6 months, 3 weeks ago by T4ng.

Just so you know, I’ve very much improved the understanding of this issue, and described it thoroughly to Elementor.

https://github.com/elementor/elementor/issues/27320

It’s obviously not W3TC’s behavior that’s in cause, but most cache plugins seem to be impacted by this issue. Since you’ve got a much better understanding what’s going under the hood, thanks for taking a look at it, and ideally, team up with Elementor to find a solution.

Thank you

• This reply was modified 6 months, 1 week ago by T4ng.

Any genuine interest in getting this issue solved, really?