When validating my Freeway-made pages ( www.larsboye.dk ) on http://validator.w3.org/ I get a number of errors. Some of them are due to some of my own added code. However, most of the error messages are related to Freeway’s automated code. Has anybody any explanation?
Sometime around 20/4/08 (at 07:11 -0400) larsboye said:
When validating my Freeway-made pages ( www.larsboye.dk ) on http://validator.w3.org/ I get a number of errors. Some of them are
due to some of my own added code. However, most of the error
messages are related to Freeway’s automated code. Has anybody any
Absolutely. The error your custom code has caused has made the
validator trip over things that are not actually wrong. This is very
common with validators when they see something that isn’t quite
right: they see an unexpected element of some sort, and they never
quite get over it.
Fix the problem with your custom-added code and you’ll find that
Freeway’s own output will, as usual, validate perfectly.
By the way, PLEASE could everyone remember to put http:// in front of
your URLs? I don’t bother looking at most of those that don’t have
this, as they’re not clickable hyperlinks in my email client. I do
look at most that do have this.
Sometime around 20/4/08 (at 08:22 -0400) larsboye said:
Thank you for your swift reply. I have erased my custom-added code.
I suspect that you haven’t uploaded it after you erased it, as the
code there now is identical to the code that you had before.
I still had the page open in a browser window from when I looked
earlier, so I compared the the two sources in BBEdit - identical. And
the error(s) is (are) exactly the same.
If you added the code to the master page it is possible that you
changed the code there but that didn’t actually affect the actual
page itself. Certain things sometimes behave like that on master
(BTW, it can make life much easier for us when taking a look at pages
if you set your Freeway document to publish code in ‘more readable’
form. See File > Document Setup, click the Output tab, and change the
setting of the HTML Code popup menu.)
I changed the output code so it’s more readable now.
Also, I have verified that the code is uploaded properly. However, I still get errors when validating. (1 error connected with MSSmartTagsPreventParsing and 3 XML parsing errors.) http://www.larsboye.dk/
The meta tag item is what’s causing the validator to get flustered.
You don’t have a slash character immediately before the closing angle
bracket, which is a requirement for such self-contained element tags.
Are you certain that this page is entirely, unequivocably vanilla
Freeway output? Because it really don’t look like it to me…
Anyway, you can of course use custom code in your Freeway pages
without problems! You just have to make sure that it is constructed
properly. In this case, put a forward slash just before the closing
angle bracket in the MSSmartTagsPreventParsing meta tag.
Unless I’m very much mistaken, you still have custom code in that
Well, I have to admit that I use two Freeway Actions (“Remove Explorer Glow” and “Google Analytics”) on this page. with “Remove Explorer Glow” as the prime suspect here. I was under the impression that Freeway’s built-in actions made valid code but I may have misunderstood this…
By the way, is the “Remove Explorer Glow” necessary when displaying pages in modern versions of IE (6 and 6)?
Sometime around 20/4/08 (at 09:53 -0400) larsboye said:
“Remove Explorer Glow” as the prime suspect here. I was under the
impression that Freeway’s built-in actions made valid code but I may
have misunderstood this…
I belive the built-in ones do, but Remove Explorer Glow is actually a
third-party one that was written rather a long time ago.
Make sure you’re not using one of the original versions, as it does
cause significant accessibility problems. I suggest that you leave
the Explorer glow as it is; those poor saps running Internet Explorer
will be completely used to this visual behaviour. Don’t use that
action at all for a while and see how things go. I haven’t used it
for years, although I have to admit I was part of the clamour for
someone to write this, back in the day.