Document Actions
Updating add-on products for Plone 3.0
Up one level
Plone 3.0 ships with new releases of Zope, CMF and Archetypes. When any framework updates, some things will be removed or changed. This is a list of the most common updates that need to be applied by product authors to ensure that their products work on Plone 3.0.
All content on one page (useful for printing, presentation mode etc.)
- General product development and migration tips for Plone 3.0
- CMFCore.permissions import syntax change
- Transaction module is no longer implicitly in Archetypes
- get_transaction module rename
- ContentFactoryMetadata deprecation
- Update your workflows to use GenericSetup profiles
- Searching users/groups via the Membership tool is deprecated
- Portlets have a new infrastructure
- main_template now uses Zope 3 viewlets
- Plone 3 does not create member folders by default
- Plone Tableless theme no longer exists
- Document Actions now use Zope 3 viewlets
- Products installing workflows may need to add permissions
- Indexes declared in Archetypes schemata need to be moved to GenericSetup
- The "Sharing" tab is now a global action
- Multi page schemas
- Enable inline editing (aka. QuickEdit)
Next:
General product development and migration tips for Plone 3.0
Previous:
Upgrading a Plone 2.5 site to 3.0
Previous:
Upgrading a Plone 2.5 site to 3.0
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.
Add roles for new permissions
Posted by
George Lee
at
September 4, 2007 - 07:07
If a third-party product adds a new permission, especially related to adding, viewing, or editing, make sure to grant Contributors and Editors the appropriate permissions upon the product's installation in a Plone site. See, for example, CMFPlone/profiles/default/rolemap.xml. In general Contributors should be granted "Add" and "View" permissions and Editors should be granted "Modify" and "View" permissions.
... and the Reader role too
Posted by
George Lee
at
September 4, 2007 - 07:11
for "View" permissions!
Talk about migration of actions
I'm hoping that by leaving a comment here about this specific issue, it will get re-worked into this manual. -darci hanning]
I was trying to update an old product, and had trouble with updateActions. I didn't find anything useful in
http://plone.org/documentation/tutorial/richdocument/migrations/ referenced from
[http://plone.org/documentation/manual/upgrade-guide/version/2.5-3.0/products/general-product-development-tips-for-plone-3.0/]
(first bullet in this section of the manual)
13:26 < neaj> lurker: you happen to know anything about updateActions in Plone
3.0? looks like it went away .. i'm trying to update an old
product and that's the 1st thing i fell over
[...]
13:28 <@wiggy> neaj: actions are part of the FTI in the generic setup profile
13:29 < neaj> OK so I should add "<action ...>" for what used to be in "actions
= .."
13:30 <@wiggy> indeed
13:31 <@wiggy> pretty much everything you used to configure in the class is now
in the profile
[...]
13:33 < neaj> it confused me that the actions for
ATContentTypes/content/image.py are way over in
CMFPlone/profiles/default/types/Image.xml
13:34 <@wiggy> CMFPlone has a base profile
13:34 <@wiggy> it includes the entire config for all products plone uses
13:34 <@wiggy> ATCT is weird though, its view templates are also in CMFPlone