[wp-trac] [WordPress Trac] #24551: Post locking prevents collaboration

[WordPress Trac]

#24551: Post locking prevents collaboration
----------------------------+------------------------------
 Reporter:  johnbillion     |       Owner:
     Type:  defect (bug)    |      Status:  new
 Priority:  high            |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  ui-feedback     |
----------------------------+------------------------------

Comment (by azaozz):

 > "The shortcode I entered isn't working for some reason, can you take a
 look?"

 Still better to take over post editing in these cases imho. The problem
 with disabling the Post Locked dialogs is that nobody would know who has
 the lock. Going to a read-only Edit Post screen won't help as user B won't
 be able to make changes. If the post lock is ignored, user A (who opened
 the post first) would overwrite (autosave) any edits made by user B after
 user B closes the post.

 There is a [http://core.trac.wordpress.org/ticket/23697#comment:20 patch]
 to make superadmins "invisible" when viewing a post on a blog they are not
 a member of, followed by a discussion in
 [http://irclogs.wordpress.org/chanlog.php?channel=wordpress-
 dev&day=2013-04-17&sort=asc#m596550 #wordpress-dev] about it. The
 consensus was to leave that for plugins.

 The best solution here would be to have full collaborative editing.
 However this is very server-intensive. Every keystroke is send to the
 server and updates are pushed every few seconds to the browsers, so there
 are several simultaneous connections per second while the users are
 typing. I doubt we would ever be able to have this as default in core as
 there are even concerns about heartbeat "overloading" a shared hosting
 server with one connection every 15 sec.

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