內容簡介
Atelixo Changelog Digest 外掛提供一個簡易的控制台介面，讓使用者能夠快速查看所有待更新外掛的變更紀錄，避免盲目更新或延遲更新，特別是針對安全性修補。
【主要功能】
• 顯示待更新外掛的安裝版本與新版本
• 提供版本之間的變更紀錄摘要
• 標示需要更新的 PHP 版本與安全性警告
• 支援一鍵啟用或停用檢查功能
• 安全輕量，不會自動更新任何內容
外掛標籤
開發者團隊
原文外掛簡介
When plugin updates are available, WordPress does not show what they contain unless you open each changelog one by one. So updates are either applied blindly or postponed, security fixes included.
Atelixo Changelog Digest adds a Dashboard → Changelog Digest screen that lists every pending plugin update with:
the installed version and the new version;
only the changelog entries between those two versions (long ranges show their start, with the rest behind a “Show full changelog” toggle);
a red Requires PHP badge, from the official WordPress.org data, when your server runs an older PHP version than the update requires;
Security and Breaking / Important badges based on keywords found in those entries, each followed by the lines that triggered it, keywords in bold;
a link to the plugin’s page on WordPress.org.
Plugins with a security badge or an incompatible PHP requirement are listed first.
Your consent first
After activation, nothing is requested from WordPress.org. A notice on the Plugins screen (only there) explains what will be sent and offers an Enable checks button; each user can dismiss it, and the digest screen offers the same button. The notice never appears elsewhere in the admin and disappears for good once checks are enabled. Once enabled, the plugin’s row offers Stop checks, which deletes the cached changelogs and stops all requests until checks are enabled again. Deactivating the plugin does the same.
Read-only
The digest never updates anything. Use the regular Updates or Plugins screen to update.
Safe and lightweight
Changelogs come from WordPress.org as HTML and are always cleaned before display: scripts, event handlers, styles and non-http(s) links are removed, and only basic formatting is kept.
Changelogs are fetched in the background after WordPress finds new updates, and cached per plugin version. Nothing is requested from WordPress.org on the front end or on other admin screens.
No JavaScript, and only a few lines of CSS on the digest screen.
Premium plugins (updates that do not come from WordPress.org) are listed with “Changelog not available”.
External services
This plugin connects to the WordPress.org Plugins API (https://api.wordpress.org/plugins/info/1.2/) to read the changelog of plugins that have a pending update.
Consent: no request is made and no background task is scheduled until an administrator (a user who can update plugins) clicks Enable checks, in the notice shown on the Plugins screen after activation or on the Changelog Digest screen. Stop checks on the plugin’s row (or deactivating the plugin) withdraws this consent: the scheduled task is removed and cached changelogs are deleted.
What is sent: the slug (folder name) of each plugin with a pending update from WordPress.org, one request per plugin, along with the standard WordPress HTTP headers (WordPress version and site URL in the user agent). No personal data is sent.
When: only while checks are enabled: right after Enable checks, in the background via WP-Cron after WordPress has checked for plugin updates, and when an administrator opens the Changelog Digest screen and some changelogs are not cached yet (at most 2 requests per page view). Each changelog is cached for 7 days for a given version. Never on the front end or on other admin screens.
Not sent: plugins without a pending update, and updates that do not come from WordPress.org.
This service is provided by WordPress.org: WordPress.org privacy policy.
