[wp-trac] Re: [WordPress Trac] #6043: Post Edit Collision Detection
WordPress Trac
wp-trac at lists.automattic.com
Fri Feb 29 23:53:22 GMT 2008
#6043: Post Edit Collision Detection
-------------------------------------+--------------------------------------
Reporter: mdawaffe | Owner: anonymous
Type: enhancement | Status: closed
Priority: normal | Milestone: 2.5
Component: Administration | Version: 2.5
Severity: normal | Resolution: fixed
Keywords: has-patch needs-testing |
-------------------------------------+--------------------------------------
Comment (by mdawaffe):
Some ideas josephscott and I brainstormed in no particular order.
XMLRPC ideas:
Make available a new XMLRPC method that reports the lock status for a
post.
Return an error when an XMLRPC client tries to edit a post that is locked.
----
Web ideas:
If you leave your browser open overnight, autosave will keep the lock
fresh indefinitely. Maybe add logic to expire locks that have been
refreshed so many times without any actual changes to the content of the
post. We could then send a message back to the overnight computer via
AJAX saying that someone else has edited the post and disable autosave on
that post.
If you're editing a post and have been warned that someone else is already
editing it, maybe to a JS AYS if you click save/publish/whatever as a
final warning.
----
General ideas:
Currently, locks are only tied to a user. We could tie the lock to a
"session" by storing some random string (found as a hidden field on the
post edit page or created and remembered by the XMLRPC client) so that the
same user can't stomp his/her post with multiple browsers and/or XMLRPC
clients.
----
These are just some random ideas. We haven't actually identified any
specific problems yet or decided if they need solutions :)
--
Ticket URL: <http://trac.wordpress.org/ticket/6043#comment:3>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list