Install and update in Free-first order, then install or activate the matching Pro package and finally Aurelia. Confirm WordPress 6.5 or newer, PHP 8.1 or newer, required PHP extensions, writable plugin directories and a supported database engine before replacing files. Pro cannot boot its normal runtime when Free is missing or incompatible; that is a safe dependency failure, not a reason to delete the Free package.
If activation is blocked, read the admin notice and verify the exact package versions and declared dependency slug. Do not install a random ZIP, reuse old RC bytes under a new label or run an uninstall to “reset” the site. After a bind-mounted replacement, reload PHP workers and flush persistent object cache when enabled so stale OPcache cannot mask the files. Recheck the compatibility banner and a real HTTP request through Home, Rooms, Search, Book Now and Admin.
For an Aurelia update, a rejected origin, version, byte-size or SHA-256 check must leave the last valid theme active. Child themes should fall through to a valid parent when an override is invalid. Keep the rollback packages until the smoke passes; restore Pro before Free when rolling back a pair and do not change database data unless a documented migration requires it.
Capture the redacted error, package identities and environment, then escalate a repeatable supported failure rather than disabling security checks.