quote:

83,000

quote:

1. So far as I am aware, at the moment, the only reason that I have for making any change to the way that the site is set up and updated is to overcome the problem of FrontPage Extensions having gone down - assuming Fasthosts (who host my web site) tell me that they are unable to reinstall FrontPage Extensions successfully, or that I am likely to have ongoing problems with FPE.

quote:

2. You suggest that I consider moving to Experession Web. Is that because it should overcome the 'FrontPage Extensions' problem or for some other reason? Even if the number of _vti folders (whatever they are!) reduced, the number of files in my web would remail very much higher than Fasthosts recommend for a site using FPE. Fasthosts is the company that hosts my web site.

quote:

3. I had assumed that ExpressionWeb was really just newer release of FrontPage, and so it would need FrontPage Extensions to be installed on the server for my site, just as FrontPage does. But, are you tellimg me that if I started to use Expression Web AND used CSS, then FrontPage Extensions would not be needed?

quote:

4. Would it be likely to be easier for me to move to "Expression Web + CSS" than to move to "Dreamweaver + CSS". Which would you recommend? If I'm making such a change, I'd like to be sure that I make the right choice and don't regret it later.

quote:

5. You say that I might consider using some type of photo album, but in fact, I'm happy with the way that my photos are included on the web site. Adding the photos individually, myself, is not difficult and avoids the possible constraints that a photo album might impose - and it works so I'd prefer not to change it!

quote:

6. You say that it may take some time to convert to CSS, and say that" if a lot of the code is the same, a copy and replace might help". In fact I would hope that I don't have to go anywhere near the code.

I can see from viewing my www.edinphoto.org.uk web site on the internet at the moment, just how it looks without FrontPage Extensions working. Most of it is intelligibel, but it looks very untidy, and is missing some links at the top and bottom of pages.

If I moved to CSS, I would like there to be a simple way for me to tell CSS to follow the front page 'Style' that I am currently using. In particular, for:
- Aerial font to be used throughout the site.
- The lines at the top and bottom of my home page (images with links) to appear at the top and bottom of all pages.
If I could do that easily, it would go a long way to making my web site more presentable and usable for others.
How easy do you thing it would be for me to get CSS to achieve that?

font-family: Arial, Verdana, Helvetica, sans-serif;

<p style="font-family:'Times New Roman', Times, serif">Times New Roman</p>

<font face="Times New Roman, Times, serif">Times New Roman</font>

quote:

7. I'll take your advice on keeping a back-up copy of the site locally before doing anything major. In fact, I make all the changes to my site locally, then publish them periodically, and I keep copies of the site usually about 1,2,3 4,30 days ago, on my PC for back-up.

quote:

2. Thanks for the advice on possibly using a test site, but perhaps that will not be necessary because of the way I do my updating. I do all the updates on my local PC, then publish the updates at least daily, but I also keep copies of the web site at the end of the day (for each of the past few days for back-up). So if I publish, and don't like how it looks, I can go back to "yesterday's version" and publish again.

I think it quite likely that my site will not have its FrontPage Extensions working agian by the time that I try to make the move to Expression Web. So, I'll assume that when I make changes in Expression Web (to set the default font, set the background for pages, add borders) even if I don't get it right first time, the result is likely to be no worse than what is already on the site! I hope that's true.

quote:

4. You recommended use of 'include pages' rather than shared borders. I'll try to follow that advice, but I have a question (three paragraphs below).

I've already made a lot of use of include pages already on my site. They have worked well, and still seem to be working well despite the web site no longer having Front Page Extensions, so I assume they will continue to work when I move to Expression Web.

However, when I have added 'include pages' to the site, I've had to change each page individually to get it to use the appropriate 'include page'.

Q. Is there some way (perhaps on one of the CSS pages) to get Expression Web to add the top and bottom borders (as 'include pages') to ALL pages on the web with a single instruction to do so.

Inidentally, if I am able to use 'include pages' for top and bottom borders on the web site, that would have another advantage.

At present, if I click on a top or botom border while I'm updateing the web site, but forget to hold the CTL key down, FrontPage sometimes thinks that I have made a change to one of these borders. This can result in long delays before I am able to update and publish the site normally again Presumably this would not happen if the top and bottom borders have been set up as 'include pages'.

#navcontainer
{
width: 140px;
border-right: 1px solid #000;
padding: 0 0 1em 0;
margin-bottom: 1em;
font-family: Verdana, Lucida, Geneva, Helvetica, Arial, sans-serif;
background-color: #001F7A;
color: #333;
text-align: left;
}

#navcontainer ul
{
list-style: none;
margin: 0;
padding: 0;
border: none;
}

#navcontainer li
{
border-bottom: 1px solid #90bade;
margin: 0;
}

#navcontainer li a
{
display: block;
padding: 5px 5px 5px 0.5em;
border-left: 10px solid #001F7A;
border-right: 10px solid #001F7A;
background-color: #2175bc;
color: #fff;
text-decoration: none;
width: 100%;
}

html>body #navcontainer li a { width: auto; }

#navcontainer li a:hover
{
border-left: 10px solid #1c64d1;
border-right: 10px solid #5ba3e0;
background-color: #2586d7;
color: #fff;
}

quote:

TESTING: Coreybriant: I'll read your comments about creating a sub-web, again if I feel that I need to do that, but I'm at about the limit of my understanding with just the one web!

quote:

ORIGINAL: Peter

However, the error message: "The web site contains folders used by FrontPage Extensions but you are updating it via FTP ..." did not appear to give me the option to say "OK but publish anyway".

quote:

ORIGINAL: coreybryant

If the hosting company is having problems (re)installing the FPSE and you are on Windows, ask them to remove the FPSE. And then, if any _vti folders are in the website, delete them. The hosting company will have to do this or you will need to use an FTP client (like FileZilla) to see if these folders are there. Once these files are deleted, re-install FPSE.