Personal tools
You are here: Home → Documentation → Manuals → Plone Upgrade Guide → Version-specific migration procedures and tips → Upgrading Plone 2.5 to 3.0
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

Upgrading Plone 2.5 to 3.0

Up one level
Upgrading your site and your products from Plone 2.5 to Plone 3.0.

All content on one page (useful for printing, presentation mode etc.)

  1. Upgrading a Plone 2.5 site to 3.0
  2. Updating add-on products for Plone 3.0
    1. General product development and migration tips for Plone 3.0
    2. CMFCore.permissions import syntax change
    3. Transaction module is no longer implicitly in Archetypes
    4. get_transaction module rename
    5. ContentFactoryMetadata deprecation
    6. Update your workflows to use GenericSetup profiles
    7. Searching users/groups via the Membership tool is deprecated
    8. Portlets have a new infrastructure
    9. main_template now uses Zope 3 viewlets
    10. Plone 3 does not create member folders by default
    11. Plone Tableless theme no longer exists
    12. Document Actions now use Zope 3 viewlets
    13. Products installing workflows may need to add permissions
    14. Indexes declared in Archetypes schemata need to be moved to GenericSetup
    15. The "Sharing" tab is now a global action
    16. Multi page schemas
    17. Enable inline editing (aka. QuickEdit)
  3. Updating 2.5.3 to 3.0.3
    1. Migration Procedure
Next: Upgrading a Plone 2.5 site to 3.0 Previous: Upgrading from Plone 2.1 to 2.5  
by Alexander Limi — last modified April 25, 2007 - 20:42
Contributors: Martin Aspeli, Geir Bækholt, Sisi Nutt
All content is copyright Plone Foundation and the individual contributors.

Extra step: contentValues

Posted by Maurits van Rees at June 5, 2007 - 12:41
This is an issue not specific for Plone but for CMF, but as CMFCore.permissions is also mentioned as a step here, this is probably fine.

contentValues('my portal type') should be changed to contentValues(filter={'portal_type': 'my portal type'})

Otherwise you get an error. The above code works on Plone 2.5 and 3.0.

Okay, this might get messed up when submitting, but here is a traceback:

File "/home/maurits/instances/xm/Products/eXtremeManagement/content/Iteration.py", line 77, in startable
stories = self.contentValues('Story')
File "/home/maurits/instances/poi3/Products/CMFCore/PortalFolder.py", line 203, in contentValues
return [ item[1] for item in self.contentItems(filter) ]
File "/home/maurits/instances/poi3/Products/CMFCore/PortalFolder.py", line 189, in contentItems
return self._filteredItems(ids, filter)
File "/home/maurits/instances/poi3/Products/CMFCore/PortalFolder.py", line 154, in _filteredItems
filt = filt.copy()
AttributeError: 'str' object has no attribute 'copy'

Example changeset

Posted by Maurits van Rees at June 5, 2007 - 12:43
http://dev.plone.org/collective/changeset/43188

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