You are here: Home Plone products Locking Workflow

Locking Workflow (0.2)

by Ihor Berehulyak last modified 2009-02-09
Released on 2005-09-29 by Raphael Ritz under Unavailable License available for All platforms.
Software development stage: alpha
Locking Workflow prevents concurrent editing in Plone.

The locking workflow is a simple two state workflow (unlocked and locked) restricting the edit permission in the locked state to the newly introduced Editor role.

Per default, nobody has this editor role but it gets assigned as local role to the current user as soon as (s)he invokes the edit action which also triggers the lock transitions which takes the content item into the locked state. Saving the edit form triggers the unlock transition which takes the content item back to the unlocked state. The unlock transition can also be triggered TTW like any other workflow transition.

The locking workflow can be combined with any other workflow as it exploits the fact that content types can be subject to several workflows at once.


When adding the locking workflow to a type in ZMI make sure that you also change the edit action of this type to invoke lock_and_edit, the form controller settings for the actions of lock_and_edit and the form controller settings of the method that invokes the view after successful editing (for Archetypes that's validate_integrity). If you add further types in the locking workflow's config file instead, a simple (re)install should take care of all of this.

Document Actions
Powered by Plone