Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 82,
Column 16:
there is no attribute "property"
<meta property="fb:admins" content="648235154,789168297,688620285,650984415" />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 297,
Column 8:
required attribute "type" not specified
<script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 303,
Column 37:
character ";" not allowed in attribute specification list
for (i=0;i<metaCollection.length;i++) { for (i=0;i<metaCollection.length;i++) {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 314,
Column 91:
cannot generate system identifier for general entity "browser_path"
…m/ams/page-ads.js?ad_category_prefix=&browser_path=%2F&cat_prefixes=%2C&keywor…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 314,
Column 91:
general entity "browser_path" not defined and no default entity
…m/ams/page-ads.js?ad_category_prefix=&browser_path=%2F&cat_prefixes=%2C&keywor…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 314,
Column 103:
reference not terminated by REFC delimiter
…ds.js?ad_category_prefix=&browser_path=%2F&cat_prefixes=%2C&keywords='+metaKey…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 314,
Column 103:
reference to entity "browser_path" for which no system identifier could be generated
…ds.js?ad_category_prefix=&browser_path=%2F&cat_prefixes=%2C&keywords='+metaKey…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 314,
Column 90:
entity was defined here
…om/ams/page-ads.js?ad_category_prefix=&browser_path=%2F&cat_prefixes=%2C&keywo……?ad_category_prefix=&browser_path=%2F&cat_prefixes=%2C&keywords='+metaKeyWords…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 314,
Column 108:
general entity "cat_prefixes" not defined and no default entity
…?ad_category_prefix=&browser_path=%2F&cat_prefixes=%2C&keywords='+metaKeyWords…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 314,
Column 120:
reference not terminated by REFC delimiter
…_prefix=&browser_path=%2F&cat_prefixes=%2C&keywords='+metaKeyWords+'&position_…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 314,
Column 120:
reference to entity "cat_prefixes" for which no system identifier could be generated
…_prefix=&browser_path=%2F&cat_prefixes=%2C&keywords='+metaKeyWords+'&position_…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 314,
Column 107:
entity was defined here
…s?ad_category_prefix=&browser_path=%2F&cat_prefixes=%2C&keywords='+metaKeyWord……ix=&browser_path=%2F&cat_prefixes=%2C&keywords='+metaKeyWords+'&position_list=…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 314,
Column 125:
general entity "keywords" not defined and no default entity
…ix=&browser_path=%2F&cat_prefixes=%2C&keywords='+metaKeyWords+'&position_list=…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 314,
Column 133:
reference not terminated by REFC delimiter
…ser_path=%2F&cat_prefixes=%2C&keywords='+metaKeyWords+'&position_list=AMS_WIR_…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 314,
Column 133:
reference to entity "keywords" for which no system identifier could be generated
…ser_path=%2F&cat_prefixes=%2C&keywords='+metaKeyWords+'&position_list=AMS_WIR_…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 314,
Column 124:
entity was defined here
…fix=&browser_path=%2F&cat_prefixes=%2C&keywords='+metaKeyWords+'&position_list……refixes=%2C&keywords='+metaKeyWords+'&position_list=AMS_WIR_GLOBAL_NAVBAR%2CAM…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 314,
Column 151:
general entity "position_list" not defined and no default entity
…refixes=%2C&keywords='+metaKeyWords+'&position_list=AMS_WIR_GLOBAL_NAVBAR%2CAM…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 314,
Column 164:
reference not terminated by REFC delimiter
…eywords='+metaKeyWords+'&position_list=AMS_WIR_GLOBAL_NAVBAR%2CAMS_WIR_GLOBAL_…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 314,
Column 164:
reference to entity "position_list" for which no system identifier could be generated
…eywords='+metaKeyWords+'&position_list=AMS_WIR_GLOBAL_NAVBAR%2CAMS_WIR_GLOBAL_…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 314,
Column 150:
entity was defined here
…prefixes=%2C&keywords='+metaKeyWords+'&position_list=AMS_WIR_GLOBAL_NAVBAR%2CA……CAMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name…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 314,
Column 408:
general entity "site_prefix" not defined and no default entity
…CAMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name…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 314,
Column 419:
reference not terminated by REFC delimiter
…AMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name='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 314,
Column 419:
reference to entity "site_prefix" for which no system identifier could be generated
…AMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name='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 314,
Column 407:
entity was defined here
…2CAMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_nam……AMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name='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 314,
Column 426:
general entity "subdomain" not defined and no default entity
…AMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name='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 314,
Column 435:
reference not terminated by REFC delimiter
…AMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name='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 314,
Column 435:
reference to entity "subdomain" for which no system identifier could be generated
…AMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name='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 314,
Column 425:
entity was defined here
…AMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name='…AMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name='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 314,
Column 440:
general entity "url_name" not defined and no default entity
…AMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name='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 314,
Column 448:
reference not terminated by REFC delimiter
…AMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name='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 314,
Column 448:
reference to entity "url_name" for which no system identifier could be generated
…AMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name='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 314,
Column 439:
entity was defined here
…AMS_WIR_GLOBAL_RIGHTRAIL_SUBSERVICES&site_prefix=wired&subdomain=www&url_name=' document.write('<scr' + 'ipt src="'+src+'" language="javascript…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 321,
Column 37:
element "scr" undefined
document.write('<scr' + 'ipt src="'+src+'" 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:
Line 321,
Column 87:
delimiter "'" invalid: only S separators and TAGC allowed here
…cument.write('<scr' + 'ipt src="'+src+'" language="javascript"></scr' + 'ipt>')</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 303,
Column 15:
start tag was here
for (i=0;i<metaCollection.length;i++) {<script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 1093,
Column 40:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_GLOBAL_NAVBAR…This message may appear in several cases:
Line 1093,
Column 41:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_GLOBAL_NAVBAR …This message may appear in several cases:
Line 1093,
Column 97:
character "&" is the first character of a delimiter but occurred as data
…geAds.AMS_WIR_GLOBAL_NAVBAR != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
Line 1093,
Column 98:
character "&" is the first character of a delimiter but occurred as data
…geAds.AMS_WIR_GLOBAL_NAVBAR != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
Line 1151,
Column 8:
required attribute "type" not specified
<script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 1154,
Column 40:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_GLOBAL_NAVBAR…This message may appear in several cases:
Line 1154,
Column 41:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_GLOBAL_NAVBAR_…This message may appear in several cases:
Line 1154,
Column 106:
character "&" is the first character of a delimiter but occurred as data
…_WIR_GLOBAL_NAVBAR_ROLLOVER != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
Line 1154,
Column 107:
character "&" is the first character of a delimiter but occurred as data
…_WIR_GLOBAL_NAVBAR_ROLLOVER != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
Line 1290,
Column 79:
there is no attribute "autocomplete"
… <input id="q" name="query" size="19" type="text" autocomplete="on" value="" />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 3648,
Column 11:
cannot generate system identifier for general entity "A"
<h5>Q&A</h5>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 3648,
Column 11:
general entity "A" not defined and no default entity
<h5>Q&A</h5>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 3648,
Column 12:
reference not terminated by REFC delimiter
<h5>Q&A</h5>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 3648,
Column 12:
reference to entity "A" for which no system identifier could be generated
<h5>Q&A</h5>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 3648,
Column 10:
entity was defined here
<h5>Q&A</h5><script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 7591,
Column 40:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_HOMEPAGE_RIGH…This message may appear in several cases:
Line 7591,
Column 41:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_HOMEPAGE_RIGHT…This message may appear in several cases:
Line 7591,
Column 104:
character "&" is the first character of a delimiter but occurred as data
…MS_WIR_HOMEPAGE_RIGHTRAIL_A != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
Line 7591,
Column 105:
character "&" is the first character of a delimiter but occurred as data
…MS_WIR_HOMEPAGE_RIGHTRAIL_A != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
Line 7631,
Column 24:
document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<h4><a href=""></a></h4>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 7633,
Column 24:
document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<h2><a href=""> </a></h2>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 7635,
Column 32:
document type does not allow element "blockquote" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<blockquote><!-- start brightcove - wired.com homepage xrai…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 7661,
Column 23:
document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<p>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 7665,
Column 22:
end tag for "p" omitted, but OMITTAG NO was specified
</div>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 7629,
Column 36:
start tag was here
<div class="inner"><p> <h4><a href=""></a></h4>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 7693,
Column 24:
document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<h2><a href=""> </a></h2>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 7695,
Column 32:
document type does not allow element "blockquote" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<blockquote> <script type="text/javascript">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 7799,
Column 108:
required attribute "alt" not specified
…-btn-left" src='http://www.wired.com/images_blogs/about/2011/11/left-up.png' />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 7803,
Column 213:
required attribute "alt" not specified
…ww.wired.com/images_blogs/wiredscience/2012/05/heikkileis_mould11-xrail.jpg" />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 7804,
Column 47:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
…v class="xrail-photo-glide-disp-label"><h2><em>Afterlife</em>: Making Rotten F…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 7808,
Column 178:
required attribute "alt" not specified
…disp-img" src="http://www.wired.com/images_blogs/rawfile/2012/05/bunnyx.jpg" />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 7809,
Column 47:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
…v class="xrail-photo-glide-disp-label"><h2>Country Fair Photos Parade Jolly Br…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 7814,
Column 178:
required attribute "alt" not specified
…disp-img" src="http://www.wired.com/images_blogs/rawfile/2012/05/bunnyx.jpg" />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 7815,
Column 47:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
…v class="xrail-photo-glide-disp-label"><h2>Country Fair Photos Parade Jolly Br…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 7821,
Column 110:
required attribute "alt" not specified
…tn-right" src="http://www.wired.com/images_blogs/about/2011/11/right-up.png" />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 7825,
Column 23:
document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<p>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 7829,
Column 22:
end tag for "p" omitted, but OMITTAG NO was specified
</div>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 7689,
Column 36:
start tag was here
<div class="inner"><p> <h4><a href=""></a></h4>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 7861,
Column 24:
document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<h2><a href="http://www.wired.com/geekdad/geekdaddaypackage…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 7878,
Column 32:
ID "multi" already defined
<div class="multi_home" id="multi">An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 7846,
Column 32:
ID "multi" first defined here
<div class="multi_home" id="multi"> <h3 id="multi_mod_title">Sponsorship</h3>An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 7849,
Column 17:
ID "multi_mod_title" first defined here
<h3 id="multi_mod_title">GeekDad</h3> <h4><a href=""></a></h4>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 7893,
Column 24:
document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<h2><a href="http://www.wiredinsider.com/skype/">You could …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 7919,
Column 24:
document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<h4><a href=""></a></h4>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 7921,
Column 24:
document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<h2><a href=""> </a></h2>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 7923,
Column 32:
document type does not allow element "blockquote" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<blockquote><iframe src="http://promotion.monster.com/wired…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 7926,
Column 23:
document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<p>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 7930,
Column 22:
end tag for "p" omitted, but OMITTAG NO was specified
</div>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 7917,
Column 36:
start tag was here
<div class="inner"><p><script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 7997,
Column 40:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_GLOBAL_RIGHTR…This message may appear in several cases:
Line 7997,
Column 41:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_GLOBAL_RIGHTRA…This message may appear in several cases:
Line 7997,
Column 112:
character "&" is the first character of a delimiter but occurred as data
…LOBAL_RIGHTRAIL_SUBSERVICES != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
Line 7997,
Column 113:
character "&" is the first character of a delimiter but occurred as data
…LOBAL_RIGHTRAIL_SUBSERVICES != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
Line 8047,
Column 15:
end tag for element "span" which is not open
</span>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 8064,
Column 44:
required attribute "action" not specified
<form id="footer_dropdowns">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 8245,
Column 8:
required attribute "type" not specified
<script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 8248,
Column 40:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_HOMEPAGE_RIGH…This message may appear in several cases:
Line 8248,
Column 41:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_HOMEPAGE_RIGHT…This message may appear in several cases:
Line 8248,
Column 101:
character "&" is the first character of a delimiter but occurred as data
…s.AMS_WIR_HOMEPAGE_RIGHTNAV != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
Line 8248,
Column 102:
character "&" is the first character of a delimiter but occurred as data
…s.AMS_WIR_HOMEPAGE_RIGHTNAV != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
Line 8279,
Column 8:
required attribute "type" not specified
<script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 8282,
Column 40:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_FOOTER_NAVBAR…This message may appear in several cases:
Line 8282,
Column 41:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_FOOTER_NAVBAR_…This message may appear in several cases:
Line 8282,
Column 103:
character "&" is the first character of a delimiter but occurred as data
…AMS_WIR_FOOTER_NAVBAR_POPUP != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
Line 8282,
Column 104:
character "&" is the first character of a delimiter but occurred as data
…AMS_WIR_FOOTER_NAVBAR_POPUP != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
Line 8313,
Column 8:
required attribute "type" not specified
<script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 8316,
Column 40:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_FOOTER_NAVBAR…This message may appear in several cases:
Line 8316,
Column 41:
character "&" is the first character of a delimiter but occurred as data
… if((typeof pageAds != 'undefined') && (typeof pageAds.AMS_WIR_FOOTER_NAVBAR …This message may appear in several cases:
Line 8316,
Column 97:
character "&" is the first character of a delimiter but occurred as data
…geAds.AMS_WIR_FOOTER_NAVBAR != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
Line 8316,
Column 98:
character "&" is the first character of a delimiter but occurred as data
…geAds.AMS_WIR_FOOTER_NAVBAR != 'undefined') && (CN.url.params('nojoy') !=1) ) {This message may appear in several cases:
