[wp-trac] [WordPress Trac] #18515: UX: better management of workflow in editor (joe is currently editing this post, etc.)

WordPress Trac wp-trac at lists.automattic.com
Tue Sep 27 19:04:12 UTC 2011


#18515: UX: better management of workflow in editor (joe is currently editing this
post, etc.)
------------------------------------+---------------------------
 Reporter:  azaozz                  |       Owner:  jayminkapish
     Type:  enhancement             |      Status:  reopened
 Priority:  normal                  |   Milestone:  3.3
Component:  Editor                  |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |
------------------------------------+---------------------------

Comment (by nacin):

 Replying to [comment:16 azaozz]:
 > Looking through 18515.diff there's still a possibility to have collision
 when the user reloads the edit-post page. The post meta is updated with
 the XHR and just few milliseconds later `wp_set_post_lock()` is called as
 the page is loaded again. The XHR always calls update_meta and loading a
 post always calls set_post_lock. We need to think of a better way.

 The XHR does not always update the meta, though. It will only update the
 metadata if the lock it is trying to cancel is still the current lock.  It
 does this atomically, so if the new page has already set a new lock, then
 the XHR will not. That's the whole crux of this patch. See the last two
 paragraphs in [comment:13 comment 13].

 > Also perhaps we can make the lock expiration faster. No need to wait 4
 min (AUTOSAVE_INTERVAL * 2), maybe AUTOSAVE_INTERVAL + 10 would be good.

 AUTOSAVE_INTERVAL is 60 seconds, so two minutes. I think it's fine for
 now.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/18515#comment:17>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list