shared borders 2002/2003 issue

[Mark]

I have a few websites that were developed with FP2002. They use shared
borders.
I am about to upgrade to FP 2003 ( have it on my desk already). What will
happen if I open any of them in FP 2003? Will I lose the shared borders
functionality?
Mark

 

[Corrie Wiles]

Nothing should happen to your shared borders if you open your web in FP2003.
Dynamic web templates are definitely the way to go, I highly recommend
checking them out. Microsoft has removed the shared borders menu item from
the menus, but left the functionality intact. You can add the menu item
back to the command well easily. If you open a site that has shared
borders, the menu item will appear without having to add it back. You'll
only notice the item removed from the menu if you open a site that does not
have Shared Borders enabled (or a new site is created)


I have a few websites that were developed with FP2002. They use shared
borders.
I am about to upgrade to FP 2003 ( have it on my desk already). What will
happen if I open any of them in FP 2003? Will I lose the shared borders
functionality?
Mark

 

[Mark]

Thanks a lot.
Mark.

 

[Richard Jackson]

I recently upgraded to FP2003 and used the shared borders option in
previous versions, I found no problem, the shared borders still
function.

I have decided to go the dynamic template route, however, I have found
that when attaching the dynamic template to the page after deleting
shared borders the title tag is correct but my meta tags are no longer
on the page. Other than copy and paste has anyone any idea how I
retain the meta tags after attaching the template?

Richard

 

[Terry Crowley \(MSFT\)]

When applying a template to a page for the first time, FrontPage examines
which tags are in an editable region in the head of the template to
determine whether to keep them in the page or override them with the
template's version.

So, if there is some set of meta tags that you want to be different on each
page that uses a template, simply add a default version of those meta tags
to an editable region of the template itself. This way you can control in a
straight-forward way which meta tags are customized per page (e.g.
"Keywords") and which ones are enforced by the template (e.g.
"Content-Language" or "Content-Type").

Terry

 

[Richard Jackson]

Terry

Many thanks for advice, it works a treat.

Richard