Linux 软件免费装

在这里免费安装WordPress以及其他软件

Atelixo Changelog Digest

开发者 nicognito23
更新时间 2026年10月14日 12:37
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

security changelog updates plugin updates release notes

下载

1.0.0

详情介绍:

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: 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 Premium plugins (updates that do not come from WordPress.org) are listed with "Changelog not available".

安装:

  1. Upload the plugin to /wp-content/plugins/ or install it from the Plugins screen.
  2. Activate it.
  3. Click Enable checks in the notice on the Plugins screen (or on Dashboard → Changelog Digest). There is nothing else to configure.

常见问题:

Can I trust the Security and Breaking badges?

They are hints, not guarantees. They are based on keywords and phrases (for example "security", "vulnerability", "XSS", "CVE", "breaking change", "minimum PHP version", "no longer supported") found in the changelog entries of the update. A changelog can mention a security fix without these words, or use them for something harmless. The absence of a badge never means that an update contains no security change: always read the changelog. Each badge lists the changelog lines that triggered it, with the matching keywords in bold, so you can judge for yourself. The Requires PHP badge is different: it comes from the official WordPress.org data and is reliable. It is only shown when your server's PHP version is too old for the update.

Why does a plugin show "Could not determine the exact version range"?

Changelogs have no standard format. When the version headings cannot be recognized (or the changelog only links to an external page), the digest shows the latest entries instead, collapsed.

Why does a plugin show "Changelog unavailable right now"?

WordPress.org could not be reached, or returned an unexpected answer. The digest tries again later; other plugins are not affected.

Who can see the digest?

Users who can update plugins (update_plugins). If your site defines DISALLOW_FILE_MODS, nobody has this capability and the digest is not available.

My site uses DISABLE_WP_CRON

Background fetching only runs when WP-Cron runs. Without it, changelogs are fetched when you open the digest, 2 at a time: reload the page to load the next ones.

Does it work on WordPress Multisite?

Multisite is not officially supported in version 1.0 and has not been tested. Use it on single-site installations.

Why does the digest only show an "Enable checks" button?

The plugin waits for your consent before requesting anything from WordPress.org. Click Enable checks: changelogs are then fetched and the digest is displayed.

What is removed on deactivation, "Stop checks" and uninstall?

Deactivation and "Stop checks" remove the cached changelogs (a single option), the consent setting, the lock and the scheduled event; after reactivation, checks must be enabled again. Uninstall removes the same data plus each user's "notice dismissed" setting.

更新日志:

1.0.0