A small, focused release after 0.0.34's very large one — 2 commits, not 47.
⚠️ Breaking
The backups/* abilities introduced in 0.0.34 are replaced by updraftplus/* and all-in-one/*. There are no aliases — anything holding a backups/ slug needs updating. Those slugs were one release old.
Backups are now two tabs, one per plugin
UpdraftPlus and All-in-One WP Migration each get their own tab, toolset, folder and abilities, the same way Elementor, Rank Math, WPCode and every other integration works.
0.0.34 shipped them as a single "Backups" tab reaching both plugins through a shared provider layer. That made two genuinely different plugins look interchangeable, and turned every real difference into a capability flag you had to go and check before acting.
Each suite now offers only what its plugin can actually do:
| UpdraftPlus | All-in-One WP Migration | |
|---|---|---|
| Abilities | 8 under updraftplus/* | 9 under all-in-one/* |
| Schedules backups | ✅ | ❌ (paid extension) |
| Restores | ✅ | ❌ (paid Unlimited Extension) |
| Labels archives | ❌ — so there is no label ability | ✅ |
Where All-in-One cannot restore, the ability asks the plugin and passes its own answer back — with ServMask's upgrade link and the manual import route — rather than refusing on its behalf. A site that has the extension is therefore not blocked by us.
The fix existing users need
Restoring never worked outside the admin screens in 0.0.34.
The restore checked whether WordPress could write to the filesystem directly — the check that stops a restore dying half-way through and leaving a site part-replaced. It used get_filesystem_method(), which lives in wp-admin/includes/file.php and is not loaded for a REST request. Every call into the suite is a REST request, so every restore failed on that line before checking anything, whatever it was asked to do.
Found by running it on an activated site. It had been gate-tested but never executed end to end. If you rely on restoring through this plugin, this is the release that makes it work.
Also
The backup-exposure check is now shared and reports per plugin rather than on everything at once. Whether the web server will hand out a backup archive has nothing to do with which plugin wrote it, so that logic exists once — but each tab reports on its own storage.
Full changelog: changelog.txt
Quality gates: 2981 tests green · PHPCS clean · PHPStan level 8 clean · PHPCompatibility 8.1- clean.