• Update 10/18/21: The latest version of the plugin now works as it should.

    After the latest update, this plugin will no longer activate. It forces the site into Maintenance Mode and then I have to manually delete the .maintenance file in order to regain access to the site.

    • This topic was modified 3 years, 1 month ago by Josh Mckibbin. Reason: It works now
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @joshmckibbin

    First of all, thank you for your review.
    I am sorry about the issue you experienced after the update to the latest version of the plugin.
    Can you please make a backup of wp-content/w3tc-config/master.php and completely remove and re-install W3 Total Cache?
    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 (make a backup)
    – 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)
    3. 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.
    4. Go to your wp dashboard and re-install W3 Total Cache

    Most likely some files broke during the update.
    Please let me know if the issue persists.
    Thanks!

    Thread Starter Josh Mckibbin

    (@joshmckibbin)

    I deleted everything associated with the plugin and performed a fresh install of it. It still fails to activate and triggers Maintenance Mode. Falling back to version 2.1.7 fixes my issue.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @joshmckibbin

    Thank you for the information. Just to confirm we found an issue in the latest release related to Util_WpFile_FilesystemOperationException
    This will be fixed soon in the next release.
    Thank you for understanding and your patience!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘It works again!’ is closed to new replies.