RE: [cobalt-developers] CMUImport and FrontPage Ext

["Or-Or" <or-or.list2@xxxxxxxxxxxxxx>]

I have been migrating several thousand sites from raq3's to raq550's over
the last six months. 90% of the sites implement FrontPage extensions. It is
a pain in the a$$.

My work around for this problem is to export/import the site as usual.
Delete all files from the web directory and then reinstall FrontPage
extensions on the new server. Next, ftp all the web files from the old
server to the new one excluding the FrontPage garbage (_vti* directories and
postinfo.html). Then, just change all the file permissions back to nobody
(chown -R nobody.site123 /home/sites/www.foo.com/web).

I have been able to automate this process with a few bash and perl scripts.
If anyone knows of a better way, please let me know.

Regards, 

Chris

-----Original Message-----
From: cobalt-developers-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-developers-admin@xxxxxxxxxxxxxxx] On Behalf Of Kham Vue
Sent: Friday, January 16, 2004 9:24 AM
To: cobalt-developers@xxxxxxxxxxxxxxx
Subject: [cobalt-developers] CMUImport and FrontPage Ext


When using CMUExport/CMUImport to export a virtual site from one RAQ to
another (RAQ4 to RAQ4), we're finding that sites with FrontPage extensions
do not transfer correctly? Especially the navigation bar and the banner
bars.

Our solution so far is to create www2.site.com on the second RAQ server,
open on www.site.com with frontpage, then publish www.site.com to
www2.site.com.  This works, but if we restore from the CMU in the case of an
emergency, the navigation and banner bars are missing?

Anyone got a solution for this?

Kham Vue
Wadsworth Internet Service

_______________________________________________
cobalt-developers mailing list cobalt-developers@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-developers