• So, maybe I’m crazy or maybe another plugin is causing the problem or maybe I missed some warning somewhere. It seems like when I deactivate w3 (why would I ever do such a thing, I know) but don’t first disable the various caches, then the caches are still active. This makes for a veryyyyyyyy frustrating experience when developing and trying to deactivate other plugins – they remain active due to the page cache.

    I’d love to know if anyone else has noticed this or can test this on various set ups to see if this is a reliable bug.

    P.S. To put more of an empirical spin, I did a few test cases.

    a.) I activated all caches and deactivated then w3 then deactivated another plugin to see if it’s functions would stop working. They wouldn’t most of the time, though I have to admit this didnt happen consistently. This partly may be because sometimes the cache seems to take a while to kick in.

    b.) I deactivated all caches and then deactivated w3 and then deactivated another plugin. This makes the plugins functions stop working 100% of the time.

    Deactivating all caches BEFORE deactivating w3 cache worked 100% of the time.

    https://wordpress.org/plugins/w3-total-cache/

  • The topic ‘[Bug Report] Potentially site breaking huge bug?’ is closed to new replies.