I started out at 200 errors most i have fixed myself and got my home page down to 27 Errors, 4 warning(s). I posted the rrors and woarns if anyone has fixed these can you please let me know Thanks
Error Line 56, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
document.write("<script id=__ie_onload defer><\/script>");
✉
Error Line 56, Column 49: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
document.write("<script id=__ie_onload defer><\/script>");
✉
"VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.
How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...
Error Line 56, Column 49: required attribute "type" not specified
document.write("<script id=__ie_onload defer><\/script>");
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
Error Line 56, Column 49: document type does not allow element "script" here
document.write("<script id=__ie_onload defer><\/script>");
✉
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).
Warning Line 56, Column 50: character "<" is the first character of a delimiter but occurred as data
document.write("<script id=__ie_onload defer><\/script>");
✉
This message may appear in several cases:
* You tried to include the "<" character in your page: you should escape it as "<"
* You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
* Another possibility is that you forgot to close quotes in a previous tag.
Error Line 110, Column 115: document type does not allow element "script" here
…ipt/cot.js" type="text/javascript" /></script>
✉
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).
Error Line 122, Column 68: required attribute "type" not specified
…fe.com/private/rollover/rollover.js"></script><span id="BuySafeSealSpan"><scr
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
Error Line 198, Column 10: ID "navMain" already defined
<div id="navMain"><div id="logo"><a href="http://www.lextechs.com/"><img src="in
✉
An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Info Line 131, Column 13: ID "navMain" first defined here
<div id="navMain">
Error Line 198, Column 28: ID "logo" already defined
<div id="navMain"><div id="logo"><a href="http://www.lextechs.com/"><img src="in
✉
An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Info Line 144, Column 13: ID "logo" first defined here
<div id="logo"><a href="http://www.lextechs.com/"><img src="includes/templat
Error Line 233, Column 31: document type does not allow element "td" here; assuming missing "tr" start-tag
<td align="center" colspan="2">
✉
Error Line 235, Column 111: document type does not allow element "link" here
…ss" type="text/css" media="screen" />
✉
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).
Error Line 409, Column 277: Attribute "oncontextmenu" is not a valid attribute
…to see a BBB report." oncontextmenu="alert('Use without permission is prohibi
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Error Line 409, Column 445: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
…aus, Inc.'); return false;" /></a><p><a href="http://www.lextechs.com/index.p
✉
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>").
Error Line 409, Column 599: end tag for "p" omitted, but OMITTAG NO was specified
…all our Credentials</b></a></p></div></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 ">".
Info Line 408, Column 61: start tag was here
…id="hackersideboxContent" class="sideBoxContent"><p></p><p><!-- Start bbbonline-->
Error Line 443, Column 353: end tag for "hr" omitted, but OMITTAG NO was specified
…increased as of 1/2/08</a><br /><hr><a href="http://www.lextechs.com/index.ph
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 443, Column 348: start tag was here
…ates increased as of 1/2/08</a><br /><hr><a href="http://www.lextechs.com/ind
Error Line 468, Column 4: document type does not allow element "ul" here; assuming missing "li" start-tag
<ul>
✉
Error Line 471, Column 6: end tag for "li" 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 ">".
Info Line 468: start tag was here
<ul>
Error Line 471, Column 6: end tag for "ul" 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 ">".
Info Line 457: start tag was here
<ul>
Error Line 521, Column 96: character "/" is not allowed in the value of attribute "target"
…ws__mid--109914.html" target="https://www.shopzilla.com"><img src="https://ww
✉
It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.
Warning Line 526, Column 92: cannot generate system identifier for general entity "utm_source"
…hs.1-866-569-9443?utm_medium=widget&utm_source=MClogo" target="_new" style="b
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Error Line 526, Column 92: general entity "utm_source" not defined and no default entity
…hs.1-866-569-9443?utm_medium=widget&utm_source=MClogo" target="_new" style="b
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Warning Line 526, Column 102: reference not terminated by REFC delimiter
…69-9443?utm_medium=widget&utm_source=MClogo" target="_new" style="border:none
✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Warning Line 526, Column 102: reference to external entity in attribute value
…69-9443?utm_medium=widget&utm_source=MClogo" target="_new" style="border:none
✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Error Line 526, Column 102: reference to entity "utm_source" for which no system identifier could be generated
…69-9443?utm_medium=widget&utm_source=MClogo" target="_new" style="border:none
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Info Line 526, Column 90: entity was defined here
…echs.1-866-569-9443?utm_medium=widget&utm_source=MClogo" target="_new" style=
Error Line 526, Column 253: required attribute "alt" not specified
…_widget1.gif" style="border:none;" /></a>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
Error Line 56, Column 31: XML Parsing Error: AttValue: " or ' expected
document.write("<script id=__ie_onload defer><\/script>");
✉
Error Line 56, Column 31: XML Parsing Error: attributes construct error
document.write("<script id=__ie_onload defer><\/script>");
✉
Error Line 56, Column 31: XML Parsing Error: Couldn't find end of Start Tag script line 56
document.write("<script id=__ie_onload defer><\/script>");
✉
Error Line 56, Column 50: XML Parsing Error: StartTag: invalid element name
document.write("<script id=__ie_onload defer><\/script>");
✉
Error Line 110, Column > 80: XML Parsing Error: Opening and ending tag mismatch: head line 3 and script
…secure.comodo.net/trustlogo/javascript/cot.js" type="text/javascript" /></scr…
✉
Error Line 111, Column 7: XML Parsing Error: Opening and ending tag mismatch: html line 2 and head
</head>
