Shared border question

[Susan]

With dial-up and disconnect problems, I have resorted to selective
publishing. I use the shared borders for links. I understood that shared
borders on a web page was like having two independent pages together? But
when I change the shared borders, I notice that every pages that has the
shared border must be published again. Is there anyway around this? I mean
to somehow point to code in one place so that only one change would have to
be uploaded?

My ignorance is probably showing, but thanks for information!

Susan

 

[Mark Fitzpatrick]

Susan,
Unfortunately not natively in FrontPage. This can be done on many
servers using Server-Side Includes (SSI). Some hosts though don't allow SSI
so this isn't always a good option (also, some web servers require special
file extensions like .shtml or on IIS servers it's done thorugh the ASP
processor so all files have to end in .asp). Basically, FP is forced to
follow the rules of the least common denominator, which means grabbing these
files and integrating them in design time. Even though you may not see the
code from the shared borde when you look at the HTML code in FP, you can see
it's there if you look at the HTML using another editor such as notepad.
You can see if your host supports SSI, but you'll have to enter all the SSI
commands and table by hand in each and every web page.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage

 

[Ronx]

This can be done with FrontPage, but only if
1) The server has working FrontPage extensions
2) You HTTP Publish the whole web (All pages) at least once.
3) Subsequent publishing is Changed Pages Only.

Item 3) will publish just the pages you changed. If you changed a shared
border, then only the shared border file will upload, the pages using that
file will be rebuilt on the server. But this will not work unless 1) is
true and 2) has been completed.

 

[Andrew Murray]

Yes if you change the contents within the shared border on one page, it changes
on all - that's why it's called "Shared" Borders. It is doing exactly as
intended.

If you want "two pages within one" try using the "Include Page" feature instead.
You design your main page; then as a separate,new page you make a page of what
you want "included" then on the original page, go to Insert > Web Component >
Included Content (or similar) then choose Include Page.

It is put into the page at the place you want, then you publish both pages, and
the 'included page' will show inthe original page.

I hope that makes sense.

 

[Wes]

A site I manage uses Shared Borders that are attached to about 600 pages.
Whenever I modify any shared border, only the shared border is published,
not any of the 600 pages. FP seems to make that happen when the page is
loaded in the browser.

 

[Stefan B Rusynko]

It is not the browser controlling it
Shared borders are saved as hard coded html in the pages using them
When you publish w/ FP in http mode, the FP SE publish the shared border and in the background resave all affected pages (w/ the SB
content hard coded in the affected pages) in the background

--




| A site I manage uses Shared Borders that are attached to about 600 pages.
| Whenever I modify any shared border, only the shared border is published,
| not any of the 600 pages. FP seems to make that happen when the page is
| loaded in the browser.
|
| | > Yes if you change the contents within the shared border on one page, it
| > changes
| > on all - that's why it's called "Shared" Borders. It is doing exactly as
| > intended.
| >
| > If you want "two pages within one" try using the "Include Page" feature
| > instead.
| > You design your main page; then as a separate,new page you make a page of
| > what
| > you want "included" then on the original page, go to Insert > Web
| > Component >
| > Included Content (or similar) then choose Include Page.
| >
| > It is put into the page at the place you want, then you publish both
| > pages, and
| > the 'included page' will show inthe original page.
| >
| > I hope that makes sense.
| >
| > | >> With dial-up and disconnect problems, I have resorted to selective
| >> publishing. I use the shared borders for links. I understood that shared
| >> borders on a web page was like having two independent pages together? But
| >> when I change the shared borders, I notice that every pages that has the
| >> shared border must be published again. Is there anyway around this? I
| >> mean
| >> to somehow point to code in one place so that only one change would have
| >> to
| >> be uploaded?
| >>
| >> My ignorance is probably showing, but thanks for information!
| >>
| >> Susan
| >>
| >>
| >
| >
|
|

 

[Wes]

Yes, what I was trying to say is that those pages are not uploaded to the
server, they are resaved on the server itself which is a much faster
process. Only the shared border(s) affected should be uploading. The OP
stated that FP was uploading all the affected pages. It shouldn't be doing
that so there is a problem there.
I think a recalc would help and a complete publish. Thereafter changed
pages only should keep FP on track. Maybe her manipulation of the files
somehow distracted FP.

 

[Susan]

Okay, my website was moved to server without FP extensions since we dropped
renewal for FP extensions. It fixed my problem with "smartquotes", etc.
which was due to quirky problem with their server. It is better than
fighting quotes, appostrophes, special symbols, etc. that the hosting
company refused to fix. (Any recommendations for hosting companies?)

Since there are no FP extensions, does that mean that all pages containing
changed shared borders will have to be uploaded?

 

[Thomas A. Rowe]

Yes, and also if you have use any of the FP run-time webbots, such as forms, then those will no
longer work.

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

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================