Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Long name JavaScript Muddle
Message
 
À
30/04/2001 11:52:51
Information générale
Forum:
Internet
Catégorie:
FrontPage
Divers
Thread ID:
00494894
Message ID:
00501901
Vues:
20
>Do you know of a way to get around the problems you have encountered with FrontPage 2000.

I've only had minor problems trying to use FrontPage has a generic html editor for stuff that does not live within a FrontPage web. This is mainly because FrontPage tries to second guess you and sometimes will make bogus changes to your markup. My solution was to find a better generic html editor. IF you want to use FrontPage to manage a non-frontpage project, you got to get use to nuances and hassles and figure your way around all the stuff FrontPage likes to screw up.

>Currently I have inherited a site that was developed using FrontPage 2000 and everytime any changes occur the site breaks. I account this to FrontPage and would like to remove the front page extentions.

It sounds like you didnt setup the local copy of the FrontPage web correctly (something that's not documenting very well either). Best way to do this to create a new empty project on a local drive. Then open the live root web on the internet web server and publish it to your local project to make a fool proof working copy. Then close all frontpage windows and reopen your local web project (crucial step - some of the mucking around frontpage does when creating a new project from an existing one isnt visible until your close & reopen).

If you really want to pull the website off of frontpage completely, your better off using a different tool to import and maintain the website. You can then re-engineer all pages that had a dependency on FrontPage extensions... stuff like forms, shared borders, include files, anything theme based (biggest mess of all). When your ready to publish the new version, have FrontPAge extensions removed from the web server, wipe out everything from the old version, then upload a fresh project.

And one last all important tip - if you need to salvage a local web project that seems to have gone totally haywire, and you cant do the above suggestion for creating a fresh local copy by publishing from the live root web... Turn off your local web server service, then go into windows explorer and delete all the wacky underscore subdirectories. Then open the web project, go to reports view, and run all the hyperlink related reports (fix errors, close frontpage, reopen & run next report) and component error report. HTH.
Roxanne M. Seibert
Independent Consultant, VFP MCP

Code Monkey Like Fritos
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform