Showsite.us

Message Error

• Line 50, Column 10: document type does not allow element "noscript" here; assuming missing "object" start-tag

  <noscript><img src="http://ctag.hu/dc/cs?p12=tag-adnetwork-atv" style="display:…

• Line 67, Column 43: document type does not allow element "style" here

  	<style type="text/css" id="edited_styles">

  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 82, Column 7: end tag for "object" omitted, but OMITTAG NO was specified

  </head>

  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 50, Column 1: start tag was here

  <noscript><img src="http://ctag.hu/dc/cs?p12=tag-adnetwork-atv" style="display:…

• Line 85, Column 71: there is no attribute "hasparameters"

  …" id="zone-header"><div hasparameters="1" bpm="BlockParameter_Basic" blockid="…

  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.

• Line 85, Column 79: there is no attribute "bpm"

  …ne-header"><div hasparameters="1" bpm="BlockParameter_Basic" blockid="100022" …

  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.

• Line 85, Column 110: there is no attribute "blockid"

  …1" bpm="BlockParameter_Basic" blockid="100022" class="block bk_commonitems-hea…

  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.

• Line 88, Column 74: an attribute specification must start with a name or name token

  …pt">if(!window.goA)document.write('<sc'+'ript src="http://imgs.adverticum.net/…

  An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

• Line 88, Column 74: element "sc" undefined

  …pt">if(!window.goA)document.write('<sc'+'ript src="http://imgs.adverticum.net/…

  You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
  • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
  • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
• Line 88, Column 203: character "<" is the first character of a delimiter but occurred as data

  …1000000000)+'" type="text/javascript"><\/sc'+'ript>');</script><script type="t…

  This message may appear in several cases:

  • You tried to include the "<" character in your page: you should escape it as "&lt;"
  • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
  • Another possibility is that you forgot to close quotes in a previous tag.
• Line 88, Column 227: end tag for "sc" omitted, but OMITTAG NO was specified

  …t/javascript"><\/sc'+'ript>');</script><script type="text/javascript">if(windo…

  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 88, Column 71: start tag was here

  …cript">if(!window.goA)document.write('<sc'+'ript src="http://imgs.adverticum.n…

• Line 93, Column 188: end tag for "img" omitted, but OMITTAG NO was specified

  …://static.atv.hu/images/reklam.png" width="15" height="44" alt="Reklám"></span>

  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 93, Column 96: start tag was here

  …gin-top: 24px;  margin-left: 234px; "><img src="http://static.atv.hu/images/re…

• Line 96, Column 22: end tag for "ul" which is not finished

    			            </ul>

  Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

  Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

• Line 139, Column 20: character ")" not allowed in attribute specification list

                     ) />

• Line 139, Column 21: end tag for "input" omitted, but OMITTAG NO was specified

                     ) />

  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 137, Column 13: start tag was here

              <input type="button" class="button" onclick="

• Line 218, Column 16: end tag for "h2" omitted, but OMITTAG NO was specified

             </li>

  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 213, Column 10: start tag was here

          	<h2>

• Line 219, Column 16: end tag for element "h2" which is not open

             </h2>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 226, Column 16: end tag for "h2" omitted, but OMITTAG NO was specified

             </li>

  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 221, Column 10: start tag was here

          	<h2>

• Line 227, Column 16: end tag for element "h2" which is not open

             </h2>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 234, Column 16: end tag for "h2" omitted, but OMITTAG NO was specified

             </li>

  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 229, Column 10: start tag was here

          	<h2>

• Line 235, Column 16: end tag for element "h2" which is not open

             </h2>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 242, Column 16: end tag for "h2" omitted, but OMITTAG NO was specified

             </li>

  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 237, Column 10: start tag was here

          	<h2>

• Line 243, Column 16: end tag for element "h2" which is not open

             </h2>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 250, Column 16: end tag for "h2" omitted, but OMITTAG NO was specified

             </li>

  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 245, Column 10: start tag was here

          	<h2>

• Line 251, Column 16: end tag for element "h2" which is not open

             </h2>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 264, Column 19: required attribute "type" not specified

              <style>

  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>.

• Line 264, Column 19: document type does not allow element "style" here

              <style>

  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 272, Column 41: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag

  <div id="zone55248" class="goAdverticum"></div>

  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 310, Column 16: end tag for "h2" omitted, but OMITTAG NO was specified

             </li>

  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 305, Column 10: start tag was here

          	<h2>

• Line 311, Column 16: end tag for element "h2" which is not open

             </h2>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 318, Column 16: end tag for "h2" omitted, but OMITTAG NO was specified

             </li>

  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 313, Column 10: start tag was here

          	<h2>

• Line 319, Column 16: end tag for element "h2" which is not open

             </h2>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 326, Column 16: end tag for "h2" omitted, but OMITTAG NO was specified

             </li>

  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 321, Column 10: start tag was here

          	<h2>

• Line 327, Column 16: end tag for element "h2" which is not open

             </h2>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 341, Column 173: end tag for "br" omitted, but OMITTAG NO was specified

  …_1szazalek.gif" alt="Hit Gyülekezet Egy százalékos felajánlás" /></a></div><br>

  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 341, Column 169: start tag was here

  …_1szazalek.gif" alt="Hit Gyülekezet Egy százalékos felajánlás" /></a></div><br>

• Line 345, Column 5: end tag for "ul" which is not finished

  </ul>

  Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

  Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

• Line 378, Column 16: end tag for "h2" omitted, but OMITTAG NO was specified

             </li>

  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 373, Column 10: start tag was here

          	<h2>

• Line 379, Column 16: end tag for element "h2" which is not open

             </h2>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 386, Column 16: end tag for "h2" omitted, but OMITTAG NO was specified

             </li>

  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 381, Column 10: start tag was here

          	<h2>

• Line 387, Column 16: end tag for element "h2" which is not open

             </h2>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 394, Column 16: end tag for "h2" omitted, but OMITTAG NO was specified

             </li>

  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 389, Column 10: start tag was here

          	<h2>

• Line 395, Column 16: end tag for element "h2" which is not open

             </h2>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 409, Column 135: end tag for "br" omitted, but OMITTAG NO was specified

  …p://hetek.hu/files/banners/hetek_banner_13_04.gif" alt="Hetek" /></a></div><br>

  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 409, Column 131: start tag was here

  …p://hetek.hu/files/banners/hetek_banner_13_04.gif" alt="Hetek" /></a></div><br>

• Line 720, Column 5: end tag for "br" omitted, but OMITTAG NO was specified

  <br>

  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 720, Column 1: start tag was here

  <br>

• Line 726, Column 380: there is no attribute "allowtransparency"

  …8px; height:555px;" allowtransparency="true" frameborder="0" scrolling="no"></…

  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.

• Line 726, Column 431: end tag for "br" omitted, but OMITTAG NO was specified

  …allowtransparency="true" frameborder="0" scrolling="no"></iframe><br><br></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 726, Column 427: start tag was here

  …allowtransparency="true" frameborder="0" scrolling="no"></iframe><br><br></div>

• Line 726, Column 440: end tag for "br" omitted, but OMITTAG NO was specified

  …allowtransparency="true" frameborder="0" scrolling="no"></iframe><br><br></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 726, Column 431: start tag was here

  …allowtransparency="true" frameborder="0" scrolling="no"></iframe><br><br></div>

• Line 747, Column 5: end tag for element "ul" which is not open

  </ul>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 749, Column 5: end tag for element "li" which is not open

  </li>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 753, Column 5: end tag for element "li" which is not open

  </li>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 757, Column 5: end tag for element "li" which is not open

  </li>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 761, Column 5: end tag for element "ul" which is not open

  </ul>

  The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

  If this error occurred in a script section of your document, you should probably read this FAQ entry.

• Line 867, Column 22: there is no attribute "language"

  		  <SCRIPT language="JavaScript">

  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.

• Line 867, Column 34: element "SCRIPT" undefined

  		  <SCRIPT language="JavaScript">

  You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
  • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
  • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
• Line 869, Column 21: S separator in comment declaration

  document.write('<!-- Medián WebAudit ATV Online Nyitólap 1/2 --><img style="pos…

  This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

• Line 869, Column 22: invalid comment declaration: found name start character outside comment but inside comment declaration

  document.write('<!-- Medián WebAudit ATV Online Nyitólap 1/2 --><img style="pos…

• Line 868, Column 1: comment declaration started here

  <!--

• Line 869, Column 183: cannot generate system identifier for general entity "dc"

  …u/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">'…

  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 "&amp;" (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 &aelig; 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.

• Line 869, Column 183: general entity "dc" not defined and no default entity

  …u/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">'…

  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.

• Line 869, Column 185: reference not terminated by REFC delimiter

  …/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">');

  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.

• Line 869, Column 185: reference to external entity in attribute value

  …/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">');

  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 '&amp;'.

• Line 869, Column 185: reference to entity "dc" for which no system identifier could be generated

  …/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">');

  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.

• Line 869, Column 182: entity was defined here

  …hu/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">…

• Line 869, Column 188: cannot generate system identifier for general entity "ui"

  …/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">');

  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 "&amp;" (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 &aelig; 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.

• Line 869, Column 188: general entity "ui" not defined and no default entity

  …/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">');

  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.

• Line 869, Column 190: reference not terminated by REFC delimiter

  …/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">');

  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.

• Line 869, Column 190: reference to external entity in attribute value

  …/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">');

  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 '&amp;'.

• Line 869, Column 190: reference to entity "ui" for which no system identifier could be generated

  …/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">');

  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.

• Line 869, Column 187: entity was defined here

  …/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">');

• Line 869, Column 221: required attribute "alt" not specified

  …/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">');

  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>.

• Line 869, Column 222: end tag for "img" omitted, but OMITTAG NO was specified

  …/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">');

  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 869, Column 65: start tag was here

  …n WebAudit ATV Online Nyitólap 1/2 --><img style="position:absolute;top:-100px…

• Line 872, Column 10: element "NOSCRIPT" undefined

  <NOSCRIPT>

  You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
  • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
  • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
• Line 874, Column 121: reference not terminated by REFC delimiter

  …audit.median.hu/cgi-bin/track.cgi?uc=12094877207789&dc=1" width="1" height="1">

  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.

• Line 874, Column 121: reference to external entity in attribute value

  …audit.median.hu/cgi-bin/track.cgi?uc=12094877207789&dc=1" width="1" height="1">

  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 '&amp;'.

• Line 874, Column 121: reference to entity "dc" for which no system identifier could be generated

  …audit.median.hu/cgi-bin/track.cgi?uc=12094877207789&dc=1" width="1" height="1">

  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.

• Line 869, Column 182: entity was defined here

  …hu/cgi-bin/track.cgi?uc=12094877207789&dc=1&ui='+same+'" width="1" height="1">…

• Line 874, Column 145: required attribute "alt" not specified

  …audit.median.hu/cgi-bin/track.cgi?uc=12094877207789&dc=1" width="1" height="1">

  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>.

• Line 874, Column 146: end tag for "img" omitted, but OMITTAG NO was specified

  …audit.median.hu/cgi-bin/track.cgi?uc=12094877207789&dc=1" width="1" height="1">

  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 874, Column 1: start tag was here

  <img style="position:absolute;top:-100px;left:-100px" src="http://audit.median.…

• Line 878, Column 10: end tag for "div" omitted, but OMITTAG NO was specified

     </body>

  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 84, Column 2: start tag was here

  	<div id="container"><div class="layout layout-homePage" id="layout-homePage">