| Author |
upon saving Frontpage inserts multiple <body> tags
|
|
| BrantP 2005-12-29, 5:55 pm |
| Multiple <body> tags triggers multiple sets of borders. Frontpage 2003
inserts another tag each time the page is saved. We have a windows 2000
server and the Frontpage extensions are current.
| |
| Thomas A. Rowe 2005-12-29, 5:55 pm |
| Check your html code for your border pages and regular page to be sure that you have all opening and
closing tag sets.
--
========================================
======
Thomas A. Rowe (Microsoft MVP - FrontPage)
========================================
======
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
========================================
======
"BrantP" <BrantP@discussions.microsoft.com> wrote in message
news:E989CB2D-FFB4-4A07-9ECD-2B1F97A62599@microsoft.com...
> Multiple <body> tags triggers multiple sets of borders. Frontpage 2003
> inserts another tag each time the page is saved. We have a windows 2000
> server and the Frontpage extensions are current.
| |
| BrantP 2005-12-29, 5:55 pm |
| In fact i found a stray <body> tag toward the end of the Shared bottom
border page. That seems to have fixed the problem. THANKS! It was creating
havoc on any page i opened. Now how did it get there?
"Thomas A. Rowe" wrote:
> Check your html code for your border pages and regular page to be sure that you have all opening and
> closing tag sets.
>
> --
> ========================================
======
> Thomas A. Rowe (Microsoft MVP - FrontPage)
> ========================================
======
> If you feel your current issue is a results of installing
> a Service Pack or security update, please contact
> Microsoft Product Support Services:
> http://support.microsoft.com
> If the problem can be shown to have been caused by a
> security update, then there is usually no charge for the call.
> ========================================
======
>
> "BrantP" <BrantP@discussions.microsoft.com> wrote in message
> news:E989CB2D-FFB4-4A07-9ECD-2B1F97A62599@microsoft.com...
>
>
>
| |
| Thomas A. Rowe 2005-12-29, 5:55 pm |
| Glad to hear the you solve it. I don't have a clue how the extra and/or missing tags happen when
using Shared Borders. For more flexibility, consider switching to FP Include Pages.
--
========================================
======
Thomas A. Rowe (Microsoft MVP - FrontPage)
========================================
======
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
========================================
======
"BrantP" <BrantP@discussions.microsoft.com> wrote in message
news:35ACCD36-55E7-476E-8880-22881FBBA9CB@microsoft.com...[vbcol=seagreen]
> In fact i found a stray <body> tag toward the end of the Shared bottom
> border page. That seems to have fixed the problem. THANKS! It was creating
> havoc on any page i opened. Now how did it get there?
>
> "Thomas A. Rowe" wrote:
>
|
|
|
|