Title: Titanium Compatibility Control – Rollback, Download & Update History Author: Admin Plugins Published: ސެޕްޓެމްބަރ 5, 2026 Last modified: ސެޕްޓެމްބަރ 5, 2026 --- Search plugins ![](https://ps.w.org/titanium-compatibility-control/assets/banner-772x250.png?rev =3682402) ![](https://ps.w.org/titanium-compatibility-control/assets/icon-256x256.png?rev= 3682402) # Titanium Compatibility Control – Rollback, Download & Update History By [Admin Plugins](https://profiles.wordpress.org/aplugins/) [Download](https://downloads.wordpress.org/plugin/titanium-compatibility-control.1.0.0.zip) * [Details](https://dv.wordpress.org/plugins/titanium-compatibility-control/#description) * [Reviews](https://dv.wordpress.org/plugins/titanium-compatibility-control/#reviews) * [Installation](https://dv.wordpress.org/plugins/titanium-compatibility-control/#installation) * [Development](https://dv.wordpress.org/plugins/titanium-compatibility-control/#developers) [Support](https://wordpress.org/support/plugin/titanium-compatibility-control/) ## Description 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. ### External Services Titanium Compatibility Control – Rollback, Download & Update History uses WordPress. org services for compatibility, repository-maintenance and rollback metadata. No external account or API key is required. The plugin uses: * `wp_update_plugins()` during manual refreshes and the scheduled monthly refresh. WordPress sends its standard plugin-update request to `api.wordpress.org`, including installed/active plugin information, installed translation data, site locales, WordPress version and the site home URL in the User-Agent. * `plugins_api()` to retrieve Last Repository Update and other required repository metadata for identified WordPress.org plugins. Requests run in small batches after relevant changes, when data is missing and during scheduled refreshes. WordPress includes its version and the site home URL in the request User-Agent. * `plugins_api()` when an administrator opens Rollback, to retrieve older versions and official `downloads.wordpress.org` package URLs. The chosen package is downloaded only after explicit confirmation; the WordPress HTTP request User-Agent includes the WordPress version and site home URL. It does not send post/user content, administrator email addresses or its own telemetry identifiers to WordPress.org. Service: https://api.wordpress.org/ WordPress.org Downloads: https://downloads. wordpress.org/ WordPress.org Plugin Directory: https://wordpress.org/plugins/ WordPress. org Privacy Policy: https://wordpress.org/about/privacy/ ### Privacy The plugin has no telemetry, ads, analytics or developer cloud account. Compatibility, repository and history metadata remain in WordPress. Remote communication is limited to the WordPress.org services above. Update History may store the local WordPress user ID for a manual update so the administrator can be shown in History. It stays in the site’s database. ## Screenshots [⌊Compatibility information displayed directly in plugin rows, with supported WordPress and PHP versions and clear warnings for incompatible versions.⌉⌊Compatibility information displayed directly in plugin rows, with supported WordPress and PHP versions and clear warnings for incompatible versions.⌉[ Compatibility information displayed directly in plugin rows, with supported WordPress and PHP versions and clear warnings for incompatible versions. [⌊WordPress Plugins screen in light mode, showing compatibility ranges for installed plugins and the compatibility data refresh controls.⌉⌊WordPress Plugins screen in light mode, showing compatibility ranges for installed plugins and the compatibility data refresh controls.⌉[ WordPress Plugins screen in light mode, showing compatibility ranges for installed plugins and the compatibility data refresh controls. [⌊WordPress Plugins screen in dark mode, with compatibility ranges integrated directly into the standard plugin list.⌉⌊WordPress Plugins screen in dark mode, with compatibility ranges integrated directly into the standard plugin list.⌉[ WordPress Plugins screen in dark mode, with compatibility ranges integrated directly into the standard plugin list. [⌊Compatibility status for Titanium plugins, clearly highlighting when the current WordPress version falls outside a plugin's tested range.⌉⌊Compatibility status for Titanium plugins, clearly highlighting when the current WordPress version falls outside a plugin's tested range.⌉[ Compatibility status for Titanium plugins, clearly highlighting when the current WordPress version falls outside a plugin’s tested range. [⌊Compatibility Control dashboard showing installed and latest versions, WordPress and PHP requirements, repository update status, and download and rollback tools.⌉⌊ Compatibility Control dashboard showing installed and latest versions, WordPress and PHP requirements, repository update status, and download and rollback tools.⌉[ Compatibility Control dashboard showing installed and latest versions, WordPress and PHP requirements, repository update status, and download and rollback tools. ## Installation 1. Upload the `titanium-compatibility-control` folder to `/wp-content/plugins/`, or install it through WordPress when available in the Plugin Directory. 2. Activate the plugin. On multisite, activate it for the network. 3. Open Plugins for compact compatibility information and Download. 4. Open Titanium Compatibility > Plugin List for the detailed table, repository status, Download and Rollback. 5. Use History for recorded plugin updates and Settings for the Unmaintained threshold. ## FAQ ### Does Titanium scan plugin PHP source code? No. It reports declared plugin and WordPress.org metadata; it does not claim to prove source-code compatibility. ### What is the difference between Last Repository Update and Update History? Last Repository Update is the repository date reported by WordPress.org. Update History records version changes that occurred on this WordPress installation after Titanium was installed. ### What does Repository not detected mean? Titanium could not reliably identify the installed plugin as a WordPress.org repository plugin. This is intentionally different from Removed from WordPress.org. ### Does Unmaintained mean unsafe? No. It only means the repository update age reached your configured threshold. ### Can every plugin be rolled back? No. Rollback is limited to eligible WordPress.org plugins installed in their normal repository folder. Private, custom, removed or unidentified plugins do not receive WordPress.org rollback versions. ### Can private or premium plugins be downloaded? Yes, when their installed files are inside the normal WordPress plugins directory and can be packaged safely. Download contains files only; it is not a database or full-site backup. ### Why might an update be missing from History? History starts after Titanium is installed and relies on successful WordPress updater events with a reliable before/after version. Direct external file replacement cannot be detected reliably. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Titanium Compatibility Control – Rollback, Download & Update History” is open source software. The following people have contributed to this plugin. Contributors * [ Admin Plugins ](https://profiles.wordpress.org/aplugins/) [Translate “Titanium Compatibility Control – Rollback, Download & Update History” into your language.](https://translate.wordpress.org/projects/wp-plugins/titanium-compatibility-control) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/titanium-compatibility-control/), check out the [SVN repository](https://plugins.svn.wordpress.org/titanium-compatibility-control/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/titanium-compatibility-control/) by [RSS](https://plugins.trac.wordpress.org/log/titanium-compatibility-control/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.0 * Initial release ## Meta * Version **1.0.0** * Last updated **6 hours ago** * Active installations **Fewer than 10** * WordPress version ** 6.5 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/titanium-compatibility-control/) * Tags * [compatibility](https://dv.wordpress.org/plugins/tags/compatibility/)[plugin backup](https://dv.wordpress.org/plugins/tags/plugin-backup/) [Plugin Updates](https://dv.wordpress.org/plugins/tags/plugin-updates/)[rollback](https://dv.wordpress.org/plugins/tags/rollback/) [update history](https://dv.wordpress.org/plugins/tags/update-history/) * [Advanced View](https://dv.wordpress.org/plugins/titanium-compatibility-control/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/titanium-compatibility-control/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/titanium-compatibility-control/reviews/) ## Contributors * [ Admin Plugins ](https://profiles.wordpress.org/aplugins/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/titanium-compatibility-control/)