Upgrade Assist

v3.2.4 (2026-11-12)

In one line: back up and check the environment before upgrading; roll back in one click if anything breaks.

Features

Backup

1. "Back up now": packs the whole site plus the database into a snapshot with a full file manifest and checksums, restorable precisely.
2. Backup list: each entry shows number, time, site version, file count, size and whether the database is included; downloadable and deletable.
3. Old snapshots are pruned beyond the retention count; the pre-restore point and pre-upgrade backups are never pruned.
4. If several sites share one database, the dump only takes this site's own tables (table prefix aware) — it never carries another site's tables into your backup or overwrites them on restore.

Health check

1. 26 checks: PHP version and extensions, database, web server, free disk, plugin state, directory permissions.
2. Fixable items repaired in one click, then re-checked — no trusting a return code.

Upgrade

1. Pick a version → check that version's requirements item by item → back up → upgrade, all four steps in one dialog.
2. Upgrading is blocked without a backup; take one first.
3. If an upgrade breaks midway it rolls back to the pre-upgrade state automatically.
4. If it stopped at the "files replaced" stage you can run just the finishing part (dependencies + migrations) instead of starting over.

Restore

1. Pick a backup and restore: its files are written back onto the site.
2. A restore point is saved automatically first, so a wrong restore can be undone.
3. The database is untouched by default; tick "restore database too" to import it.

Rescue

1. If the site or admin panel won't open, you can run the plugin's built-in rollback code over SSH and go straight back to the pre-upgrade backup.
2. That rescue code ships with the plugin: nothing extra to install, and it does not depend on the admin panel or on the framework booting.
3. It targets the BT Panel / aaPanel directory layout. On any other panel or a bare-metal stack it detects the mismatch, explains what is missing and stops without touching a single file.
4. After restoring it smoke-tests the site through four fallbacks (configured APP_URL → https host → http host → local loopback with Host header), so a site whose folder name differs from its domain is not wrongly reported as broken.

Plugin ledger

1. One screen lists every installed plugin: code, name, version, enabled state, disk usage, whether it has migrations.
2. After an upgrade, compare the count: N at backup time, one fewer now means the official upgrade removed it.

Activity log

• Who backed up, upgraded, restored or repaired what, and when.

Requirements

1. BeikeShop v1.0.0 – v2.0.0.
2. PHP 8.0+ (a major-version upgrade prompts for the PHP version the target requires).
3. storage/app writable (for backups); MySQL 5.7+ / 8.0.
4. The rescue command follows the BT Panel / aaPanel directory layout (/www/wwwroot, /www/server/php, the www runtime user). On other panels or bare metal it is stopped by a built-in check and explains why — it will not touch the site. Everything else in the plugin (backup, health check, upgrade, restore, ledger) has no panel dependency.

Compatibility

Where to find it

• The "Update" button in the admin top bar (with a red dot when a new version exists).
• Plugin list → Settings to open the console.

Access verification

1. The console requires one verification before backup, upgrade, restore or delete.
2. Two methods, pick one (TOTP recommended):
   • TOTP: any app such as Microsoft Authenticator, Google Authenticator or 1Password.
   • Secondary password: a separate password for this page only (at least 8 characters), completely separate from your admin login password.
3. Binding TOTP gives you one-time recovery codes — write them down.
4. A pass lasts 10 minutes with a countdown; 5 wrong attempts lock it for 15 minutes.
5. Without verification the dangerous buttons are never rendered into the page, and the server rejects hand-made requests too.

If the site breaks

When the page won't open (white screen / 500 after an upgrade), the in-panel Restore is unreachable. Use SSH: run the plugin's built-in rollback code from the site root to return to the pre-upgrade backup.

It does not depend on the framework or the admin panel, and there is nothing to install — it ships with the plugin and runs as is.

Prerequisite: the server must be BT Panel / aaPanel. On other panels the script detects the mismatch and stops before touching anything, telling you exactly which directories are missing.

What it does: saves the current state first → clears the code directories (keeping runtime dirs, uploads and config) → unpacks the backup over the site → restores the config file → fixes file ownership → imports the database → clears caches → aligns PHP with the version recorded in the backup → smoke-tests the site through four fallbacks.

Why use it

1. See clearly before upgrading: whether this server actually meets the target version's requirements, not a guess.
2. Keep a copy before upgrading: files and database are both recoverable.
3. Recover when an upgrade breaks: one click in the panel, or one command over SSH.
4. Reconcile after upgrading: how many plugins you had and which one went missing.