PDA

View Full Version : Want to dump FrontPage, but how?



howdypez
07-10-2007, 07:41 PM
I searched and didn't find this answer...

I've been using FrontPage [I didn't know it was bad until I had built my sites]...

Now I want to switch to something else [Dreamweaver is too expensive, have downloaded Nvu and another one]...

Is there a way to load the pages I've done into a new editor without having to rewrite the entire site? I have 4 sites with about 30 - 40 pages and I just don't want to start over!!!

Thanks for any advice and/or help!!!

Stacie
www.cyfairironmen.org

bobdog
07-10-2007, 09:14 PM
You would need to learn how to write your own html. That would be a start.

Don't be afraid, you can do it!

Dreamweaver is nice and well worth the money. But I still edit my own source code all the time.

NVU could save you some headaches, but no substitute for writing your own code.

Oh Lawd, how many times have I taken a site built in FrontPage and cleaned up the source code...the code looked like it was written by a monkey on crank.

Necron99
07-10-2007, 09:16 PM
Is there a way to load the pages I've done into a new editor without having to rewrite the entire site? I have 4 sites with about 30 - 40 pages and I just don't want to start over!!!
www.cyfairironmen.org

There's not much you can do to strip out the Front Page gunk. You'll have to do that by hand (unless someone knows about a "de-FrontPager").

Use wget or HTTrack to copy your site to your local drive and then use any one of several infinitely better editors (Nvu, CoffeeCup, HTML-Kit, Arachnophilia, jEdit and-the-list-goes-on).

Dave

howdypez
07-11-2007, 07:57 AM
That's what I was afraid of :(

I volunteered to do the website for the lacrosse team [since my brother plays] and don't expect to be involved more than one more year... it'll probably take me that long to learn to code!

I'll see if the team will spring for a copy of Dreamweaver that we can pass along to the webmaster after me and so on... Hmmm... wonder if one of these kids knows HTML and would be willing to help recode the pages...

Thanks for the replies!

Stacie

jbladeus
07-12-2007, 06:24 AM
De-frontpager. :)
Now that product would sell and would make its creator a rich man alright.

Vegetta
07-13-2007, 11:45 AM
There's not much you can do to strip out the Front Page gunk. You'll have to do that by hand (unless someone knows about a "de-FrontPager").

Use wget or HTTrack to copy your site to your local drive and then use any one of several infinitely better editors (Nvu, CoffeeCup, HTML-Kit, Arachnophilia, jEdit and-the-list-goes-on).

Dave

There is a dreamweaver extension that will strip out frontpage garbage

http://www.adobe.com/cfusion/exchange/index.cfm?event=extensionDetail&extid=1010001

bobdog
07-14-2007, 07:24 AM
Yes, I have used this extention many times. It still leaves some garbage in the code anyway, but a good start and definitely a time saver.

wildwillie6
07-21-2007, 05:16 PM
I work at a college that uses FrontPage, so I manage my pages there with that -- and that made it a natural to use FrontPage for my Bluehost-hosted private sites. Our college will soon make a decision between MS Expressions Web and Dreamweaver CS3, so naturally I'll be leaving FrontPage behind before too long.

However, during the transition I need to keep using FrontPage, and it's gotten rather squirrelley at Bluehost lately. So I have some questions:

Can I really use the home directory backup like a "snapshot" to save and restore a working configuration? (Like Windows System Restore, only it would work?) Or does FrontPage do funny things so that even a complete backup and restore of a working configuration -- before changing any files -- would leave a non-working configuration?

Here's my story: I used FrontPage at home and at work with little difficulty the first couple of years since I came over from www.addr.com . Long ago I did my first "publish to web using FP extensions" on each of those sites. Then I would only open and save files, operating live from the server. Now Bluehost support tells me the reason sites were messed up this morning was that I "published using FTP." Maybe I did, but not knowingly . . . in fact, it had been years since I had "published" at all since I was only opening and saving files.

I didn't pay much attention to FP versions, but it turns out the one that caused all the trouble was FrontPage 2000 on my computer at home, obviously an older computer. Yet it opened and saved files without corrupting the FP extensions for a long time.

While I'm transitioning away from FrontPage, is there any advice about how to keep it creaking along? (Can I really mess up the FP extensions just by opening and saving files the way I did all along?)

And, final note: Hats off to Bluehost tech support for sticking with me until we got the sites working again. (Example: see www.plainmoney.com ).