UpdraftPlus 1.11.20 (free) / 2.11.20 (paid) Release

UpdraftPlus 1.11.20 (free version) / 2.11.20 (paid versions) is in the process of being released, and should be available from your WordPress ‘Updates’ dashboard page during the next day or so.

The main highlights of this release are two new features for WordPress multisite (i.e. WordPress Network) users on UpdraftPlus Premium:

• WordPress multisite backup administrators can now selectively restore data from a chosen site, instead of restoring the entire WordPress install – (requires WP 3.5+, UpdraftPlus Premium)
• Import a WordPress single-site backup into WordPress multisite, as a new site (requires WP 3.5+, UpdraftPlus Premium)

Beyond that, there’s a raft of small fixes and minor improvements. As ever, we strongly recommend updating to the latest version when it becomes available.

• Fix: Properly encode folder paths with Copy.Com, allowing some previously prevented folder names to work
• Fix: In-dashboard decryption using some decryption keys with URL-encodable characters failed
• Fix: Prevent PHP fatal error on settings page on a buggy old PHP version (5.2.10) when Google Cloud storage add-on not present
• Fix: When using multiple remote storage providers, a race condition could lead to some old backups not being deleted on the storage not uploaded to last
• Fix: Views are now placed after tables in the database backup
• Fix: In-page uploader widget was not working on sub-domain based multisites in some dashboard access scenarios
• Fix: Package Net/URL2 (PEAR), so that servers without it already can use Microsoft Azure blob storage
• Tweak: Upgrade Microsoft OneDrive API usage to latest version
• Tweak: Automatic backups are now hooked into the themes page in the network admin on WP multisite installs
• Tweak: Dashboard messages were not being clearly shown when trying to use UpdraftPlus Vault without PHP Curl available
• Tweak: Protect against other plugins loading incompatible Google SDKs when Google Cloud is being used
• Tweak: When trying to use S3, DreamObjects or UpdraftPlus Vault without PHP Curl available, make the cause of the problem more obvious
• Tweak: When sending data to remote site, keep re-trying on receipt of an HTTP 413 (request entity too large) down to 64Kb (instead of previous 128Kb) – a webserver was seen in the wild configured at this level
• Tweak: Detect the WordPress scheduler invoking a scheduled backup multiple times, in some cases where the existing semaphore lock wasn’t helping (because the backup already finished, or the WP scheduler invoked multiple instances of the same event minutes apart – apparently possible when very heavily overloaded)
• Tweak: Detect an inconsistent semaphore locking state, and fix it (apparently only possible upon unexpected server crash)
• Tweak: Provide a button to cancel (not just continue) an interrupted restore
• Tweak: Work around buggy Ubuntu PHP versions
• Tweak: Make sure that backup options get passed on with continuation data, when resuming an interrupted restore
• Tweak: Catch a few untranslated strings (in the decryptor widget for encrypted backups)
• Tweak: Log more information if a connection to UpdraftPlus Vault fails
• Tweak: The internal info shown when triple-clicking a backup set’s date had messed-up formatting