Hyper Cache 2.5.5
I know, I stopped to answer your precious questions. But my regular job overwhelmed me and I decided to do not release a new version, even if almost ready of Hyper Cache.
Today I had 30 minutes, I gave an look to all the code and decided to release.
Hyper Cache 2.5.5 has deep changes. To solve problem with not writable wp-content, with directory creation and so on, I moved almost all the hyper cache generated files in to the hyper-cache.
On installation and activation only one file will be written in wp-content, the advanced-cache.php which is a required file by WordPress. So now you can safely delete other hyper-cache related files or directories.
To do a clean job, you can disable hyper-cache, clean up (delete the advanced-cache.php too) and the reactivate. Now there is the “one click install mode”, so on activation hyper cache starts to work immediately.
The cache file count in the configuration panel is of all cache files, even if they are expired, so it doesn’t measure the real valid cache pages. Distinct counts will be available in a future release. Still, the new invalidation process do not remove expired cache files, but only store the invalidation time. Is more efficient specially with blog with a great amount of pages.
SO DOT NOT THINK THAT A PAGE IS NOT EXPIRED IF IT’S FILE IS IN THE CACHE FOLDER.
On auto update from WordPress, the cache repository is deleted which is the correct way to update: some people claim that after updating Hyper Cache the cache pages are lost: would you keep cached pages with a different format due to version change? I don’t believe so…
If you enable gzip compression, the cached page are stored compress. There is good reasons to do that, so do not ask me why you cannot use gzip compression and store uncompressed pages.
Autoclean: it’s better to leave it enabled. I don’t know why people want to disable it, but is not recommended. Leave for autoclean a time of 30-60 minutes otherwise your cache folder will explode.
My personal setting: timeout at 1440 minutes, autoclean 60 minutes, compression enables, redirects cached, invalidation “single post” with archive invalidation flag enabled (but for best performance can be left unchecked).
I'm Stefano Lissa. 10 years ago I was building web sites for my pleasure. Blogs didn't exist, web content systems were ugly, hosting really expensive. And my student pocket was empty.
Dont worry about your english. You laid out everything nicely. thanks for the info Stefano. Ill check Hyper Cache later.
I have this version installed, but when I publish a post I get this error:
Warning: touch() [function.touch]: Unable to create file /home/mysite/public_html/wp-content/plugins/hyper-cache/invalidation.dat because Permission denied in /home/mysite/public_html/wp-content/plugins/hyper-cache/plugin.php on line 147
Warning: Cannot modify header information – headers already sent by (output started at /home/mysite/public_html/wp-content/plugins/hyper-cache/plugin.php:147) in /home/mysite/public_html/wp-includes/pluggable.php on line 865
What should I do?
Thank you.
Have you installed the plugin from wordpress plugins panel or by hand? If by hand you have to set the plugin folder as writable and the subfolder cache writable too.
I have the latest version Installed:
Cached pages timeout – 0 (minutes)
Cache autoclean – 0 (minutes)
I opened all pages but still:
Files in cache (valid and expired) 1
What should I do?
Richard
Just downgraded to the previous version and all my cashed pages are back again ??
I suppose you have deactivate hyper cache, deleted the plugin folder, uploaded the new version and reactiveted it, right?
With the upgrade to new version 2.5.5 I used auto-update
Now when im saving my post my tag and category vanish
here is my cache config:
Hyper cache
Ask apache crazy cache
DB cache reload
Ok so first off great plugin.
Wanted to say you might want to add a check for chmod 777 on the cache directory, or a notice some where that this is needed.
It’s obvious that is would be, but not for every one.
(just to help people who don’t understand why the plugin isn’t working)
On another note, i really like the fact that you keep supporting this plugin, that is in my opinion the best caching plugin available. I does one thing and it does it well.
Aditionnaly it works with ask apache crazy cache and db cache reloaded just brilliant.
Any way i’m getting irritated that there is no CHANGELOG, even a note in the readme would be appreciated.
I know i have no right to request this, but i’d like to know what changes i’m commiting to when doing an update.
Thanks again for a great plugin. But please at least write a line somewhere about what you’re changing. If i mist it please direct me where to find it.
When I have the time (and usually it’s hard for me to solve bugs, test them, commit new versions to help people as quickly as possible in my spare time) i try to write a version note on this blog. All posts about Hyper Cache versions are tagged and, as written in the plugin page, can be found here: http://www.satollo.net/tag/hyper-cache-versions.
About the CHMOD 777, usually people update the plugin with the automatic update function of WordPress: that grants the folders are created by PHP with its running user and with that user’s permissions. So, usually, there is no problem. Ok, I’ll add a note in the hyper cache page, even if I know no one will read it
or insert better tests on hyper cache installation.
Thanks for posting about the new version(s).
I only said something about the chmod thing cause I installed the new hypercache version on my dedicated server trough automatic updates and i had this issue.
I do have to set the the plugins folder’s chmod to 777 that doesn’t mean that it’s recursive…
It’s really strange: usually PHP runs as CGI/FastCGI or Apache module, so it’s a real unix user. When a unix user create a directory permission are set (or should be set) so that such user can create files inside that folder. I’m not expert maybe PHP can be configured to create directory with unusual permission, but it is a big problem: when you auto uodate wordpress delete the plugin directory and recreate it so on each update the problem will be back again.
What folder you set to 777? wp-content/plugins or wp-content/plugins/hyper-cache or wp-content/plugins/hyper-cache/cache???
I ALWAYS look for the changelog notes of any plugin and new WP versions. Sometimes the risk to update does not worth it. If it is something critical, or related to my server setup I update as soon as possible. If not I usually wait for a version with bigger changes.