UpdraftCentral 0.4.1 Release

UpdraftCentral 0.4.1 has now been uploaded to wordpress.org. This sees the debut of the ‘updates’ module.

• Tweak: Fix a few minor layout regressions in 0.4.0
• Fix: Fix a JavaScript error in 0.4.0 when checking updates on sites with none

0.4.0

• Feature: Management of updates (for plugins, themes and WordPress core)
• Feature: The UpdraftPlus module now includes the Rackspace setup wizard (when the add-on exists on the controlled site)
• Compatibility: Marked as compatible with WP 4.6
• Fix: Modals were not showing when in fullscreen mode (regression in 0.3.6)
• Fix: Restore the ability to communicate with WP versions older than 3.5 in certain modes (regression in 0.3.8)
• Tweak: Route communications via admin-ajax.php in the back-end, instead of index.php, to avoid issues from security plugins that intercept on index.php.
• Tweak: Store the last time that a user loaded their dashboard as usermeta
• Tweak: Update bundled UDRPC library to 1.4.8
• Tweak: Integrate new WebDAV configuration mode from UpdraftPlus
• Tweak: Re-worked template loader, to make it possible/straightforward for external modules to use Handlebars
• Tweak: Straighten out some incorrect use of error codes
• Tweak: Update bundled Labelauty version to our patched (added accessibility) version
• Tweak: All JavaScript and JSDoc now linted
• Documentation: Finished adding JSDoc documentation to the UpdraftPlus control module

0.3.10

• Fix: Fix a JavaScript error when attempting to run the connection test since 0.3.8

0.3.9

• Performance: Small change to the JS API, such that listeners are now only registered when a tab is active, thus significantly reducing the number active
• Internals: The core JS library now has methods for browser-local storing and caching
• Tweak: The network timeout parameter was not being correctly passed through in all situations
• Tweak: Communications are now posted to a back-end URL, instead of front-end, because some plugins will only initiate relevant code (e.g. update checkers) on the back-end. Theoretically, some sites may need to remove and re-create their key, and/or adjust their advanced settings, if they are deploying different security measures (e.g. different HTTP password) to access the back-end.
• Tweak: In the connection test dialog, if there is an HTTP error code, then display more info about it
• Tweak: Strip out extraneous PHP debug output sent by remote sites that broke communications in more situations
• Tweak: Audit/update all use of wp_remote_ functions to reflect API changes in the upcoming WP 4.6. Amongst other things, this is required for UpdraftVault to work with WP 4.6+ (release expected August 2016).
• Tweak: When the remote site does not support a particular command, then report this more gracefully
• Tweak: Move to lazy-loading command on the client side as needed for a particular action
• Tweak: Update bundled UDRPC library to 1.4.7