內容簡介
此 WordPress 外掛可啟用 WordPress 核心、佈景主題、外掛程式和翻譯的自動更新功能。WordPress 核心的版本控制可增加自動更新的安全性。
功能：
- 自動更新 WordPress 核心
- 自動更新佈景主題、外掛程式和翻譯
- 設定自動更新的排程
- 停用每個佈景主題和外掛程式的自動更新
- 紀錄更新歷史
- 更新通知
重要說明：在更新前，請先備份您的資料庫和檔案。
自動更新流程：
首先，我們會建立一個自動更新流程，決定 WordPress 自動更新的政策。您可以從以下五種 WordPress 核心的自動更新方式中選擇：
- 小型版本更新（建議）
- 大型版本更新
- 僅小型版本更新
- 前一代版本更新
- 手動更新
小型版本更新（建議）會啟用小型的更新。對於 WordPress 的安全性更新，這是預設的行為。版本號碼的變化如下：從 4.8 更新至 4.8.1、4.8.2…等。
大型版本更新將啟用大型的更新。版本號碼的變化如下：從 4.7 更新至 4.8、4.9…等。
僅小型版本更新啟用大型的更新和除了 x.y.0 版本以外的小型更新。使用已修正安全性問題的 WordPress 核心版本（例如 x.y.1 或更晚版本）。不會自動更新最新的大型版本 x.y.0。版本號碼的變化如下：從 4.7.z 更新至 4.8.z、4.9.z…等；跳過 4.7.0、4.8.0、4.9.0…等。
前一代版本更新啟用大型的更新和除了最新大型版本以外的小型更新。如果已安裝 WordPress 核心版本為 4.6.z，且最新的 WordPress 核心版本釋出為 4.8.0，則自動更新至版本 4.7.z。它將自動更新至上一代 WordPress 核心版本，其中可能有安全性修復。
手動更新停用自動更新。您可以在控制台更新畫面上手動更新 WordPress 核心。佈景主題、外掛程式和翻譯可用自動更新或手動更新，同時也可以停用每個佈景主題和外掛程式的自動更新。
排程自動更新：接下來，我們將為自動更新設定排程。更新間隔可以從以下四個中選擇：
- 每天兩次（12 小時的間隔）
- 每天
- 每週
- 每月
您也可以設定更新日期的日期、星期幾、小時和分鐘。在自動更新時，將自動更新 WordPress 核心、佈景主題、外掛程式和翻譯。
測試矩陣：為了運作相容性，請參閱以下 Github Actions 中 PHP 版本與 WordPress 版本的運作矩陣。
貢獻：可以透過在 Github 的問題追蹤器提交小型的補丁和錯誤報告，亦可透過複製 Github 上的專案進行改進，並提交拉取請求。
外掛連結：WP Auto Updater - https://wordpress.org/plugins/wp-auto-updater/
外掛標籤
開發者團隊
📦 歷史版本下載
原文外掛簡介
WP Auto Updater plugin enables automatic updates of WordPress Core, Themes, Plugins and Translations. Version control of WordPress Core makes automatic update more safely.
Features
Automatically update WordPress Core
Automatically updates Themes, Plugins and Translations
Set up a schedule automatic updates
Disable automatic updating of each Themes and Plugins
Record update history
Update notification
Important: before updating, please back up your database and files.
Auto Update Scenario
First of all, we will make an Auto Update Scenario which decide the policy of WordPress automatic updates.
You can choose from the following five automatic updates of WordPress Core.
Minor Version Update
Major Version Update
Minor Only Version Update
Previous Generation Version Update
Manual Update
Minor Version Update
Minor Version Update enable minor updates. Minor updates is default behavior in WordPress for security updates. The transition of the version number is as follows: update from 4.8 to 4.8.1, 4.8.2 …
Major Version Update
Major Version Update enable major updates. The transition of the version number is as follows: update from 4.7 to 4.8, 4.9 …
Minor Only Version Update
Minor Only Version Update enable major updates and minor updates except version x.y.0. It make sense to take a “skip” approach to avoid introducing new vulnerabilities into the latest major version release.
Update the WordPress Core version (eg. x.y.1 or later) with security fixed. Not automatically update the latest major version of x.y.0. The transition of the version number is as follows: update from 4.7.z to 4.8.z, 4.9.z … skiped 4.7.0, 4.8.0, 4.9.0 …
Previous Generation Version Update
Previous Generation Version Update enable major updates and minor updates except the latest major version. It make sense to take a “wait and see” approach to ensure the latest major version release is stable before.
With the installed WordPress Core version as 4.6.z. If the latest WordPress Core version released to 4.8.0, automatically update it to version 4.7.z. It will be always automatically updated to the previous generation WordPress Core version with probably security fixed.
Manual Update
Manual Update disable automatic updates. You update WordPress Core manually on the Dashboard Updates Screen.
Automatic updates and manual updates are available for themes, plugins and Translations.
It is also possible to disable automatic updating of each Themes and Plugins.
Scheduled automatic updates
Next we will set up a schedule for automatic updates.
The update interval can be selected from the following four.
Twice Daily (12 hours interval)
Daily
Weekly
Monthly
You can also set the day, the day of the week, the hour and the minute of the Update Date.
At the time of automatic update, Automatically updates WordPress Core, Themes, Plugins and Translations to be updated.
Support
If you have any trouble, you can use the forums or report bugs.
Forum: https://wordpress.org/support/plugin/wp-auto-updater/
Issues: https://github.com/thingsym/wp-auto-updater/issues
Contribution
Small patches and bug reports can be submitted a issue tracker in Github. Forking on Github is another good way. You can send a pull request.
Translating a plugin takes a lot of time, effort, and patience. I really appreciate the hard work from these contributors.
If you have created or updated your own language pack, you can send gettext PO and MO files to author. I can bundle it into plugin.
VCS – GitHub
Homepage – WordPress Plugin
Translate WP Auto Updater into your language.
You can also contribute by answering issues on the forums.
Forum: https://wordpress.org/support/plugin/wp-auto-updater/
Issues: https://github.com/thingsym/wp-auto-updater/issues
Contribute guidlines
If you would like to contribute, here are some notes and guidlines.
All development happens on the develop branch, so it is always the most up-to-date
The master branch only contains tagged releases
If you are going to be submitting a pull request, please submit your pull request to the develop branch
See about forking and pull requests
Test Matrix
For operation compatibility between PHP version and WordPress version, see below Github Actions.
