Comments on: Hyper Cache 2.6.0

By: Bert

Bert — Fri, 16 Dec 2011 20:40:23 +0000

You can always tell an expert! Thanks for cotnirbuting.

By: MuJE

MuJE — Sun, 08 May 2011 20:18:15 +0000

no more error message now. i just create a new folder name ‘cache’ in wp-content/plugins/hyper-cache then walla!

By: www.mersinevdenevenakliyat.co

www.mersinevdenevenakliyat.co — Thu, 14 Apr 2011 21:16:34 +0000

thank you for plugin.

By: Mike

Mike — Mon, 21 Feb 2011 21:12:24 +0000

Not liking the idea of having a folder world writable I did a bit of experimenting.

It appears that setting the cache folder perms to 744 works fine.

Cheers!

By: chodirin

chodirin — Fri, 31 Dec 2010 17:29:17 +0000

Here’s the solution:
Create folder “cache” here /wp-content/plugins/hyper-cache/
So it will be /wp-content/plugins/hyper-cache/cache

Change permission your “cache” folder to 777.
Done. Your problem solved.

By: Rhalmi Mohammed

Rhalmi Mohammed — Sun, 25 Jul 2010 23:04:27 +0000

Thanks for the plug in

By: Stefano

Stefano — Fri, 07 May 2010 22:19:24 +0000

Ask your web master to fix your problems giving him such message. Some permission changes are needed.

By: TechGyo

TechGyo — Fri, 07 May 2010 10:14:59 +0000

I’m getting this error:

Hyper Cache was not able to create the folder “cache” in its installation dir. Create it by hand and make it writable.
Your wp-content folder is not writable. Hyper Cache needs to create a file called advanced-cache.php in to that folder in order to work. Make it writable and deactivate and reactivate Hyper Cache.
The WordPress cache system is not enabled! Please, activate it adding the line of code
define(“WP_CACHE”, true);
in the file wp-config.php just after the define(“WPLANG”, …).

By: Nicola

Nicola — Fri, 15 Jan 2010 15:55:44 +0000

This happened to me with HyperCache 2.6.4 and WordPress 2.9.1.

The message ‘Hyper Cache was not able to create the folder “cache”‘ refers to wp-content/plugins/hyper-cache/cache , not to other places like wp-content/hyper-cache/cache. You may not need 777, stricter permissions may be fine too depending on your configuration.

It would be useful adding the full dirname(__FILE__) path in the error message. I had to print it out by changing plugin.php in order to find out the actual path it was complaining about.

By: Stefano

Stefano — Thu, 31 Dec 2009 09:00:45 +0000

On current version with automatic install or automatic upgrade the filder is included in the plugin distribution, so there is no need to create such folder. What vesion are you using? May be you found some old code or some old messages that need to be fixed.