Normal Page

  • Thread starter Thread starter George Hester
  • Start date Start date
G

George Hester

Making a new page in FrontPage 2002 newly installed does this:

<html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>New Page 2</title>
</head>

<body>

</body>

</html>

Notice these:

<meta name="GENERATOR" content="Microsoft FrontPage 6.0" />
<meta name="ProgId" content="FrontPage.Editor.Document" />

are no longer being put in my New Normal Page from the templates. What's wrong and how do I fix this? It seems FrontPage 2003 hasforgotten what it is. No COM addins are being loaded although I have 4. Thanks.

Maybe I've lost the ProgIDs???
 
Under Tools > Authoring there is a setting to enable/disable the Generator
and ProgID tags. I'd look there first.

Robb Topolski

Making a new page in FrontPage 2002 newly installed does this:

....
Notice these:

<meta name="GENERATOR" content="Microsoft FrontPage 6.0" />
<meta name="ProgId" content="FrontPage.Editor.Document" />

are no longer being put in my New Normal Page from the templates. What's
wrong and how do I fix this? It seems FrontPage 2003 hasforgotten what it
is. No COM addins are being loaded although I have 4. Thanks.

Maybe I've lost the ProgIDs???
 
FP 2003 no longer includes the "generator" tag - why worry?



Making a new page in FrontPage 2002 newly installed does this:

<html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>New Page 2</title>
</head>

<body>

</body>

</html>

Notice these:

<meta name="GENERATOR" content="Microsoft FrontPage 6.0" />
<meta name="ProgId" content="FrontPage.Editor.Document" />

are no longer being put in my New Normal Page from the templates. What's wrong
and how do I fix this? It seems FrontPage 2003 hasforgotten what it is. No COM
addins are being loaded although I have 4. Thanks.

Maybe I've lost the ProgIDs???
 
Sure it does. Here it is:

<meta name="GENERATOR" content="Microsoft FrontPage 6.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
 
Thanks Robby. Unfortunately I cannot check that. I know I didn't touch it
and of course it is enabled in a new installation. It just happened and
became persistent. But it's all moot anyway. I tried to demote the server
and whoop belly-up.
 
No I don't think so. Not in FrontPage anyway. See it uses those meta tags
so that it is aware that it is using a FrontPage 2003 document. For example
if you open a html that was made in a previous version of FrontPage upon
opening the file in FrontPage, those meta tags will change automatically to
the version of FrontPage you are using. FrontPage 2003 in this case. It
isues those for Intellisense purposes I believe.
 
Not sure what you mean by that. Yes when you are designing a htm then yes
that is when the meta tags are used. If the page is appearing in your
browser then no those meta tags mean nothing. The client would have to
interpret them to mean anything. In this case yes they could mean
something. The client may know that the application used to edit the html
is FrontPage based on those meta tags and if you edit directly from the
client then it could know what application to use to do the editing.. In
fact that's the whole idea. But whether they are actually used by a client
is a different matter and likely not.
 
Back
Top