Copyright symbol in Webbots wrong

[Guest]

I find that the copyright symbol does not render on Web pages from the webbot
use of the copyright character in it's borders. Is there a way to stop the
Webbot from using the character and instead use the copyright HTML code?

 

[Thomas A. Rowe]

Insert the code that you want.

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

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

 

[Guest]

<h5>Copyright © 1999 - 2005 <a href="http://www.ycoln-resources.com"> Thomas
A. Rowe (Microsoft MVP - FrontPage)</a>.&nbsp; All rights reserved.<br>

 

[Guest]

Gee, Tom, then the next time it regenerates the page border it overwrites
what I changed manually, so what am I missing?

 

[Thomas A. Rowe]

I have never had a problem with using FP to insert the copyright symbol. Where are you insert this,
in your navigation title, etc., as the shared border is not regenerated unless you delete it.

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

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

 

[Wes]

Exactly what does this mean Thomas "the shared border is not regenerated
unless you delete it"

 

[Thomas A. Rowe]

Wes,

Very simple, once you apply a theme or add a shared border to your site, FP will create the top.htm,
bottom.htm left.htm or right.htm file and place in the hidden _borders folder, there after FP does
not regenerate the file, however if you add FP navigation component, then if changes are made to the
navigation structure the navigation component will regenerate the links.

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

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

 

[Wes]

Sorry, I don't follow.

When I modify an already created shared border, whether opening it directly
(from the _borders folder) or in any page that has the shared border
applied, FP does regenerate the file and prompt to save on exit.
Am I missing the point here? Maybe the Coors effect.

 

[Thomas A. Rowe]

Must be the Coors... so are saying that if you open _borders\top.htm and make a change, then save
the page, that FP deletes the change you have made and recreates the page the way it was before you
made a change?

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

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

 

[Wes]

No, you said "the shared border is not regenerated unless you delete it"
I would like to know what that means. I hoped my thread was clearly stated,
but you didn't get it. What do you mean by REGENERATED? As far as I'm
concerned, that means that FP changed *something*. How do you consider that
it "if you open _borders\top.htm and make a change, then save

the page, that FP deletes the change you have made and recreates the page
the way it was before you made a change?

Where did that come from? Doesn't make sense.

 

[Thomas A. Rowe]

The original poster used the word "Regenerated" and I think I did ask what they meant.

If you delete a shared border file, then FP should recreate the file when you recalculate hyperlink
as long as you have shared borders enabled within the site.

However, as long as the shared border file is in the web, FP will not regenerate it, it will however
regenerate any navigation component, if used and changes are made within the navigation structure of
the site.

Better?

Disregard

"if you open _borders\top.htm and make a change, then save the page, that FP deletes the change you
have made and recreates the page the way it was before you made a change?"

as you are correct it doesn't make any sense!

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

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

 

[Wes]

inline

The original poster used the word "Regenerated" and I think I did ask what
they meant.
OK

If you delete a shared border file, then FP should recreate the file when
you recalculate hyperlink as long as you have shared borders enabled
within the site.
OK

However, as long as the shared border file is in the web, FP will not
regenerate it, it will however regenerate any navigation component, if
used and changes are made within the navigation structure of the site.

This is where I lost it. Are you saying that if I modify a shared border FP
will NOT regenerate the code if I make a change to it?

Better?

Disregard

"if you open _borders\top.htm and make a change, then save the page, that
FP deletes the change you have made and recreates the page the way it was
before you made a change?"

as you are correct it doesn't make any sense!

Thanks for clearing that up. Thought I had a bad case of coors light

 

[Thomas A. Rowe]

inline

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

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

inline



This is where I lost it. Are you saying that if I modify a shared border FP will NOT regenerate
the code if I make a change to it?

The actual file is not re-generated, just the content of the Shared Border file is re-generated if
you are using any FP navigation components that have changed. If you add a image or other content,
then the file is not re-generated, just updated.

 

[Wes]

inline

inline

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

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




The actual file is not re-generated, just the content of the Shared Border
file is re-generated if you are using any FP navigation components that
have changed. If you add a image or other content, then the file is not
re-generated, just updated.

OK, I get it now, re-generate and update are not the same. Udate was not
mentioned originally, hense the confusion

Thanks for explaining it.