nav bars (& sometimes themes) missing when published from FtPg 200

  • Thread starter John from Puget Sound
  • Start date
J

John from Puget Sound

Site working fine for months. I mess with one of the following (I've not
narrowed it down yet):
- Edit a generic page (i.e., not anything in nav structure)
- Reinstall FrontPage Server Extensions (2002?)
- Recalulate Navigation structure

And when I republish the site everything related to the theme does not show
up. Spending a couple hours messing with the above items (and usually also
now changing a minor element with the theme, forcing it to update) will
sometimes get things basically working -- except the navigation bars are
still not rendering!

I've had missing nav bars before & resorted to (completely!) destroying,
recalulating, republishing, resetting FtPg Extensions, then rebuilding the
navstruture and repeating all of the above.

Grrrr, any suggestions?!
 
J

John from Puget Sound

I see after browsing about the last ten pages of this forum that all the
shared borders (in _Borders/) have head & body tags. I'll try removing them
but suspect it may be mor ethan this...
 
J

John from Puget Sound

Forgot to mention I'm on FtPg 2003 w/ SP2 on XP Pro publishing to commercial
outfit with Windows Server 2003. I'm removing the <body> tags (that FrontPage
must have put htere itself!), but wnoder about the <html> & <head> tags too.
Are these border files just accessed using <#include file="myborder.htm">, or
is something fancier at work here?!

Thanks for all your fast replies to others!
 
J

John from Puget Sound

Yet more...
- _Borders with NO HTML, HEAD, nor BODY tags just don't display at all.
- _Borders with HTML & HEAD tags but NO BODY tags also fails to display.

BTW, the nav bars appear fine on my local machine - just not on the
published site: www.dignursery.com.
 
R

Rob Giordano \(Crash\)

How are you uploading, or Publishing your site to the server?


in message | Yet more...
| - _Borders with NO HTML, HEAD, nor BODY tags just don't display at all.
| - _Borders with HTML & HEAD tags but NO BODY tags also fails to display.
|
| BTW, the nav bars appear fine on my local machine - just not on the
| published site: www.dignursery.com.
|
| "John from Puget Sound" wrote:
|
| > Forgot to mention I'm on FtPg 2003 w/ SP2 on XP Pro publishing to
commercial
| > outfit with Windows Server 2003. I'm removing the <body> tags (that
FrontPage
| > must have put htere itself!), but wnoder about the <html> & <head> tags
too.
| > Are these border files just accessed using <#include
file="myborder.htm">, or
| > is something fancier at work here?!
| >
| > Thanks for all your fast replies to others!
| >
| > "John from Puget Sound" wrote:
| >
| > > I see after browsing about the last ten pages of this forum that all
the
| > > shared borders (in _Borders/) have head & body tags. I'll try removing
them
| > > but suspect it may be mor ethan this...
| > >
| > > "John from Puget Sound" wrote:
| > >
| > > > Site working fine for months. I mess with one of the following (I've
not
| > > > narrowed it down yet):
| > > > - Edit a generic page (i.e., not anything in nav structure)
| > > > - Reinstall FrontPage Server Extensions (2002?)
| > > > - Recalulate Navigation structure
| > > >
| > > > And when I republish the site everything related to the theme does
not show
| > > > up. Spending a couple hours messing with the above items (and
usually also
| > > > now changing a minor element with the theme, forcing it to update)
will
| > > > sometimes get things basically working -- except the navigation bars
are
| > > > still not rendering!
| > > >
| > > > I've had missing nav bars before & resorted to (completely!)
destroying,
| > > > recalulating, republishing, resetting FtPg Extensions, then
rebuilding the
| > > > navstruture and repeating all of the above.
| > > >
| > > > Grrrr, any suggestions?!
| > > >
| > > >
 
S

Steve Easton

I don't see references to shared borders, however I do see that a DWT has
been attached to the home page.

Have you made sure you updated the attached pages after you made changes to
the DWT??
This needs to be done on your disk based web on your machine, and then
publish to the server.

There is an issue with DWT pages updating properly on a server, or in IIS on
a local machine.
They only update properly in a windows 2003 server **If** the server has had
the extensions hot fix applied: Windows Server 2003 hotfix Microsoft KB
article 895193

Any other "server" version requires updating in a disk based web and then
publishing changed pages.

Or, opening all pages containing the DWT and then saving the DWT will
sometimes work.


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
J

John from Puget Sound

Oh ya. I definitely update all ~50 pages that rely on the DWT. Then I use
FtPg to "publish" all those chged pages to IIS on Win Svr 2003.

I've just checked
http://support.microsoft.com/default.aspx?scid=kb;en-us;895193 and I don't
think that is it. When I update the DWT, it does update (on my local machine)
all ~50 files. Then FrontPage definitely wants (& does) publish all ~50 files
to the server. I'm especially tracking default.asp, since that is the most
critical.

I left shared borders with HTML, HEAD and BODY tags in them - otherwise they
wouldn't display. I guess others had *multiple* BODY tags in each of the
shared border files.

Thanks for your ideas Crash & Steve!

Oh, I've also deleted all the navigation structure & rebuilt it from scratch
but that hasn't worked this time.

I guess I'll delete the DWT and rebuild it from scratch. Frustrating!

Thanks for any more ideas to check.
-J
 
J

John from Puget Sound

I prume using a generic FTP approach (or some hosts have a "upload this file,
upload that file" utility versus using Frontpage's Remote Site
Synchronize/Publish option. Right Rob?!
 
R

Rob Giordano \(Crash\)

Correctomundo.

Generally the word upload is used when people use a third party ftp client
to upload to the host. When you're using FP to upload via the http:// method
it's referred to as; Publishing. If your hosted website has FP extensions
(FPSE) enabled and working you should not use a third party ftp program to
upload files as it will break the extensions and things may not work, or you
may not be able to log into the website "live".

FPSE makes life easy if you follow the rules.


in message |I prume using a generic FTP approach (or some hosts have a "upload this
file,
| upload that file" utility versus using Frontpage's Remote Site
| Synchronize/Publish option. Right Rob?!
|
| "Jerome Ranch" wrote:
|
| >
| > >How are you uploading, or Publishing your site to the server?
| >
| > Rob
| > I fear I am missing something important..what is the difference?
| > Jerry
| >
 
J

John from Puget Sound

Yes it is easy - except when it breaks...

I almost had it working after creating virgin top and left borders, then
adding a navbar to both, then changing the "remote site" Publishing
Properties to publish all files, not just changed files. It displayed room
for the icons, but no actual pictures appeared. Then removing the navbar from
the left border (and a bit of extra text I had inserted in the top border and
a republish & it's back to where it was. 8-<

I'll retry the above some more, but also wonder if someone with things
WORKING could look at a local page and tell me if all the references are to
the local file system? (My ISP said this issue usually boils down to things
pointing to my local box, not the remote web site.) FOr instance if I
Preview my home page and then "View Source," I get the following:

[Note all the instances of file:///E:/]

<link rel="stylesheet" type="text/css"
href="file:///E:/www-local/www.DIG.com/style.css"/>
<!--mstheme--><link rel="stylesheet"
href="file:///E:/Documents%20and%20Settings/John.XP-PRO3/Local%20Settings/Temporary%20Internet%20Files/FrontPageTempDir/mstheme/-dig-sky-grn-bkgnd/-dig1011.css">
<meta name="Microsoft Theme" content="-dig-sky-grn-bkgnd 1011, default">
<meta name="Microsoft Border" content="tlb, default">
</head>

<body>
<table msnavigation border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td style="border-bottom: 1px dotted; padding-left: 1px; padding-right:
1px; padding-top: 1px; padding-bottom: 0px">
<!--webbot bot="Include" s-border="top" u-include="_borders/top.htm"
tag="BODY" startspan --><table border="0" width="100%" id="table1"
cellspacing="0" cellpadding="0" height="120">
<tr>
<td rowspan="2" width="151" height="150" bgcolor="#CCCC00">
<a href="file:///E:/www-local/www.DIG.com/Art-Mosaics.asp">
<img border="0"
src="file:///E:/www-local/www.DIG.com/images/ff_1085965.cropped175x174.jpg"
alt="Clare Dohna's Mosaic Eggs" width="175" height="174"></a>
</td>
<td bgcolor="#CCCC00"> <a href="http://www.DIGNursery.com">
<img border="0" src="file:///E:/www-local/www.DIG.com/images/DIG-Head.jpg"
width="642" height="100" alt="Visit DIG at 19028 Vashon Hwy. SW • Vashon, WA
98070 • 206.463.5096 • www.DIGNursery.com"></a>
</td>
</tr>

Is this right? If not how do I change it?!
 
J

John from Puget Sound

Nope it wasn't local vs server paths. It was delete & recreate the shared
borders, update everything - then copy over the _Derived folder (which
FrontPage designers hide even when you have "Show Hidden Folders" checked!).
This had the missing graphics.

Geese, what a pain, and there's still one button missing. All for a an area
I wasn't even touching.

For future reference, just reinstalling the FrontPage extensions appeared to
reliably delete everything used by the DWT/theme: things like nav bars, page
bakgrounds, etc.

Once one edited the DWT & rippled out the changes, then would the server
have what it needed to display (most) of the pages again.

Grrr. Now after wasting >10 hours on this, I can finally go back to my
project to install FreeTextBox...

FrontPage is great - but also a great pain in trying to hide & micromanage
what happens - when in this case I would have voted for transparency.

Thanks though to every one who had ideas for me!

John from Puget Sound said:
Yes it is easy - except when it breaks...

I almost had it working after creating virgin top and left borders, then
adding a navbar to both, then changing the "remote site" Publishing
Properties to publish all files, not just changed files. It displayed room
for the icons, but no actual pictures appeared. Then removing the navbar from
the left border (and a bit of extra text I had inserted in the top border and
a republish & it's back to where it was. 8-<

I'll retry the above some more, but also wonder if someone with things
WORKING could look at a local page and tell me if all the references are to
the local file system? (My ISP said this issue usually boils down to things
pointing to my local box, not the remote web site.) FOr instance if I
Preview my home page and then "View Source," I get the following:

[Note all the instances of file:///E:/]

<link rel="stylesheet" type="text/css"
href="file:///E:/www-local/www.DIG.com/style.css"/>
<!--mstheme--><link rel="stylesheet"
href="file:///E:/Documents%20and%20Settings/John.XP-PRO3/Local%20Settings/Temporary%20Internet%20Files/FrontPageTempDir/mstheme/-dig-sky-grn-bkgnd/-dig1011.css">
<meta name="Microsoft Theme" content="-dig-sky-grn-bkgnd 1011, default">
<meta name="Microsoft Border" content="tlb, default">
</head>

<body>
<table msnavigation border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td style="border-bottom: 1px dotted; padding-left: 1px; padding-right:
1px; padding-top: 1px; padding-bottom: 0px">
<!--webbot bot="Include" s-border="top" u-include="_borders/top.htm"
tag="BODY" startspan --><table border="0" width="100%" id="table1"
cellspacing="0" cellpadding="0" height="120">
<tr>
<td rowspan="2" width="151" height="150" bgcolor="#CCCC00">
<a href="file:///E:/www-local/www.DIG.com/Art-Mosaics.asp">
<img border="0"
src="file:///E:/www-local/www.DIG.com/images/ff_1085965.cropped175x174.jpg"
alt="Clare Dohna's Mosaic Eggs" width="175" height="174"></a>
</td>
<td bgcolor="#CCCC00"> <a href="http://www.DIGNursery.com">
<img border="0" src="file:///E:/www-local/www.DIG.com/images/DIG-Head.jpg"
width="642" height="100" alt="Visit DIG at 19028 Vashon Hwy. SW • Vashon, WA
98070 • 206.463.5096 • www.DIGNursery.com"></a>
</td>
</tr>

Is this right? If not how do I change it?!




Rob Giordano (Crash) said:
Correctomundo.

Generally the word upload is used when people use a third party ftp client
to upload to the host. When you're using FP to upload via the http:// method
it's referred to as; Publishing. If your hosted website has FP extensions
(FPSE) enabled and working you should not use a third party ftp program to
upload files as it will break the extensions and things may not work, or you
may not be able to log into the website "live".

FPSE makes life easy if you follow the rules.


in message |I prume using a generic FTP approach (or some hosts have a "upload this
file,
| upload that file" utility versus using Frontpage's Remote Site
| Synchronize/Publish option. Right Rob?!
|
| "Jerome Ranch" wrote:
|
| >
| > >How are you uploading, or Publishing your site to the server?
| >
| > Rob
| > I fear I am missing something important..what is the difference?
| > Jerry
| >
 
J

John from Puget Sound

SUMMARY OF ALL THE REST (up to time of this post):

Running FtPg 2003 SP 2 on Win XP Pro SP 2, Publishing to Win Server 2003

1) Reinstall Front Page Extensions on Server (for me) always caused Dynamic
Web Template (DWT) information (e.g., page background, shared borders) to
disappear from site.

2) To reinstall, I tried Tools | Recalculate Hyperlinks, then modify my DWT,
let it update all child pages, then republish. At this point the background
and shared borders would reappear, but navigation bar was blank (only on the
www, but was fine on my local development machine).

3) To fix:
a) back things up
b) use Format Menu | Shared Borders to remove shared borders from all pages
(I also manually the files in _Borders directory to be sure); reupdate DWT &
child pages
c) Recreate shared borders from scratch (editing in the HTML from my backed
up copy); reupdate DWT & child pages
d) then I had to MANUALLY FTP the changed files to my web server. Publishing
said it worked and would show some changes, but nav bar would not get sent
out (as if Optimize HTML - not in use though - would eat it).
d) then I had to MANUALLY locate & copy the hidden _Derived folders (using
FTP) to my web server. Otherewise the GIF images for the nav bar wouldn't get
out to the server. FrontPage has these hidden - even if you set the option
for show hidden files set. Grrrr!!!

So I've learned:
- NOT to trust FrontPage, especially its Publish functionality: it doesn't
necessarily do what it reports & doesn't handle hidden directories in all
cases
- Viewing "Files To Publish" does NOT show "Files in Conflict", so using
that to publish parts of your site at a time (to overcome "The server
unexpectedly closed the connection" errors)
- Instead use FTP, though many have (other) problems with that apparently too

There's proibably more, but enough on this 12 hour sidetrack...
 
R

Ronx

Please help me understand why you are using a DWT AND shared borders.
If you are using a DWT, the shared borders are not required, since the
DWT will incorporate everything in the shared borders anyway - or
should if you use them efficiently.

--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/

"John from Puget Sound" <[email protected]>
wrote in message
news:[email protected]...
 
J

John from Puget Sound

Well I originally was *just* using DWT, then after resetting the server
extensions (I don't recall what now, but something hadn't updated properly,
and a web search recommended this) and everything associated with DWT
dissappeared I started trying anything related to my issue. Ye olde
Blunderbluss approach, eh?

I presume that shared borders technology is incorporated into DWT (& that
they are not using distinct technologies), so it was an easy way to "force"
removal of the shared borders that had the missing navbars, i.e., to start
from a blank slate.

After using Frontpage on 10+ sites, since the early really 'interesting'
days, I've never had such issues with FrontPage publishing, which is what
this basically boiled down to in retorspect. I'm not aware of any unusual
network/software/hardware issues or changes that could have impacted things
either. Oh well, life as a developer!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top