Updating with Web Component

  • Thread starter Thread starter Latitude
  • Start date Start date
L

Latitude

We are using a web component "Included Content-Page" to place what we call
our Navigation Bar at the top of most of our web pages. Recently when we
'published' updates to they updates do not appear on the top of all the web
pages.

Here's a real live example:
The page is found at www.folkart.com/common/bar-1.htm. Today we added our
"what's new September" and 'published' the revised bar-1.htm.

The revised bar appears on some but not all of the web pages.

For example it is not appearing on http://www.folkart.com/home/africa.htm or
on http://www.folkart.com/home/usa.htm

But it is appearing on http://www.folkart.com/home/baby.htm and
http://www.folkart.com/home/amindian.htm

What is happening?

BTW we continue to get the following error when we 'publish' bar1.htm.
"The Server sent a response which FrontPage could not parse. If you are
trying to connecdt to a FrontPage Server, check with the Server's
Administrater to make sure the FrontPage Extensions are installed properly".

Could this be part of the problem? Our Service Provider says the server is
behaving normally, but they have no tools provided by Microsoft to know or
explain the cause of the error message. Besides the error message implies
that the problem is with FrontPage not handling a response from the server.
This does not appear to be the problem with the server. (the server is a
unix machine).

Also it takes 10 to 15 minutes for this update to take place. We have high
speed cable access so the long time is not because of a slow connection. Why
does this update take so long; when we update other web pages the update
happens in one to two seconds.?

Thanks, Cecil:)
 
Well Thomas, I did as you suggested. First we Recalculated Hyperlinks then
we republished the entire web site with the Change Page Only Option
selected. Some web pages still do not show the latest iteration of the
bar-1.htm. For example: http://www.folkart.com/home/usa.htm still shows the
older version of the bar.1.htm.

I can understand why it would be necessary to publish all web pages that
contain the bar-1.htm. But why would some web pages show the latest
interation and others not reflect the latest?

Thanks, Cecil:)
 
Cecil,

Not sure why this is happening, the only thing I can suggest, is on this
specific or other pages with this problem, is to open each in FP, and delete
the include, then save, then open and re-insert it.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================
 
I did the whole Recal Hyperlinks and republished the entire web site again
just be certain.

Got the same error message "The Server sent a response which FrontPage could
not parse. If you are trying to connect to a FrontPage Server, check with
the Server's Administrater to make sure the FrontPage Extensions are
installed properly". Is there any chance that whatever is causing this error
message is causing the problem?

Does anyone have any experience with this error message? Is there anyone
from Microsoft on the newsgroup that could shed light on what going on? I
recheck with our Service Provider and they assure me the FP Extensions are
installed properly and the unix server is and has behaved properly and
without incedent.

The concept of using the Include Page Component is to allow you to make a
change in one place and then have it promulgated throughtout the web site.
We have literally thousands of web pages on folkart.com and we can't go to
every web page to be certain it is getting the updated bar-1.htm page.

Help in finding the cause of the problem is needed. Any ideas from
anyone????

Thanks, Cecil:)
 
I used to get this sort of error myself. The server was actually timing out
when "processing updates" but the error message was as you get, and the
results similar.
The work around, until the host updated the server - more RAM, faster
processor, fewer websites on the server - was to split the web into subwebs,
and publish in the early hours of Sunday morning, when the internet was
relatively quiet.
HTH
Ron
 
Back
Top