Backup creation is more resilient to concurrent runs, unsafe cleanup, archive failures, and database or filesystem errors.
Google Drive operations, multisite schedules, legacy upgrades, site identification, and the PHP iconv fallback are also more reliable.
BASE [LITE]
[UPD] Backups: Hardened concurrent backup processing with coordinated SQL and file locks, clearer diagnostics, and safe failure when no locking engine is available.
[UPD] Backups: Improved failure classification and guidance for disappearing database tables, disk-space and filesystem errors, and unreadable scan directories.
[UPD] Base: Removed obsolete process-lock files during eligible legacy upgrades without affecting current locks.
[FIX] Backups: Prevented temporary-cache cleanup from removing active backup artifacts and distinguished missing indexes from empty ones.
[FIX] Backups: Validated archive prerequisites earlier, preserved actionable filesystem errors, and recovered from eligible archive and database edge cases (Installer)
[FIX] Storage: Stopped invalid-storage notices from retaining storage entries that no longer exist.
[FIX] Base: Fixed fatal errors on servers without PHP iconv by completing the bundled fallback integration.
PRO
[FIX] Schedules: Ensured multisite scheduled backups use the network main-site context for backup names, metadata, and failure notifications.
[FIX] Storage: Routed Google Drive directory-creation, upload, and resumption failures through storage retry handling instead of aborting backups.
[FIX] Storage: Contained Google Drive directory-listing exceptions so transient failures follow the normal retry flow.
[FIX] Storage: Prevented non-recursive Google Drive directory deletion when content listing fails.
Backups are now more resilient to transient issues: files that vanish mid-compression, temporarily invalid storages, or disk-full conditions no longer crash the entire backup; the build completes and surfaces warnings instead. Notification emails now always use the site’s configured language. On multisite, the installer no longer hangs during subsite import when a source-site mapping is incomplete. Users also get clearer, phase-specific guidance when a backup times out, and the activity log now shows the actual failure reason when a backup fails.
BASE [LITE]
[NEW] Backups: ZipArchive multi-thread builds now recover from a chunk-close failure caused by files vanishing between add and close, instead of failing the entire backup (Installer)
[NEW] Backups: Added a build warnings system that lets backups complete with warnings instead of failing on transient conditions such as files vanishing mid-compression, unverifiable post-build file counts, or database row-count drift on write-active tables
[NEW] Backups: Backups with an invalid configured storage now skip the broken storage and fall back to the default local storage instead of failing the entire build, with a dismissible admin notice explaining what was skipped
[UPD] Backups: Improved recommended fix suggestions for Max Build Time failures — guidance is now tailored to the specific build phase (scan, database, or archive) and kickoff mode (client-side vs. server-side) instead of showing generic advice
[UPD] Backups: The failure reason is now shown directly in the Activity Log detail view as a “Failure Message” field, giving an immediate human-readable explanation of why a backup failed
[UPD] Backups: Improved scan performance on large sites by aligning the scan chunk timeout with the environment-aware worker time budget instead of a fixed 5-second limit
[UPD] Base: Notification emails (build results, schedule failures, email summaries) now always use the site’s configured language instead of the logged-in admin’s profile language
[FIX] Backups: Fixed a race condition where double-clicking or resubmitting the manual backup confirmation could create duplicate backup packages
[FIX] Backups: Fixed a race condition where concurrent build workers could both report the same failure, duplicating cleanup and failure notifications
[FIX] Backups: Fixed shell zip engine silently treating some non-zero exit codes as success when stderr was empty, which could produce incomplete archives without surfacing any error
[FIX] Backups: Fixed false “skipped files” warning on DupArchive backups caused by benign skip-count increments including the archive root directory
[FIX] Base: Fixed email summary subject containing HTML-encoded entities (e.g. &😉 due to incorrect use of esc_html_x() instead of _x()
PRO
[UPD] Backups: Disk-full and quota-exhaustion errors are now detected and reported consistently across installer build, database export, and all archive engines, with centralized user-facing messages (Installer)
[UPD] Storage: Google Drive storage no longer passes the refresh token to the Google SDK client, preventing an unhandled exception when the SDK attempted auto-refresh without client credentials
[FIX] Multisite: Fixed multisite subsite import hanging indefinitely on the “Parameters update” step when a source-site mapping entry was missing (Installer)
We’ve improved reliability across several backup build scenarios based on real-world usage data. Backup builds and WordPress core/plugin/theme updates can no longer run at the same time, preventing potential file conflicts. We’ve also improved error messages so it’s clearer what to do when a backup build doesn’t complete, and fixed an issue where custom user permissions could be affected on load.
BASE [LITE]
[UPD] Backups: Backup builds and WordPress core/plugin/theme updates no longer run concurrently, an update waits for an active backup build to finish, and a new backup build waits for an in-progress update to complete, avoiding potential file conflicts
[UPD] Backups: Improved the error messages shown when a backup build doesn’t complete, so they better identify the specific issue (e.g. a missing, incomplete, or truncated file) and how to resolve it
[FIX] Backups: Improved reliability of the backup archive process, resolving an occasional “Invalid or uninitialized Zip object” message and related issues that could interrupt a build
[FIX] Backups: Resolved an edge case where a backup build could leave the system in a busy state after an unexpected issue, delaying the next scheduled or manual build
[FIX] Capabilities: Fixed an issue where custom user capabilities contributed by certain features could be removed on load if registered later in the startup sequence
PRO
[FIX] Backups: Resolved a multisite edge case where a build started from a subsite could conflict with one started from the main site
This release fixes staging-site backups that included wrong database tables, resolves a connectivity issue that caused unnecessary Client-side Kickoff on sites with strict firewalls, and adds an admin notice when encrypted settings (such as storage credentials) are automatically reset after an encryption key change. It also ensures staging site tables are properly cleaned up when uninstalling the plugin.
BASE [LITE]
NEW] Base: Admin notice when encrypted settings are reset to defaults after a decrypt failure, explaining the likely cause and how to recover
[UPD] Base: Reduced false positives from web application firewalls blocking the loopback connectivity probe, preventing unnecessary Client-side Kickoff fallback on affected hosts
[UPD] Base: Expanded package build log header with richer diagnostics including SQL engine, build/transfer time limits, and auto-detect vs manual-override indicators
[FIX] Base: Fixed loopback probe false negative caused by WAF keyword blocking, which incorrectly enabled Client-side Kickoff and stalled scheduled builds on low-traffic sites
PRO
[NEW] Staging: Staging site database tables are now removed when uninstalling the plugin with “Delete plugin settings” enabled
[UPD] Staging: Updated Uninstall settings descriptions to clarify what each option deletes, including staging site data
[FIX] Staging: Fixed staging-site backups including wrong database tables — backups created on a staging site now correctly contain only that site’s own tables
[FIX] Staging: Fixed restoring a staging-site backup onto a normal site leaving the destination deindexed with outbound email blocked
This release adds support for the new Enterprise license plan, fixes Dropbox upload failures that could leave large backups stuck after an interrupted transfer, prevents unnecessary mysqldump checks when using PHP dump mode, and improves reliability of scheduled backups during cleanup operations.
BASE [LITE]
[FIX] Backups: Fixed mysqldump path discovery running unnecessarily in PHP dump mode, which caused extra shell invocations and potential failures in restricted hosting environments
[FIX] Storage: Fixed storage uploads continuing one extra cycle after exhausting retry attempts instead of stopping cleanly
[FIX] Base: Fixed activity logging failing during cron or scheduled backups when events like backup deletion or orphan cleanup ran outside the admin context
PRO
[FIX] Storage: Fixed Dropbox chunked uploads failing permanently when a resume attempt found a gap between the local and server offset, by automatically recovering from Dropbox incorrect_offset errors and reworking the upload into a timeout-driven append loop
This release adds support for the new Enterprise license plan, fixes Dropbox upload failures that could leave large backups stuck after an interrupted transfer, prevents unnecessary mysqldump checks when using PHP dump mode, and improves reliability of scheduled backups during cleanup operations.
BASE [LITE]
[FIX] Backups: Fixed mysqldump path discovery running unnecessarily in PHP dump mode, which caused extra shell invocations and potential failures in restricted hosting environments
[FIX] Storage: Fixed storage uploads continuing one extra cycle after exhausting retry attempts instead of stopping cleanly
[FIX] Base: Fixed activity logging failing during cron or scheduled backups when events like backup deletion or orphan cleanup ran outside the admin context
PRO
[FIX] Storage: Fixed Dropbox chunked uploads failing permanently when a resume attempt found a gap between the local and server offset, by automatically recovering from Dropbox incorrect_offset errors and reworking the upload into a timeout-driven append loop
Improved backup reliability on servers where the internal loopback connection fails silently (e.g. exhausted PHP-FPM pools). Backups that would previously stall now automatically resume via a fallback mechanism, keeping the build moving without manual intervention.
BASE [LITE]
[NEW] Backups: Added a cron-based fallback that automatically resumes package builds when the primary loopback kickoff fails silently, preventing backups from stalling on constrained servers
This release fixes a problem where some hosting environments appeared to support background backup processing but actually didn’t, causing backups to silently stall or fail during creation. The detection check now verifies that background processing genuinely works before relying on it, so backups run reliably on affected hosts.
BASE [LITE]
[FIX] Backups: Fixed the background-processing capability test giving false positives on hosts that drop non-blocking connections, which caused backup builds to silently fail; the check now confirms the background worker actually ran, and any stale test result is reset automatically on plugin upgrade
This release improves backup reliability and smooths out a few situations that could interrupt backups and upgrades. Sites running behind a reverse proxy or SSL terminator will no longer be wrongly switched to the slower client-side backup mode. Interrupted scans now pick up from the last good checkpoint instead of starting over, so an unexpected stop mid-backup no longer loses files. We’ve also made upgrades from much older versions more reliable, and corrected a misleading message when saving import settings.
BASE [LITE]
[FIX] Backups: Fixed incorrect “loopback failed” detection that wrongly switched sites behind a reverse proxy or SSL terminator to client-side backup mode; the working connection scheme is now detected automatically and reused.
[FIX] Backups: Backup scans now resume reliably after an unexpected interruption — the file index is checkpointed and restored from a backup copy on resume, instead of starting the scan over or leaving files out.
PRO
[FIX] Base: Made upgrades from older installations more reliable by handling missing custom-path settings gracefully.
[FIX] Migration: Fixed the import settings screen wrongly reporting a save failure even when settings were saved successfully.
This release resolves two compatibility problems introduced in 4.5.26. On some sites, plugins or themes that customize the WordPress admin footer (for example the Avada theme) could prevent Duplicator’s admin pages from loading; those pages now open normally. In addition, updating Duplicator from an older version (4.5.25.4 or earlier) could fail in rare cases involving other active plugins; that update path is now handled safely.
BASE [LITE]
[FIX] Base: Resolved a compatibility issue that could prevent Duplicator’s admin pages from loading in 4.5.26 when another plugin or theme set a non-text value in the WordPress admin footer
[FIX] Base: Improved reliability when updating Duplicator from version 4.5.25.4 or earlier, preventing a rare conflict that could interrupt the update on sites with certain active plugins.