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

[WordPress Trac]

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

 * keywords:  has-patch ux-feedback => has-patch ux-feedback dev-feedback


Comment:

 Took a *very* rough first pass at improved post locking. If a post is
 locked (e.g., user2 is editing), if user1 attempts to save (either via
 autosave, by clicking the update button), the post is saved as a
 "conflicted revision" and the live post is not touched. Any changes to
 taxonomies, etc. will be ignored.

 If user1 is is an editor or greater (and has a "override_edit_lock" cap),
 he will have the ability to override user2's lock (AJAX) via link in the
 standard lock notification, in which case user2 will get an HTML5
 notification or JS alert, will automatically do an emergency autosave
 (which will be conflicted), and the post is reloaded with the lock.

 Also made times in the revision table relative, and now update live.

 Approach is analogous to how autosaves are handled, it appends
 "-conflicted" to the post_name.

 Again, *very* rough (will most likely break under anything other than
 ideal conditions), but thought I'd sketch out one possible approach.

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