Personal tools
You are here: Home → Documentation → Manuals → Plone Upgrade Guide → Version-specific migration procedures and tips → Upgrading Plone 2.5 to 3.0 → Updating add-on products for Plone 3.0 → Products installing workflows may need to add permissions
Support

Get Help

Join our chat rooms or support forums if you have more specific questions.

Plone Training
Learn how to design, build, and deploy a website in Plone through one of the numerous Plone training sessions around the world.
Find Plone training…
 
Document Actions

6.4.2.13. Products installing workflows may need to add permissions

Up one level
If your product wants to make use of the new "Editor" role that ships with Plone 3, you will have to add explicit permissions to any workflows you add.

The new "Editor" (aka. "Can Edit" on the Sharing page) in Plone 3.0 makes it easy to let people collaborate on content authoring. In some cases, editing also means the ability to add new objects inside the object people are editing.

For this to work, third party content types that add custom workflows will have to either use one of the standard "add content" permissions or explicitly give Editor the Add portal content role.

See Ticket #6265 for the changeset and full explanation.

Next: Indexes declared in Archetypes schemata need to be moved to GenericSetup Previous: Document Actions now use Zope 3 viewlets  
by Alexander Limi — last modified April 25, 2007 - 20:44
Contributors: Martin Aspeli, Geir Bækholt, Sisi Nutt
All content is copyright Plone Foundation and the individual contributors.

For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by