Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 124,
Column 121:
there is no attribute "border"
…infoletenky&a_bid=3e618418" width="1" height="1" border="0" alt="" > </img>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 124,
Column 133:
end tag for "img" omitted, but OMITTAG NO was specified
…infoletenky&a_bid=3e618418" width="1" height="1" border="0" alt="" > </img>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 124,
Column 4:
start tag was here
<img src="http://partner.pelikan.sk/scripts/sb.php?a_aid=infoletenky&a_b……infoletenky&a_bid=3e618418" width="1" height="1" border="0" alt="" > </img>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 126,
Column 90:
cannot generate system identifier for general entity "a_aid"
…elikan.sk/jsgenerator.aspx?id=600x200&a_aid=infoletenky&a_bid=3e618418" ch…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.
Line 126,
Column 90:
general entity "a_aid" not defined and no default entity
…elikan.sk/jsgenerator.aspx?id=600x200&a_aid=infoletenky&a_bid=3e618418" ch…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 126,
Column 95:
reference not terminated by REFC delimiter
…n.sk/jsgenerator.aspx?id=600x200&a_aid=infoletenky&a_bid=3e618418" charset…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 126,
Column 95:
reference to external entity in attribute value
…n.sk/jsgenerator.aspx?id=600x200&a_aid=infoletenky&a_bid=3e618418" charset…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 '&'.
Line 126,
Column 95:
reference to entity "a_aid" for which no system identifier could be generated
…n.sk/jsgenerator.aspx?id=600x200&a_aid=infoletenky&a_bid=3e618418" charset…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 126,
Column 89:
entity was defined here
…pelikan.sk/jsgenerator.aspx?id=600x200&a_aid=infoletenky&a_bid=3e618418" c…<script language="JavaScript" type="text/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 307,
Column 37:
document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
alt="TOPlist" width="1" height="1" /></noscript>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 314,
Column 116:
document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
…13981&ty=b_1" width="1" height="1" border="0" title="" alt="" /></noscript>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 316,
Column 10:
there is no attribute "id"
<SPAN id="szmtr"></SPAN>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 316,
Column 17:
element "SPAN" undefined
<SPAN id="szmtr"></SPAN>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:
Line 317,
Column 11:
element "SCRIPT" undefined
<SCRIPT>document.write('<scr'+'ipt src="https://szm.com/reklamatr.phtml?URL=…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:
Line 317,
Column 32:
an attribute specification must start with a name or name token
<SCRIPT>document.write('<scr'+'ipt src="https://szm.com/reklamatr.phtml?URL=…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 317,
Column 32:
element "scr" undefined
<SCRIPT>document.write('<scr'+'ipt src="https://szm.com/reklamatr.phtml?URL=…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:
Line 317,
Column 135:
delimiter "'" invalid: only S separators and TAGC allowed here
…URL='+document.location.href+'" type="text/javascript"></sc'+'ript>');</SCRIPT>…URL='+document.location.href+'" type="text/javascript"></sc'+'ript>');</SCRIPT>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 317,
Column 154:
end tag for "scr" omitted, but OMITTAG NO was specified
…URL='+document.location.href+'" type="text/javascript"></sc'+'ript>');</SCRIPT>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 317,
Column 28:
start tag was here
<SCRIPT>document.write('<scr'+'ipt src="https://szm.com/reklamatr.phtml?URL=… <SPAN id="szmad"></SPAN>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:
Line 319,
Column 11:
element "SCRIPT" undefined
<SCRIPT>document.write('<scr'+'ipt src="https://szm.com/reklamafr.phtml?URL=…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:
Line 319,
Column 32:
an attribute specification must start with a name or name token
<SCRIPT>document.write('<scr'+'ipt src="https://szm.com/reklamafr.phtml?URL=…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 319,
Column 32:
element "scr" undefined
<SCRIPT>document.write('<scr'+'ipt src="https://szm.com/reklamafr.phtml?URL=…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:
Line 319,
Column 135:
delimiter "'" invalid: only S separators and TAGC allowed here
…URL='+document.location.href+'" type="text/javascript"></sc'+'ript>');</SCRIPT>…URL='+document.location.href+'" type="text/javascript"></sc'+'ript>');</SCRIPT>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 319,
Column 154:
end tag for "scr" omitted, but OMITTAG NO was specified
…URL='+document.location.href+'" type="text/javascript"></sc'+'ript>');</SCRIPT>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 319,
Column 28:
start tag was here
<SCRIPT>document.write('<scr'+'ipt src="https://szm.com/reklamafr.phtml?URL=…