WordPress “Don’t Nag Me About Upgrades” Hack

Do you have a WordPress blog that, every time you log on to it you get this big honking notice that you need to upgrade? Have you pretty much decided that you’ll deal with an upgrade when you’re darn good and ready and don’t want to be nagged about it?

That’s pretty much where I’m sitting. Oh, I am not a hamster, I know full well that there is already a “Disable WordPress Core Update” plugin, It just occurred to me that there was an elegant, simple fix for the whole thing.

Tell WordPress that it’s version number is higher than the “new” versions. This way you can upgrade when you’re good and ready, don’t have to look at the nag stripe on the admin screens all the time.

Before I go any farther, be warned that this hack is NOT supported by anyone, especially WordPress developers. Whom I suspect will wholeheartedly frown on the very idea. I don’t even guarantee that it’s going to work for you at all. It did for me but your mileage may vary.

That said and my thoroughly Non-Hamster butt covered just in case, here’s what you need to do:

Start your favorite FTP utility (I use FileZilla) and connect to your blog’s webspace. When you look at the directory there will be a bunch of files and at least three directories. You need to open the directory “wp-includes”. In that directory is a file called “version.php”. Download that file and open it in Notepad or your favorite plain text editor.

Look for this line:
$wp_version = ‘2.5.1’;

Change the number to whatever you want and save the file, and upload it back to the server, overwriting the old copy.

If, for example, you changed it to $wp_version = ‘82.5’;, then when you log into your dashboard, the version number reported at the bottom of the page will be “Version 82.5”

The way this works is by changing the version number that WordPress reports even to itself, you won’t have to look at upgrade nag notices anymore. Of course, when you DO finally upgrade, this hack will be overwritten by the new version.

Remember, I have no doubt that WordPress developers and such will not approve of or even like this hack, definitely won’t support it. In fact, they may well not be thrilled with me for publishing it but I figure what the heck. I’m tired of MY blog nagging me to upgrade and I’ll get around to it when I’m bloody well good and ready.

[Tags]WordPress, WordPress hack, version, version hack, WordPress version hack, stop nagging, no nag hack, no nags[/tags]

2 Replies to “WordPress “Don’t Nag Me About Upgrades” Hack”

  1. Ack! The updates are often security related, and it is generally a Good Thing to update. I hope your readers take that to heart!

    Also, upgrading really isn’t that bad if you set up subversion. My upgrade process goes a little like this: ‘ssh mybox.com cd /path/to/wordpress; svn update’. One-liner upgrades are yummy 🙂

  2. It’s true that they usually are involved with security but sometimes there’s other stuff in there that isn’t so nice.

    For example I consider myself to have been burned on the release of 2.5.x because of all the changes in the admin panels. Therefore before I upgrade any more blogs to 2.5.x I am waiting for either someone to write a plugin that will give me the same look, feel and overall functionality of 2.3.3 … or the time it will take for me to become familiar enough with PHP in general and WordPress source in particular so that I can fix the thing myself. I’m not holding my breath for the second option… I don’t have that kind of time these days.

    For example, how about we lose that bloody flash uploader!!! I hate how that thing doesn’t work most of the time and I hate the way it puts stuff into posts. I now have to re-code EVERY image I use because that %@^^@^ thing isn’t doing it the same way anymore. It’s also using CSS definitions that I don’t have and frankly resent the idea that I’ll probably have to figure out how to code them in. with 2.3.3 I had stuff that worked just fine. Fix security, sure. Add new functions? Could be good, but they need to be optional to enable or not. Do what 2.5.x did to WordPress? No! Absolutely not.

    There was no need to change the layout of the Admin panels without at least giving the users the shot to revert to something familiar without sacrificing security.

Comments are closed.