The way the edit lock works now, if you …

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Denis de Bernardy 5:25 pm on July 22, 2009

That would be nice, yeah.
Andrew Ozz 7:21 pm on July 22, 2009

It’s currently renewed with the autosave XHR every 120 sec. Don’t think we need another AJAX specifically for the post lock, perhaps will be better to add something onbeforeunload that will remove it when the user navigates away or closes the browser (of course the “remove lock” XHR will not be sent when saving the post).
- Mark Jaquith 7:36 pm on July 22, 2009
  
  Yeah, that could work. Are onunload XHRs fairly reliable?
  - Andrew Ozz 7:41 pm on July 22, 2009
    
    Will have to test that more but the browser waits until “true” is returned to proceed with the unload (it’s not a typical DOM event), so don’t think there will be a problem sending the request.
- Aaron D. Campbell 8:44 pm on July 22, 2009
  
  If it’s already renewed every 120 seconds, couldn’t we just set the lock to expire in 150 or 180 seconds?
  - Mark Jaquith 9:49 pm on July 22, 2009
    
    Could do that in conjunction. I was going to suggest this as well, as a sole mechanism. But where this issue is a problem is on very active blogs with a lot of contributors. On such blogs, even with a maximum lockout of 2.5 minutes, they could run into it a lot.

Comments are closed.

Welcome!

Communication

Share this: