RE: [cobalt-users] Virtual Sites-Moving and Preserving Paths

["Carrie Bartkowiak" <admin@xxxxxxxxxxxxxxxxxx>]

||>There is no software
||>available today that can correct hard-coded paths without potentially
||>corrupting binaries or even regular code.
<snip>
||>So, THIS TIME, Cobalt is more or less innocent,

Jan,
I have to disagree.
If the migration software moved the sites *as they are* on the original box,
none of the hard-coded scripts would break. Site12 on the original machine
would be Site12 on the new machine, etc. etc.
If scripts are breaking, it must not be moving the sites like it *should*.
(Not "like it is supposed to", cuz I don't know how it's "supposed" to do
it.)

I'll be moving all of my sites to a new machine in a couple of days, and I
plan to do the whole thing by hand. Tarballing if I can, if not, then via
FTP down to my machine and up to the new machine. I've got a list of exactly
which site is which site#, and I'll add them into the GUI in that order.
Then I'll upload the site's stuff. That way, none of the scripts or
hard-coded anything will break. I'm also gonna have tons of lists of
permissions that I'll have to check and redo if necessary.

I anticipate it to be a pain, but it's the only way I can be absolutely sure
that my clients' stuff is just as it's supposed to be on the new machine. :(

Carrie Bartkowiak