Hi
I have just gone through a number of migrations/upgrades from 2.0.3
to 3.0.6. For the most part it was successful with a couple of
exceptions. The sites I migrated however were NOT heavily customised. My
steps were the following
1. Create a test server with instances of plone 2.0.5, 2.5.5 and 3.0.6
2. On the production plone server I used the export functionality to
export .zexp files for each plone site. I did this because I was doing a
little consolidation of the sites. I only had a few ~6 but they were in
different Data.fs files and I wanted to put them all together for easier
management.
3. On the test server in the plone2.0.5 instance I made sure I had all
the same 3rd party products as I had on the plone-2.0.3 production
server. This was easily done by just rsyncing all the 3rd part products.
I imported the .zexp instances and did the trivial migration from 2.0.3
up to 2.0.5
4. I then went through and uninstalled all 3rd party products I found
that were not being used by the sites. For example I had Zwiki
installed but only on one site. I knew this because I used the Find tab
in the ZMI for each site and looked for all Zwiki pages. IF I did not
find any for that site I uninstalled ZWIKI for that site. I did this for
all 3rd party products installed for each site. It was time consuming
but it cleaned up my sites. Also not many products are yet supported in
plone3 CMFBOARD which we were using is not even supported in plone 2.1,
So I had to leave all that behind.
4a. If you see a site with portal Transforms installed in your plone
2.0.5 site uninstall it first otherwise I got problems with missing
files that had been uploaded when I upgraded later on. I also found the
order in which you uninstall some products also mattered due to
dependencies. It was a long process and as Nick mentioned you will start
wishing you had never started using plone. I was always hesitant to put
all my docs into a binary ZODB database to begin with (this just comes
from my own inadequacies using Zope). I like flat filesystem based ascii
files. But it will be worth it in the end.
5. I then exported each site as a .zexp file and imported it into the
plone2.5.5 site. Did the migration etc. you also might have to do a
ATcontenttype migration as well.
6. IN going from plone 2.5.5 to plone 3.0.6 I found I had to add a mime
type in the mimetype registry for text/x-web-intelligent. I can provide
instructions for this if you get this error when you try importing into
plone3
7. I then exported the site as a .zexp again and imported it into
plone3.0.6 and did the migration up.
9. This all took me about a week since the process was quite iterative.
In the end there was only one site I could not migrate.
10. The one outstanding issue I have is that some files that were
uploaded seem to be missing there mimetype info in plone3. This happened
in the migration from 2.5.5 -> 3.0.6 and all uploaded files know get the
name "File" when you try do download them. I have posted this, on the
plone-users list a few weeks back several times but it has not been
resolved. Nor is it localised to my experience. I have a colleague also
using plone and he experienced the same problem.
Anyway. This is a bit long but if you have specific questions I can try
to help out. But as Nick mentioned your success will depend on how much
customization and dependency on 3rd party products each site has. Try
to eliminate these first before you attempt a migration.
Steve
peyyetir wrote:
Hello,
Need some help in upgrading Plone from 2.0.5 to 3.0. I belive that upgrade
from 2.0 to 2.1 is a major upgrade. I just wanted to know if I can upgrade
from 2.0.5 to 3.0 directly or do I have to upgrade from 2.0.5 to 2.1 to 2.5
and then 3.0. Which path would be a better option? Can somebody provide some
pointers here?
If anyone has done the upgrade from 2.0.5 to 3.0, please let me know.
Thanks,
Rohit
_______________________________________________
Setup mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/setup
