UpdraftPlus 1.13.5 (free version) / 2.13.5 (paid versions) Release

The latest release of UpdraftPlus is in the process of making it out into the world…

This release focuses upon the internals, making sure that the code-base is ready for the future. Not just the code itself, but our in-house processes (which don’t appear in the changelog) for building and releasing the software, have seen an upgrade. As our team grows, we’re making sure that the code and other processes are easy to dive into, so that we can focus more time on coding, and less on internal processes and “gardening”. We believe that this is our best UpdraftPlus yet, and recommend it as an upgrade for everyone.

If you’ve not yet taken a look at our flagship product, UpdraftPlus Premium, then please do take a look!

• Tweak: Update plugin-updates-checker library to current (4.2), and manage via composer, replacing bundled copy in the build source
• Tweak: Replace uses of create_function(), which is deprecated on PHP 7.2
• Tweak: Replace deprecated constructors (PHP 7+) in webdav module
• Tweak: Documentation showing plugin developers how easy it is to add in-page backups to their plugin
• Tweak: Make the UpdraftCentral updates checking able to cope with a wider range of third-party schemes
• Tweak: General code tidy-up, making older code conform to our current standards
• Tweak: Minor version updates of some bundled libraries
• Tweak: Produce and use minified resources (CSS/JS) where available
• Tweak: Update class-udrpc to latest (1.4.14) which removes a conflict with other code that may interact with ‘CORS OPTIONS’ requests
• Tweak: Escape log lines when sending for display (theoretically an XSS security issue, but to achieve a successful attack, someone would have to first get something malicious into the log file, which is difficult as there are not many places where foreign input can end up in the log file – e.g. hack into Dropbox and cause Dropbox to send you back malicious HTML in an error message – and then be able to persuade you to both take a backup triggering the problem and then view the log file in your WP dashboard)
• Tweak: Update Google Cloud bucket locations