Title: Update Control
Author: George Stephanis
Published: <strong>2013 年 9 月 24 日</strong>
Last modified: 2016 年 4 月 12 日

---

搜尋外掛

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

![](https://s.w.org/plugins/geopattern-icon/update-control.svg)

# Update Control

 由 [George Stephanis](https://profiles.wordpress.org/georgestephanis/) 開發

[下載](https://downloads.wordpress.org/plugin/update-control.1.5.zip)

 * [詳細資料](https://tw.wordpress.org/plugins/update-control/#description)
 * [使用者評論](https://tw.wordpress.org/plugins/update-control/#reviews)
 *  [安裝方式](https://tw.wordpress.org/plugins/update-control/#installation)
 * [開發資訊](https://tw.wordpress.org/plugins/update-control/#developers)

 [技術支援](https://wordpress.org/support/plugin/update-control/)

## 外掛說明

This plugin adds some options to your Settings > General page, letting you specify
how auto-upgrades should function, without the need to specify constants or add 
filters by hand.

## 安裝方式

Installation using “Add New Plugin”

 1. From your Admin UI (Dashboard), use the menu to select Plugins -> Add New
 2. Search for ‘Update Control’
 3. Click the ‘Install’ button to open the plugin’s repository listing
 4. Click the ‘Install’ button

Activiation and Use

 1. Activate the plugin through the ‘Plugins’ menu in WordPress
 2. From your Admin UI (Dashboard), use the menu to select Settings -> General
 3. Configure settings, and save

## 常見問題集

  Installation Instructions

Installation using “Add New Plugin”

 1. From your Admin UI (Dashboard), use the menu to select Plugins -> Add New
 2. Search for ‘Update Control’
 3. Click the ‘Install’ button to open the plugin’s repository listing
 4. Click the ‘Install’ button

Activiation and Use

 1. Activate the plugin through the ‘Plugins’ menu in WordPress
 2. From your Admin UI (Dashboard), use the menu to select Settings -> General
 3. Configure settings, and save

  Why doesn’t this Plugin have its own settings page?

Plugin settings can be found under Settings -> General.

Not having a separate settings page is a decision based on UI philosophy. The Plugin
simply isn’t complex enough to warrant a separate settings page. Perhaps a different
admin page, such as Dashboard -> Updates, would be more appropriate; however, core
does not provide a way to hook into that page to add settings sections.

This Plugin is intentionally very simple. If you want a Plugin with more complexity
and its own settings page, you might want to check out [Automatic Updater](https://wordpress.org/plugins/automatic-updater).

  How do I use this Plugin in a multisite network?

Activate the Plugin on the main network site, and configure options via Settings-
> General.

  What do “Minor”, “Major”, and “Development” core updates mean?

 * “Minor”: minor versions will be updated automatically. Minor versions in WordPress
   are “X.Y.Z”. A minor-version update is a change from “X.Y.Z” to “X.Y.Z+1”. This
   is the default core behavior.
 * “Major”: major versions will be updated automatically. Major versiosn in WordPress
   are “X.Y”. A major-version update is a change from “X.Y” to “X.Y+1”.
 * “Development”: development versions will be updated automatically. Development
   versions, also referred to as “bleeding-edge nightlies”, are daily updates in
   the current development branch. While usually quite stable, this option should
   be used only if you’re comfortable with using potentially unstable, development
   software. This option should only be used on production sites if your name is“
   Otto”.

  Which setting should I use?

Core Updates:

 * If you want minor versions to update automatically (default WordPress core behavior):
   leave “Automatic Core Update Level?” set to “Minor”.
 * If you want both minor and major versions to update automatically: set “Automatic
   Core Update Level?” to “Major”.
 * If you want bleeding-edge nightlies: set “Automatic Core Update Level?” to “Development”
 * If you want to disable core updates altogether: set “Automatic Updates Enabled?”
   to “no”

Plugin/Theme/Translation Updates:

 * If you disable updates, Plugin, Theme, and Translation updates will also be disabled
 * Separately enable Plugin, Theme, and Translation updates via the appropriate 
   checkboxes

  What are advanced settings?

Enable updates for VCS installations

 * By default, WordPress will check for the existence of VCS (version control system)
   files, and if any are found, will not perform automatic updates. Selecting “Enable
   updates for VCS installations?” will force WordPress to bypass this check, and
   perform updates regardless of the existence of VCS files.

Update Result Emails

 * By default, WordPress sends an update result email for successful, failed, and
   critically failed updates
 * Selectively disable emails for each result type via the appropriate checkboxes

Debug Email

 * This email is sent by default when an update is performed on a site that is running
   a development version of WordPress. Enable this option to override the debug 
   email, and prevent it from being sent.

  Why don’t automatic updates happen right away?

You may find that you receive an update notification, but automatic updates don’t
happen right away. That’s okay! WordPress performs automatic updates according to
timing based on certain transient values, and it is possible for the update check
to happen some time before the automatic update routine executes. The Plugin doesn’t
modify the timing of the automatic update routine; rather, it just tells WordPress
which update types are enabled.

Also, core now has two separate types of updates: manual updates and automatic updates.
When you see the manual upgrade notice, WordPress has received the manual update
offer, but has not yet received the automatic update offer. The two offers are fetched
based on two different transients, and do not happen at the same time. Automatic
core updates are served on a staggered rollout, which means that it may take up 
to 36 hours for the automatic update to execute after receiving the manual upgrade
notice. For Plugins and Themes, you should normally see the automatic update routine
execute within 12 hours of receiving the manual upgrade notice.

## 使用者評論

![](https://secure.gravatar.com/avatar/307bc1e86722fd1b9eb221a6c4b8863fd1f14550ca030430b0f66f9f1e22a163?
s=60&d=retro&r=g)

### 󠀁[Doesn’t work at all](https://wordpress.org/support/topic/doesnt-work-at-all-40/)󠁿

 [Pietro](https://profiles.wordpress.org/patm2g/) 2016 年 10 月 28 日 1 則留言

None plugin neither wordpress minor or major release was started by this plugin,
despite it ru by 6 months in my website.

![](https://secure.gravatar.com/avatar/a2e32b6b9b25a39e48be8c1e3230524019ee82ebb290a3b42b5634b1899d4c03?
s=60&d=retro&r=g)

### 󠀁[Works great.](https://wordpress.org/support/topic/works-great-3607/)󠁿

 [pmoffett](https://profiles.wordpress.org/pmoffett/) 2017 年 2 月 8 日

![](https://secure.gravatar.com/avatar/8665de9d64b89c443dd37c03c7def3788f5c5fab2b696bc81bb4705d0fa238f9?
s=60&d=retro&r=g)

### 󠀁[Cool](https://wordpress.org/support/topic/cool-513/)󠁿

 [Matthew](https://profiles.wordpress.org/kidsguide/) 2017 年 2 月 7 日

Awesome

 [ 閱讀全部 19 則使用者評論 ](https://wordpress.org/support/plugin/update-control/reviews/)

## 參與者及開發者

以下人員參與了開源軟體〈Update Control〉的開發相關工作。

參與者

 *   [ George Stephanis ](https://profiles.wordpress.org/georgestephanis/)
 *   [ Chip Bennett ](https://profiles.wordpress.org/chipbennett/)

[將〈Update Control〉外掛本地化為台灣繁體中文版](https://translate.wordpress.org/projects/wp-plugins/update-control)

### 對開發相關資訊感興趣？

任何人均可[瀏覽程式碼](https://plugins.trac.wordpress.org/browser/update-control/)、
查看 [SVN 存放庫](https://plugins.svn.wordpress.org/update-control/)，或透過 [RSS](https://plugins.trac.wordpress.org/log/update-control/?limit=100&mode=stop_on_copy&format=rss)
訂閱[開發記錄](https://plugins.trac.wordpress.org/log/update-control/)。

## 變更記錄

#### 1.5

 * Bugfix. Fixes filtering of debug email sent when using a development version 
   of WordPress.

#### 1.4

 * Bugfix. Fixes disabling all automatic updates not working.

#### 1.3.2

 * Bugfix. Correct handling of VCS check filter.

#### 1.3.1

 * Bugfix. Correct filter name.

#### 1.3

 * Maintenance Update. Add multisite awareness, more FAQs.

#### 1.2.1

 * Make Advanced Settings UI a bit more intuitive.

#### 1.2

 * Feature Update. Add advanced options toggle, and options for VCS check disabling
   and debug email.

#### 1.1.3

 * Bugfix. Declare static functions to eliminate e-strict PHP notice.

#### 1.1.2

 * Bugfix. Use selected() instead of checked() in select form fields.

#### 1.1.1

 * Bugfix. Correct variable name typo

#### 1.1

 * Update for WordPress 3.7 final, add update email options.

#### 1.0

 * Initial Release.

## 中繼資料

 *  版本 **1.5**
 *  最後更新 **9 年前**
 *  啟用安裝數 **4,000+**
 *  WordPress 版本需求 ** 3.7 或更新版本 **
 *  已測試相容的 WordPress 版本 **4.5.33**
 *  語言
 * [English (US)](https://wordpress.org/plugins/update-control/)
 * 標籤:
 * [Automatic updates](https://tw.wordpress.org/plugins/tags/automatic-updates/)
   [updates](https://tw.wordpress.org/plugins/tags/updates/)
 *  [進階檢視](https://tw.wordpress.org/plugins/update-control/advanced/)

## 評分

 4.4 星，滿分為 5 星

 *  [  14 個 5 星使用者評論     ](https://wordpress.org/support/plugin/update-control/reviews/?filter=5)
 *  [  0 個 4 星使用者評論     ](https://wordpress.org/support/plugin/update-control/reviews/?filter=4)
 *  [  1 個 3 星使用者評論     ](https://wordpress.org/support/plugin/update-control/reviews/?filter=3)
 *  [  0 個 2 星使用者評論     ](https://wordpress.org/support/plugin/update-control/reviews/?filter=2)
 *  [  2 個 1 星使用者評論     ](https://wordpress.org/support/plugin/update-control/reviews/?filter=1)

[Your review](https://wordpress.org/support/plugin/update-control/reviews/#new-post)

[查看全部使用者評論](https://wordpress.org/support/plugin/update-control/reviews/)

## 參與者

 *   [ George Stephanis ](https://profiles.wordpress.org/georgestephanis/)
 *   [ Chip Bennett ](https://profiles.wordpress.org/chipbennett/)

## 技術支援

使用者可在技術支援論壇提出意見反應或使用問題。

 [檢視技術支援論壇](https://wordpress.org/support/plugin/update-control/)