Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 43,
Column 631:
cannot generate system identifier for general entity "u"
…eoptimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math…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 43,
Column 631:
general entity "u" not defined and no default entity
…eoptimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math…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 43,
Column 632:
reference not terminated by REFC delimiter
…optimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.…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 43,
Column 632:
reference to entity "u" for which no system identifier could be generated
…optimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.…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 43,
Column 630:
entity was defined here
…teoptimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Mat……_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement…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 43,
Column 663:
general entity "r" not defined and no default entity
…_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement…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 43,
Column 664:
reference not terminated by REFC delimiter
…id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement(…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 43,
Column 664:
reference to entity "r" for which no system identifier could be generated
…id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement(…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 43,
Column 662:
entity was defined here
…t_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElemen……ref="http://www.fhi.ox.ac.uk/" target="_blank">Future of Humanity Institute</a…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 255,
Column 77:
end tag for "br" omitted, but OMITTAG NO was specified
<div lang="en" id="mw-content-text" dir="ltr" class="mw-content-ltr"><p><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 255,
Column 73:
start tag was here
<div lang="en" id="mw-content-text" dir="ltr" class="mw-content-ltr"><p><br><p><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 271,
Column 4:
start tag was here
<p><br></p><p><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 277,
Column 8:
start tag was here
</p><p><br><hr>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 279,
Column 1:
start tag was here
<hr><p><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 302,
Column 4:
start tag was here
<p><br>…rc="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en"></script>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 378,
Column 29:
required attribute "action" not specified
<form style="display:none">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 379,
Column 65:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
<input type="hidden" id="cse-search-transformed" value="0" />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 507,
Column 46:
end tag for "br" omitted, but OMITTAG NO was specified
Co-work with other rationalists online.<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 507,
Column 42:
start tag was here
Co-work with other rationalists online.<br> <ul id="https://wiki.lesswrong.com/mediawiki/index.php?title=Special:RecentCh…
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.
Line 584,
Column 136:
end tag for "ul" which is not finished
…title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0"></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 587,
Column 116:
cannot generate system identifier for general entity "feed"
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 116:
general entity "feed" not defined and no default entity
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 120:
reference not terminated by REFC delimiter
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 120:
reference to entity "feed" for which no system identifier could be generated
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 115:
entity was defined here
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 125:
general entity "hideminor" not defined and no default entity
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 134:
reference not terminated by REFC delimiter
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 134:
reference to entity "hideminor" for which no system identifier could be generated
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 124:
entity was defined here
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 137:
general entity "namespace" not defined and no default entity
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 146:
reference not terminated by REFC delimiter
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 146:
reference to entity "namespace" for which no system identifier could be generated
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 136:
entity was defined here
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");…ar delpattern = new RegExp(".*<a href=\"/wiki/User:.*\" title=\"User:.*\">.*</…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 589,
Column 70:
an attribute value must be a literal unless it contains only name characters
…new RegExp(".*<a href=\"/wiki/User:.*\" title=\"User:.*\">.*</a> deleted page")You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 589,
Column 81:
document type does not allow element "a" here
…new RegExp(".*<a href=\"/wiki/User:.*\" title=\"User:.*\">.*</a> deleted page")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 594,
Column 131:
reference not terminated by REFC delimiter
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 594,
Column 131:
reference to entity "feed" for which no system identifier could be generated
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 115:
entity was defined here
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 594,
Column 145:
reference to entity "hideminor" for which no system identifier could be generated
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 124:
entity was defined here
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 594,
Column 157:
reference to entity "namespace" for which no system identifier could be generated
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0");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 587,
Column 136:
entity was defined here
…awiki/index.php?title=Special:RecentChanges&feed=rss&hideminor=1&namespace=0"); for (var i = 0; i < result.feed.entries.length; i++) {This message may appear in several cases:
Line 597,
Column 48:
character "&" is the first character of a delimiter but occurred as data
… if (!delpattern.test(entry.content)&&pages.indexOf(entry.title)==-1) {This message may appear in several cases:
Line 597,
Column 50:
cannot generate system identifier for general entity "pages.indexOf"
… if (!delpattern.test(entry.content)&&pages.indexOf(entry.title)==-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 "&" (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 597,
Column 50:
general entity "pages.indexOf" not defined and no default entity
… if (!delpattern.test(entry.content)&&pages.indexOf(entry.title)==-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 597,
Column 63:
reference not terminated by REFC delimiter
… if (!delpattern.test(entry.content)&&pages.indexOf(entry.title)==-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 597,
Column 63:
reference to entity "pages.indexOf" for which no system identifier could be generated
… if (!delpattern.test(entry.content)&&pages.indexOf(entry.title)==-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 597,
Column 49:
entity was defined here
… if (!delpattern.test(entry.content)&&pages.indexOf(entry.title)==-1) { var href = entry.link.replace(/&diff=\d+&oldid=prev$/, "");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 600,
Column 47:
general entity "diff" not defined and no default entity
var href = entry.link.replace(/&diff=\d+&oldid=prev$/, "");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 600,
Column 51:
reference not terminated by REFC delimiter
var href = entry.link.replace(/&diff=\d+&oldid=prev$/, "");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 600,
Column 51:
reference to entity "diff" for which no system identifier could be generated
var href = entry.link.replace(/&diff=\d+&oldid=prev$/, "");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 600,
Column 46:
entity was defined here
var href = entry.link.replace(/&diff=\d+&oldid=prev$/, ""); var href = entry.link.replace(/&diff=\d+&oldid=prev$/, "");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 600,
Column 56:
general entity "oldid" not defined and no default entity
var href = entry.link.replace(/&diff=\d+&oldid=prev$/, "");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 600,
Column 61:
reference not terminated by REFC delimiter
var href = entry.link.replace(/&diff=\d+&oldid=prev$/, "");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 600,
Column 61:
reference to entity "oldid" for which no system identifier could be generated
var href = entry.link.replace(/&diff=\d+&oldid=prev$/, "");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 600,
Column 55:
entity was defined here
var href = entry.link.replace(/&diff=\d+&oldid=prev$/, ""); <h2 id="http://www.overcomingbias.com/feed_title"></h2>
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.
Line 632,
Column 16:
character "/" is not allowed in the value of attribute "id"
<ul id="http://www.overcomingbias.com/feed"></ul>
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.
Line 632,
Column 51:
end tag for "ul" which is not finished
<ul id="http://www.overcomingbias.com/feed"></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 644,
Column 25:
character "<" is the first character of a delimiter but occurred as data
for (var i = 0; i < 9; i++) {This message may appear in several cases:
Line 649,
Column 31:
character "<" is the first character of a delimiter but occurred as data
for (var i = 0; i < result.feed.entries.length; i++) {This message may appear in several cases:
Line 655,
Column 33:
character "<" is the first character of a delimiter but occurred as data
for (var i = 0; i < 5; i++) {This message may appear in several cases:
Line 754,
Column 16:
there is no attribute "target"
target="_top">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 755,
Column 50:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
<input type="hidden" name="reason" value="" />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 756,
Column 49:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
<input type="hidden" name="op" value="reg" />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 895,
Column 50:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
<input type="hidden" name="reason" value="" />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 896,
Column 51:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
<input type="hidden" name="op" value="login" />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>").
