• Hi, after updating to WordPress 6.9.3, the Add Post action has become very slow—around 6 seconds or more to open Gutenberg. If I clear the cache it drops to about 2 seconds, but then it slows down again. If I disable the cache, everything works normally.

    My editors don’t have caching enabled. Does anyone know if there might be any incompatibility between the latest version of WP Super Cache (3.0.3) and the latest version of WordPress?

    Currently I have everything updated to the latest versions, including WordPress, which is now on 6.9.4.

    Thanks a lot! 🙂

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Stef (a11n)

    (@erania-pinnera)

    Hi there, @eferpar,

    It seems like there might be a conflict between WP Super Cache and the latest WordPress version.

    While we’re checking with our tech team, could you please check the following?

    • Try disabling WP Super Cache altogether to see if the issue persists.
    • If the problem resolves, consider checking for plugin or theme conflicts as described here.
    • Additionally, ensure that your wp-content/ directory is writable and that PHP’s safe mode is disabled.

    Let me know what you find out. Thanks!

    (Internal ref: /C0CMN0V97/p1773325915427899)

    Plugin Support Stef (a11n)

    (@erania-pinnera)

    Hello @eferpar,

    Do you have updates about that, do you still need help?

    I checked with our tech team, and they confirmed that they didn’t notice this is happening on their sites. You could enable debug logging in the plugin and see if it’s doing anything. Another plugin might be deleting the cache, and it was added around the same time they updated WordPress.

    We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

    Thread Starter eferpar

    (@eferpar)

    Hi!

    The issue: since updating to WordPress 6.9.4, when the list of cached pages goes above 100–150, the Add Post functionality starts to slow down on load, eventually reaching the point of throwing a 500 error. If I clear the cache, performance returns to normal, but it slows down again as the number of cached pages increases.

    It’s not just that the issue disappears if I disable the plugin—if I simply disable caching while keeping the plugin active, the problem goes away completely.

    In the logs, I’m seeing this warning:

    PHP Warning: Object of class WP_Post could not be converted to int in /usr/share/nginx/beta.rtvc.es/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 3247

    I’m using the Newspaper theme.

    Everything was working fine until the latest WordPress update—I insist, everything was working fine until the latest WordPress update—no plugins have been added.

    Thanx

    Plugin Support Jen H. (a11n)

    (@jenhooks)

    Hey @eferpar, thanks a bunch for that extra context. I’ve asked our engineers to look into this, but since it’s nearly the weekend, it will be Monday at the earliest before we’ll get word back from them. We appreciate your patience and tenacity with troubleshooting this!

    Cheers. 🙂

    Plugin Author Donncha O Caoimh (a11n)

    (@donncha)

    Was any other plugin or that theme updated when you updated WordPress? I suspect that something else updated around the same time and is causing the problem. My photoblog has 4GB of cached files and making a new post happens very fast. We haven’t received reports of this problem from anywhere else either.

    Please enable the debug log in the plugin. That may reveal what is calling that code that’s causing the problem for you.

    Thread Starter eferpar

    (@eferpar)

    Hi! Over the past week I’ve been trying to replicate the scenario that was causing the Add Post issue with Gutenberg so I could analyze the logs, but everything has been working correctly. So I assume that one of the plugins that got updated during this time was causing the problem with WP Super Cache. Thanks for the help!

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.