- Author:Scott Reilly
- First released:2009-06-12
- Last update:2015-02-26
- Compatibility:WP 2.5 – 4.1.5
- Download:[ zip ]
Removes the WordPress update nag that appears at the top of all admin pages when a new version of WordPress is released
This plugin removes the WordPress update nag that appears at the top of all admin pages when a new version of WordPress is released
Tired of WordPress nagging you about a new release? Maybe you already know about it and want to hold off on an update and would rather not see the update nag on every admin page you visit. Activate this plugin and be bothered no more!
Of course, the status of your version of WordPress (be it current or out-of-date) is still reflected in the footer of your admin pages and in the update count link in the admin bar.
And certainly, of course, I don’t advocate completely ignoring the fact that updates often contain fixes for critical bugs or exploits. However, there are various other means of learning about updates; and once known, not everyone is able or willing to update immediately.
Find out more at the plugin’s WordPress Plugin Repository page.
Click to see full-size image.
/wp-content/plugins/directory (or install via the built-in WordPress plugin installer)
- Activate the plugin through the ‘Plugins’ admin menu in WordPress
Frequently Asked Questions
Q. What is this update nag?
A. In versions 2.5 and later of WordPress, your WordPress will alert you to the release of a newer version of WordPress via an update notice at the top of every admin page. WordPress 2.5 and later reports “WordPress X.X is available! Please update now!” or “WordPress X.X is available! Please notify the site administrator.” See the screenshot for an example.
Q. Why would I want to remove the update nag about new releases of WordPress?
A. Maybe you know about the newer WordPress release (either from the nag, news, etc) and don’t want to be constantly reminded by your current WordPress install (not everyone can or wants to upgrade to the newest version immediately). Also, you’d like to recover that much real estate on the page for something of more interest to you.
Q. How will I know WordPress has been updated if the nag doesn’t appear?
A. Within the context of your WordPress admin, the footer of your admin pages will reflect that status of your version of WordPress (be it current or out-of-date). And if you are tracking WordPress progress at all (i.e. blogs, forums, your WordPress dashboard) then you likely don’t need to be made aware of new releases anyhow since you’ll likely already know about them.
Q. So I should ignore the update nag and continue using my older version of WordPress?
A. Most certainly not. The latest version of WordPress will contain the latest security and bug fixes, as well as new features. Backwards compatibility is of paramount importance to the project so in most cases you should be safe to upgrade (especially for minor releases). However, some people in special circumstances manage their sites in different ways for different reasons, which may preclude delaying an update to the latest version.
- Reformat plugin header
- Change documentation links to wp.org to be https
- Note compatibility through WP 4.1+
- Update copyright date (2015)
- Add plugin icon
- Remove nag from network_admin_notices
- Minor documentation improvements
- Note compatibility through WP 3.8+
- Update copyright date (2014)
- Change donate link
- Add assets directory to plugin repository checkout
- Add screenshot
- Add banner
- Add check to prevent execution of code if file is directly accessed
- Re-license as GPLv2 or later (from X11)
- Add ‘License’ and ‘License URI’ header tags to readme.txt and plugin file
- Remove ending PHP close tag
- Minor code reformatting (spacing)
- Note compatibility through WP 3.5+
- Update copyright date (2013)
- Note compatibility through WP 3.3+
- Add link to plugin directory page to readme.txt
- Update copyright date (2012)
- Add function c2c_no_update_nag()
- Hook c2c_no_update_nag() into ‘admin_init’ action rather than use create_function() (as was done prior to v1.1)
- Note compatibility through WP 3.2+
- Minor code formatting changes (spacing)
- Fix plugin homepage and author links in description in readme.txt
- Remove header documentation from plugin file (all that info and more are in the readme.txt)
- Add package info to top of plugin file
- Add link to plugin homepage to description in readme.txt
- Note compatibility through WP 3.1+
- Add Upgrade Notice section to readme.txt
- Update copyright date (2011)
- Update readme.txt, including adding Changelog section
- Note compatibility through WP 2.9+, 3.0+
- Update copyright date
- Remove the sole function no_update_nag() and embed its functionality directly in add_action() call via create_function()
- Hook ‘admin_init’ instead of ‘admin_head’, which causes a drop in support for WP2.3
- Note compatibility with WP 2.8+
- Tweak readme.txt
- Note compatibility with WP 2.6+ and 2.7+
- Update copyright date
- Minor tweaks to readme.txt;
- Initial release
Copyright & DisclaimerCopyright © 2009-2015 by Scott Reilly (aka coffee2code)
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
Discussion / Support
Have any questions, comments, or suggestions? Please provide them via the plugin’s WordPress.org support forum. I’ll do my best to reply in a timely fashion and help as best I can.
Unfortunately, I cannot provide guaranteed support, nor do I provide support via any other means.
Was this plugin useful useful to you? Consider giving it a rating. If you’re inclined to give it a poor rating, please first post to the support forum to give me a chance to address or explain the situation.