Document Actions
6.4.1.
Upgrading a Plone 2.5 site to 3.0
Up one level
- To migrate from Plone 2.5 to 3.0, please follow the steps outlined in the General approach to upgrading.
- One thing to make sure you have right is that Plone is now not only files in the
Products directory, but also modules insidelib/pythonin your instance. If you're using the installers, this is taken care of for you, but if you're doing it manually, make sure thelib/pythoncomponents are in the right location.
Third party products
If you have installed and depend on a lot of third-party products produced by developers outside the Plone Team, it's hard to say something definite - make sure the products you depend on are certified to work with Plone 3. GroupUserFolder is NOT supported! (NOTE: It may not be possible to upgrade a site using GRUF with external user folders such as LDAPUserFolder. In those cases it is advised to create a new site and move the content over manually.)
If you have a big site running Plone and want a painless transition to the much-improved version 3, we suggest that you hire a company that can do the migration properly for you. Send a mail to the Plone Developer mailing list, and we can recommend a company in your area if needed.
Notes on Zope migration
Migration from Zope 2.8.7 or 2.9.5 to Zope 2.10.x is mandatory but Plone 3 does not run natively on Zope 3. If you are upgrading from Zope 2.8.7 and you have a separate Five product you need to delete the Five product from your product directory before your upgrade.
Zope 2.10.x requires Python 2.4.3+ (Python 2.4.2 is still acceptable). Also mandatory is Python Imaging Library 1.1.5 or newer, Python ElementTree.
Caching
* Caching related changes required (or maybe none!)
procedure for 2.5.x to 3.0.x
Is this something that might be helpful here (or elsewhere as a separate guide), or is it too much detail or too specific to one environment?
re: procedure for 2.5.x to 3.0.x
sure thing...
not sure until we've seen it
draft procedure created
http://plone.org/documentation/manual/upgrade-guide/version/2.5-3.0/updating-2-5-3-to-3-0.3/migration-procedure
No doubt this will need to be moved to the proper place in the manual if it's to be kept (not sure why it went where it did), and I'd need to add more detail afterward.
Installer Error on Windows
I get an error message on install of: PythonService.exe - Entry Point Not Found : The procedure entry point LogonUserExW could not be located in the dynamic link library ADVAPI32.dll.
This is then followed up this error message: pythonw.exe - Entry Point Not Found : The procedure entry point LogonUserExW could not be located in the dynamic link library ADVAPI32.dll.
From here it fails to start Zope and the few times it has started the service it will not allow me to do a migration; when I go into the ZMI and click on Plone it returns an error.
Any help would be appreciated as I am reinstalling the server now and have the back-up server going. I'd like to migrate while the server is down for hardware issues and bring it up clean without having to dump the DB and import it (don't know if that is even possible).
Thanks,
BT
www.indychampionshipseries.com
More info needed?
Is it possible that the "General procedure" is based on a previous Plone version, in which Plone was installed as a directory in /Products/ ? This procedure implies that the migrate process is simply: shut down; replace the existing, relevant Product directories with new ones; restart; and Upgrade/Migrate. I don't think that's the case anymore: for instance, porting over the database file isn't mentioned in the "basic manual procedure" checklist (it's mentioned in "Performing the migration," but that's not a step in the checklist).
The standard 3.0.2 installer for Linux doesn't permit installing "over" existing installations. And if you "trick" the installer into doing so (comment out the $PLONE_HOME check) in a Zeo installation, the cluster never starts afterward. Perhaps this should be explained somewhere, or discouraged explicitly, since "Performing the migration" in the general section seems to list this as the first of two available options for migrating ("Migrating your site content, products and customizations in-place").