Im joining this thread as I may have similar issues although I didnt know it was related to w3 total cache. Do you have gutenberg disabled via classic editor or other plugins or code? I get 502 errors.
@dan14 – Yes we are using Classic Editor, but we have already ruled that out as we disabled all other plugins during our test.
We are 95% sure that W3 Total Cache is causing the server overload.
If you disable classic editor and update using gutenberg then it will work, you won’t get any errors. At least that’s how it is for me.
For me, if the posts/pages are small then it will save with classic editor but when they are big then it crashes. I had no idea w3 total cache is causing this. Lets see what they say.
Hello @thefriendlancer
I am sorry about the issue you are experiencing and I am happy to assist you with this.
Can you please share some additional information like if you are on shared hosting or VPS/dedicated?
Also, are Object Cache and Database cache enabled, and if so are you caching to disk and for logged-in users?
Thanks!
Im on shared, no object or database cache enabled. Logged-in users no cache. Page cache is enhanced, disk.
-
This reply was modified 3 years ago by Dan14.
Hello @dan14
I’ve checked this using both classic and Gutenberg editor, on shared hosting and no 502 errors.
Does the issue persist if you disable W3 Total Cache?
Thanks!
its only happening with big pages. The first time it might work, but in the second or third time it will not. I gave a solution for the guy that opened a thread so maybe thats why he is not responding. But I would rather get it to work with the classic editor.
thanks @dan14 and @vmarko
I would like to update you on this from my end.
Unfortunately, I won’t be able to provide you my previous configuration for Object Cache, Database cache, etc.
We have already deactivated and deleted W3 Total Cache plugin from our site.
We also have other caching plugins installed, and removing it did not affect our speed tests.
We no longer are experiencing the extreme surges since then.
So I am afraid goodbye W3 Total Cache for now, thank you for the service!
I hope you will be able to address the issue whatever is causing it.
You can now mark this issue as resolved.