Hyper Cache 2.6.0
07. Oct, 2009 
25 Comments
Take a moment to subscribe my newsletter:
This version is a simple fix only for people who experienced errors because Hyper Cache wasn’t able to write in the cache folder.
Now Hyper Cache creates its own cache folder ON ACTIVATION, so, I hope, there are no more problem with folder permissions.
Another important modification is about some header Hyper Cache sends to browsers that should solve the issues about browsers (Chrome and Safari) to not verify if a page has been modify since the latest download.
My excuses for my bad english but it's the only way I have to communicate with you. Would you suggest
a correction? Leave a comment, thank you!
I'm Stefano Lissa. Ten years ago I was building web sites for pleasure. Blogs didn't exist, web content systems were ugly, hosting was really expensive... and my student pocket was empty.
Thia version is a simple fix only for people who experienced Hyper Cache not working because unable to write in the cache folder.
This version is a simple fix only for people who experienced errors because Hyper Cache wasn’t able to write in the cache folder.
Edited, thank you!
Hello,
I just updated to the new version and get this error message:
“Hyper Cache was not able to create files in the folder “cache” in its installation dir. Make it writable (eg. chmod 777).”
The folder exists and is writable (777), but I keep getting the error message.
Thank you
Hyper Cache was not able to create files in the folder “cache” in its installation dir. Make it writable (eg. chmod 777).
when i chmod 777 the folder and deactivate and activate the hypercache the site is becoming kinda slower?
Hyper Cache was not able to create files in the folder “cache” in its installation dir. Make it writable (eg. chmod 777).
The folder IS chmod 777.
whats happening? this plugin was so cool some version ago and now its become a real pain in the ass work wit it
Hyper Cache is still cool, but to implement requested features, controls for many different situations and so on created those bugs. Evolution is not free of errors
Same thing here:
“Hyper Cache was not able to create files in the folder “cache” in its installation dir. Make it writable (eg. chmod 777).”
I saw this after trying to publish an article.
I’ve checked the automatically created /cache/ folder and it’s 755, so that might be the problem. I’ll have to recreate it myself with the correct folder permissions.
Same things:
Hyper Cache was not able to create files in the folder “cache” in its installation dir. Make it writable (eg. chmod 777).
BUT the folder IS chmod 777.
What to do?
do nothing is a wrong message. update.
Thanks.
And thanks a lot for such a good plugin.
Comparing how many times supercache brokes my sites, yours is ideal.
Same here – it worked until 2.6.0, now this error is coming up: “Hyper Cache was not able to create files in the folder “cache” in its installation dir. Make it writable (eg. chmod 777).” HOWEVER, it IS actually writing files and caching properly, so the error message is, erm, an error. As far as I can tell.
The plugin works, but is giving an incorrect error: files are loading from cache, and everything is working as it should, just the error message is nagging when it needn’t be!
So don’t worry those of you who are getting it – as long as the plugin WORKS should be your first concern. In my opinion. While the error message is a little irritating, at least Hyper Cache doesn’t burn up RAM like other similar plugins might…
Thank you, I’m looking to it. So many people asked me to add more strict controls on hyper cache probably a check is “too much paranoic”
No problem – as I said, it works, and that’s the main thing
Just the error might be triggering incorrectly (this happens on a couple of wordpress blogs we manage).
I had to create a folder named ‘cash’ (chmod 777) myself. Thank you works A-Okay now!
Just send you and e-mail about my right sidebar, hope you can help me out!
I like you work!
Does the folder ‘wp-content/hyper-cache’ needs to be 777 all the time ? I now have 744 but when making a backup I read “No such file or directory, -125: remote chdir failed”.
Or can this folder be removed ?
The folder wp-content/hyper-cache is NO more used. You can safely delete it (oh, only if you use the latest Hyper Cache version…)
Thank you !
Fixed!
you have to create the ‘cache’- Folder in the plugin directory, NOT in the original wordpress installation directory. This was confusing ‘caus i made everything right until i checked the plugin.php file.
Best luck everyone.
@stefano you may change the message to “Hyper Cache was not able to create the folder “cache”. Create it by hand in the ‘plugins/hyper-cache’ folder and make it writable ’777′”
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.
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.
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”, …).
Ask your web master to fix your problems giving him such message. Some permission changes are needed.
Thanks for the plug in