[wp-trac] [WordPress Trac] #15130: Lock is not set to correct user until there is a save

WordPress Trac wp-trac at lists.automattic.com
Sun Oct 31 20:58:40 UTC 2010


#15130: Lock is not set to correct user until there is a save
--------------------------+-------------------------------------------------
 Reporter:  lancehudson   |       Owner:             
     Type:  defect (bug)  |      Status:  new        
 Priority:  normal        |   Milestone:  3.1        
Component:  Editor        |     Version:  3.0        
 Severity:  normal        |    Keywords:  needs-patch
--------------------------+-------------------------------------------------

Comment(by duck_):

 You can also reproduce with two users with essentially the same steps.
 Update and save a post with the first user and logout. Wait until the lock
 expires and visit the edit post page with the second user without saving
 (to bump the lock) and then refresh the page. You can also bump the lock
 time and then be blocked from bulk and quick editing that post.

 We don't update _edit_last on every lock because of #12763.

 We can't clear _edit_last on every lock because that means that _edit_last
 is cleared every save. This will making it useless for
 get_the_modified_author (will not display anything) and will stop
 wp_check_post_lock from working as desired (i.e. returning an empty string
 instead of the ID of the last user) which in turn stops all current core
 code using wp_check_post_lock to stop functioning properly.

 The two 'solutions' I can think of: either we have a separate way to store
 the user on lock as suggested by lancehudson (or combine the ID into
 _edit_lock somehow) or don't show the name of the user currently holding a
 lock.

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


More information about the wp-trac mailing list