UpdraftCentral 0.4.1 has now been uploaded to wordpress.org. This sees the debut of the ‘updates’ module.
Here’s the changelog since the last wordpress.org release (0.3.6).
* 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 – 04/Aug/2016 =
* 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 – 15/Jun/2016 =
* FIX: Fix a JavaScript error when attempting to run the connection test since 0.3.8
= 0.3.9 – 07/Jun/2016 =
* PERFORMANCE: Small change to the JS API, such that listeners are now only registered when a tab is active, thus signifiantly reducing the number active
* INTERNALS: The core JS library now has methods for browser-local storing and cacheing
* 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
Just set this up on one of my sites, early tests are very positive, but ran into a security issue with a WP plugin, Pareto Security. It must be deactivated to allow site access. This will probably be a killer for using this app on my sites, as we have used Pareto security on ecommerce and various CMS sites for many years, and incorporated it into our WP sites we manage from the time a plugin became available. If a solution can be found, fine. If not, I will not be able to continue using your dashboard as my control center.
Hi George,
Thanks for your interest in UpdraftCentral! Realistically, given that that plugin has only 100 active installs, we’re unlikely to be able to investigate that conflict any time soon. We’ve tested UC against the 4 most popular security plugins, but these have tens and hundreds of thousands of active installs. You could try liaising with the developer of that plugin to work out exactly what it doesn’t like, if he’s willing to help you.
David