Where can I set the automatic check-in time?

Oh well i have to correct the README. The whole feature has been removed as it does not fit for the idea of "dont let people edit concurrently". That "checkin for ever" thing was just something completely different. More like a permission thing "i dont want other people to edit this node for some time". Well this is something for node_access or similar, not for "edit locking".

I think that timing out locks is an important feature, especially for my scenario where many wiki-like pages of a small size need to be edited (actually, proofread). If one user clicks ``edit'' and closes his browser or forgets about it, this would prevent another user from working on that page. Since these pages are small and would take an insignificant amount of time to edit, the user would either submit the page within ten minutes or never submit the page.

Simple things like browser crashes and bad network connections could leave certain nodes in need of an administrator's attention. The requirement that one ``never ever have editing conflicts'' is overkill for my use of your module ;-).

However, I think it's easy enough to call content_lock_release() from outside of this module to get the same effect.

ohnobinki is see your point. I will not implement this in content_lock just to seperate the cases. As you stated, you can easily create a submodule with a cronjob checking for expired locks. Iam not sure iam tracking the checkin time, but i could add this so you feature will work.

If you contribute it back, i will include it as a submodule.

thanks for the feedback

A submodule for this would be great! I'll be happy to test if someone works on one.

croryx: you may try the content_lock_timeout submodule by cloning the dev branch of http://github.com/EugenMayer/content_lock or grabbing http://ohnopub.net/~ohnobinki/tmp/content_lock_timeout.tar.bz2

merged into dev now, will be part of the 1.1 release.

released in 6.2.0 rather then in 1.1. 1.0 will be discontinued