Check plugin compatibility, watch repository health and keep rollback options close at hand.
Titanium Compatibility Control – Rollback, Download & Update History adds clear WordPress and PHP compatibility information to the Plugins screen, a detailed plugin inventory, WordPress.org repository-maintenance signals, local update history, official WordPress.org rollback tools and ZIP downloads of the versions currently installed on your site.
- 100% free WordPress plugin
- Compatibility metadata on Plugins
- WordPress.org rollback
- Download installed plugin ZIPs
The complete Titanium Compatibility Control plugin is Free.
There is no Pro plan, licence checkout or paid feature gate. Compatibility information, repository status, Update History, Rollback, Download, Site Health checks, Dark Mode and multisite support are included in the WordPress.org version.
See more useful plugin information without leaving WordPress.
Titanium combines declared compatibility, WordPress.org repository metadata and local update events in one administration workflow. It reports what the available metadata says; it does not pretend to prove source-code compatibility.
Compatibility on Plugins
See Requires WordPress, Tested up to and Requires PHP directly on the normal Plugins screen, with clear status colouring against the environment you are running.
Detailed Plugin List
Review Installed, Latest, Requires WP, Tested up to, Requires PHP, Last Repository Update and available tools in one dedicated plugin table.
Repository Health Signals
Distinguish Unmaintained, Removed from WordPress.org, Repository not detected and explicitly External / private plugins without turning temporary API failures into false removal warnings.
Update History
Record successful plugin updates after Titanium is installed, including previous and new versions, manual or automatic update type, user when available and date.
WordPress.org Rollback
For eligible repository plugins, load older official versions from WordPress.org and reinstall a selected older package with WordPress Core's Plugin Upgrader.
Download Installed Version
Create a ZIP from the plugin files actually installed on the site. This can also work for private and premium plugins because Titanium packages the current local files instead of fetching another copy.
Site Health Integration
Add Site Health checks for declared compatibility and WordPress.org plugins detected as removed or old enough to meet your configured Unmaintained threshold.
Refresh, Dark Mode & Multisite
Refresh after external file changes, use per-user Dark Mode, schedule monthly metadata refreshes and manage multisite compatibility centrally from Network Admin.
Repository signals with careful wording.
Maintenance metadata can help you decide what deserves attention, but it should not be confused with a security verdict. Titanium keeps the states separate so missing or temporary data is not presented as certainty.
What each status means
Clear signals instead of guessed conclusions.
| Status or field | Meaning |
|---|---|
| Requires WordPressThe minimum WordPress version declared by the installed plugin. | Declared metadata |
| Tested up toThe WordPress version through which the plugin author declares testing. | Declared metadata |
| Requires PHPThe minimum PHP version declared by the installed plugin. | Declared metadata |
| UnmaintainedThe WordPress.org Last Repository Update age reached your configured threshold. Default: 180 days. | Maintenance signal |
| Removed from WordPress.orgA previously identified WordPress.org plugin is reported as not found by the Plugins API. | Repository status |
| Repository not detectedTitanium could not reliably identify the installed plugin as a WordPress.org repository plugin. | Unknown repository |
| External / privateThe plugin explicitly declares a non-WordPress.org update source. | External source |
| LatestShown only when reliable WordPress update metadata is available; Titanium does not invent a latest version. | No guessing |
Useful recovery tools before and after an update.
Compatibility Control does more than display metadata. It keeps the currently installed plugin files downloadable and provides a guarded WordPress.org rollback path for supported repository plugins.
Download Before Updating
Package the exact files currently installed into a ZIP before replacing them. The archive contains plugin files only, not site content or database data.
Official Older Versions
Rollback is offered only when the plugin is currently identified on WordPress.org and installed in its normal repository folder.
Only Older Packages
The rollback chooser filters out the current and newer versions and accepts official package URLs from downloads.wordpress.org.
Local History
Titanium rollbacks are recorded alongside successful normal plugin updates, with the newest 250 history records retained.
Frequently asked questions
Clear answers about compatibility metadata, repository status, rollback, downloads, update history and multisite behaviour.
Does Titanium scan plugin PHP source code?
No. Titanium reports declared plugin metadata and WordPress.org repository information. It does not claim to prove source-code compatibility.
What does a red Tested up to value mean?
It means the plugin author has not declared testing through the WordPress version being compared. It does not by itself prove that the plugin is broken.
How does Version Check compare Tested up to?
You can use major/minor or exact comparison. By default, Tested up to 7.0 remains valid through WordPress 7.0.x and becomes outdated when WordPress reaches 7.1.
What does Unmaintained mean?
The Last Repository Update age reached your configured threshold. The default threshold is 180 days. It is a maintenance signal, not a claim that the plugin is unsafe.
What does Repository not detected mean?
Titanium could not reliably identify the installed plugin as a WordPress.org repository plugin. It intentionally does not claim that the plugin definitely is not on WordPress.org.
Can temporary WordPress.org API failures mark a plugin as removed?
No. Temporary WordPress.org or API failures are kept separate and are not treated as proof that a plugin was removed from the repository.
Can every plugin be rolled back?
No. Rollback is limited to eligible WordPress.org plugins installed in their normal repository folder and requires the relevant plugin-update permission and permitted file modifications.
Where do rollback packages come from?
Older versions are requested through the WordPress.org Plugins API. Titanium accepts official older package URLs from downloads.wordpress.org and installs the selected version with WordPress Core's Plugin Upgrader.
Does rollback also restore a plugin's database settings?
No. Rollback replaces plugin files. Titanium does not intentionally change that plugin's database settings, although an older plugin version may handle its own stored data differently.
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 creates a ZIP from the local installed files instead of fetching another package.
What is included in a downloaded ZIP?
The currently installed plugin files only. It is not a database backup and does not include general site content.
Why might an update be missing from Update History?
History starts after Titanium is installed and relies on successful WordPress updater events with a reliable before-and-after version. Direct FTP or file-manager replacement cannot be identified reliably as a normal update event.
How many Update History records are retained?
The newest 250 records are retained.
When should I use Manual Refresh?
Use it after plugin files are replaced by FTP, file manager or another external method, or whenever you want Titanium to rebuild its current compatibility and update metadata.
How often is the scheduled refresh?
A monthly refresh is scheduled for the first day of each month at 4:00 a.m. site time. WP-Cron must be triggered, including on sites that use an external cron runner.
Does the plugin work on WordPress Multisite?
Yes. Management is network-level, plugin actions require network plugin-management permissions, repository work is centralized on the main site and subsites do not get separate Titanium pages.
Does Titanium add frontend scripts, analytics or telemetry?
No. The plugin adds no frontend assets, developer account, ads, analytics or telemetry. Its remote communication is limited to WordPress.org services used for update, repository and rollback metadata.
Does Dark Mode affect every administrator?
No. Dark Mode is stored as a per-user preference across Titanium and supported plugin-management screens.
Know what is installed before the next plugin update changes it.
Check declared compatibility, watch WordPress.org maintenance signals, keep a local ZIP of the installed version and use guarded rollback tools when an eligible repository plugin needs to go back.
10 practical ways to manage plugin compatibility, updates and recovery with clear WordPress-native tools.
These step-by-step tutorials explain how to read compatibility information on the Plugins screen, understand Tested up to and repository states, use the detailed Plugin List, adjust the Unmaintained threshold, refresh metadata after external file changes, download the version currently installed, roll back an eligible WordPress.org plugin, read Update History and use Site Health or Multisite safely.
- Compatibility metadata
- Repository status
- Rollback and Download
- Update History
Step-by-step plugin compatibility and recovery tutorials.
Start with the compact information on the normal Plugins screen. Open the detailed Plugin List when you need repository status, latest-version metadata, Download or Rollback, then use History and Site Health to understand what changed and what deserves attention.
How to read WordPress and PHP compatibility directly on the Plugins screen
Titanium adds compact compatibility information beside each installed plugin so you can compare its declared requirements with the WordPress and PHP environment currently running on the site.
Read the compatibility row
- Open Plugins in wp-admin or Network Admin on Multisite.
- Find Requires WordPress for the minimum WordPress version declared by the plugin.
- Read Tested up to for the WordPress version through which the plugin declares testing.
- Read Requires PHP for the minimum PHP version declared by the plugin.
- Use the colour as a quick signal, then read the actual version values before making a decision.
- Use Download from the Plugins screen when you want a ZIP of the files currently installed.
How to interpret Tested up to without treating an old declaration as a broken plugin
Tested up to is an author declaration. Titanium compares that declaration with your WordPress version, but a red value means the declaration is behind the compared version — not that the plugin has been proven incompatible.
Choose the comparison style
- Open Titanium Compatibility → Settings.
- Find the Version Check comparison preference.
- Use major/minor comparison when patch releases inside the same WordPress branch should count together.
- Use exact comparison when the complete version number must match the tested declaration more strictly.
- Save the setting and return to Plugins or Plugin List.
- Use the result as a testing signal, especially before major WordPress changes.
How to use the detailed Plugin List for versions, repository dates and recovery tools
The dedicated Plugin List combines local installation data with reliable WordPress update and repository metadata so you do not need to open every plugin separately.
Review the table
- Open Titanium Compatibility → Plugin List.
- Compare Installed with Latest when reliable WordPress update metadata is available.
- Review Requires WP, Tested up to and Requires PHP.
- Check Last Repository Update for identified WordPress.org plugins.
- Read the repository status instead of assuming every missing value means the same thing.
- Use Download or Rollback from the Tools column when the plugin is eligible.
How to distinguish Removed, Unmaintained, Repository not detected and External / private
These states answer different questions. Titanium keeps them separate because “not found”, “old”, “unknown” and “privately updated” are not interchangeable.
Read each repository state
- Use Unmaintained when Last Repository Update has reached your configured age threshold.
- Use Removed from WordPress.org only when a previously identified repository plugin is reported as not found by the Plugins API.
- Read Repository not detected as an identification uncertainty, not a removal verdict.
- Read External / private when the plugin explicitly declares a non-WordPress.org update source.
- Retry or refresh later when WordPress.org is temporarily unavailable.
- Combine repository status with your own testing and maintenance requirements before taking action.
How to choose when a WordPress.org plugin should be labelled Unmaintained
The age threshold is configurable because update cadence differs between plugins. A simple utility can be stable for a long time, while another plugin may normally publish updates much more often.
Change the threshold
- Open Titanium Compatibility → Settings.
- Find the Unmaintained threshold.
- Choose a value between 1 and 3650 days.
- Leave the default at 180 days when you do not need a custom maintenance policy.
- Save the setting.
- Review Plugin List and Site Health again with the new threshold in mind.
How to refresh compatibility data after replacing plugin files by FTP or File Manager
WordPress updater events can tell Titanium when a normal plugin change happened. External file replacement is different, so Manual Refresh gives you a direct way to rebuild the current local view.
Refresh after an external change
- Finish the FTP, SSH or hosting File Manager replacement first.
- Open the Titanium Compatibility plugin-management screen.
- Run Manual Refresh.
- Allow WordPress update metadata and local plugin compatibility data to rebuild.
- Let repository metadata refresh separately in its small batches where needed.
- Recheck Installed, Latest and the compatibility fields for the replaced plugin.
How to download the exact plugin version currently installed on the site
Titanium creates the archive from the installed plugin files instead of downloading a fresh repository package. That makes Download useful before updates and for private or premium plugins whose exact installed package may not be available elsewhere.
Create the ZIP
- Open Plugins or Titanium Compatibility → Plugin List.
- Find the plugin whose installed files you want to preserve.
- Choose Download.
- Save the generated ZIP somewhere outside the live WordPress installation.
- Confirm the filename and keep the archive with your update notes if it is part of a planned change.
- Remember that database settings and site content are not part of this ZIP.
How to roll back an eligible WordPress.org plugin to an older official version
Rollback is deliberately limited to currently identified WordPress.org plugins in their normal repository folder. Titanium requests older official versions and installs the selected package through the WordPress Core upgrader.
Roll back step by step
- Create a normal site backup and consider downloading the current installed plugin ZIP first.
- Open Titanium Compatibility → Plugin List.
- Choose Rollback for an eligible WordPress.org plugin.
- Review the older versions loaded from WordPress.org.
- Select the required older version and confirm the action.
- After WordPress installs it in overwrite mode, test the site and check Titanium Update History.
How to see which plugin version changed, how it changed and when it happened
Update History records successful WordPress plugin updater events after Titanium is installed. It can help explain when a version changed and whether the change was manual, automatic or a Titanium rollback.
Read an event
- Open Titanium Compatibility → History.
- Find the plugin name and previous version.
- Compare the previous and new version values.
- Check whether the event was manual, automatic or a rollback.
- Review the local WordPress user when one was available for a manual update.
- Use the date to match the version change with any site issue or maintenance window.
How to use Site Health checks and manage Compatibility Control on WordPress Multisite
Titanium adds compatibility and repository-maintenance checks to WordPress Site Health. On Multisite, plugin management is centralized at network level so the same installation is not managed independently from every subsite.
Use the diagnostic view
- Open Tools → Site Health on a normal site and review the Titanium compatibility checks.
- Investigate unmet declared compatibility separately from repository-maintenance warnings.
- For Multisite, network activate Titanium Compatibility Control.
- Manage the plugin from Network Admin.
- Use network plugin-management permissions for Download and Rollback actions.
- Keep the WordPress cron runner active so the main site can perform centralized scheduled repository refresh work.
Check first, keep a copy, then update with a recovery path.
Titanium Compatibility Control keeps declared compatibility, repository maintenance signals, installed-version downloads, official rollback and local update history together in one Free WordPress plugin.
Want a clearer picture before the next plugin update?
Use Titanium Compatibility Control to review declared compatibility, repository status and update history, then keep the installed ZIP or use an official rollback when recovery is needed.
Get Titanium Compatibility Control