A new UpdraftPlus release is making its way to your WordPress dashboard…
The main new feature (all versions) is that if you are restoring a database backup that uses a collation that is not supported on your destination site, then UpdraftPlus will detect it, and offer to swap for a different one. (What’s a collation? It’s a list of rules for how to sort alphabetically – i.e. how to handle different sets of characters, languages, accents). It’ll even suggest the one that it thinks is the best alternative for you. So, one less situation in which you need to become a database expert, and in which things “just work” !
Also, when cloning a website, if you had an .htaccess file which hard-coded the old website address, UpdraftPlus will detect this and warn you about it… so that why you keep getting redirected back to the old website is no longer a mystery.
Beyond that, there are lots of small tweaks and internal improvements and some fixes. The full changelog is included, below. It is a recommended update for all!
If you’ve not yet looked at our flagship product, UpdraftPlus Premium, then please do so: it’s the version that includes all UpdraftPlus features, and its sales make what we’re doing possible!
- Feature: Warn the user if their .htaccess seems to contain a redirect (or any other reference) to the old site after migration.
- Feature: When importing a database, warn the user if the current MySQL server does not support a used collation, and offer to replace it
- Fix: Saving of S3 settings had taken a dislike to buckets beginning with a capital ‘B’
- Fix: UpdraftCentral users’ module was failing to handle loading a very large number of users
- Tweak: Allows the installation and/or activation of the WP-Optimize plugin from UpdraftCentral
- Tweak: Add multisite attribute to the error response object for the create user, delete user and edit user actions.
- Tweak: All remote storage methods are ported over to using configuration templates internally
- Tweak: Include a method to add a manifest file inside each backup archive
- Tweak: All code relating to the now-dead Dropbox APIv1 removed (N.B. If you’ve not updated UpdraftPlus since November 2016 and were using Dropbox, it won’t be working – https://blogs.dropbox.com/developers/2017/09/api-v1-shutdown-details/)
- Tweak: Prevent a PHP log notice upon database backup restore when using Google Drive without a client ID
- Tweak: Prevent the final ‘Restore’ button being pressed a second time
- Tweak: Improvements to the UpdraftCentral wizard
- Tweak: Update to trunk version of plugin updater (paid versions), restoring the ability to work on older WP versions (3.8 and before)
- Tweak: Add lbakut_activity_log to the list of large log tables
- Tweak: Updater in paid versions now requests JSON as response format for responses when claiming entitlements
- Tweak: Resolve: Backup labels could end up with extraneous slashes in output
- Tweak: Updater in paid versions can now receive and process update information in respond to entitlement claim – one less HTTP round-trip
- Tweak: Improve Google Cloud authentication success message for bucket name is not defined
- Tweak: UpdraftVault commands now pass an instance identifier
David Anderson (lead developer, UpdraftPlus)
