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

[Alfredo <alfredo@xxxxxxxxxxxxxxx>]

> I tried to be grateful to Cobalt
> for such a neat
> free resource like the migration script but that's hard when you have to
> spend 12 unpaid
> hours vi'ing through script after script that the free tool broke.
> Sometimes it seems Cobalt goes out of their way to deliver stuff that ends
> up making our
> business lives a living hell. i.e.: patches that are pulled 5 hours after
> public posting.

Vi is a pretty demanding solution for this task; I'm shuddering as I 
picture you going through all those lines on your screen!

For the future, an alternative is using ftp to download the script 
pages to your own computer, using a good text program to do global 
changes on paths and urls and then ftping the scripts back up.

We run into this site migration problem all the time. I use BBedit (I 
have a Mac) but I'm sure there are similar programs for other 
platforms and these do global changes on entire directories (or 
folders in a Mac). I just go site by site and it asks for 
confirmation of every change so you can't screw it up too easily. You 
just do a change from the previous url and path to the new one and, 
of course, those scripts using relative urls and paths aren't going 
to be affected (since they don't have the old uls and paths in there 
in the first place).

BTW, relative paths used in personal web pages (the users' ones in 
virtual domain directories) seem to choke the script since the script 
starts looking at the top directory of each virtual domain (i.e. 
/web). If a user is doing cgi in his/her user directory, he or she 
has to use full paths and full urls in any configs and calls. Haven't 
figured out a way to address that problem so we just advise users to 
do it that way.

Alfredo
--
People-Link/Institute for Mass Communications
www.people-link.org
Communications for a Better World...and for the People Who are Building One!
Members, Local 1180, Communications Workers of America, AFL-CIO