Releases for Content locking (anti-concurrent editing)

Release notes

This release addresses some issues with the 6.x-2.7 security release and also also addresses some longstanding issues.

• Address a problem described in #1419142: on IE7 and IE8, Save Button displays "If you proceed all of your changes will be lost" message, but does Save properly. where saving the node triggered the “Are you sure you want to navigate away” Javascript popup, untested on IE.
• Issue #927356: When reverting a node to a prior revision, users' locks are disrespected by omaster: Enforce content locks when reverting nodes to prior revisions.
• Fix Issue #1505022: content_lock new version cancel button does not work by izmeez: cancel button does not work.
• Fix issue #1112092: Make Javascript confirmation popup when leaving node edit page optional by mshick: Make Javascript confirmation popup when leaving node edit page optional.
• Inform a content lock administrator of the owner of the lock the admin is breaking when the lock is broken.

Release notes

This release of content_lock primarily addresses a CSRF security issue whereby locked nodes can be unlocked by the user's browser without the user's intention.

As this is the first release in over a year, it also includes other minor bug fixes and touch ups which were accumulating in the development VCS repository:

• content_lock_timeouts submodule: The default lock timeout is now 30 minutes. This is overridable in content_lock's configuration page.
• Fix issue #1130220: Content is not unlocked when navigating away from the page (javascript error) by Zombienaute, halcyonCorsair: Content is not unlocked when navigating away from the page (javascript error) for nginx.
• Fix issue #1203812: Use drupal's Drupal.behaviors API instead of jQuery(document).ready() to support drupal7 overlays: Use Drupal.behaviors instead of jQuery(document).ready().
• Issue #1206370: Remove package="Drupal Wiki" from content_lock.info by agentrickard: Remove package="Drupal Wiki" from content_lock.info.
• Fix CSRF security vulnerability reported by Charlie Gordon (cwgordon7) by using tokens for action URIs. Original patch by @larowlan. Tokens are used to prevent an attacker from being able to guess the proper action URI to use in a CSRF for unlocking a node.

Module developers may be interested to know that API documentation is now accessible at drupalcontrib.org.

Release notes

First release supporting drupal7. Feature- and UI-equivalent to the drupal6 (6.x-2.x) versions.

Changes

• #1002788: Drupal7 port
• Start migrating API from API.txt to doxygen-able API.
• Miscellaneous touch-ups and fixes.

Release notes

This release finally fixes the cancel button issues, thank mikestefff for the patch. Now, the javascript “don't leave this page” popup's text is configurable which should help mitigate some complaints about our bad grammar ;-). A new hook was added for increased flexibility of determining whether or not a node is lockable, allowing a node's lockability to be controlled by more than its node type or rendering filters.

Bugs fixed

• #1092424: Make JavaScript alert text configurable
• #792800: Issues with cancel button form handling

Features

• #1046226: dynamically control lockability of a node

Notes

Because of policy changes bundled into the Great Git Migration, translation files are no longer distributed in content_lock's release tarballs.

Please continue reporting bugs and feature suggestions!

Release notes

Fixing up english string. Thanks Andre

Release notes

Fixed:#926258: Suggested fixes for Content Lock.

Minor fix

Release notes

Added: #762730: Integration with views franz, brunodb
Added: #821300: Remove all user-locks on logout EugenMayer
Added: #810764: Dutch translation brunodbo
Added: #798184: Popup settings EugenMayer
Added: #843100: Restrict Lock by Node Type or Format ohnobinki
Added: #792862: Where can I set the automatic check-in time? ohnobinki
Added: #764750: German translation FrankT
Added: #787482: Change wording in warning for locked node croryx

Fixed:#821302: Click on Edit tabs in edit form make node unlock nicomar31

This is a new milestone one the way of content_lock. Thanks to a lot of work out of the community we now have
- views integration
- you can now chose which node types you want to activate locking on
- you can activate a submodule to have automatic release of locking ( time-checkins)
- you have a API to implement your own logic when to skip locking
- User-locks are removed on user logout

A lot of fine-tuning in wording has been done. Also quiet some code-cleanup and documentation. Main goals were to simplify the code for better undestanding for reviews and maintainance.

Special thanks to Nathan Phillip Brink who triggered a lot of features, reviews the module and did quiet some work on it.

He will co-maintain this module and iam very glad to have in on-board already!

All early-adopters can upgrade. I have tested the module with quiet some edge cases and expect it to work stable. But i think 2.1 / 2.2 will be more rock solid

Release notes

Fixing: http://drupal.org/node/749798
Fixed: http://drupal.org/node/743114
Added: http://drupal.org/node/740752

Now a JS-Handler watches the user not to leave the edit page and asks for confirmation, if that happens. If the user confirms, he will navigation away but also the lock is removed (clear decision made). With that feature it wont happen again, that you press on back and lose all your content accidently :)

Protected against:
- Closing Browser
- Closing window
- Clicking a link

With this functionality this plugin is nearly a must, considered how many times i lose my content

Have fun

Release notes

Reworked cancel button fix. Added support for the user "delete button" and fixed order
Fixing non closing diff in button wrapper
Updated: Included the patch from Kars-T for the drupal_schema_api
Updated: Using drupal_write_record for all updates/inserts
Added: Added the first simpletests for testing this module

Updating is recommended.