Something fried the color coding in FrontPage 2003

[George Hester]

Now all my scripts are showing the color for Normal Text. For example when I change the color for Normal text then all text be it in a script tag or not is effected. All my js files have lost all their color coding. All my scripts have lost their color coding. What did I do? Well I installed the latest security updates for Microsoft Windows 2000 Server. Those that came out in the middle of last month. That's what I did. Thanks Microsoft. Is it any wonder no one trusts your security updates?

 

[Stefan B Rusynko]

Tools Page Options color Coding - reset




Now all my scripts are showing the color for Normal Text. For example when I change the color for Normal text then all text be it
in a script tag or not is effected. All my js files have lost all their color coding. All my scripts have lost their color coding.
What did I do? Well I installed the latest security updates for Microsoft Windows 2000 Server. Those that came out in the middle
of last month. That's what I did. Thanks Microsoft. Is it any wonder no one trusts your security updates?

 

[George Hester]

That is what I said. When I change the color for Normal text ALL code
changes their color be the code be in a <SCRIPT ...> or not. That should
not happen. Reset does nothing as nothing was changed. What has changed is
the color coding for the <SCRIPT tags as seen but it is set no different
then what it always was in that interface. In other words FrontPage 2003 is
not listening. By the way the only script coloring that hasn't changed is
that in <%%>. But in <script></script> it has and is effected if I change
the color scheme for Normal text. The only coloring that has survived in
the <script tags is that for strings ie: var a = 'Help' that Help still
shows green. The rest has flown the coop.

--
George Hester
_________________________________

Tools Page Options color Coding - reset




Now all my scripts are showing the color for Normal Text. For example

when I change the color for Normal text then all text be it

in a script tag or not is effected. All my js files have lost all their

color coding. All my scripts have lost their color coding.

What did I do? Well I installed the latest security updates for Microsoft

Windows 2000 Server. Those that came out in the middle

of last month. That's what I did. Thanks Microsoft. Is it any wonder no

one trusts your security updates?

 

[Stefan B Rusynko]

Almost sounds like an open script or comment tag on your page
- or a video driver issue




| That is what I said. When I change the color for Normal text ALL code
| changes their color be the code be in a <SCRIPT ...> or not. That should
| not happen. Reset does nothing as nothing was changed. What has changed is
| the color coding for the <SCRIPT tags as seen but it is set no different
| then what it always was in that interface. In other words FrontPage 2003 is
| not listening. By the way the only script coloring that hasn't changed is
| that in <%%>. But in <script></script> it has and is effected if I change
| the color scheme for Normal text. The only coloring that has survived in
| the <script tags is that for strings ie: var a = 'Help' that Help still
| shows green. The rest has flown the coop.
|
| --
| George Hester
| _________________________________
| | > Tools Page Options color Coding - reset
| >
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > To find the best Newsgroup for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
| > _____________________________________________
| >
| >
| | > Now all my scripts are showing the color for Normal Text. For example
| when I change the color for Normal text then all text be it
| > in a script tag or not is effected. All my js files have lost all their
| color coding. All my scripts have lost their color coding.
| > What did I do? Well I installed the latest security updates for Microsoft
| Windows 2000 Server. Those that came out in the middle
| > of last month. That's what I did. Thanks Microsoft. Is it any wonder no
| one trusts your security updates?
| >
| > --
| > George Hester
| > __________________________________
| >
| >
|
|

 

[George Hester]

No I am using a different Op sys in a different Partition and all is well
there. Nope it was the security updates I installed. Before the updates no
issue after the updates this issue. So it can't be a Video driver issue or
this Op sys would also have the issue. This Op sys has not and will not
install those security fixes for Windows 2000 in October 2004. Maybe the
security updates messed up the system that has been known to happen. One
reason why I don't install those like I should. Too risky.

As for the other suggestion an open tag. No I made a new page and just put
in a test script tag. Same issue. Furthermore there are no meta tags that
FrontPage puts in when I make a new html. The ProgId and the Generator no
longer appear. They flew the coup too. It's like the enties in the
Registry for that stuff just disappeared.

When we make a new html Normal page we should get:

<html>

<head>
<meta name="GENERATOR" content="Microsoft FrontPage 6.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>New Page 1</title>
</head>

<body>

</body>

</html>

but I get:

<html>

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

<body>

</body>

</html>

See? Not good. This happened right after I applied the security updates
and then rebooted. This was in Windows 2000 Server SP3. I went to SP4 I
uninstalled and reinstalled Microsoft FrontPage 2003 I removed IE 5.5 SP2
re-installed IE 5.5 SP2. Still broke.

--
George Hester
_________________________________

Almost sounds like an open script or comment tag on your page
- or a video driver issue




| That is what I said. When I change the color for Normal text ALL code
| changes their color be the code be in a <SCRIPT ...> or not. That should
| not happen. Reset does nothing as nothing was changed. What has changed is
| the color coding for the <SCRIPT tags as seen but it is set no different
| then what it always was in that interface. In other words FrontPage 2003 is
| not listening. By the way the only script coloring that hasn't changed is
| that in <%%>. But in <script></script> it has and is effected if I change
| the color scheme for Normal text. The only coloring that has survived in
| the <script tags is that for strings ie: var a = 'Help' that Help still
| shows green. The rest has flown the coop.
|
| --
| George Hester
| _________________________________
| | > Tools Page Options color Coding - reset
| >
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > To find the best Newsgroup for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
| > _____________________________________________
| >
| >
| | > Now all my scripts are showing the color for Normal Text. For example
| when I change the color for Normal text then all text be it
| > in a script tag or not is effected. All my js files have lost all their
| color coding. All my scripts have lost their color coding.
| > What did I do? Well I installed the latest security updates for Microsoft
| Windows 2000 Server. Those that came out in the middle
| > of last month. That's what I did. Thanks Microsoft. Is it any wonder no
| one trusts your security updates?
| >
| > --
| > George Hester
| > __________________________________
| >
| >
|
|

 

[Stefan B Rusynko]

The generator tags are turned off (by default) in Tools Page Options Authoring

FP heavily uses IE for "display" so yes it could be an IE SP or OS SP issue




| No I am using a different Op sys in a different Partition and all is well
| there. Nope it was the security updates I installed. Before the updates no
| issue after the updates this issue. So it can't be a Video driver issue or
| this Op sys would also have the issue. This Op sys has not and will not
| install those security fixes for Windows 2000 in October 2004. Maybe the
| security updates messed up the system that has been known to happen. One
| reason why I don't install those like I should. Too risky.
|
| As for the other suggestion an open tag. No I made a new page and just put
| in a test script tag. Same issue. Furthermore there are no meta tags that
| FrontPage puts in when I make a new html. The ProgId and the Generator no
| longer appear. They flew the coup too. It's like the enties in the
| Registry for that stuff just disappeared.
|
| When we make a new html Normal page we should get:
|
| <html>
|
| <head>
| <meta name="GENERATOR" content="Microsoft FrontPage 6.0">
| <meta name="ProgId" content="FrontPage.Editor.Document">
| <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
| <title>New Page 1</title>
| </head>
|
| <body>
|
| </body>
|
| </html>
|
| but I get:
|
| <html>
|
| <head>
| <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
| <title>New Page 1</title>
| </head>
|
| <body>
|
| </body>
|
| </html>
|
| See? Not good. This happened right after I applied the security updates
| and then rebooted. This was in Windows 2000 Server SP3. I went to SP4 I
| uninstalled and reinstalled Microsoft FrontPage 2003 I removed IE 5.5 SP2
| re-installed IE 5.5 SP2. Still broke.
|
| --
| George Hester
| _________________________________
| | > Almost sounds like an open script or comment tag on your page
| > - or a video driver issue
| >
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > To find the best Newsgroup for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
| > _____________________________________________
| >
| >
| | > | That is what I said. When I change the color for Normal text ALL code
| > | changes their color be the code be in a <SCRIPT ...> or not. That
| should
| > | not happen. Reset does nothing as nothing was changed. What has
| changed is
| > | the color coding for the <SCRIPT tags as seen but it is set no different
| > | then what it always was in that interface. In other words FrontPage
| 2003 is
| > | not listening. By the way the only script coloring that hasn't changed
| is
| > | that in <%%>. But in <script></script> it has and is effected if I
| change
| > | the color scheme for Normal text. The only coloring that has survived
| in
| > | the <script tags is that for strings ie: var a = 'Help' that Help still
| > | shows green. The rest has flown the coop.
| > |
| > | --
| > | George Hester
| > | _________________________________
| > | | > | > Tools Page Options color Coding - reset
| > | >
| > | > --
| > | >
| > | > _____________________________________________
| > | > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > | > "Warning - Using the F1 Key will not break anything!" (-;
| > | > To find the best Newsgroup for FrontPage support see:
| > | > http://www.net-sites.com/sitebuilder/newsgroups.asp
| > | > _____________________________________________
| > | >
| > | >
| > | | > | > Now all my scripts are showing the color for Normal Text. For example
| > | when I change the color for Normal text then all text be it
| > | > in a script tag or not is effected. All my js files have lost all
| their
| > | color coding. All my scripts have lost their color coding.
| > | > What did I do? Well I installed the latest security updates for
| Microsoft
| > | Windows 2000 Server. Those that came out in the middle
| > | > of last month. That's what I did. Thanks Microsoft. Is it any wonder
| no
| > | one trusts your security updates?
| > | >
| > | > --
| > | > George Hester
| > | > __________________________________
| > | >
| > | >
| > |
| > |
| >
| >
|
|

 

[George Hester]

Stefan I don't know why you say that about the Meta tags in FrontPage 2003.
I have never experienced that. I have installed FrontPage 2003 many many
times on user machines. And all of them by default will include those meta
tags for New Page. I have never seen what you are describing. It may be
because of the options I choose when installing FrontPage 2003 but I have
never changed what you say needs to be changed to get those meta tags. Heck
I don't even know where it is.

So yes FP is dependent on IE to some extant. But it was not a Service Pack
or IE installation after which this issue began. It was right after the
security updates for Windows 2000 SP3 Server that came out in October 2004
installed at Windows Update. The Op sys updates no IE sec fixes. I tried to
fix the issue by installing SP4. Didn't help. I tried to fix the issue by
uninstalling and reinstalling FrontPage 2003. Didn't help. I tried to fix
the issue by going to Microsoft Office 2003 SP1. Didn't help. I tried to
fix the issue by uninstalling and reinstalling IE 5.5 SP2. Didn't help.

Anyway I should say that Op sys is toast. I'll be rebuilding it shortly.
It still exists but I am not using it anymore. When issues such as this
happen I know when to fold them. Thanks for participating in this
discussion with me.

--
George Hester
_________________________________

The generator tags are turned off (by default) in Tools Page Options Authoring

FP heavily uses IE for "display" so yes it could be an IE SP or OS SP issue




| No I am using a different Op sys in a different Partition and all is well
| there. Nope it was the security updates I installed. Before the updates no
| issue after the updates this issue. So it can't be a Video driver issue or
| this Op sys would also have the issue. This Op sys has not and will not
| install those security fixes for Windows 2000 in October 2004. Maybe the
| security updates messed up the system that has been known to happen. One
| reason why I don't install those like I should. Too risky.
|
| As for the other suggestion an open tag. No I made a new page and just put
| in a test script tag. Same issue. Furthermore there are no meta tags that
| FrontPage puts in when I make a new html. The ProgId and the Generator no
| longer appear. They flew the coup too. It's like the enties in the
| Registry for that stuff just disappeared.
|
| When we make a new html Normal page we should get:
|
| <html>
|
| <head>
| <meta name="GENERATOR" content="Microsoft FrontPage 6.0">
| <meta name="ProgId" content="FrontPage.Editor.Document">
| <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
| <title>New Page 1</title>
| </head>
|
| <body>
|
| </body>
|
| </html>
|
| but I get:
|
| <html>
|
| <head>
| <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
| <title>New Page 1</title>
| </head>
|
| <body>
|
| </body>
|
| </html>
|
| See? Not good. This happened right after I applied the security updates
| and then rebooted. This was in Windows 2000 Server SP3. I went to SP4 I
| uninstalled and reinstalled Microsoft FrontPage 2003 I removed IE 5.5 SP2
| re-installed IE 5.5 SP2. Still broke.
|
| --
| George Hester
| _________________________________
| | > Almost sounds like an open script or comment tag on your page
| > - or a video driver issue
| >
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > To find the best Newsgroup for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
| > _____________________________________________
| >
| >
| | > | That is what I said. When I change the color for Normal text ALL code
| > | changes their color be the code be in a <SCRIPT ...> or not. That
| should
| > | not happen. Reset does nothing as nothing was changed. What has
| changed is
| > | the color coding for the <SCRIPT tags as seen but it is set no different
| > | then what it always was in that interface. In other words FrontPage
| 2003 is
| > | not listening. By the way the only script coloring that hasn't changed
| is
| > | that in <%%>. But in <script></script> it has and is effected if I
| change
| > | the color scheme for Normal text. The only coloring that has survived
| in
| > | the <script tags is that for strings ie: var a = 'Help' that Help still
| > | shows green. The rest has flown the coop.
| > |
| > | --
| > | George Hester
| > | _________________________________
| > | | > | > Tools Page Options color Coding - reset
| > | >
| > | > --
| > | >
| > | > _____________________________________________
| > | > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > | > "Warning - Using the F1 Key will not break anything!" (-;
| > | > To find the best Newsgroup for FrontPage support see:
| > | > http://www.net-sites.com/sitebuilder/newsgroups.asp
| > | > _____________________________________________
| > | >
| > | >
| > | | > | > Now all my scripts are showing the color for Normal Text. For example
| > | when I change the color for Normal text then all text be it
| > | > in a script tag or not is effected. All my js files have lost all
| their
| > | color coding. All my scripts have lost their color coding.
| > | > What did I do? Well I installed the latest security updates for
| Microsoft
| > | Windows 2000 Server. Those that came out in the middle
| > | > of last month. That's what I did. Thanks Microsoft. Is it any wonder
| no
| > | one trusts your security updates?
| > | >
| > | > --
| > | > George Hester
| > | > __________________________________
| > | >
| > | >
| > |
| > |
| >
| >
|
|