Update Recovery
A safe update protects configuration, content, approved customizations, themes, and any files the package is expected to replace.
Guarded Update Flow
1. Confirm the package version, release-index signature, package-manifest signature, and checksum. 2. Create a recoverable backup of the current site state. 3. Stage the update before changing live files. 4. Enter maintenance mode for the shortest practical interval. 5. Apply only files declared by the reviewed update manifest. 6. Clear generated caches and run health checks. 7. Reopen the site only after navigation, content, administration, and publishing checks pass.
If guarded application or health checks fail, restore the matching backup and verify the recovered site before accepting traffic. Keep update and recovery permissions limited to trusted administrators.
Update checks should use PHP cURL when allow_url_fopen is disabled and report transport diagnostics clearly. Verified HTTPS streams are only a fallback when cURL is unavailable and stream access is enabled. During staging, keep diagnostics separate for transport failure, signature failure, unknown release key, HTML release pages, non-ZIP uploads, empty or incomplete archives, corrupt ZIPs, missing ZipArchive support, ambiguous desktop ZIP wrappers, and unsafe target collisions so recovery starts from the right cause.