No Update Nag
- Author:Scott Reilly
- Version:1.3
- Last update:2012-12-18
- Compatibility:WP 2.5 – 3.5.1
- Comments:go here
- Download:[ zip ]
- Description:
Removes the WordPress update nag that appears at the top of all admin pages when a new version of WordPress is released
-
Extended Description
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 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.
Links: Plugin Homepage | Plugin Directory Page | Author Homepage
Find out more at the plugin’s WordPress Plugin Repository page.
Installation
- Unzip
no-update-nag.zipinside the/wp-content/plugins/directory (or install via the built-in WordPress plugin installer) - Activate the plugin through the ‘Plugins’ admin menu in WordPress
- Unzip
Frequently Asked Questions
Q. What is this update nag you mention?
A. In versions 2.5 and later of WordPress, your WordPress will alert you to the release of a newer version of WordPress via a yellow-background 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.”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.
Release Log
1.3
- 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)
1.2.1
- Note compatibility through WP 3.3+
- Add link to plugin directory page to readme.txt
- Update copyright date (2012)
1.2
- 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
1.1.3
- 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
1.1.2
- Note compatibility through WP 3.1+
- Add Upgrade Notice section to readme.txt
- Update copyright date (2011)
1.1.1
- Update readme.txt, including adding Changelog section
- Note compatibility through WP 2.9+, 3.0+
- Update copyright date
1.1
- 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
1.0.1
- Note compatibility with WP 2.6+ and 2.7+
- Update copyright date
- Minor tweaks to readme.txt;
1.0
- Initial release
Copyright & Disclaimer
Copyright © 2009-2012 by Scott Reilly (aka coffee2code)Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
