More Plugins and One Offs
Posted on July 12, 2007
8 Comments
Following up from last night’s post, here’s a bit more on the WordPress Plugin front. This time, with a bit of a wrinkle…
One plugin that I didn’t mention yesterday was WP-Cache2 — a classic that’s often used to help reduce server loads and enable a a blog to handle larger amounts of traffic. I used to run it here more out of “duty” than need…
I disabled it when I started using the Popularity Contest plugin though as they didn’t play well together. Fortunately, I’m Mike figured that out and patched Popularity Contest back in May.
So now I have a “one off” version of Popularity Contest.
Just to keep it interesting, I figured I’d better make sure I had the latest WP-Cache (2.1.1 as of this writing). While perusing the comments (I always read the comments about plugins!) I noticed that Dougal had made a tweak to fix a content-type issue.
Thus, I have a “one off” of WP-Cache as well.
That’ll make it more interesting when checking for updates!
Tags: blog, plugin, Popularity-Contest, WordPress, wp-cache
Possibly Related Posts
Comments
8 Responses to “More Plugins and One Offs”
Leave a Reply
Please read the "Comments" section on the Disclaimer page. Don't use SEO terms instead of a name. That drives me nuts.
Oh, and contrary to what you might have read on some SEO forum, this is not a "Do Follow" blog.
This is exactly why I love version control systems. Particularly for bigger apps like Wordpress itself (I’ve tweaked my install a bit). When they release a new version I just run an “svn diff” and look for any clashes.
Good tip, Mike.
For the moment, I regressed both plugins and disabled wp-cache again. I was getting some odd “white page” action along with arrays being dumped into my posts (yikes!). When I have more time I’ll need to do a little more investigating to figure what’s going on.
The arrays (and other code) should be in the cached copy of the post, but should be executed and removed by WP-Cache. I’m using 2.1.1, so it shouldn’t be a version thing…
If you get a white screen again, try checking the cached page on the server (it should be under ./wp-content/cache/) sometimes an error message is dumped to the cache file.
I haven’t had a problem with the content-type, but I just remembered an issue regarding gzip. When WP-Cache is enabled you have to turn off gzip in WordPress, but there’s a hack somewhere to keep both going. I actually got it to work on my blog, yet another reason why my @$$ won’t even thinking up of upgrading WordPress overall. God only knows how many of these tweaks are all going to get fried if I take that kind of plunge. :O
Hrm. Don’t know how the popularity-contest mod will play with gzip enabled. I’ve never bothered with it since I have virtually unlimited (2.25TB/month) data transfer for my servers.
Upgrading WP definitely scares me. I’d never do it without 1. testing it on a development server first, and 2. making a backup of _everything_.
Oh yeah, I’m totally a chicken about the gzip mod for WP-Cache! I ain’t going there quite yet… I’m at 2.8TB/mo and climbing so not too worried.
As for upgrading, well, I’m a WP support forum volunteer. It helps if I know what folks are talking about!
I tend to upgrade my dev site first, play with it a bit and then if all goes well bulk update the other sites.
Weird, I have gzip, WP-Cache and the Popularity Contest (PC) all enabled. No hiccups at all. I dont think Im using the latest version of PC though.
But then again for me, that’s the problem with having all those other 75+ plugins installed. There’s no way you can do a major upgrade on a setup like that without sirens going off at a NOC somewhere. It’s like callously dealing with a nuclear bomb (oooh heck, let me just cut this red wire here….)
Ok, so far I’ve realized that Mike’s modified Popularity Contest gets a bit silly (displays the array code in the post) if WP-Cache is disabled. I can work with that.
Now for more experimenting. FOr the moment, I’m back to the non-modified WP-Cache 2.1.1. I seem to get a white page after a cached page has expired, so waiting for that to happen.
[Update] – I get a white page on my main index even before the cache expires. Shoot. Took Mike’s advice and tried to find the cached version of that page in the cache directory, but no luck. Off to check the error logs now.