A nice Hyper Cache user showed me that Hyper Cache had a bug when managin the mobile user agents list. Please, upgrade to version 2.2.7 AND go to the admin panel. DELETE the mobile user agents list, SAVE. The list will be regenerated. RESAVE the options.
You’re are done.
Otherwise opera mini and windows ce user agents won’t be detected.
Sorry for this bug, it created me a lot of problem on www.dopopranzo.net just the day I had 30.000 page view (this is the proof Hyper Cache works… the hosting plan of www.dopopranzo.net costs me 12 euro per year… yes you read well, 12 euro per year).
PLEASE: give a look to Protector, and let me know what do you think about it.
The version 1.3 of Global Translator Pro is available for memebers (gold and silver). The new version features tha page caching on database as major upgrade. This will surely be useful to people with low resources on disk space but with a good database service.
You can find more reading the official Global Translator Pro page (the link is direct, I’m not affiliate, just a friend!)
Remember that Hyper Cache detects Global Translator (both the Pro and free version) and suggest the right url prefix to not cache. That avoids double page caching and a big disk space waste.
Why Hyper Cache doesn’t preserve the commenter data? It’s simple to understand. When a user leaves a comment, WordPress set on it’s browser some cookies to keep he’s name, email and blog url.
On subsequent visits, WordPress pre-fill the comment form fields with user data.
If Hyper Cache lets WordPress to do that, it can happen that a cache page contains a user detail. These details would be shown to all visitors who are served with a cached page.
Read more…
I knoweldge of WPMU is ZERO. Many people asked me to make Hyper Cache compatible with WPMU, but really I don’t know what that means.
If I find enough time to install and test WPMU, enough time to read it’s documentation I will be happy to modify Hyper Cache for it.
The new version fix a warning message and add the nice feature of “last modified” http header compatibility. The latter improve e little more the cache efficiency.
All details can be read in the official Hyper Cache page.
I’ve just released a new version of Hyper Cache. There are a couple of new options to avoid the home page caching for who need it and a syntax for exact match of URI rejection.
Read more on the official Hyper Cache page and have a look to the new Hyper Cache Configuration page.
I’ve just submitted the 2.0.2 version of Hyper Cache. This version corrects a small bug in the timeout option, adds the russian translation and a “integration” with Global Translator by Davide Pozza.
The latter plugin has its own cache, so it’s better to avoid caching the translated pages. The main reason is disk space, the second is due to the fact that when a page cannot be traslated the plugin tries to translate if on subsequent request.
Is the “non traslated” page is cached, not request are sent to the plugin…
Check the “advanced options” from this integration with global translator.
Comments