BackupEase

Changelog

2.2.3

• Added: BackupEase now checks your storage connections once a day and emails you as soon as one stops working, instead of you finding out days later when a backup fails.
• Added: A Settings button to change the Folder ID of a storage service you are already connected to.
• Fixed: Your backups could be downloaded by anyone who knew where to look. BackupEase kept them in a fixed, predictable folder and relied on a protection file that Apache servers obey but nginx and IIS servers ignore. On those servers, a visitor who was not logged in could read your database backup and your site files, which include your site’s passwords and settings. Backups are now kept in a folder whose name ends in a long random code that cannot be guessed, so they are protected on every type of server. Your existing backups are moved into the new folder automatically and stay in your Backup Log. Thanks to Ananda Dhakal of Patchstack for reporting this.
• Fixed: When a backup fails, the activity log now tells you the full story: which backup it was, how far it got, what it managed to create, and exactly what each storage service said went wrong.
• Fixed: On some hosts, a scheduled backup would say, “Backup started” and then stop at 5% and stay there. These hosts block the tool BackupEase normally uses to run a backup in the background, so nothing was left to carry the backup forward once the browser was out of the picture. Scheduled backups on these hosts now carry themselves forward step by step and finish on their own.
• Fixed: A backup that got stuck and was given up on after 10 minutes now explains what happened instead of just saying it stopped unexpectedly.
• Fixed: You now get a failure email when a backup is built, but none of your storage services will accept it.
• Fixed: A backup that could not start because a storage connection had expired now appears in the Backup Log, instead of only in the log file.
• Fixed: Google Drive kept disconnecting every 7 days. This happens when your Google app is left in “Testing” mode, which Google cuts off after a week. The setup guide now tells you to publish your app, which takes one click and does not need a review from Google, and the connection then stays active.
• Fixed: When Google disconnected, BackupEase told you that your authorization code had expired and to connect again, which only bought you another week. It now explains what actually happened and how to stop it from happening again.
• Fixed: Some error messages appeared as “An unknown error occurred” instead of saying what actually went wrong. Every message BackupEase sends to the screen now comes through in full.
• Fixed: Clicking Download twice in a row on the same backup could log a harmless PHP warning on some hosts. This did not affect the download itself.
• Fixed: A backup sent to FTP, SFTP, OneDrive, Dropbox, or S3-compatible storage said nothing about the upload while it was happening, and a files-only backup left no record of it at all in either the progress log or the activity log. Every storage service now reports when its upload starts and when it finishes, the same way Google Drive always has.
• Fixed: On hosts that run backups in PHP mode, a backup sent to FTP, SFTP, OneDrive, Dropbox, or S3-compatible storage could send your files successfully and then sit at the final step until it was given up on ten minutes later. It now finishes as soon as the upload is done.
• Improved: A failed backup is now correctly shown as Full, Database, or Files in the Backup Log.
• Improved: A scheduled backup no longer gives up completely when one storage service is unavailable. It now saves to the ones that are working and tells you which it had to skip. Before, an expired Google Drive connection also cost you the copy kept on your own server.
• Improved: Settings → Storage now has a more consistent look across all storage services.
• Improved: Settings → Storage now shows every storage service BackupEase can use, including the ones in BackupEase Pro (FTP, SFTP, OneDrive, Dropbox, and S3-compatible). Without Pro, they are greyed out and marked “Pro”, so you can see what is available at a glance.
• Improved: A manual backup now checks your storage services before it starts, so you find out about a broken connection at the click instead of half an hour later when the finished backup has nowhere to go. If one service is unavailable, the backup still runs and saves to the rest.
• Improved: Google Drive uploads are now resumable whatever the size of the backup. A small file used to be sent in one go, so a dropped connection meant starting it again from the beginning.
• Improved: BackupEase now renews its Google Drive access before it lapses rather than after, which saves a wasted round trip at the start of every backup.
• Improved: Old failed backup entries are now cleared out of the Backup Log during the regular tidy-up. The 20 most recent are kept, and anything older than 90 days is removed, so the log stays readable.
• Improved: Storage services are now named properly in the logs. FTP, SFTP, and S3 Compatible used to appear as “Ftp”, “Sftp” and “S3compatible”.
• Updated: Translations template.

2.2.2

• Fixed: On Windows setups (Local, WAMP, XAMPP, IIS), every completed backup was deleted moments after it finished, with no error shown – the tidy-up that runs after each backup mistook the brand-new files for leftovers. Backups now stay put and show their correct size; backups already lost to this cannot be recovered.
• Fixed: On servers where WP-CLI isn’t available, “%” characters were not always preserved in the database backup file. This could affect permalinks that use non-Latin characters (Hebrew, Arabic, Cyrillic, and similar) and page-builder content stored as serialized data, such as Elementor layouts. Backups now store these values exactly as they appear in your database – if you have backups from before this update, we recommend taking a fresh one.
• Fixed: On some hosts, a backup could get stuck at the very beginning and never move past “Starting WP-CLI background process”. These hosts keep your site’s security keys in a separate file next to wp-config.php, and the background process was started from the wrong folder, so it couldn’t find that file and stopped before it even began. It now starts from your site’s main folder, so the file is always found.
• Fixed: On Hostinger, starting a backup could fail right away with just “An unknown error occurred”, and nothing useful in the log. These hosts fully remove a server function BackupEase normally uses to launch WP-CLI backups, and the plugin wasn’t checking for that before trying to use it, causing a crash instead of a graceful switch to its PHP-based backup method. BackupEase now checks for this correctly, so the backup runs in PHP mode instead of failing.
• Fixed: Clicking “Cancel” on a running backup would report success and say its temporary files were deleted, but the backup kept running in the background and made further progress anyway. Cancel now reliably stops the backup and cleans up its files.
• Fixed: In rare cases a backup that produced no files at all could be recorded in your history as if it had succeeded.
• Fixed: Clicking “Run Now” on a schedule could look like nothing happened. The progress bar it uses lived on the Dashboard tab, so it stayed out of sight, and when the backup couldn’t start, no reason was shown. You are now taken to the progress bar, and if the backup can’t start, you get a message telling you why.
• Improved: Backups now check their storage destinations before they start – Google Drive, and with BackupEase Pro also FTP, SFTP, OneDrive, Dropbox and S3-compatible storage. If a connection has expired or was never finished, you’re told straight away instead of waiting for the whole backup to be built and only then failing at the upload step. This applies to both “Run Now” and backups that run automatically on their schedule.
• Improved: Background backups no longer load your theme. They don’t need it, and it’s one less thing that can interrupt a backup.

2.2.1

• Fixed: Some scheduled backups completed successfully but didn’t show up in Recent Backups. Backups are now reliably recorded every time, and a clear error is logged in the rare case a backup record still can’t be saved.
• Fixed: A “file not within allowed path” warning could appear on the Recent Backups and Backup Log screens after moving or cloning a site (for example, promoting a staging site to production).
• Fixed: Fatal error on PHP 7.4 (“must be an instance of BackupEase\mixed”) caused by a PHP 8.0-only mixed type declaration on Plugin::get_settings() and Plugin::wp_recursive_sanitize(). The plugin now loads correctly on PHP 7.4 as documented.
• Fixed: Backups could fail to start if the path to WP-CLI contained a space.
• Fixed: Some UI issues.
• Fixed: A scheduled backup started via wp backupease run --schedule=<id> would run even if the schedule was disabled/paused in the UI; WP-CLI now checks the schedule’s enabled state just like WP-Cron does.
• Fixed: The cleanup summary counted a backup once for every destination it was stored to, so “Deleted X old backup(s), kept Y backup(s)” reported a backup saved to three places three times. Each backup is now counted once.
• Improved: WP-CLI is now detected on more hosts, including many shared hosting setups.
• Improved: Clearer message when WP-CLI is installed, but your host blocks it.
• Improved: In Settings → Retention, each storage provider’s retention options (Google Drive, Local Server) now only show up when that provider is selected as a storage destination.
• Improved: Consolidated design guide to PrecisionWP.css
• Security: The WP-CLI Path setting is now checked before it is saved.
• Added: New filter for developers to set a custom WP-CLI location.
• Added: New filters for developers to add their own storage providers to the retention cleanup run and supply each one’s keep-count/keep-days policy.
• Added: New settings field for email notifications theme (light or dark).
• Updated: Translations template.

2.2.0

• Fixed: Issue with download ZIP file in some cases.
• Fixed: Backup Summary destinations text.
• Fixed: UI fixes.
• Fixed: A folder could be left out of a backup by mistake when its name simply started with the name of an excluded folder (for example, “cacheplus” being treated like the excluded “cache”). Exclusions now match the intended folder only.
• Fixed: Manual backups now always skip the cache, staging, and backup-storage folders automatically – just like scheduled backups do – so an in-progress backup can never accidentally be packed into itself.
• Fixed: Exclusion paths typed with a leading or trailing slash (e.g. “/wp-content/cache/”) are now saved in a consistent form so they reliably exclude the right folder.
• Fixed: Live backup log shows more accurate information.
• Added: Google Drive connection wizard.
• Improved: Added domain name to the backup files.
• Improved: Faster admin pages. The automatic check for leftover folders from other backup/migration plugins now runs at most once per hour instead of on every admin page load.
• Improved: Faster backups on sites with large excluded folders. Excluded folders are now skipped entirely instead of being scanned file by file.
• Updated: Translations template.

2.1.0

• Added: Every scheduled backup now shows a ready-to-paste cron line. If you have SSH access to your server, you can run any backup schedule straight from your server’s crontab – no PHP timeouts to worry about.
• Added: A new WP-CLI flag, wp backupease run --schedule=<id>, runs any saved schedule from the command line.
• Improved: Smarter auto-detection of leftover folders from other backup and migration plugins (UpdraftPlus, Duplicator, BlogVault, WP Time Capsule, WPvivid, All-in-One WP Migration). They show up pre-excluded in your exclusion list, so they don’t bloat your backups – uncheck any of them if you want a fully comprehensive backup.
• Improved: Friendlier wording when WP-CLI isn’t installed. Backups still run reliably in pure PHP – that’s a normal, supported setup, not a fallback.
• Improved: The “How to enable WP-CLI” guide is tucked into an “Advanced” section, so it stays out of the way until you need it.
• Updated: Translations template.

2.0.0

• Redesign release: Brand-new dark-theme admin UI with the “moss” accent palette across the Dashboard, Manual Backup, Scheduled Backups, Backup Log, License, and Settings tabs.
• Fixed: A backup that failed to upload to every configured storage destination was incorrectly reported as “complete”. Such a backup is now correctly marked as failed, so failure notifications fire, and the local copy is kept for a retry.
• Fixed: A corrupted or zero backup-retention value (by count or by age) could cause a cleanup to delete every backup for that storage provider. Retention now falls back to safe defaults instead of removing everything.
• Fixed: Resuming an interrupted Google Drive upload could miscalculate the resume position when Google did not return a progress header, stalling the upload. The resume offset is now tracked reliably.
• Fixed: Database dump chunks are now verified to be fully written to disk. A partial writing (for example, when the server runs out of disk space) is treated as an error instead of silently producing a truncated .sql file.
• Improved: Backup progress is now read using a blocking lock and re-read once on a partial read, so the live progress display no longer briefly resets while a backup is updating its status.
• Fixed: Exclusions not showing on Scheduled Backups.
• Fixed: Google Drive integration using saved settings value instead of current input.
• Added: Dedicated Backup Log screen separated from the dashboard, with its own paginated table view.
• Added: New License tab introducing the BackupEase Pro upgrade path.
• Improved: More accurate server-capability detection: ServerCapabilities now explicitly checks PHP exec() availability and reports whether WP-CLI wp db export can run, falling back to PHP chunked mode automatically when it cannot.
• Improved: More reliable WP-CLI detection using a recheck transient so capability changes on the host are picked up without manual reactivation.
• Improved: Hardened settings persistence.
• Improved: Better Pro plugin support.
• Updated: Translations template.

1.0.0

• Initial release of BackupEase