TrustBrain Update Manager

Апісанне

TrustBrain Update Manager gives you fine-grained control over how your WordPress site is updated:

Update Policies

• Set an update policy per target type (core / plugins / themes / translations)
• Policy levels: follow WordPress / auto-update patch versions only / up to minor versions / everything including major versions
• Per-plugin and per-theme policy overrides on top of the global policy; the policy decides on its own, and the Plugins / Themes lists show which policy applies to each item
• Core updates are additionally checked against the required PHP and MySQL/MariaDB versions before updating
• Branch pinning for plugins and themes distributed on WordPress.org: a patch-only or minor-only policy installs the newest release inside the allowed branch instead of skipping the update entirely

Where the list of versions comes from

Branch pinning needs to know which versions exist. For an item distributed on WordPress.org, the list comes from WordPress.org, and the chosen version is downloaded from WordPress.org and installed automatically.

For an item distributed elsewhere, the tags of the public GitHub or GitLab repository its source is published from are read instead, found from the item’s own Plugin URI / Theme URI / Update URI, the URL its update comes from, or its composer.json. The newest version within the policy is then shown on the Plugins / Themes lists, the per-item policies page and the update targets page, but it is not installed automatically: nothing is downloaded from outside WordPress.org. The offer outside the policy is not installed either, so you can get that version from the repository and upload it yourself.

GitHub access token (optional)

Without a token GitHub answers sixty requests an hour per IP address, which is shared with every other site on the same server. When that runs out the version list cannot be read, and the newest version within the policy is not shown until it recovers. A token raises the limit and is set on the Maintenance page.

The token needs no permissions at all: it is only used to read public tags. It is sent to api.github.com and to nowhere else, is stored outside the other settings, and is deleted when the plugin is uninstalled whatever else you keep.

Scheduled Updates

• Run automatic updates on your own schedule (hourly to monthly, with day-of-week / day-of-month and time settings)
• While the schedule is enabled, the WordPress native automatic updater is paused so updates never run twice
• “Check for updates” and “Run update now” buttons for immediate execution with real result feedback
• “Check for updates” asks every source again, including the version lists, so it never answers with what was true an hour ago

Update Logging

• All installs, updates, and deletions of core, plugins, themes, and translations are recorded in a dedicated log
• Filterable log screen (by type, by status, and by the individual plugin or theme) with version, update level, user, and failure messages
• When an update fails and leaves the item unusable on disk, the row says so: a failure that needs hands is not left looking like one that will simply be retried

Update Status

• One unified status page showing available core, plugin, theme, and translation updates with the auto-update decision for each item
• Every item that will not be updated says why, and an item held back by its own update source is listed with the version that exists and the requirement this site does not meet
• The time the update information was fetched is shown, so a screen describing a stale answer can be recognised as one
• A policy overview card on the native WordPress Updates screen (update-core.php)

Email Notification

• One consolidated notification email after automatic updates, replacing the individual WordPress native emails
• Several recipients and Bcc addresses, separated with commas
• Every piece of wording is editable: subject, body, the heading of each section, the guidance heading, and the format of the core and item detail lines. Clearing a field puts the bundled wording back
• Includes post-update check guidance when a major or minor version upgrade is involved

Multisite

• On a network every screen is in the network admin, and the settings apply to the whole network. WordPress runs automatic updates on the main site of a network, and the plugin and theme files are shared by every site, so there is one set of policies and one update log rather than one per site
• What an uninstall removes is set for the network, because uninstalling takes the plugin off every site at once

Third-Party Services

This plugin communicates with the following services. No personal data is sent to any of them.

WordPress.org API, to retrieve core version and requirement information, and the list of released versions of a plugin or theme hosted there. This is the same endpoint WordPress core uses.

• Endpoints: api.wordpress.org/core/version-check/1.7/ , api.wordpress.org/plugins/info/1.2/ , api.wordpress.org/themes/info/1.2/
• Terms of Service: https://wordpress.org/about/privacy/

GitHub API, to read the tags of a public repository, only for an item whose source is published there and only while a patch-only or minor-only policy is in use. The request carries the repository owner and name, and the access token when one has been set.

• Endpoint: api.github.com/repos/{owner}/{repository}/tags
• Terms of Service: https://docs.github.com/site-policy/github-terms/github-terms-of-service
• Privacy Policy: https://docs.github.com/site-policy/privacy-policies/github-privacy-statement

GitLab API, for the same purpose and under the same conditions as GitHub.

• Endpoint: gitlab.com/api/v4/projects/{project}/repository/tags
• Terms of Service: https://about.gitlab.com/terms/
• Privacy Policy: https://about.gitlab.com/privacy/