Several errors

  • eludlow

    (@eludlow)


    13 years, 1 month ago

    Installed this successfully, but now on the plugins page (and on every W3TC page) I get:

    W3 Total Cache Error: Could not change permissions 755 on /home/qoru/public_html/wp-content back to original permissions 755.

    What’s weirder, I get the error twice – right after each other.

    What’s happening?

    Thanks,
    Ed

    I’ve tried temporarily changing the permission on wp-content (eg 777) but the error then reads:

    W3 Total Cache Error: Could not change permissions 777 on /home/qoru/public_html/wp-content back to original permissions 777.

    http://wordpress.org/extend/plugins/w3-total-cache/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter eludlow

    (@eludlow)

    13 years, 1 month ago

    I’m also getting:

    Page caching is not available. The current add-in /home/qoru/public_html/wp-content/advanced-cache.php is either an incorrect file or an old version. De-activate the plugin, remove the file, then activate the plugin again.

    Oddly, wp-content/advanced-cache.php doesn’t exist!

    Daniel Sachs

    (@danielsachs)

    13 years, 1 month ago

    Same here. The error started with 0.9.2.6, remains after 0.9.2.7 update.

    alanhenry

    (@alanhenry)

    13 years, 1 month ago

    I have the same problems. Something is clearly broken.

    I also get that it cannot create the cache directory and derivatives. The prior versions used a w3tc-config directory.

    M Asif Rahman

    (@asif2bd)

    13 years, 1 month ago

    Folder permission thing got changed. As an effort to fix the exploit, plugin Author trying to harden the security. Deactivate and Activate again should work. Either give temporary full read-write(777) permission to “wp-content” but must be for a very limited time. Or follow the guide and change code as necessary and advised by W3TC itself.

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    13 years, 1 month ago

    @m Asif Rahman incorrect.

    Long before the security issue, we switched to using the WP FileSystem API instead of the previous implementation that worked for years because we thought doing it the “WP Way” would provide more reliability and survive changes in WP core better, that is not the case and we’re working on getting things back to normal.

    Furthermore, the features in this release have been using by enterprise and other paying customers for the past year, these are simply the latest public releases.

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

The topic ‘Several errors’ is closed to new replies.