Clearing Cache Error

[Jake]

Hi, I really like this plugin, but I have a small issue with clearing the cache. Whenever I clear I get an error that it couldn't be completely cleaned and to manually do this myself. When I check it seems to have been completely cleared, even upon a refresh in the FTP. Is this a bug?

[Jake]

I have discovered this happens when my wp-content is set to 755. If I set it to 777 it does not give me the error. Is it safe to leave it at 777? I run 1 website on my own VPS, so it is not a shared environment.

Thanks!

[Jake]

I would also like to know if running DB Cache Reloaded is safe (or necessary) with this plugin. I have been running it with Hyper Cache and found good results.

[Jason Caldwell]

I have discovered this happens when my wp-content is set to 755. If I set it to 777 it does not give me the error. Is it safe to leave it at 777? I run 1 website on my own VPS, so it is not a shared environment.

Thanks!

I would not suggest leaving /wp-content/ at 777 long term. Instead, I would set your /wp-content/cache/ directory to 777. This way the entire /wp-content/ directory is not writable, only the /wp-content/cache/ directory. That should resolve the problem that you're having.

[Jason Caldwell]

I would also like to know if running DB Cache Reloaded is safe (or necessary) with this plugin. I have been running it with Hyper Cache and found good results.

Nope, not necessary. DB Cache Reloaded is all about optimizing MySQL queries. Quick Cache goes way beyond this, and avoids any database connections at all; because it caches pages after they're generated. Having the DB Cache Reloaded plugin installed along with Quick Cache, is NOT going to increase speed.

The author of this plugin "DB Cache Reloaded", has provided a very confusing description for his software.

In his description, he states:

I think you've heard of WP-Cache or WP Super Cache, they are both top plugins for WordPress, which make your site faster and responsive. Forget about them - with DB Cache Reloaded your site will work much faster and will use less disk space for cached files. Your visitors will always get actual information in sidebars and server CPU loads will be as low as possible.

He is comparing apples to oranges. A DB Cache plugin might be better if you're not concerned that much about speed, and you just want to optimize WordPress a "little bit". Caching database queries WILL speed up your site. However, it will NOT speed it up more than Quick Cache, or WP Super Cache will.

The DB Cache Reloaded plugin, WILL improve the speed of your site, because it caches MySQL DB queries, giving WordPress less work to do. However, it does NOT cache pages after they've been generated. So all of the PHP processing routines, along with several DB queries that just cannot be cached, must still be processed for each and every page view.

The DB Cache Reloaded plugin, and others like it, are not comparable to Quick Cache or to WP Super Cache. They take two completely different approaches. Quick Cache stores snapshots of entire pages, and DB Cache Reloaded, caches only database queries.

The result is that DB Cache Reloaded will always be slower. That is not to say it's better or worse than Quick Cache. It just depends on what you'd prefer, and the way your site is designed. If you can get away with running Quick Cache, your site will be faster overall. If you can't ( i.e. your site depends on dynamic content at all times ), then running DB Cache Reloaded is better than nothing at all.

[Jake]

Thanks for the info. I had to SSH in as root and force it to 777 as it wouldn't let me via FTP. Even then it still gives me the same error unless I also make the wp-content folder 777. None of the other caching programs I used have had an issue with the wp-content folder being 755. Let me know if there is anything else I can try.

[Jason Caldwell]

Thanks for reporting back Jake. Quick Cache does not absolutely require a 777 permission, it only requires write access to your /wp-content/ and /wp-content/cache/ directories. Depending on your server configuration, this write permission may or may not require a 777 permission. Under most circumstances, 755 would be enough. I'm not sure why your server is requiring 777.

The "write access" test is handled by the "is_writable()" function for PHP.
http://php.net/manual/en/function.is-writable.php

Quick Cache only needs write access to your/wp-content/ directory at the following times:

• During activation/de-activation.
• When updating your Quick Cache options.

So once you have Quick Cache installed/configured, you can ( only if you wish ) change the permissions on your /wp-content/ directory, and just leave the /wp-content/cache/ directory writable.