Disabling the update nag
WordPress' core update nag is quite the useful thing, I'll usually know before it shows that there's an update, but a lot of people won't. If you don't know what I mean with core update nag, it's this thing:
The issue is that this thing doesn't only show to you, it shows to all users of your blog. Now there's a plugin that will disable this for you, but it will disable it for everyone, yourself included.
A better thing to do, in my humble opinion, is either edit that plugin to have the following code, or add this code to your themes functions.php:
if ( !current_user_can( 'edit_users' ) ) { add_action( 'init', create_function( '$a', "remove_action( 'init', 'wp_version_check' );" ), 2 ); add_filter( 'pre_option_update_core', create_function( '$a', "return null;" ) ); }
This will show the nag to you, but prevent "normal" users from seeing it.
Update, as asked by Kevin in the comments, here's how to show them to a certain username, in this case "admin":
global $user_login , $user_email; get_currentuserinfo(); if ($user_login == "admin") { add_action( 'init', create_function( '$a', "remove_action( 'init', 'wp_version_check' );" ), 2 ); add_filter( 'pre_option_update_core', create_function( '$a', "return null;" ) ); }
Related posts
- Update of Robots Meta plugin: more duplicate content issues solved
- Update to users to CSV plugin
- More WordPress SEO: robots-meta update
- Sociable & SlideShare update
- Update to Robots Meta plugin
Want more WordPress tips?
You should subscribe to my WordPress Newsletter, as you'll get a whole lot more WordPress tips and tricks there! Also, subscribe to this blog right now with RSS, or daily or weekly emails!
Cats: WordPress Tags: WordPress, WordPress Plugins
Both comments and pings are currently closed.
Now this is very handy. Thanks.
Indeed very useful. Thanks for sharing this :)
This is possibly a very bad idea. The nag is there for a reason, the correct thing to do is take the 5-10 minutes to simply update your version of wordpress. Don't be LAZY! Do it an be done with it.
@Jay: you're obviously not running 25+ blogs, or multi author blogs with more than 2 users. The email will kill you sometimes.
@Joost I run a blog with multi-authors, but it's only 2 blogs. I don't run 25+ blogs though. So my statement applies to people with less than 25 blogs. :)
What about making it show to a certain user id/name?
@Kevin: good question, updated the post!
Wow that was fast - thanks!
Liking the userid/name.
I had no idea that showed to multiple users!
Thanks a lot. That was driving me crazy. I am content to wait until Godaddy updates and pushes the automated Wordpress patches. I just don't have time to mess with installing WP so frequently on multiple blogs. Keep up the good work.
That is a nice way of handling this !
This nag has been bothering me for quite a while but just cutting it out of the code was too crude.
I have just started to use WordPress2.6.5 and this is really cool.
What about a plugin that instead of disabling the nag entirely gives you the option to 'remind me later' - and then re-nags 1 day, week or other amount later... Then it can also tell you how long you have procrastinated.
I try to update when I can - but with a regular job, I can't always get to it right away. Sometime I need to wait for the weekend.
Its about time there was a plugin for that. I use WordPress for a multi-author blog and there is one user who will email me every time she sees that message come up!
Whilst we're on the subject of 2.6.5 .. is it stable, time to wait or time to upgrade? I thought 2.7 was due out in Nov anyway?
Thanks for the post. Interesting to say the least, I have to wait until cPanel updates it's version, then update there. This would be nice so that only I know what the latest version number is.
Oh thats why I'm got notice for the update. Thanks for this tips.
Thank god we don't have to fight with these kinda things after 2.7 (auto upgrade system )
Thanks for all the comments!
@Shanker: so right.
Hey Joost,
That's a really good way, here's another one I used to make mine disappear a few months ago: http://www.rajaietalks.com/how-to-get-rid-of-the-annoying-wordpress-update-nag
Basically I made it go away by editing the CSS file.
Rajaie
Perhaps those with multiple blogs should consider using single installation such as virtual multiblog, wp mu, wp-hive plugin etc. There's no more excuse as there's only one set of codes to update. Not doing updates is simply too risky in some cases.
Thank you so much, I was not even aware anyone else could see that nag, which I hate but I guess it's useful.
Thank god we don't have to fight with these kinda things after 2.7
Great code sample. I often just use the plugin, but I prefer this method.
@Rajaie, great CSS hack. I didn't think of that either. :-)
I did not know that. Just began to pickup Wordpress again for several projects. The auto updater/ multiblog sounded good to me. A lot happened since my last WP install. :) Thanks for the fine news.