Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 55,
Column 140:
there is no attribute "TARGET"
…;cb=INSERT_RANDOM_NUMBER_HERE' target='_blank'><img src='http://adserver.barra…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 55,
Column 148:
document type does not allow element "A" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
…RT_RANDOM_NUMBER_HERE' target='_blank'><img src='http://adserver.barrapunto.co…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 55,
Column 276:
there is no attribute "BORDER"
…b=INSERT_RANDOM_NUMBER_HERE&n=aa1847ba' border='0' alt='' /></a></noscript>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 55,
Column 287:
NET-enabling start-tag requires SHORTTAG YES
…b=INSERT_RANDOM_NUMBER_HERE&n=aa1847ba' border='0' alt='' /></a></noscript>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 55,
Column 303:
end tag for "NOSCRIPT" which is not finished
…b=INSERT_RANDOM_NUMBER_HERE&n=aa1847ba' border='0' alt='' /></a></noscript>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 74,
Column 148:
document type does not allow element "A" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
…RT_RANDOM_NUMBER_HERE' target='_blank'><img src='http://adserver.barrapunto.co…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 74,
Column 287:
NET-enabling start-tag requires SHORTTAG YES
…b=INSERT_RANDOM_NUMBER_HERE&n=a7366b1c' border='0' alt='' /></a></noscript>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 74,
Column 303:
end tag for "NOSCRIPT" which is not finished
…b=INSERT_RANDOM_NUMBER_HERE&n=a7366b1c' border='0' alt='' /></a></noscript>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 325,
Column 6:
document type does not allow element "LI" here; missing one of "UL", "OL" start-tag
<LI><A HREF="http://qixite.sourceforge.net">Qixite</A></LI>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 326,
Column 4:
document type does not allow element "LI" here; missing one of "UL", "OL" start-tag
<LI><A HREF="http://www.coffeecup.com"> CoffeCup</A></LI>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 327,
Column 4:
document type does not allow element "LI" here; missing one of "UL", "OL" start-tag
<LI><A HREF="http://quanta.sourceforge.net">Quanta</A></LI>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 328,
Column 4:
document type does not allow element "LI" here; missing one of "UL", "OL" start-tag
<LI><A HREF="http://bluefish.openoffice.nl">BlueFish</A></LI>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 329,
Column 4:
document type does not allow element "LI" here; missing one of "UL", "OL" start-tag
<LI><A HREF="//barrapunto.com/search.pl?topic=internet">Más en Internet</A></LI>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 330,
Column 4:
document type does not allow element "LI" here; missing one of "UL", "OL" start-tag
<LI><A HREF="//barrapunto.com/search.pl?op=stories&author=4">También por poncho…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 330,
Column 52:
cannot generate system identifier for general entity "author"
…EF="//barrapunto.com/search.pl?op=stories&author=4">También por poncho</A></LI>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 330,
Column 52:
general entity "author" not defined and no default entity
…EF="//barrapunto.com/search.pl?op=stories&author=4">También por poncho</A></LI>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 330,
Column 58:
reference to entity "author" for which no system identifier could be generated
…EF="//barrapunto.com/search.pl?op=stories&author=4">También por poncho</A></LI>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 330,
Column 51:
entity was defined here
…EF="//barrapunto.com/search.pl?op=stories&author=4">También por poncho</A></LI>…RT_RANDOM_NUMBER_HERE' target='_blank'><img src='http://adserver.barrapunto.co…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 438,
Column 287:
NET-enabling start-tag requires SHORTTAG YES
…b=INSERT_RANDOM_NUMBER_HERE&n=a5985538' border='0' alt='' /></a></noscript>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 438,
Column 303:
end tag for "NOSCRIPT" which is not finished
…b=INSERT_RANDOM_NUMBER_HERE&n=a5985538' border='0' alt='' /></a></noscript>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 439,
Column 4:
end tag for element "P" which is not open
</p>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 2424,
Column 48:
character data is not allowed here
…="comment_body_124126"> <BLOCKQUOTE>No se porque debería pagar para que mi c…You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 2424,
Column 233:
end tag for "BLOCKQUOTE" which is not finished
…me podría plantear un programa propietario para mi uso exclusivo. </BLOCKQUOTE>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 2431,
Column 1:
character data is not allowed here
Si la comunidad no ofrece esas herramientas y no se convencen las empresas desa…You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 2432,
Column 13:
end tag for "BLOCKQUOTE" which is not finished
</BLOCKQUOTE>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 2536,
Column 137:
NET-enabling start-tag requires SHORTTAG YES
…ges/somerights.png" alt="Licencia CC" /></a><br />Barrapunto © 1999-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 2536,
Column 147:
NET-enabling start-tag requires SHORTTAG YES
…ghts.png" alt="Licencia CC" /></a><br />Barrapunto © 1999-2007. Cont…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 2588,
Column 69:
NET-enabling start-tag requires SHORTTAG YES
alt="Valid HTML 4.01 Strict!" height="31" width="88" /></a>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
