Titanium Compatibility Control – Rollback, Download & Update History

Titanium Compatibility Control – Rollback, Download & Update History combines compatibility, repository status, update history, rollback and current-version download tools. It adds compact data to Plugins plus detailed Plugin List, History, Settings and More Plugins pages. It reports declared metadata; it does not scan source code. Compatibility on the Plugins screen

• Requires WordPress shows the minimum WordPress version declared by the installed plugin.
• Tested up to shows the WordPress version through which the installed plugin declares testing.
• Requires PHP shows the minimum PHP version declared by the installed plugin.
• Green indicates the declared range covers the compared environment; deep red highlights an unmet/outdated declaration. Missing metadata is shown as unavailable instead of guessed.
• Version Check supports major/minor or exact comparison. By default, Tested up to 7.0 stays valid throughout WordPress 7.0.x and becomes outdated at 7.1.
• Manual refresh is available after plugin files are replaced by FTP, file manager or another external method.
• Download is available directly from the normal Plugins screen for authorized administrators.

A red Tested up to value does not prove that a plugin is broken. It means the author has not declared testing through the compared WordPress version. Detailed Plugin List Plugin List shows Installed, Latest, Requires WP, Tested up to, Requires PHP, Last Repository Update and Tools. Latest is not guessed without reliable WordPress update metadata. Repository status For plugins identified as WordPress.org-hosted, repository metadata is retrieved in small batches.

• Unmaintained: the Last Repository Update age reached the configured threshold. Default: 180 days.
• Removed from WordPress.org: a previously identified WordPress.org plugin is reported as not found by the WordPress.org Plugins API.
• Temporary WordPress.org/API failures are not treated as removal.
• Repository not detected: the plugin could not be reliably identified as a WordPress.org repository plugin. This does not claim it definitely is not on WordPress.org.
• External / private: the plugin explicitly declares a non-WordPress.org update source.

These are maintenance signals, not proof that a plugin is unsafe or incompatible. Update History History records successful WordPress plugin updates after Titanium is installed: plugin, previous/new version, manual/automatic type, user when available, and date. Titanium rollbacks are also recorded. The newest 250 records are retained. Direct FTP/file-manager replacement cannot be identified reliably and is not recorded as a normal update event. Rollback Rollback requires a currently identified WordPress.org plugin in its normal repository folder, update permission and permitted file modifications. Opening Rollback requests older versions from WordPress.org. Only older versions are offered. The chosen official package is installed with the core Plugin Upgrader in overwrite mode. Rollback replaces plugin files. Titanium does not intentionally change that plugin's database settings, but an older plugin version may handle its own data differently. A normal site backup and/or Download of the current installed version is recommended first. Download current installed version Download creates a ZIP from the currently installed files instead of fetching a fresh copy, so it can also work for private and premium plugins. Download is available from Plugin List and Plugins. Outside paths are rejected and symlinks are skipped. The ZIP contains plugin files only, not database or site content. Settings, Dark Mode and Site Health Settings controls the Unmaintained threshold from 1 to 3650 days, default 180. Dark Mode is per-user across Titanium and supported plugin-management screens. Site Health includes checks for declared plugin compatibility and WordPress.org plugins detected as removed or unmaintained. Refresh and multisite Compatibility data rebuilds after relevant plugin changes and newer WordPress update data. Repository metadata refreshes separately in small batches. A monthly refresh is scheduled for the first day of each month at 4:00 a.m. site time. WP-Cron must be triggered; external-cron sites must keep their WordPress cron runner configured. On multisite, management is network-level, actions require network plugin-management permissions, repository work is centralized on the main site, and subsites get no separate Titanium pages. Data storage and frontend impact Settings, metadata and history use WordPress options/network options; Dark Mode uses user meta. No custom tables, frontend assets, developer account, ads, analytics or telemetry are added.

1.0.0

• Initial release