[wp-trac] [WordPress Trac] #32202: Add support for options page locking (settings API concurrency)

WordPress Trac noreply at wordpress.org
Fri Jul 31 20:10:01 UTC 2015


#32202: Add support for options page locking (settings API concurrency)
-------------------------------------+------------------------------
 Reporter:  westonruter              |       Owner:
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Options, Meta APIs       |     Version:  3.6
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  administration
-------------------------------------+------------------------------

Comment (by azaozz):

 There are several things that need to be considered:
 - The removal of locks (AJAX on `unload`) doesn't work well in all
 browsers and in all circumstances. Sometimes the AJAX request doesn't
 fire, sometimes the browser aborts it. We need to look at improving
 it/making it more reliable.
 - To be able to do "take over", we may need to save the current user's
 changes somehow. Not all settings screens will need this but there are
 several where we wouldn't want to discard unsaved changes/loose the
 current user's data.

 One way this may work is by storing all form fields in session storage and
 restore on page reload. Another option is to show an "attempted take over"
 dialog with a cancel button instead of locking the screen.

 edit_lock.patch is a good start, but we will need to implement the above
 too. Also, not sure we need variable lock timeouts. That complicates
 things without adding any benefits. If we manage to fix lock removal, a 5
 min lock timeout would be good.

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


More information about the wp-trac mailing list