Jump to content

Validator alerts


limages

Recommended Posts

Hey, all.I just validated a file I've been working on for quite a while (integrating PayPal Buy Now buttons). It's been validating fine over time butsuddenly I've gotten warnings from the w3c validator about:1. Warning No Character Encoding Found! Falling back to UTF-8.>> I have this in my header: <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">2. Unable to Determine Parse Mode!The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because: * the MIME Media Type (text/html) can be used for XML or SGML document types * No known Document Type could be detected * No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document. * No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.>> I have this doctype coding in my html doc header: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">and finally,3. Validation Output: 1 Error 1. Error Line 1, Column 0: end of document in prolog.>>I don't have a clue to what this one means.Can anyone give me some direction?The only thing different as I mentioned is the incorporation of Buy Now button code into the data cells of the table on my site. It's FORM coding. It validated just fine the other day.Thanks,Limages.

Link to comment
Share on other sites

Hey, all.I just validated a file I've been working on for quite a while (integrating PayPal Buy Now buttons). It's been validating fine over time butsuddenly I've gotten warnings from the w3c validator about:1. Warning No Character Encoding Found! Falling back to UTF-8.>> I have this in my header: <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">2. Unable to Determine Parse Mode!The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because: * the MIME Media Type (text/html) can be used for XML or SGML document types * No known Document Type could be detected * No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document. * No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.>> I have this doctype coding in my html doc header: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">and finally,3. Validation Output: 1 Error 1. Error Line 1, Column 0: end of document in prolog.>>I don't have a clue to what this one means.Can anyone give me some direction?The only thing different as I mentioned is the incorporation of Buy Now button code into the data cells of the table on my site. It's FORM coding. It validated just fine the other day.Thanks,Limages.
Hey, you know what, I'm getting this same validator response for every html file I throw at it.I thought I'd just check on some files that I did for a class and some other simple ones that have been validated and given the Congrats signal. They ALL get the same result as I've provide above.Hmmmmm.Is something going on with the Validator?Limages
Link to comment
Share on other sites

Download the Web Developer's extension for Firefox, or the Firebug extension, don't recall which one exactly, but that includes a local Tidy validator that shows errors and warnings.

Link to comment
Share on other sites

You didn't change the character encoding (not the meta) to some weird one did you?
Not that I know of, but you've got a good thought there. Let me see if there's been a high-level/umbrella change. The only thing I can think of immediately is that yesterday, Firefox updated my browser to a new version.I'll check.Thanks, guys.
Link to comment
Share on other sites

Not that I know of, but you've got a good thought there. Let me see if there's been a high-level/umbrella change. The only thing I can think of immediately is that yesterday, Firefox updated my browser to a new version.I'll check.Thanks, guys.
Well, guess what? It all validates today.The only other thing I can think of that I had to do yesterday in order to "test" my site at PayPal was to throw out all cookies so PP would see me as an unknown customer. I wonder if getting rid of the cookies affected validator . . . .Anyway, thanks again for reading and offering your ideas. It's always reassuring to know someone is out there who may have the answer when a problem arises.Limages
Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...