[wp-trac] [WordPress Trac] #31819: Shiny updates: more sophisticated locking

[WordPress Trac]

#31819: Shiny updates: more sophisticated locking
-------------------------------------+-------------------------------------
 Reporter:  DavidAnderson            |       Owner:  jorbin
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  4.2
Component:  Upgrade/Install          |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  shiny-updates has-patch  |     Focuses:  ui, javascript,
  dev-feedback close                 |  administration
-------------------------------------+-------------------------------------

Comment (by DavidAnderson):

 OK...

 I've just emailed both those addresses with a file autobackup.php. Install
 UpdraftPlus from https://wordpress.org/plugins/updraftplus/ , and then
 drop this file into <plugin_dir>/updraftplus/addons/

 This code was developed on the core trunk 6 days ago. It looks like there
 have been a few tweaks to shiny updates since then - so, it may not be
 100% working, but hopefully you'll see the method being used.

 Note that that file - autobackup.php - contains code for doing auto-
 backups in 3 distinct situations: 1) WP background updates 2) Traditional
 non-shiny updates 3) Shiny updates. i.e., plenty of the code in it is not
 relevant to this ticket. The method admin_footer_inpage_backup() is the
 one that outputs the JavaScript used to intercept and delay the update
 request whilst a backup is done - note that this JavaScript also is meant
 to run/work on older WP versions without shiny updates. (The actual code
 that does the backup on the back-end and monitors it via AJAX on the
 front-end is all in the free plugin - includes/updraft-admin-ui.js has the
 JavaScript in it, and admin.php has the AJAX handler; you can see it in
 action in another situation if you just press the "Backup Now" button in
 the settings page, Settings -> UpdraftPlus Backups).

 Finally - it'd be good if, on a different but related matter, the patch in
 #30441 could get into WP 4.2. That would also reduce a bit of hackiness
 when running an automatic backup in a different situation; specifically,
 just prior to automatic background updates.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/31819#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform