007AJ Backup Restore Verifier

Changelog

0.6.5

• Fix: PHP 7.4 fatal error on the Settings screen (PHP 8-only str_ends_with()). All PHP 8-only string functions are replaced with PHP 7.4-safe helpers.
• New: the plugin checks the PHP and WordPress versions and the zlib, hash and json PHP extensions before running, and shows an admin notice instead of failing; a notice also explains when the zip extension is missing.
• Change: the working and backup folder now lives in the uploads directory (uploads/brverify-working/). An existing wp-content/brverify-working/ folder is moved there automatically (once, never while a job is running) and stored paths are updated; uninstall finds both locations.
• Change: plugin, theme and content locations are found with WordPress functions instead of hardcoded constants.
• Change: removed load_plugin_textdomain(); WordPress.org loads the translations automatically.
• Change: the Settings stylesheet loads only on the plugin’s own Settings screen.
• Fix: “gmdate(): Argument #2 must be of type ?int, float given” when the site uses a city time zone or a fractional UTC offset.

0.6.4 (wordpress.org review)

• Renamed to 007AJ Backup Restore Verifier; slug and text domain are now 007aj-backup-restore-verifier. Settings, backups and history are kept (internal brverify names are unchanged).
• Removed the promotional note from the Settings screen. The only mention of the extended plugin is the “Get the full version” link in the plugin row.
• The pre-update backup result notice now appears only on this plugin’s screens and on Updates, Plugins and Themes, and is dismissible.

0.6.4

• Restores: if a request is killed after a database statement ran but before progress was saved, the next request can safely run it again (rows are written as REPLACE into the freshly recreated table, so a repeated row no longer stops the restore with a duplicate-row error). This also applies to the automatic rollback.
• Restores: a database dump supplied by an add-on is checked against its SHA-256 across requests before the first statement runs, and must come from the database member that passed validation.
• Uploads to a destination: if the archive hash was not recorded yet, it is computed across requests instead of in one request.
• Engine support used by the extended edition for resumable steps (named per-task locks, byte ranges of stored archive members, continuing a supplied database dump across requests).

0.6.3

• Restore validation is strictly one-to-one: an archive with an extra member that has no checksum entry, a duplicated path, a missing member or an extra checksum entry is rejected before any file or database change.
• Restore applies only validated members and compares each restored file’s SHA-256 with its validated checksum before it replaces the live file; it stops if the archive changed after validation.
• PHP 7.4: very large files can now pause and continue in the next request during backup, verification and restore (built-in resumable SHA-256, about 9 MB/s on PHP 7.4; PHP 8+ uses the native hash).

0.6.2

• Large sites: file discovery, packing, verification and restore now run in small resumable steps, each limited to 20 seconds or half of max_execution_time, whichever is lower. Very large files can continue in the next request (PHP 8+). The archive writer supports archives and files larger than 4 GB (Zip64).
• Large working data (file lists, checksums) is kept in protected working files; the job record only holds small references.
• Fix: only one request can advance a job at a time (per-job lock, released automatically if the request dies), so two open admin tabs can no longer write to the same backup.
• Fix: each archive entry’s data, directory record and checksum line are committed together and rolled back together, so an interrupted or retried step cannot duplicate, drop or reorder entries.
• Verification checks the archive directory and the checksum list one-for-one and names the exact entry of the first difference.
• Failures record the real error (message, phase and file) in the job and the log.

0.6.1

• Fix: when a restore fails, the database snapshot is now always applied in full before the job reports the rollback as finished (large databases could previously be left partly restored).
• Privacy: suggested privacy policy text, personal data exporter and eraser for the data the plugin stores itself.
• Requirements lowered to PHP 7.4 and WordPress 6.3 (the code was checked with static compatibility checks; the test suites run on PHP 8.4).
• No inline styles or inline event handlers in the admin screens (utility CSS classes and one small script file instead).
• Constants are defined only if not already defined.
• Wording: descriptions now state exactly what is checked (SHA-256 checksums are checked before a restore).
• The dismissible note no longer mentions a license (this edition has none).

0.6.0

• New name and slug: 007AJ Backup Restore Verifier (007aj-backup-restore-verifier). Options, tables, cron events and the working folder now use the brverify prefix; data from earlier pre-release builds is migrated automatically on first load.
• Uninstall: new setting Delete all data when the plugin is deleted (off by default). Off keeps settings, history and backup files; on removes them. Scheduled events and transients are always removed.
• Backups of the previous format are still recognised and restorable.
• If the extended edition of this plugin is also active, a single notice asks you to deactivate one of them (they share the same data).
• The small note about the extended plugin is now dismissible per user and only appears on the Settings screen.
• Reviewed every form and request handler: capability + nonce checks, input sanitising and output escaping.

0.5.5

• Fix: a stale object cache after a restore could stall the next restore tick on MySQL/MariaDB.
• Fix: pre-update core “from → to” versions are now read from the update package name first.
• Fix: restores started from the browser could stall because the maintenance file blocked the requests driving the job.
• New extension points for add-ons (defaults change nothing).

0.5.4

• Manifest records where a backup came from (site URL, paths, table prefix). Older backups still restore unchanged.
• Fixes for database dumps (placeholder tokens, comment lines) and for restores that replayed the plugin’s own tables.

0.5.3

• Opt-in automatic backups before plugin, theme and core updates with a separate retention cap and a restore button. A failed backup never blocks an update.

0.5.0

• Hardening release: security review of downloads, restores and AJAX; protected storage folder; packaging.

0.4.0

• Configurable schedule, retention, failure emails and a Settings screen.

0.3.0

• Restore engine: validation, maintenance mode, snapshot, apply, verify, rollback.

0.2.0

• Local backup engine: database dump, file pack, manifest, checksums, protected storage, Backup Now.