Community Support Forums

I am getting the following message

Error: Could not enable Quick Cache. Please check permissions on /wp-config.php, /wp-content/ and /wp-content/cache/. Permissions need to be 755 or higher.

when I press save. However the permissions for the above I've set to 777 and still the message comes up.

It does nonetheless appear to be enabled and caches pages as they are opened, but I was hoping to use the autocaching feature to speed the loading of (rather process heavy) pages and this doesn't appear to be working.

Any ideas?

Hi there. If you're sure these directories are all "writable", and you're still getting this error, please confirm that WP_Cron is available in your WordPress installation. This error can sometimes pop up whenever the function "wp_cron" is non-existent.

You can run a quick test, by adding this to your theme/functions.php file:

Code: Select all

if(!function_exists("wp_cron"))
    echo 'Nope, WP_Cron is NOT available';

Please let me know if this helps. Otherwise, I'll be happy to dig deeper.

I have the same problem. All the permissions are well set but it doesn't activate. I didn't have the file wp-cron.php in my / dicrectory (and I don't know why...) but even if now it's at its place, it doesn't work. What could be the problem?

With some web hosting companies, the Apache web server runs as a different system User than what your files run as. That would be my best guess. If you are setting all the proper permissions on your /wp-config.php file, and your /wp-content directory, but Quick Cache is still complaining about permissions, it's because Quick Cache is still unable to gain "write" access to one or all of those locations.

You can create a PHP file, just name it whoami.php.
Then put this inside it.

Code: Select all

<?php echo exec('whoami'); ?>

Upload the file, and open it in a browser.
That will tell you what your Apache installation is running as.
You might contact your hosting company and ask why PHP files are not capable of gaining "write" access. That might shed some light on things.

I had the same issue on my new servers. It turned out that my domain looked like a user as it did not have a TLD. It was also running as fastcgi and so the server administrators reset permissions to default which is needed for wordpress and such scripts to write under fastcgi.

Quick cache then worked. Blazingly fast. Hope that helps someone.