News:

Join the Facebook Fan Page.

Main Menu

XHTML not working ?

Started by riker, September 22, 2008, 03:14:26 PM

Previous topic - Next topic

riker

I keep getting errors, is this right ?


QuoteErrors found while checking this document as XHTML 1.0 Transitional!
Result: 14 Errors 
Address: 
Encoding: iso-8859-1  (detect automatically) utf-8 (Unicode, worldwide) utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2 (Central Europe) iso-8859-3 (Southern Europe) iso-8859-4 (North European) iso-8859-5 (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8 (Hebrew, visual) iso-8859-8-i (Hebrew, logical) iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-11 (Latin/Thai) iso-8859-13 (Latin 7, Baltic Rim) iso-8859-14 (Latin 8, Celtic) iso-8859-15 (Latin 9) iso-8859-16 (Latin 10) us-ascii (basic English) euc-jp (Japanese, Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email) euc-kr (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified) big5 (Chinese, traditional) Big5-HKSCS (Chinese, Hong Kong) tis-620 (Thai) koi8-r (Russian) koi8-u (Ukrainian) iso-ir-111 (Cyrillic KOI-8) macintosh (MacRoman) windows-1250 (Central Europe) windows-1251 (Cyrillic) windows-1252 (Western Europe) windows-1253 (Greek) windows-1254 (Turkish) windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim) 
Doctype: XHTML 1.0 Transitional  (detect automatically) XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset HTML 4.01 Strict HTML 4.01 Transitional HTML 4.01 Frameset HTML 3.2 HTML 2.0 ISO/IEC 15445:2000 ("ISO HTML") XHTML 1.1 XHTML + RDFa XHTML Basic 1.0 XHTML Basic 1.1 XHTML Mobile Profile 1.2 XHTML-Print 1.0 XHTML 1.1 plus MathML 2.0 XHTML 1.1 plus MathML 2.0 plus SVG 1.1 MathML 2.0 SVG 1.0 SVG 1.1 SVG 1.1 Tiny SVG 1.1 Basic SMIL 1.0 SMIL 2.0 
Root Element: html
Root Namespace: http://www.w3.org/1999/xhtml

OptionsShow Source Show Outline List Messages Sequentially Group Error Messages by Type
Validate error pages Verbose Output Clean up Markup with HTML Tidy

Help on the options is available.
   
↑ Top

Validation Output: 14 Errors
Line 68, Column 76: document type does not allow element "td" here.
...rfix" align="right"><td class="windowbg2"><script type="text/javascript"><!--✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 85, Column 14: end tag for "td" omitted, but OMITTAG NO was specified.
</script></div>✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 68, Column 55: start tag was here.
...s="windowbg2 clearfix" align="right"><td class="windowbg2"><script type="text Line 411, Column 51: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.
   <div class="tborder clearfix" id="infocenterframe">✉
The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 506, Column 6: end tag for "p" omitted, but OMITTAG NO was specified.
   </div><p align="center"><script type="text/javascript"><!--✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 385, Column 7: start tag was here.
   </div><p align="center"><script type="text/javascript"><!-- Line 524, Column 62: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.
...d="footerarea" class="headerpadding topmargin clearfix">✉
The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 535, Column 5: end tag for "p" omitted, but OMITTAG NO was specified.
</div>✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 506, Column 7: start tag was here.
   </div><p align="center"><script type="text/javascript"><!-- Line 85, Column 15: XML Parsing Error: Opening and ending tag mismatch: td line 68 and div.
</script></div>✉
Line 506, Column 7: XML Parsing Error: Opening and ending tag mismatch: p line 385 and div.
   </div><p align="center"><script type="text/javascript"><!--✉
Line 535, Column 6: XML Parsing Error: Opening and ending tag mismatch: p line 506 and div.
</div>✉
Line 536, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 136 and body.
</body></html>✉
Line 536, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 37 and html.
</body></html>✉
Line 536, Column 14: XML Parsing Error: Premature end of data in tag div line 36.
</body></html>✉
Line 536, Column 14: XML Parsing Error: Premature end of data in tag body line 35.
</body></html>✉
Line 536, Column 14: XML Parsing Error: Premature end of data in tag html line 2.
</body></html>

www.tvlicenceresistance.info/forum


H

Is this with the w3c validator?

Really 100% compliance is unnecessary as long as you're working on the majority of browser. I'd suspect any major errors would be caused by non-compliant modifications.
-H
Former Support Team Lead
                              I recommend:
Namecheap (domains)
Fastmail (e-mail)
Linode (VPS)
                             

riker

Quote from: H on September 23, 2008, 01:24:05 PM
Is this with the w3c validator?

Really 100% compliance is unnecessary as long as you're working on the majority of browser. I'd suspect any major errors would be caused by non-compliant modifications.

Thanks H,  I've been on some of the other member forums here and noticed a few of them also have this so I'll have to keep fingers crossed

riker

update:  It's the Ad Management causing the problem. Once that's switched off all the errors are gone

Advertisement: