New wp-cache-2 release (2.0.20)
I just released wp-cache version 2.0.20. This version [hopefully] solves three issues:
Blank pages for first requests and non existing pages in some installations (ticket and patch 516 by Peter Hosey).
Dropped headers in some installations, specifically FastCGI enabled servers (ticket and patch 517 by Peter Hosey).
Don’t delete cached files if a new comment is not being approved (the spam problem, thanks).
The wp-cache-2 page.
Installation note: Simply uncompress the zip file and overwrite all previous wp-cache files. The fastest method is to change to the “plugin” directory and unzip from there.
The archive still contains the version 2.0.19
I’ve got the “blank pages on first requests” problem on a new server (www.dreamhost.com), so I’d be very happy to test the fix
All the best for 2007, Wolf-Dieter
Comment by Wolf-Dieter — Sunday 31/12/2006 @ 14:57
#1, it was just a mistake in the version number (in wp-cache.php) but the archive was ok. Solved.
Thanks for noticing it.
Comment by gallir — Sunday 31/12/2006 @ 15:14
Seems to work now. Thanks!
Comment by Wolf-Dieter — Sunday 31/12/2006 @ 17:15
The only reason I don’t use this plug-in yet is that if you have a site that has multiple themes (like mine), the theme does not change if a reader selects another theme to use. Any way to fix this?
Comment by Scott-O-Rama — Sunday 31/12/2006 @ 19:27
When experimenting with your plugin, www.diejulia.net running a modified k2 theme showed some strange behaviour. To be more exact: some (visible) comments didn’t show up correctly. I’m currently updating the site and will keep you updated about the results from my tests. Wolf
Comment by Wolf-Dieter — Sunday 31/12/2006 @ 21:36
WP-Cache 2.0.20
Apunte rápido y a la cama, Ricardo lanza una nueva revisión de WP-Cache que arregla tres problemas:
Páginas en blanco para las primeras peticiones y páginas no existentes en algunas instalaciones (ticket 516 + parche.
Desaparición de las …
Trackback by SigT — Monday 1/1/2007 @ 2:14
I’m showing a weird issue I didn’t have with the previous version and the mclude statement. with a php include_once and a closing /mclude worked fine in the previous version, but in this version it doesn’t. All I get back is the actual PHP code in the cached page, rather than the code being executed as it should.
I doubt the blog will accept this example, but worth a try:
Returns only the PHP rather than executing it, as it did previously. I wrote back the old version and it works fine again.
Comment by Rirath — Monday 1/1/2007 @ 9:30
WP Cache 2
?? slashdot / digg / hemidemi effect ???? ?
WordPress ??????? blog ???????????????? dynamic ?????????????????????????????????…
Trackback by ??????? — Monday 1/1/2007 @ 13:48
advanced-cache.php link does not exist
Create it by executing:
ln -s /mounted-storage/home15a/sub001/sc17168-HREY/www.mywebsite.com/wp-content/plugins/wp-cache/wp-cache-phase1.php /mounted-storage/home15a/sub001/sc17168-HREY/www.mywebsite.com/wp-content/advanced-cache.php
in your server
Cannot continue… fix previous problems and retry.
I always get this error….how can I solve this?
Comment by andiz — Tuesday 2/1/2007 @ 1:42
I’m noticing that when I edit an existing post, the cache no longer is invalidated, so the changes do not show up unless I manually delete the cache from the options page. I didn’t seem to have this problem with 2.19, so I am rolling back to it.
Comment by Dave Seah — Tuesday 2/1/2007 @ 6:05
I’ve noticed since upgrading to 2.20 that anyone who comments to my articles has to wait for the current cache to expire before they can actually view what they’ve posted. Is there some way to fix that?
Comment by Christopher B. Wright — Tuesday 2/1/2007 @ 16:22
Ricardo… Cuando actualice a esta nueva version el cache dejo de regenerar la pagina principal despues de publicar un nuevo post, por lo que tengo que limpiar el cache manualmente para que aparesca en la portada ¿un Bug o un Error mio?. Gracias por tu ayuda y por este excelente plug-in!
Comment by fire! — Wednesday 3/1/2007 @ 7:12
Hi
Thanks for the great work. I now have a problem with this version that new comments don’t appear on a cached page until the cache expires.
Thanks
EB
Comment by Everton Blair — Wednesday 3/1/2007 @ 19:14
I have the same problem. When I post new comments, the cache page will not be replaced immediately.
Comment by derjohng — Thursday 4/1/2007 @ 9:34
The problem also occurs when I post a new article. I now have to delete the cache to get new articles to appear on the homepage
Comment by Everton Blair — Thursday 4/1/2007 @ 16:24
I’m having the exact same problem as 10, 11, 12 (I think), 13, 14 and 15.
Comment by Patrick Mylund Nielsen — Thursday 4/1/2007 @ 17:04
I’m experiencing the same behaviour as the previous few posters.
Comment by Fraser — Friday 5/1/2007 @ 17:24
I’ll check it today.
Comment by gallir — Friday 5/1/2007 @ 17:57
I’m having a problem with a Wordpress 2.0.6 install and WP-Cache-2 2.0.20. Pages do not appear to be getting cached properly. The HTML files are being saved in the cache directory, but no meta files are being created for them. The cached pages are never served.
I’m running on Apache 2.2 and PHP 5.2.0 under FastCGI, if that’s important.
Cheers.
Comment by ian — Sunday 7/1/2007 @ 1:56
Same issue of the cache not invalidating as all of the above. Ricardo, if I can do anything to help diagnose then please fell free to contact me.
Comment by James Turnbull — Sunday 7/1/2007 @ 13:28
I’ll install WP 2.0.6 today and check debug what’s going on, I suspect of the spam checking patch.
Comment by gallir — Sunday 7/1/2007 @ 13:33
Cound you try http://mnm.uib.es/gallir/wp-content/wp-cache-2-0-20a.zip to see if the preblem persists?
(I just commented out the code that checks the comment status to see if this is the problem).
Comment by gallir — Sunday 7/1/2007 @ 13:39
I’ve installed 2.0.20a, and then edited and saved my most recent post. However, on a fresh browser with no cache or cookies I only see the previous most recent post :-/
Comment by James Turnbull — Sunday 7/1/2007 @ 14:02
Please, try http://mnm.uib.es/gallir/wp-content/wp-cache-2-0-20b.zip (i think I found the stupid bug).
Comment by gallir — Sunday 7/1/2007 @ 16:17
New wp-cache 2.0.21
I just released wp-cache version 2.0.21. This versión fixes a very stupid bug introduce by a previous patch (a missing “global” declaration for $blog_id.
The wp-cache-2 page.
Installation note: Simply uncompress the zip file and overwrit…
Trackback by Ricardo Galli, de software libre — Sunday 7/1/2007 @ 16:52
Ricardo,
Thanks. I’ve tried 2.0.21, but I still seem to have the same problem with the front page’s cache not being removed when editing the most recent post. Is there still something up?
Comment by James Turnbull — Sunday 7/1/2007 @ 20:59
#26 James I tested this case and in fact I just did it again with WP 2.0.6 and it works nice. Check wether is the browser cache or WP-cache
Comment by gallir — Sunday 7/1/2007 @ 21:35
I’ve installed the new version and the cache is still having problems
Comment by Everton Blair — Tuesday 9/1/2007 @ 2:05
Please, can you provide more info? I cannot find any problems with updateing/refreshing page (with both. WP 2.0.6 and WP1.5, on Apache 1.3 and PHP4 and PHP5).
BTW, check the version is 2.0.21.
Comment by gallir — Tuesday 9/1/2007 @ 2:13
#27: Just to say that yes, everything is working really well with version 2.0.21. Many thanks for fixing the issues so quickly!
Comment by James Turnbull — Thursday 11/1/2007 @ 8:48
I’m getting periodic “500 Internal Server Error” pages when I have wp-cache enabled. I’m using the most recent version with Word Press 2.5.
Comment by mj — Friday 12/1/2007 @ 8:09
Good day - love the WP-Cache concept, but having an ugly problem. I downloaded and installed for the first time today (v2.1). I did the auto-configure, not the manual. I have changed nothing else on my blog. Haven’t posted or approved a comment since install either.
Every other (2nd, 4th, 6th) time I load a blog page I get the “500 Internal Server Error” instead of the page. A reload or opening in a new tab (Firefox 2.0.0.1) serves the page correctly, then bad, then good, etc. Same symptoms in IE 6.
Any ideas?
I notice that my home page is listed twice (with different stats) on the WP-Cache Options page under cached pages list. Does this mean anything? I have tried deleting one, then both of these, but the 500 Error problem persists.
For now I’ve disabled WP-Cache and cleared the cached pages and the problem has gone away.
I’d really like to use WP-Cache, if I can figure out what I’m doing wrong or if there’s a fix coming.
Thanks for any help!
Comment by Brian — Thursday 8/2/2007 @ 18:35