On Nov 3, 2009, at 5:03 PM, Phillip Abramson wrote:
Hi all,
Here’s what I want to do: I have an intranet site for my
organisation currently up and running which I would like to upgrade.
The current site is Plone version 2.0.5 (with 5Gb of data) and I
would like to take it to one of the more recent 3.x versions. I have
a server for a test site and then a development site which have an
instances of the newer Plone version installed on each. I’ll just
muck around with the test for Plone exploration and the development
one will have stuff migrated to it.
I’m running on the assumption that to do so I need to first do an
intermediary upgrade to either 2.1 or 2.5 and then upgrade to 3.x. I
have read the upgrade guide on plone.org but I think this makes too
many assumptions about the reader’s abilities. I am completely new
to Plone myself.
Not sure what you mean by this criticism of the upgrade guide. Are
you looking at the same document I see...
http://plone.org/documentation/manual/upgrade-guide ?
In any case, your assumption is correct.... upgrade to 2.5.x first,
then 3.x. This is also described in the guide...
http://plone.org/documentation/manual/upgrade-guide/version/upgrade-pre-2.5-releases-to-the-latest-release
The following is what I thought to be a legitimate way to proceed
1. Have installations of plone 2.5 and 3.x installed
2. Copy data.fs (just that file?) to where its stored in 2.5
replacing the old data.fs
3. Use the portal_migration tool -> migrate to convert the
content to 2.5 format.
4. Copy data.fs from the 2.5 location to the 3.x location and
doing the same.
These are the basic steps alright. But if you have third-party
products installed, modified templates, or other customizations, then
you will probably need to do a few more steps in addition.
I’ve been trying to first practice this with instances that I’ve
installed (using the windows installer) onto a virtual computer
utilizing some dummy data that I came up with on the fly. (All on
8080 but just one running at once).
When I did this from the 2.5 to the 3.3.1, start the 3.3.1 instance
and try to open up the ZMI it complains that it can’t access the
page. When I then chose to instead copy all four files data.fs,
data.fs.index, data.fs.tmp, data.fs.lock to the 3.3.1 instance it
says “we’re sorry but there seems to be an error” the provided code
matched this in the log:
2009-11-04T11:18:22 ERROR Zope.SiteErrorLog
1257293902.010.65774163263 http://localhost:8080/acl_users/credentials_cookie_auth/require_login
Traceback (innermost last):
... [snip]
Something about this url looks suspicious. How do you reach the Zope
root and where is the Plone instance relative to this root? A typical
Windows installation sets up two ports: port 8080 to reach the zope
root and port 80 to reach the plone subdirectory. The Plone site can
also be reached through port 8080 by navigating to the Plone
subdirectory.
It looks like you were redirected to
http://localhost:8080/acl_users/credentials_cookie_auth/require_login
which suggests that localhost:8080 gives you the root of your Plone
site not your Zope root.
The Plone login form (cookie-based login) may not work in a not-yet-
migrated site. I suppose sometimes the authentication credentials
from the previous install will "just work" with the new install but I
can imagine several situations where it will not. You probably need
to re-login using the Zope basic authentication process. This means
first figuring out the proper URL to reach the Zope root.
I can’t imagine how this might be important but just in case, when
using the virtual computer (via VMware, xp-sp3 installed on it, if
you’re interested), the buildout failed to access the servers to get
add-on products which I suspect to be a proxy issue since an
identical version with an identical buildout.cfg was used perfectly
well on my home computer. If this has no impact on upgrade or
migration then don’t worry too much as I don’t feel it will be an
issue using the server site.
Probably not relevant but did you check to see if the new Plone
install actually worked before replacing the virgin Data.fs with the
to-be-migrated version?
Ric
_______________________________________________
Setup mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/setup
