We’ve learned the hard way that FrontPage 2003 CAN hurt you if you don’t know what it does under the covers. The biggest thing, is if you open a page and click save, the page is now unghosted and saved in the DB. This makes future UI changes very hard (for more info on ghosting/unghosting as well as information about why FP2003 can hurt you, see article #1 in the reference links below).
So… how do you fix a unghosted site? Here’s what we did…
We had a site which we modified the UI via FrontPage 2003. This made the site unghosted, which caused big problems. We backed up the unghosted site from production and restored it to a developer VirtualPC image. Then, I installed the GhostHunter webppart (see #3 below) which I used to reghost the unghosted pages. Once the site was ghosted again, we added the necessary images to the wpresources directory and created a new CSS file that modified the UI of the site. After making sure everything was in good shape, we did it again just to be safe (backup->restore->reghost->apply file changes) to make sure it would work in production. And sure enough it did, production is now 100% ghosted and has it’s own UI.
1. What you don’t know about Front Page 2003 can hurt you (site registration required, but it’s free)
1. Dustin Miller’s response: “In response to “Barry Kouda” and his MSD2D tip…”
1. GhostHunter; part of the Web Part Toolkit
Update 9⁄21 8:55a:Just finished reading (and commenting) on Maurice’s (yes, the same one of GhostHunter… [insert additional golf clap]) post addressing my comments here. A good read… yet someone else who really gets it.comments powered by Disqus