Re-activating W3 Cache Breaks Avada Theme

  • Resolved bravesamwise

    (@bravesamwise)


    2 years, 4 months ago

    Summary: I deactivated this plugin as part of solving an issue. Now, when I try to turn it back on, it completely breaks the theme and display menus and headers with no structure.

    Details

    This morning, we had a caching issue on our website. Although the user-facing side continued to function, wp-admin slowed to a crawl, taking several minutes to load pages. I tried emptying the page, browser, object, and minify caches. This had no effect so I tried deactivating W3 Total Cache. When I did, the whole site (wp-admin and the user facing public side) crashed, anyone trying to visit received a 504 server error.

    I contacted our system administrator and he was able to restart the docker container where our site is hosted. Afterwards, the site continued to function as normal for a time, with none of the slow loading issues. I thought the issue resolved, so I reactivated the plugin. When I did, all the styling and structure from the site went away. I emptied all caches and the problem persisted.

    I’ve had to leave W3 Total Cache deactivated at the moment because we cannot leave our site in the state the plugin leaves it in.

    Do you have any suggestions or ideas as to how and why this may have occurred?

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    2 years, 4 months ago

    Hello @bravesamwise

    I am sorry about the issue you are experiencing and I am happy to help!

    Can you please disable the settings one by one in Performance>general settings, save the settings and purge the cache after each setting is disabled and see which one might be causing the issue?

    Thanks!

    Thread Starter bravesamwise

    (@bravesamwise)

    2 years, 4 months ago

    Hi Marko, thanks for your response.

    I tried to follow the steps you mentioned. I was able to disable, save settings, and flush the cache for the Page cache, Minify, and Database cache. When I tried the same for the Object Cache, the page failed to save and then I realized nothing was loading, including the front end site. Eventually, I received a 504 error on admin and a 502 error on the user side, production. I had to restart the docker containers again to get our site back up and running.

    We are using Redis with our Object Cache. Do you have any ideas as to what might be going awry?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    2 years, 4 months ago

    Hello @bravesamwise

    Can you please try to restart the redis server and flush redis

    With redis-cli:

    FLUSHDB – Deletes all keys from the connection’s current database.
    FLUSHALL – Deletes all keys from all databases on current host.
    For example, in your shell:

    redis-cli flushall

    Thanks!

    Thread Starter bravesamwise

    (@bravesamwise)

    2 years, 4 months ago

    Hi Marko,

    Thank you again for your response.

    Unfortunately, we already performed this action and it had no effect. Do you have any other suggestions?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    2 years, 4 months ago

    Hello @bravesamwise

    Thank you for your feedback.
    Have you tried deleting the object-cache.php in the wp-content folder and disabling the W3TC Object Cache?
    Restart and flush Redis, then re-enable Object Caching in W3TC.

    Let me know if this helps!

    Thanks!

    Thread Starter bravesamwise

    (@bravesamwise)

    2 years, 4 months ago

    Hello Marko,

    We tried your methodology here with one additional step – we also emptied all the caches via the front-end of the plugin (not wp-cli) after doing what you described.

    This appears to have fixed the issue, thank you for your help.

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

The topic ‘Re-activating W3 Cache Breaks Avada Theme’ is closed to new replies.