• Resolved Sérey

    (@serey)


    Hello,
    After updating W3 Total Cache from version 2.8.12 to 2.8.13, a critical error occurred on my website.
    I had to roll back to version 2.8.12, and everything is working fine again.

    Could you please help me update safely to version 2.8.13 without causing the same critical error?

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

    (@vmarko)

    Hello @serey

    Thank you for reaching out, and I am happy to help!
    I’ve just attempted an update one of our instances and everything worked as expected

    Have you tried only once or everytime you are getting the Critical error?

    There is a chance that the update did not go well and some files were not coppied.
    Please donwoload the configruration file in Performance>General settings>Export/Import.

    1. Check .htaccess File (make backup)
      W3TC will create many directives in .htaccess file to control the caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
      Ensure that no residual entries are left over in your .htaccess file after deleting the plugin.
    2. Delete wp-content files and folders
    • cache folder
    • w3tc-config folder
    • object-cache.php (if exists)
    • advanced-cache.php (if exists)
    • db.php (if exists)
    • upgrade folder
    • delete w3-total-cache folder in wp-content/plugins/ (if exists)
    1. Delete Cached Files from CDN (if using CDN)
      Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
    2. Go to your wp dashboard and re-install W3 Total Cache
    3. Import the configuration file

    Let me know if this helps!

    Thanks!


    Thread Starter Sérey

    (@serey)

    Hello @vmarko ,

    Thank you very much, it worked well!
    Best regards,
    Sérey

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

The topic ‘Critical error v2.8.13’ is closed to new replies.