infosws

Hello,

I missed that update somehow!

Running a test on the first website things are updating again great!

I’ll run some further tests and mark resolved if I can’t find anymore issues, thank you

Hi Marko,

I can confirm both versions are no longer working, when Cloudways confirmed they could not trace the request I rolled back the plugin to first check if a recent update caused it.

I found its fine upto 2.9.4 and then following versions it no longer works at all.

When I say fine, I mean I can update a page and then see my change on that page in incognito browser. Using the latest versions, this no longer happens and then trying to clear the cache from the website end fails – you have to access the server to clear it at the server level.

How we confirmed all this is starting with Cloudways support, we initially thought something on their side was the issue – debugging the problem has isolated the issue to w3tc.

A snippet from our conversation;

‘Thank you for your detailed update and for your thorough troubleshooting. Based on your findings, it seems the issue is related to recent versions of W3 Total Cache, as rolling back to version 2.9.4 restores the expected cache-purging functionality. This suggests a change or bug in newer W3TC releases rather than on the Cloudways platform.

We recommend keeping W3TC at version 2.9.4 for now and contacting the W3TC support team to report this issue, as they may be able to provide a fix or further guidance’

They have access to one of the effected websites to verify the settings are correct for their platform – they even updated the configuration to work with :80 rather then :8080 and couldn’t find w3tc sending anything.

I hope this covers everything, let me know if you need anymore info!

• This reply was modified 3 weeks, 6 days ago by infosws.

Hi, I’m not sure why this is marked as resolved. It’s not.

This issue still exists and only from this plugin.

Please can you help?

Hi,

We’ve had this problem on another install with these two plugins.

Autoptimize is a great plugin but we use W3 Total Cache for the complete system and would much prefer it works correctly with W3.

So we will be disabling this feature by default on all installs and will wait for this to be fixed.

Hi @shameemreza,

Turning off this option seems to solve the problem on one of the installations i’ve been having this problem on. I’ve managed to turn on the minification once more and do not see this error anymore.

I’ll test this on the other website that i was having this issue on and get back to you.

Thanks!

Hi @properlypurple,

This was the bundled version of Gutenberg with WordPress, I just went back through my chats when I was discussing the issue I didn’t save any screenshots. We were both looking at the website live, using Firefox / Chrome and both were seeing the same results.

This was on 6th of September so WP 6.2 to 6.3 I think.