Hyper Cache is an experimental really aggressive cache for WordPress. I wrote it because my hosting provider is very low in resources, particulary on the mysql side.
I tried to install wp-cache: it does nice, but still let WordPress engine to startup, init the plugins, do some queries. There is a "super" version of wp-cache that does similarl Hyper Cache, but you need to modify the .htaccess file.
Hyper Cache starts up just after a user requests a page, and just before WordPress starts to send queries to the database. If the page requested is already in cache, it sends the content back and stop.
Drawbacks. Any plugin that need to be called on each request (eg. the ones that collect statistics in any way) stop to work. This problem is common to wp-cache, but wp-cache is more nice about that.
If you are logged and navigate the blog with the same browser the cache is not triggered. To test the cache use a different browser and, before start the test, clear the cookies.
The cache works only with permalink active. It doesn't cache POST request or GET request with parameters. This behaviour let some plugin to work correctly.
The cache doesn't affect tracking systems, like Google Analytics or MyBlogLog.
Hyper Cache IS NOT compatible with wp-cache. Remove it and assure the the file/link "wp-content/advanced-cache.php" is removed or at least renamed. The wp-cache deactivation doesn' remove this file on my blog, I don't know if it's a bug.
Installing
Download it from the wordpress plugin repository.
Activate and go to the options page to configure and save the configuration. Now the cache is ready to work. Open your wp-config.php file and add the line of code:
define('WP_CACHE', true);
if not present, or if present modify it accordingly.
Removing the plugin
Deactivate it. The deactivation removes the file in wp-cotent (see the technocal notes). The wp-config.php is not changed, you can remove the "define" statement by hand: it doesn't hurt, anyway.
Technical notes
The plugin create two files and a directory inside the wp-content folder. The file are "advanced-cache.php" and "hyper-cache-config.php". The directory is named "hyper-cache" and is used to store the cache pages.
You need urgently to replace your php short tags with the standard long ones. Otherwise your plugin fails completely.
After I edited the tags manually the plugin seems to work very well.
Hi,
nice plugin and working well with std. long tags and if i remove wp postload from settings file. I`ve benchmarked it against wp super cache with the apache bench and it seems to be not as fast as wp super cache (about 0,6 longer), but of course it got less queries. but thats a point i didn`t have tested a hour ago.
i like it..and will follow development.
have a nice day,
Chris
sorry for really bad english by my little side.
[...] en WordPress: Hyper Cache Sitio Oficial: Hyper Cache Etiquetas: cache, compatibles, hosting, mysql, plugin, plugins, recursos, sitio, wordpress, [...]
Wp-super-cache HAS to be faster because that plugin uses drectoly apache to serve the pages, I think, removing completely the wordpress intervention.
for the long php tag, I’m so used to program with the shor one, that often I forget the world is not always as my developement environement… thankyou!
wonderful… it works very well…
i couldn’t be able to let work wpcache or supercache…
yours is easy and fast…
http://www.seriex.it
Good work! Only problem is if someone’s left a comment before and they hit a page, then their name, email and URL are cached so the next person to hit that page will see the same information.
You can fix this by using the same trick as wp-cache. I changed the following line in advanced-cache.php:
$hyper_cache_name = md5($hyper_uri);
to:
$hyper_cache_name = md5($hyper_uri.wp_cache_get_cookies_values());
and added the following function at the end of advanced-cache.php:
function wp_cache_get_cookies_values() {
$string = ”;
while ($key = key($_COOKIE)) {
if (preg_match(”/^wordpress|^comment_author_email_/”, $key)) {
$string .= $_COOKIE[$key] . “,”;
}
next($_COOKIE);
}
reset($_COOKIE);
return $string;
}
I’m sure the code isn’t correctly formatted but you get the idea!
Confirming that the email address is indeed shown!
test
By now I’ve added some code to remove the cookies with the user data, your code work great but generate a big number of files in the cache if you have a great number of visitors. The new version is the 1.0.3.
This work arounf as a problem: if the comment go in moderation state, this is not shown to the user.
Next days I’ll check more deeply the problem. Thank you!
All right, but the version on WP is still 1.0.2 as I wrote this. Do we get the newer one when we download that — or where do we get it?
Peace,
Gene
congrats . good plugin even though i didn’t use the wp-cash earlier but i think i’ll go with yours this time
just hope you keep putting the codes updates here .
or even release many updates of the plugin frequently
good work
With your 1.0.5 version, the Settings screen is mixed English and another language (French?). Maybe a localization problem?
Peace,
Gene
A suggestion: How about a changelog, so we know what is different about the newest versions?
Peace,
Gene
For the last 0ne+ month, I’m facing lots of problems with my blog, right after moving to DreamHost VPS viz. downtime, server load. And the Super Cache & WP-Cache failed to work on DreamHost VPS (using NFS). I looked around alternate plugins to reduce SQL server load and came across your plugin. It works well, only glitch is, it also caches admin pages.
For e.g. these days, due to ongoing server load my blog dies every now and then with “500 internal, 404, error establishing database connection” etc. errors and with “Hyper Cache” on when I clicked my wp-login, it generated “500 error” and I couldn’t logged-in, until I deactivated Hyper Cache.
Can you give an option to avoid admin page caching?
Also, still server load is continue, can you advice ‘how do I take-off Cache directory from wp-content/cache to /tmp/xxx-cache, because I want to test some functionality.
Please advice.
DG…
Santollo! Great plugin. The only caching plugin that I could manage to make work under Windows IIS and the simpler one too. Great job!
A problem that I’ve detected is that, when a visitor comment, even if it is held for moderation, it deletes all the cache and everithing starts over again. If I create a new post, or edit an old one the same happens.
I would like to disable that, if possible. Could you give me some advice?
Thank you.
Your latest version, 1.0.7, seems to be working all right. But after several days at the default setting (expiring cache files after 60 min.), I have over 4500 files in the cache folder.
Why not add a feature to auto delete older files, after they expire? Or at least daily? Can do?
Peace,
Gene Steinberg
Many thanks for a great plugin, I spent hours trying to get other ones to work with no luck.I had this one working within minutes and as of yet have not had any problems with it.
Regards Vinny
where the cached files are stored?? I dont see any directory named cache,,,, and please tell me in configuration page, does it starts caching only when it check the “cache active?”?
I have done all but i still see 0 cached page,, and how do i know that the site is loading fast??
Hi i just installed your plugin but it didnt create any directory of hyper-cache and nor did any files in wp-content directory,,, please help me
having the same problem as hanjra - nothing is caching. Please help. Traffic is building at my site!