Warning message when publishing my site

  • Thread starter Thread starter Chris
  • Start date Start date
C

Chris

When I publish my site to my remote web site, a "Publishing FrontPage
Components" dialog box appears, stating:

"The following pages in your web site contain link bars or navigation bars
that use new formatting options. They will not display properly because the
server you are publishing to does not support these features."
<List of files>
"To enable link bars, publish your Web site to a server running the latest
version of the FrontPage Server Extensions or SharePoint Services."

The choices are "Ignore and Continue" and "Cancel".

The web hosting company assures me that I'm publishing to a W2K3 Server with
the appropriate services installed. I've been selecting "Ignore and
Continue". My link bars are working fine, so I'm not too concerned. But what
is causing this error? Is this common with many web hosting companies?
 
Somehow your FP META data does not recognize the Win 2003 Server as having the FP2002 SE
Before opening FP, in Windows Explorer Find and delete all hidden *.web files
Usually in %USERPROFILE%\Application Data\Microsoft\Web Server Extensions\Cache

If that doesn't clear it open you online site in FP and publish to your PC

--




| When I publish my site to my remote web site, a "Publishing FrontPage
| Components" dialog box appears, stating:
|
| "The following pages in your web site contain link bars or navigation bars
| that use new formatting options. They will not display properly because the
| server you are publishing to does not support these features."
| <List of files>
| "To enable link bars, publish your Web site to a server running the latest
| version of the FrontPage Server Extensions or SharePoint Services."
|
| The choices are "Ignore and Continue" and "Cancel".
|
| The web hosting company assures me that I'm publishing to a W2K3 Server with
| the appropriate services installed. I've been selecting "Ignore and
| Continue". My link bars are working fine, so I'm not too concerned. But what
| is causing this error? Is this common with many web hosting companies?
|
|
 
Back
Top