這個外掛並未在最新的 3 個 WordPress 主要版本上進行測試。開發者可能不再對這個外掛進行維護或提供技術支援,並可能會與更新版本的 WordPress 產生使用上的相容性問題。

No Update Nag

描述

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!

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.

Links: Plugin Homepage | Plugin Directory Page | GitHub | Author Homepage

螢幕截圖

  • A screenshot of an admin page showing the update nag for a new version of WordPress.

安裝

  1. Install via the built-in WordPress plugin installer. Or install the plugin code inside the plugins directory for your site (typically /wp-content/plugins/).
  2. Activate the plugin through the ‘Plugins’ admin menu in WordPress

常見問題

What is this update nag?

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.

Why would I want to remove the update nag about new releases of WordPress?

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.

How will I know WordPress has been updated if the nag doesn’t appear?

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.

So I should ignore the update nag and continue using my older version of WordPress?

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 include temporarily delaying an update to the latest version.

Does this plugin include unit tests?

Yes.

評價

2018年12月20日
I don't want to be reminded every page I need to update but I want to know I need an update and this gets rid of the nag. Thanks!
閱讀全部2個評價

貢獻者及開發者

“No Update Nag” 是一個開源的軟體。以下的人對這個外掛作出了貢獻。

貢獻者

將 No Update Nag 外掛本地化為台灣繁體中文版。

對開發相關資訊感興趣?

任何人均可瀏覽程式碼、查看 SVN 存放庫,或透過 RSS 訂閱開發記錄

修改日誌

1.4.11 (2021-10-03)

  • Change: Note compatibility through WP 5.8+
  • Change: Improve installation instruction in readme.txt
  • Change: Minor text tweaks in readme.txt
  • Unit tests:
    • Change: Restructure unit test directories
      • Change: Move phpunit/ into tests/phpunit/
      • Change: Move phpunit/bin/ into tests/
    • Change: Remove ‘test-‘ prefix from unit test file
    • Change: In bootstrap, store path to plugin file constant
    • Change: In bootstrap, add backcompat for PHPUnit pre-v6.0

1.4.10 (2021-04-19)

  • Change: Note compatibility through WP 5.7+
  • Change: Update copyright date (2021)

1.4.9 (2020-08-28)

  • Change: Restructure unit test file structure
    • New: Create new subdirectory phpunit/ to house all files related to unit testing
    • Change: Move bin/ to phpunit/bin/
    • Change: Move tests/bootstrap.php to phpunit/
    • Change: Move tests/ to phpunit/tests/
    • Change: Rename phpunit.xml to phpunit.xml.dist per best practices
  • Change: Note compatibility through WP 5.5+
  • Change: Add an FAQ item

Full changelog is available in CHANGELOG.md.