Summary: Formal workflow is designed to prevent editing, deletion or reversion of published content from skipping review
Author: Internet Development, ILRT, University of Bristol
- <http://www.ilrt.bris.ac.uk/>`_ at University of Bristol,
April 5th 2009
+ <http://www.ilrt.bris.ac.uk/>`_ at University of Bristol, th 2009
Formal workflow is designed for sites where there may be many editors
for whom unmoderated access to change live published content on the
skin should be added near the top of the editing layer's skins listing in the
- If this workflow is applied to an existing site
... then you may require the
+ If this workflow is applied to an existing site you may require the
<http://pypi.python.org/pypi/ilrt.migrationtool>`_ to use its utility for mapping
- existing content states from the old workflow to formalworkflow
+ existing content states from one workflow to another. Otherwise changing
+ workflow reverts objects to the new workflow's default state.
If you wish to use custom types with this workflow you will need to make them versionable
plone.app.iterate will not be available for them.
+ If formal workflow is applied to folders (as is the default profile setting) then types
+ without workflow such as images and files cannot be added or deleted by editors.
+ To fix this a slightly adapted version of one_state_workflow is also included for these
+ content types that allows for editors to modify this content unrestricted.
+ You can customize which types use formal_worflow, and hence enforce a review process,
+ via the the portal_workflow tool. You could also choose to only apply formal workflow
+ to the high profile parts of your site, via `placeful workflow
Changelog for ilrt.formalworkflow
(name of developer listed in brackets)
+ ilrt.formalworkflow - 0.5 Released - 10th June 2009
+ - Added a subclass of the iterate info viewlet to redeclare the security so that
+ editors can see it and find existing checkouts.
+ [Dave Mote, Washtenaw County Government]
+ ilrt.formalworkflow - 0.4 Released - 20th May 2009
+ - Added an adapted version of one_state_workflow to allow editors to add
+ and delete images and files. Since the default formalworkflow profile adds
+ formal_workflow to folders - blocking editor modification of unworkflowed types.
+ [Ed Crewe, ILRT - University of Bristol]
ilrt.formalworkflow - 0.3 Released - 5th April 2009
- Changed action names and templates to be less versioning orientated
- Find a
different way to allow permissions of objects to be used rather
+ Find a way to allow permissions of objects to be used rather
than those of their containers for delete, copy and paste.
Currently it uses a workaround that needs proxy manager then does a
manual permission check, within the skins.
Classifier: Intended Audience :: Other Audience
Classifier: License :: OSI Approved :: BSD License
Classifier: Operating System :: OS Independent
-Classifier: Development Status ::
4 - Beta
+Classifier: Development Status :: -