I’ve had it with wp-cache. Everytime I enable it on this blog bad things happen. When I released Redoable 1.1, it got posted on weblogtoolscollection.com, and on Smashing Magazine and I got mountains of traffic very quickly. I didn’t have wp-cache installed at the time, an despite receiving about 10 times more traffic than a normal day my blog was relatively ok. Despite this I followed a couple of peoples advice and installed wp-cache….you know….just in case.
Over the next week or so my site crashed a couple of times, according to Dreamhost some was my fault ( ? ) and some was due to downtime of their servers. Then things got really bad. The first week of March my site was gone. Nothing I did would bring it back. I disabled every plugin, and then I deleted them, and then I went back to the default theme….nothing, Dreamhost couldn’t help, and I was lost for ideas. After being down for almost a week I had a brain snap, “what if I delete the cache files produced by wp-cache”, and guess what….my site came back. It would appear that something was corrupted and was killing my site. Goodbye wp-cache (attempt 1).
So I de-activated wp-cache, afterall that “should” be all you need to do to stop a plugin, right? Wrong. It was still caching files (and periodically killing my blog, wtf?). Apparently you have to disable it AND then deactivate it. Stupid…oh how stupid.
Skip forward about 6 or so weeks and it was time for me to released Redoable 1.2. I did that on the night of the 25th, and about an hour after I posted the update, I thought I’d give wp-cache another go (afterall, surely my experience last time was random, and wouldn’t be repeated). I went to the wp-cache site and downloaded the lastest version, then I installed it….everythine was ok, or so it seemed.
So last night almost exactly 24 hours after I installed, activated and configured wp-cache, guess what happened. Yes, my blog shat itself again. Thing was I was asleep and didn’t find out about it until this morning, so my site was down for 8 hours, really quite pissed off about that.
Instead of the usual disable plugins one by one routine, I went straight to the cache folder thats used by wp-cache and blew the files away….guess what. My site instantly came back. Damn you wp-cache thats the last chance. I will never be using it again, I don’t care what people say about it, but quite obviously something about my site just doesn’t like it.
Wp-cache is gone, disabled, deactivated, deleted. Good riddance.
Note: Yes I deliberately linked to just about every site that was related EXCEPT the wp-cache site. It just doesn’t deserve the link. Yes I am bitter.
(24 votes, ave: 4/5)
Loading ...
A lot of people have been frustrated with WP-Cache, which worked fantastic for years but now has problems with recent versions of WordPress with built-in caching. Have you tried Super-Cache by Donncha? It’s getting rave reviews and really is the replacement for WP-Cache.
I couldn’t help but crack up over this post.
WP-Cache works fine on my site (for the moment) but it’s a trade-off in keeping that functionality while scaling back plugins that aren’t very compatible with it. The fact that I’ve been able to make 50 plugins play nice with each other to begin with though is a flipping miracle.
Great blog, by the way. This is visually one of the best themes I’ve seen.
Gwad! it works! Thanks dean! Maraming maraming salamat! ^_^ (thank you very very much)
ok, nevermind - wp-cache or no, I set the redoable option to not show the “get firefox ad” in IE and in my IE (6) it shows it - damn - of course I can hack it out of the php file, but I’d rather have it work like it is supposed to - going to sleep now, but if you know what is not working, please let me know since this theme is slickkkkkkkkkkkkkkkkkkkk
nice work
haha - I’m starting with wordpress right now and trying your template - shit keeps breaking - I don’t know why the firefox IE prompt won’t go away when using IE - I have no plugins active - except wp-cache - figured that would be the only one that wouldn’t interfere - oh and I’m with Dreamhost as well (because they’re great) - will try to wipe out the cache thing now and start from scratch
one
Brian
Yeah, I didn’t even think that maybe we are using different plugins to display Gravatars…
I’m just using the one that is provided on the Gravatar website.
http://site.gravatar.com/site/implement#section_2_2
O wait a sec, sir. (you may delete this if you want).
What version of gravatar plugin are you using? Does it affect how redoable themes handle gravatar icons? I’m using the one with the gravatar wp-cron package.
I tried to changed the folder name but still it didn’t work T_T.
Is my config correct?
In the Gravatar options:
Default gravatar image (relative to website document root path): /www/wp-content/themes/redoable/images/defaultgravatar.jpg
or
should i leave this blank?
I’m pretty confused.
I’m not sure whats causing this problem. Your blogs url should be detected automatically by the gravatar plugin so that it can find the image, but it looks like its not detecting it correctly.
The only thing that I can think of at the moment is that it could be to do with the name you have given the theme folder. I would recommend changing the name of your folder from “redo1.2” to “redoable”, it is possiblt that the “.” is causing the error, and stopping the image from being found.
Sir Dean,
I’m having trouble with my gravatar. It seems like unregistered (or non-gravatar user) comment posters on my blog create not the silhouette image (like yours) but only a gravatar icon link. How come? T_T;;
Dean,
Are you using Dreamhost’s one-click-install of WP? If so, they implement wp-cache in a strange way. You can’t upgrade the wp-cache plugin (Dreamhost has wp-cache version 2.1 with WP 2.1.3) on your own, you have to wait til they roll it out on the newest one-click-install. -Chris
@HighTechDad: Thanks for that, I didn’t remove the line you specified in you post, however I did see that same erorr, so I commented out the lines near line 84 (or 69 as in your example) which also seem to have “fixed” this.
Whoops…also, just to add, deleting the folder and deactivating won’t completely get rid of the “issue” I don’t think. I think you need to go into your wp-config.php file and actually delete the line (as I mentioned in my post). I could be wrong though…but I think I ran into this problem twice as well… -HTD
Hi Dean,
We have corresponded a few times off-blog before and I believe that the last time you had this issue, I pointed you to my blog, specifically a post where I went through the same thing! I use Dreamhost as well…but I don’t think this is a dreamhost thing.
So for others who have encountered this issue…here is my post: http://weblog.techdad.net/2007/01/25/blog-updated-to-wordpress-21/
Love the theme (obviously)! Keep up the great work!
-HTD
Even I am on Dreamhost.
I been planning to install the Wp-cache but thanks to your post I have decided not to go ahead with it. Frankly Wordpress should have this inbuilt all good CMS like Drupal, Joomla have it in the core why not wordpress. I guess they are a bit to busy building wordpress.com