Local News, Weather, Sports | Tampa Bay, Florida | ABC Action News WFTS-TV ...

abcactionnews.com
  • Domain Name
    abcactionnews.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #59467
  • Page Size
    159.7 KB
  • Ip Address
    204.154.142.84
  • Heading
    H1: 0, H2: 38, H3: 1, H4: 2, H5: 0, H6: 0
  • Images
    5 GIF, 57 JPG, 18 PNG

Website Meta Analysis

  • Title
    Local News, Weather, Sports | Tampa Bay, Florida | ABC Action News WFTS-TV
  • Meta Keyword
    ABC Action News Homepage, Tampa Bay, Florida, Hillsborough, Pasco, Polk, Pinellas, sarasota, manatee, citrus, hernando, desoto, highlands, hardee, tampa bay news, weather, traffic, sports, tampa video, breaking news tampa, st. petersburg, brandon, clearwater, florida
  • Meta Description
    Local News, Weather, Sports | Tampa Bay, Florida | ABC Action News WFTS-TV

Technical Analysis

  • Webserver
    Apache-Coyote/1.1
  • Ip Address
    204.154.142.84
  • Domain Age
    11 Years, 2 Months, 15 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from abcactionnews.com.

HTML Analysis

  • server: Apache-Coyote/1.1
  • content-encoding: gzip
  • liferay-portal: Liferay Portal Enterprise Edition 6.0 EE SP1 (Bunyan / Build 6011 / January 13, 2011)
  • etag: "c693c54"
  • content-type: text/html;charset=utf-8
  • content-length: 27573
  • vary: Accept-Encoding
  • date: Thu, 12 Sep 2013 02:06:32 GMT
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for abcactionnews.com

DNS Analysis


DNS servers
ns1.scripps.com [67.208.144.100]
ns2.scripps.com [199.19.246.100]


DNS Records

Answer records
abcactionnews.com SOA
server: ns1.scripps.com
email: hostmaster@scripps.com
serial: 2013010401
refresh: 7200
retry: 3600
expire: 604800
minimum ttl: 3600
3600s
abcactionnews.com NS  ns2.scripps.com 3600s
abcactionnews.com NS  ns1.scripps.com 3600s
abcactionnews.com A 204.154.142.84 3600s
abcactionnews.com MX
preference: 10
exchange: abcactionnews-com.mail.eo.outlook.com
3600s
abcactionnews.com TXT v=spf1 include:eblastengine.com include:spf.scripps.com -all 3600s

Authority records

Additional records
ns1.scripps.com A 67.208.144.100 3600s
ns2.scripps.com A 199.19.246.100 3600s

IP 204.154.142.84 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 204.154.142.84

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 212 Errors
  • 47 Warnings
Ratio Text/Html
  • 0.6924657157356061
Message Error
  • Error Line 1, Column 146: there is no attribute "class"
    …nsitional.dtd"> <html id="html" class="ltr" dir="ltr" lang="en-US" xmlns="http…

    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.

  • Error Line 1, Column 806: end tag for "meta" omitted, but OMITTAG NO was specified
    …y, Florida | ABC Action News WFTS-TV"><meta name="Keywords" content="ABC Actio…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1, Column 695: start tag was here
    …a http-equiv='expires' content='-1' /><meta name="Description" content="Local …
  • Error Line 1, Column 1106: end tag for "meta" omitted, but OMITTAG NO was specified
    …rsburg, brandon, clearwater, florida"><meta http-equiv='refresh' content='300'…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1, Column 806: start tag was here
    …y, Florida | ABC Action News WFTS-TV"><meta name="Keywords" content="ABC Actio…
  • Error Line 1, Column 1147: end tag for "meta" omitted, but OMITTAG NO was specified
    …ta http-equiv='refresh' content='300'><link rel='alternate' type='application/…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1, Column 1106: start tag was here
    …rsburg, brandon, clearwater, florida"><meta http-equiv='refresh' content='300'…
  • Warning Line 1, Column 1243: cannot generate system identifier for general entity "obfType"
    …me' href='/feeds/rssFeed?siteId=10010&obfType=RSS_FEED&categoryId=10000'/><lin…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1, Column 1243: general entity "obfType" not defined and no default entity
    …me' href='/feeds/rssFeed?siteId=10010&obfType=RSS_FEED&categoryId=10000'/><lin…

    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.

  • Warning Line 1, Column 1250: reference not terminated by REFC delimiter
    …f='/feeds/rssFeed?siteId=10010&obfType=RSS_FEED&categoryId=10000'/><link rel='…

    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.

  • Warning Line 1, Column 1250: reference to external entity in attribute value
    …f='/feeds/rssFeed?siteId=10010&obfType=RSS_FEED&categoryId=10000'/><link rel='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1, Column 1250: reference to entity "obfType" for which no system identifier could be generated
    …f='/feeds/rssFeed?siteId=10010&obfType=RSS_FEED&categoryId=10000'/><link rel='…

    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.

  • Info Line 1, Column 1242: entity was defined here
    …ome' href='/feeds/rssFeed?siteId=10010&obfType=RSS_FEED&categoryId=10000'/><li…
  • Warning Line 1, Column 1260: cannot generate system identifier for general entity "categoryId"
    …rssFeed?siteId=10010&obfType=RSS_FEED&categoryId=10000'/><link rel='shortcut i…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1, Column 1260: general entity "categoryId" not defined and no default entity
    …rssFeed?siteId=10010&obfType=RSS_FEED&categoryId=10000'/><link rel='shortcut i…

    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.

  • Warning Line 1, Column 1270: reference not terminated by REFC delimiter
    …teId=10010&obfType=RSS_FEED&categoryId=10000'/><link rel='shortcut icon' type=…

    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.

  • Warning Line 1, Column 1270: reference to external entity in attribute value
    …teId=10010&obfType=RSS_FEED&categoryId=10000'/><link rel='shortcut icon' type=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1, Column 1270: reference to entity "categoryId" for which no system identifier could be generated
    …teId=10010&obfType=RSS_FEED&categoryId=10000'/><link rel='shortcut icon' type=…

    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.

  • Info Line 1, Column 1259: entity was defined here
    …/rssFeed?siteId=10010&obfType=RSS_FEED&categoryId=10000'/><link rel='shortcut …
  • Error Line 1, Column 1723: required attribute "type" not specified
    …ss/delta.css?dppversion=7156' /><style>#mfl .adPencil{height:auto;}</style><sc…

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

  • Warning Line 1, Column 5380: character "<" is the first character of a delimiter but occurred as data
    …(!(istCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 5383: character "&" is the first character of a delimiter but occurred as data
    …istCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none")==…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 5384: character "&" is the first character of a delimiter but occurred as data
    …stCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none")==-…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1, Column 5594: an attribute specification must start with a name or name token
    …e="text/javascript"> ads[tile] = '<scr' + 'ipt language="JavaScript" src="http…

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

  • Error Line 1, Column 5594: element "scr" undefined
    …e="text/javascript"> ads[tile] = '<scr' + 'ipt language="JavaScript" src="http…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1, Column 5993: delimiter "'" invalid: only S separators and TAGC allowed here
    …0000 + '" type="text/javascript"></scr' + 'ipt>'; document.write('<div class="…
  • Error Line 1, Column 6042: document type does not allow element "div" here
    … document.write('<div class="moduleAd">'); document.write(ads[tile]);</script>…

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

  • Error Line 1, Column 6081: end tag for "div" omitted, but OMITTAG NO was specified
    …'); document.write(ads[tile]);</script><script language="JavaScript" type="tex…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1, Column 6021: start tag was here
    …ipt"></scr' + 'ipt>'; document.write('<div class="moduleAd">'); document.write…
  • Error Line 1, Column 6157: end tag for "script" omitted, but OMITTAG NO was specified
    …ext/javascript"> document.write("</div>"); istCount++; </script> <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 ">".

  • Info Line 1, Column 6082: start tag was here
    …); document.write(ads[tile]);</script><script language="JavaScript" type="text…
  • Error Line 1, Column 6157: end tag for "li" omitted, but OMITTAG NO was specified
    …ext/javascript"> document.write("</div>"); istCount++; </script> <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 ">".

  • Info Line 1, Column 4950: start tag was here
    …l class='searchbar line fontStyle31'> <li><script language="JavaScript" type="…
  • Error Line 1, Column 6157: end tag for "ul" omitted, but OMITTAG NO was specified
    …ext/javascript"> document.write("</div>"); istCount++; </script> <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 ">".

  • Info Line 1, Column 4910: start tag was here
    …aylaw.tv'>Tampa Bay Law</a></li></ul> <ul class='searchbar line fontStyle31'> …
  • Error Line 1, Column 6182: end tag for element "script" which is not open
    ….write("</div>"); istCount++; </script> <script>/*<![CDATA[*/var adRefreshTime…

    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.

  • Error Line 1, Column 6191: required attribute "type" not specified
    …/div>"); istCount++; </script> <script>/*<![CDATA[*/var adRefreshTimeout=1000;…

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

  • Error Line 1, Column 6251: end tag for element "li" which is not open
    …freshTimeout=1000;/*]]>*/</script></li> <li><form name="top_search" accept-cha…

    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.

  • Error Line 1, Column 6256: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …Timeout=1000;/*]]>*/</script></li> <li><form name="top_search" accept-charset=…

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

  • Error Line 1, Column 6454: there is no attribute "autocomplete"
    …d" id="top_search_field" autocomplete="off"/> <select name="search_type" id="s…

    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.

  • Error Line 1, Column 6544: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …opdown"> <option value="site" selected>Site</option> <option value="web">Web</…

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 1, Column 6681: end tag for "input" omitted, but OMITTAG NO was specified
    …"Search" onclick="submitSearchForm()"> <input type="hidden" value="" id="sm" n…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1, Column 6602: start tag was here
    …on value="web">Web</option> </select> <input type="button" value="  GO>> " alt…
  • Error Line 1, Column 7060: end tag for element "ul" which is not open
    …d="fwl_wfts";/*]]>*/</script></li></ul><span id='header_date' class='timestamp…

    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.

  • Warning Line 1, Column 8792: character "&" is the first character of a delimiter but occurred as data
    …ews.com/subindex/weather/maps'>Radars & Maps</a></li> <li><a href='http://www.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 9809: character "&" is the first character of a delimiter but occurred as data
    …subindex/traffic/incidents'>INCIDENTS & DELAYS</a></li> <li><a href='http://ww…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 14309: character "<" is the first character of a delimiter but occurred as data
    …(!(istCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 14312: character "&" is the first character of a delimiter but occurred as data
    …istCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none")==…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 14313: character "&" is the first character of a delimiter but occurred as data
    …stCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none")==-…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1, Column 14603: an attribute specification must start with a name or name token
    …lse{zone=pageZone};  ads[tile] = '<scr' + 'ipt language="JavaScript" src="http…

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

  • Error Line 1, Column 14603: element "scr" undefined
    …lse{zone=pageZone};  ads[tile] = '<scr' + 'ipt language="JavaScript" src="http…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1, Column 15027: delimiter "'" invalid: only S separators and TAGC allowed here
    …0000 + '" type="text/javascript"></scr' + 'ipt>'; document.write(ads[tile]); i…
  • Error Line 1, Column 15094: required attribute "type" not specified
    …s[tile]); istCount++;</script> <script>/*<![CDATA[*/var adRefreshTimeout=1000;…

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

  • Error Line 1, Column 15427: there is no attribute "ttl"
    …ass='refresh'><div id='nwsAlerts' ttl='1' url='/refreshmodule/0/85525800'><h3>…

    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.

  • Error Line 1, Column 15435: there is no attribute "url"
    …resh'><div id='nwsAlerts' ttl='1' url='/refreshmodule/0/85525800'><h3><span>WE…

    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.

  • Error Line 1, Column 15537: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …><h4><div id='NWS_news_alert_scroll'  ><a href='http://www.abcactionnews.com/s…

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

  • Error Line 1, Column 16651: value of attribute "id" invalid: "8" cannot start a name
    …v  class='br'></div> </div> <div  id='85066624-1' class='ui-tabs-panel'> <div …

    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.

  • Error Line 1, Column 19231: there is no attribute "refid"
    …ampa Bay'>Read More</a></li><li refid='abcactionnews-8255420' url='http://www.…

    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.

  • Error Line 1, Column 19259: there is no attribute "url"
    …<li refid='abcactionnews-8255420' url='http://www.abcactionnews.com/dpp/news/l…

    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.

  • Error Line 1, Column 31055: there is no attribute "interval"
    …<ul class='mp-headlines-nav' interval='8000'></ul></div></div><script type='te…

    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.

  • Error Line 1, Column 31066: end tag for "ul" which is not finished
    …mp-headlines-nav' interval='8000'></ul></div></div><script type='text/javascri…

    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.

  • Error Line 1, Column 31455: value of attribute "id" invalid: "5" cannot start a name
    …v  class='br'></div> </div> <div  id='57952209-1' class='ui-tabs-panel'> <div …

    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.

  • Error Line 1, Column 31572: ID "search-results" already defined
    …l' style='display: block;'> <div  id='search-results' class='content' style='h…

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

  • Info Line 1, Column 16768: ID "search-results" first defined here
    …l' style='display: block;'> <div  id='search-results' class='content'> </div> …
  • Error Line 1, Column 31718: there is no attribute "height"
    …ng: 3px; width: 647px;"><table height="100" cellspacing="0" cellpadding="0" bo…

    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.

  • Error Line 1, Column 33061: there is no attribute "tracking"
    …riable' style='width:658px;' tracking='{provider:"Omniture", moduleName:"TRIPL…

    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.

  • Error Line 1, Column 34153: end tag for "ul" which is not finished
    …;</p> <ul class='article-options'></ul></div></li> <li> <div  class='leftConte…

    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.

  • Error Line 1, Column 34959: end tag for "ul" which is not finished
    …;</p> <ul class='article-options'></ul></div></li> <li> <div  class='leftConte…

    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.

  • Error Line 1, Column 38426: end tag for "ul" which is not finished
    …h</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 38681: end tag for "ul" which is not finished
    …y</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 39932: end tag for "ul" which is not finished
    …g</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 40191: end tag for "ul" which is not finished
    …r</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 42785: end tag for "ul" which is not finished
    …y</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 44001: end tag for "ul" which is not finished
    …d</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 44771: end tag for "ul" which is not finished
    …t</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 46124: end tag for "ul" which is not finished
    …e</a> <ul class='article-options'></ul></li></ul></div></div></div> </div></di…

    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.

  • Warning Line 1, Column 46714: character "<" is the first character of a delimiter but occurred as data
    …(!(istCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 46717: character "&" is the first character of a delimiter but occurred as data
    …istCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none")==…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 46718: character "&" is the first character of a delimiter but occurred as data
    …stCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none")==-…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1, Column 47008: an attribute specification must start with a name or name token
    …lse{zone=pageZone};  ads[tile] = '<scr' + 'ipt language="JavaScript" src="http…

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

  • Error Line 1, Column 47008: element "scr" undefined
    …lse{zone=pageZone};  ads[tile] = '<scr' + 'ipt language="JavaScript" src="http…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1, Column 47432: delimiter "'" invalid: only S separators and TAGC allowed here
    …0000 + '" type="text/javascript"></scr' + 'ipt>'; document.write(ads[tile]); i…
  • Error Line 1, Column 47499: required attribute "type" not specified
    …s[tile]); istCount++;</script> <script>/*<![CDATA[*/var adRefreshTimeout=1000;…

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

  • Error Line 1, Column 49936: end tag for "ul" which is not finished
    …;</p> <ul class='article-options'></ul></div></li> <li> <div  class='leftConte…

    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.

  • Warning Line 1, Column 51265: character "&" is the first character of a delimiter but occurred as data
    …rence' title='The difference: Meteors & meteorites'> <img src="http://media2.a…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 51447: character "&" is the first character of a delimiter but occurred as data
    …_80.JPG" alt='The difference: Meteors & meteorites' title='The difference: Met…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 51492: character "&" is the first character of a delimiter but occurred as data
    …rites' title='The difference: Meteors & meteorites'/></a><p class='padding_fix…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 51719: character "&" is the first character of a delimiter but occurred as data
    …rence' title='The difference: Meteors & meteorites'>The difference: Meteors & …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 51757: character "&" is the first character of a delimiter but occurred as data
    …& meteorites'>The difference: Meteors & meteorites</a></p> <p>Friday's meteor …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 52116: character "&" is the first character of a delimiter but occurred as data
    …video' title='The difference: Meteors & meteorites'>Watch Video</a></li></ul><…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1, Column 54020: end tag for "ul" which is not finished
    …s</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 54753: end tag for "ul" which is not finished
    …y</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Warning Line 1, Column 54943: character "&" is the first character of a delimiter but occurred as data
    …rence' title='The difference: Meteors & meteorites'>The difference: Meteors & …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 54981: character "&" is the first character of a delimiter but occurred as data
    …& meteorites'>The difference: Meteors & meteorites</a> <ul class='article-opti…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 55234: character "&" is the first character of a delimiter but occurred as data
    …video' title='The difference: Meteors & meteorites'>Watch Video</a></li></ul><…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1, Column 55508: end tag for "ul" which is not finished
    …r</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 55759: end tag for "ul" which is not finished
    …p</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 56060: end tag for "ul" which is not finished
    …t</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 57290: end tag for "ul" which is not finished
    …e</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 57997: end tag for "ul" which is not finished
    …h</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 58265: end tag for "ul" which is not finished
    …U</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 58532: end tag for "ul" which is not finished
    …s</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 59270: end tag for "ul" which is not finished
    …t</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 59511: end tag for "ul" which is not finished
    …t</a> <ul class='article-options'></ul></li> <li><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 60233: end tag for "ul" which is not finished
    …e</a> <ul class='article-options'></ul></li></ul><a href='http://www.abcaction…

    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.

  • Error Line 1, Column 60486: ID "m57952213" already defined
    …id='m57952213' class='mod'> <div  id='m57952213' class='module generic iframe'…

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

  • Info Line 1, Column 60452: ID "m57952213" first defined here
    … </div> <div  class='col3'> <div  id='m57952213' class='mod'> <div  id='m57952…
  • Error Line 1, Column 60871: value of attribute "id" invalid: "5" cannot start a name
    …, Florida</span></li> </ul> <div  id='57952213-1' class='ui-tabs-panel'> <div …

    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.

  • Error Line 1, Column 60988: ID "search-results" already defined
    …l' style='display: block;'> <div  id='search-results' class='content' style='h…

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

  • Info Line 1, Column 16768: ID "search-results" first defined here
    …l' style='display: block;'> <div  id='search-results' class='content'> </div> …
  • Warning Line 1, Column 61961: character "<" is the first character of a delimiter but occurred as data
    …(!(istCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 61964: character "&" is the first character of a delimiter but occurred as data
    …istCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none")==…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1, Column 61965: character "&" is the first character of a delimiter but occurred as data
    …stCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none")==-…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1, Column 62255: an attribute specification must start with a name or name token
    …lse{zone=pageZone};  ads[tile] = '<scr' + 'ipt language="JavaScript" src="http…

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

  • Error Line 1, Column 62255: element "scr" undefined
    …lse{zone=pageZone};  ads[tile] = '<scr' + 'ipt language="JavaScript" src="http…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1, Column 62714: delimiter "'" invalid: only S separators and TAGC allowed here
    …0000 + '" type="text/javascript"></scr' + 'ipt>'; document.write(ads[tile]); i…
  • Error Line 1, Column 62781: required attribute "type" not specified
    …s[tile]); istCount++;</script> <script>/*<![CDATA[*/var adRefreshTimeout=1000;…

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

  • Error Line 1, Column 62983: ID "m82164746" already defined
    …id='m82164746' class='mod'> <div  id='m82164746' class='module generic iframe'…

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

  • Info Line 1, Column 62949: ID "m82164746" first defined here
    …nt</div></div></div> </div> <div  id='m82164746' class='mod'> <div  id='m82164…
  • Error Line 1, Column 63236: value of attribute "id" invalid: "8" cannot start a name
    …v  class='br'></div> </div> <div  id='82164746-1' class='ui-tabs-panel'> <div …

    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.

  • Error Line 1, Column 63353: ID "search-results" already defined
    …l' style='display: block;'> <div  id='search-results' class='content' style='h…

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

  • Info Line 1, Column 16768: ID "search-results" first defined here
    …l' style='display: block;'> <div  id='search-results' class='content'> </div> …
  • Error Line 1, Column 64014: ID "m86220402" already defined
    …id='m86220402' class='mod'> <div  id='m86220402' class='module variable fham d…

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

  • Info Line 1, Column 63980: ID "m86220402" first defined here
    … </div></div> </div> </div> <div  id='m86220402' class='mod'> <div  id='m86220…
  • Error Line 1, Column 64929: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …eed to know for Friday</a> </h2> <p><p>From Bollywood and Hollywood coming to …

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

  • Error Line 1, Column 66077: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ettlement emails real?</a> </h2> <p><p>You may get an email about Facebook bei…

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

  • Error Line 1, Column 67212: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … the most out of yours</a> </h2> <p><p>The first thing you want to do is dig o…

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

  • Error Line 1, Column 68574: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …t won't do checkpoints</a> </h2> <p><p> <strong>UPDATED</strong>: The Florida …

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

  • Error Line 1, Column 69756: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …or $50 a month or less</a> </h2> <p><p>There are plenty of ways to keep that b…

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

  • Error Line 1, Column 71133: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …aglets now 1 month old</a> </h2> <p><p>Since late December, we've been watchin…

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

  • Error Line 1, Column 71851: ID "m83429955" already defined
    …id='m83429955' class='mod'> <div  id='m83429955' class='module generic iframe'…

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

  • Info Line 1, Column 71817: ID "m83429955" first defined here
    … </div></div> </div> </div> <div  id='m83429955' class='mod'> <div  id='m83429…
  • Error Line 1, Column 72117: value of attribute "id" invalid: "8" cannot start a name
    …v  class='br'></div> </div> <div  id='83429955-1' class='ui-tabs-panel'> <div …

    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.

  • Error Line 1, Column 72234: ID "search-results" already defined
    …l' style='display: block;'> <div  id='search-results' class='content' style='h…

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

  • Info Line 1, Column 16768: ID "search-results" first defined here
    …l' style='display: block;'> <div  id='search-results' class='content'> </div> …
  • Error Line 1, Column 72316: required attribute "type" not specified
    …ent' style='height:320px'><script language="javascript"> jQuery(document).ready

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

  • Error Line 18, Column 201: ID "m57952210" already defined
    …id='m57952210' class='mod'> <div  id='m57952210' class='variable module generi…

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

  • Info Line 18, Column 167: ID "m57952210" first defined here
    … </div></div> </div> </div> <div  id='m57952210' class='mod'> <div  id='m57952…
  • Error Line 18, Column 452: value of attribute "id" invalid: "5" cannot start a name
    …v  class='br'></div> </div> <div  id='57952210-1' class='ui-tabs-panel'> <div …

    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.

  • Error Line 18, Column 569: ID "search-results" already defined
    …l' style='display: block;'> <div  id='search-results' class='content'><div ali…

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

  • Info Line 1, Column 16768: ID "search-results" first defined here
    …l' style='display: block;'> <div  id='search-results' class='content'> </div> …
  • Error Line 18, Column 634: there is no attribute "margin-left:"
    …ent'><div align="center" margin-left:=""><script type="text/javascript" src="h…

    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.

  • Error Line 18, Column 860: there is no attribute "width"
    …cb");/*]]>*/</script><p><fb:fan width="300" logobar="1" connections="10" strea…

    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.

  • Error Line 18, Column 874: there is no attribute "logobar"
    …script><p><fb:fan width="300" logobar="1" connections="10" stream="0" profile_…

    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.

  • Error Line 18, Column 890: there is no attribute "connections"
    …n width="300" logobar="1" connections="10" stream="0" profile_id="58608795408"…

    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.

  • Error Line 18, Column 902: there is no attribute "stream"
    …" logobar="1" connections="10" stream="0" profile_id="58608795408"></fb:fan></…

    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.

  • Error Line 18, Column 917: there is no attribute "profile_id"
    …onnections="10" stream="0" profile_id="58608795408"></fb:fan></p></div> </div>…

    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.

  • Error Line 18, Column 930: element "fb:fan" undefined
    …0" stream="0" profile_id="58608795408"></fb:fan></p></div> </div> <div  class=…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 18, Column 2074: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … to name 2 Pluto moons</a> </h2> <p><p>Astronomers announced a contest Monday …

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

  • Error Line 18, Column 2238: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <a href='http://www.abcactio…

    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.

  • Error Line 18, Column 2886: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ck anchor to read news</a> </h2> <p><p>If you love to get your news online, bu…

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

  • Error Line 18, Column 3181: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <a href='http://www.abcactio…

    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.

  • Error Line 18, Column 3768: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … contain personal data</a> </h2> <p><p>John Matarese has a warning for anyone …

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

  • Warning Line 18, Column 4212: character "&" is the first character of a delimiter but occurred as data
    …tech' class='fontStyle2'>More Science & Tech &raquo;</a></div></div> </div></d…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 18, Column 5244: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s up after SOTU tweets</a> </h2> <p><p>Tennessee Democratic Rep. Steve Cohen c…

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

  • Warning Line 18, Column 6070: character "&" is the first character of a delimiter but occurred as data
    …rence' title='The difference: Meteors & meteorites'> <img src="http://media2.a…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 18, Column 6252: character "&" is the first character of a delimiter but occurred as data
    …_80.JPG" alt='The difference: Meteors & meteorites' title='The difference: Met…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 18, Column 6297: character "&" is the first character of a delimiter but occurred as data
    …rites' title='The difference: Meteors & meteorites'/></a> <div> <h2> <a href='…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 18, Column 6500: character "&" is the first character of a delimiter but occurred as data
    …e-difference'>The difference: Meteors & meteorites</a> </h2> <p><p>Friday's me…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 18, Column 6528: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …: Meteors & meteorites</a> </h2> <p><p>Friday's meteor impact caused a shockwa…

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

  • Error Line 18, Column 7997: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0 hurt in meteor blast</a> </h2> <p><p>A Russian health official says nearly 1…

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

  • Error Line 18, Column 9741: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …nce travel "excessive"</a> </h2> <p><p>The state's largest property insurance …

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

  • Error Line 18, Column 10825: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … your baby's pacifier?</a> </h2> <p><p>Many babies want them. Some babies need…

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

  • Error Line 18, Column 11911: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …Local warehouse stores</a> </h2> <p><p>We looked through two years of food saf…

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

  • Error Line 18, Column 14216: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …a> </div> <span class='description'><p>A few of our friends from the Northeast…

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

  • Error Line 18, Column 14981: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …a> </div> <span class='description'><p>Click inside for images from the papacy…

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

  • Error Line 18, Column 15129: end tag for "ul" which is not finished
    …  class='paginationDisplay'> <ul> </ul> </div> </div> </div></div></div> </div…

    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.

  • Warning Line 18, Column 15870: character "<" is the first character of a delimiter but occurred as data
    …(!(istCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 18, Column 15873: character "&" is the first character of a delimiter but occurred as data
    …istCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none")==…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 18, Column 15874: character "&" is the first character of a delimiter but occurred as data
    …stCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none")==-…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 18, Column 16164: an attribute specification must start with a name or name token
    …lse{zone=pageZone};  ads[tile] = '<scr' + 'ipt language="JavaScript" src="http…

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

  • Error Line 18, Column 16164: element "scr" undefined
    …lse{zone=pageZone};  ads[tile] = '<scr' + 'ipt language="JavaScript" src="http…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 18, Column 16602: delimiter "'" invalid: only S separators and TAGC allowed here
    …0000 + '" type="text/javascript"></scr' + 'ipt>'; document.write(ads[tile]); i…
  • Error Line 18, Column 16669: required attribute "type" not specified
    …s[tile]); istCount++;</script> <script>/*<![CDATA[*/var adRefreshTimeout=1000;…

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

  • Error Line 18, Column 17696: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …Preventing dryer fires</a> </h2> <p><p>Thousands of house fires are started ea…

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

  • Error Line 18, Column 18766: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …u 'like' can haunt you</a> </h2> <p><p>John Matarese warns about how "liking" …

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

  • Error Line 18, Column 18891: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <h2> <a href='http://www.abc…

    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.

  • Error Line 18, Column 19105: end tag for "ul" which is not finished
    …</h2> <ul class='article-options'></ul></li> <li> <h2> <a href='http://www.abc…

    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.

  • Error Line 18, Column 19660: end tag for "ul" which is not finished
    …</h2> <ul class='article-options'></ul></li> </ol> <div  class='moreLinkFooter…

    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.

  • Error Line 18, Column 20756: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …test 'parachute' heart</a> </h2> <p><p>If you watched Grey's Anatomy on Thursd…

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

  • Error Line 18, Column 21751: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …obs linked to chemical</a> </h2> <p><p>There are many men who have unusually l…

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

  • Error Line 18, Column 22002: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <h2> <a href='http://www.abc…

    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.

  • Error Line 18, Column 22642: end tag for "ul" which is not finished
    …</h2> <ul class='article-options'></ul></li> <li> <h2> <a href='http://www.abc…

    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.

  • Error Line 18, Column 24123: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … needs a forever home!</a> </h2> <p><p>Caesar is a very special doggie from th…

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

  • Error Line 18, Column 24371: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <a href='http://www.abcactio…

    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.

  • Error Line 18, Column 24810: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …paghetti squash recipe</a> </h2> <p><p>The next time you're in the mood for pa…

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

  • Error Line 18, Column 24967: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <h2> <a href='http://www.abc…

    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.

  • Error Line 18, Column 25181: end tag for "ul" which is not finished
    …</h2> <ul class='article-options'></ul></li> <li> <h2> <a href='http://www.abc…

    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.

  • Error Line 18, Column 25344: end tag for "ul" which is not finished
    …</h2> <ul class='article-options'></ul></li> <li> <h2> <a href='http://www.abc…

    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.

  • Error Line 18, Column 26847: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …d by strange 911 calls</a> </h2> <p><p>New York City police said Thursday they…

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

  • Error Line 18, Column 27059: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <a href='http://www.abcactio…

    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.

  • Error Line 18, Column 27612: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …Lady Gaga's Tampa show</a> </h2> <p><p>Lady Gaga canceled the rest of her tour…

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

  • Error Line 18, Column 27788: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <h2> <a href='http://www.abc…

    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.

  • Error Line 18, Column 28014: end tag for "ul" which is not finished
    …</h2> <ul class='article-options'></ul></li> <li> <h2> <a href='http://www.abc…

    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.

  • Error Line 18, Column 28259: end tag for "ul" which is not finished
    …</h2> <ul class='article-options'></ul></li> <li> <h2> <a href='http://www.abc…

    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.

  • Warning Line 18, Column 28435: character "&" is the first character of a delimiter but occurred as data
    …s-spread-the-love-all-around'>Mumford & Sons wins Album of the Year</a> </h2> …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 18, Column 28507: end tag for "ul" which is not finished
    …</h2> <ul class='article-options'></ul></li> </ol> <div  class='moreLinkFooter…

    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.

  • Error Line 18, Column 28813: ID "m57952208" already defined
    …id='m57952208' class='mod'> <div  id='m57952208' class='module generic iframe'…

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

  • Info Line 18, Column 28779: ID "m57952208" first defined here
    …'></div> <div  class="ftr"> <div  id='m57952208' class='mod'> <div  id='m57952…
  • Error Line 18, Column 29079: value of attribute "id" invalid: "5" cannot start a name
    …v  class='br'></div> </div> <div  id='57952208-1' class='ui-tabs-panel'> <div …

    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.

  • Error Line 18, Column 29196: ID "search-results" already defined
    …l' style='display: block;'> <div  id='search-results' class='content' style='h…

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

  • Info Line 1, Column 16768: ID "search-results" first defined here
    …l' style='display: block;'> <div  id='search-results' class='content'> </div> …
  • Error Line 18, Column 29381: document type does not allow element "style" here
    …tyles.css" />--><style type="text/css">#mfl .wex3 .city-state{margin:-25px 0 2…

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

  • Error Line 18, Column 31687: there is no attribute "href"
    …td>--><td width="10%"><g:plusone href="http://www.abcactionnews.com" size="med…

    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.

  • Error Line 18, Column 31723: there is no attribute "size"
    …f="http://www.abcactionnews.com" size="medium"></g:plusone></td> <td width="14…

    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.

  • Error Line 18, Column 31731: element "g:plusone" undefined
    …//www.abcactionnews.com" size="medium"></g:plusone></td> <td width="14%"><a hr…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 18, Column 36432: end tag for "tr" which is not finished
    …brity">Celebrity</a></td></tr><tr></tr><tr><td class="footernav" width="20%"><…

    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.

  • Error Line 18, Column 39262: end tag for "tr" which is not finished
    …/news/sitemap">Sitemap</a></td>--></tr><tr><td class="footernav" width="20%"><…

    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.

  • Error Line 24, Column 2256: document type does not allow element "link" here
    …ction/tinybox2.css" rel="stylesheet" /></p><script type="text/javascript" src=…

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

  • Warning Line 24, Column 4571: character "<" is the first character of a delimiter but occurred as data
    …(!(istCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 24, Column 4574: character "&" is the first character of a delimiter but occurred as data
    …istCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none")==…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 24, Column 4575: character "&" is the first character of a delimiter but occurred as data
    …stCount>0)){istCount=1}if(istCount<3 && ("" + location).indexOf("ist=none")==-…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 24, Column 4865: an attribute specification must start with a name or name token
    …lse{zone=pageZone};  ads[tile] = '<scr' + 'ipt language="JavaScript" src="http…

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

  • Error Line 24, Column 4865: element "scr" undefined
    …lse{zone=pageZone};  ads[tile] = '<scr' + 'ipt language="JavaScript" src="http…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 24, Column 5302: delimiter "'" invalid: only S separators and TAGC allowed here
    …0000 + '" type="text/javascript"></scr' + 'ipt>'; document.write(ads[tile]); i…
  • Error Line 24, Column 5369: required attribute "type" not specified
    …s[tile]); istCount++;</script> <script>/*<![CDATA[*/var adRefreshTimeout=1000;…

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

  • Error Line 24, Column 5599: there is no attribute "url"
    … <a href='http://www.scripps.com' url='http://media2.abcactionnews.com//photo/…

    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.

  • Error Line 24, Column 6045: element "nobr" undefined
    …opy;2013 The E.W. Scripps Co.</p><nobr> <div  class='legal'> <ul class='fontSt…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 24, Column 6815: required attribute "type" not specified
    ….com --> <script language="JavaScript"> var lin_s_account, lin_linkInternalFil…

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

  • Error Line 28, Column 164: required attribute "type" not specified
    …code_scripps_new2.js"></script> <style>#mfl #m57952207{background:transparent …

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

  • Error Line 28, Column 164: document type does not allow element "style" here
    …code_scripps_new2.js"></script> <style>#mfl #m57952207{background:transparent …

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

  • Warning Line 28, Column 2559: cannot generate system identifier for general entity "limit"
    …beat.com/toppages/?host="+d.hostUrl+"&limit=15&apikey=06de469f576be61d2dcc350e…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 28, Column 2559: general entity "limit" not defined and no default entity
    …beat.com/toppages/?host="+d.hostUrl+"&limit=15&apikey=06de469f576be61d2dcc350e…

    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.

  • Warning Line 28, Column 2564: reference not terminated by REFC delimiter
    …com/toppages/?host="+d.hostUrl+"&limit=15&apikey=06de469f576be61d2dcc350e4e602…

    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.

  • Error Line 28, Column 2564: reference to entity "limit" for which no system identifier could be generated
    …com/toppages/?host="+d.hostUrl+"&limit=15&apikey=06de469f576be61d2dcc350e4e602…

    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.

  • Info Line 28, Column 2558: entity was defined here
    …tbeat.com/toppages/?host="+d.hostUrl+"&limit=15&apikey=06de469f576be61d2dcc350…
  • Warning Line 28, Column 2568: cannot generate system identifier for general entity "apikey"
    …toppages/?host="+d.hostUrl+"&limit=15&apikey=06de469f576be61d2dcc350e4e602f0a"…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 28, Column 2568: general entity "apikey" not defined and no default entity
    …toppages/?host="+d.hostUrl+"&limit=15&apikey=06de469f576be61d2dcc350e4e602f0a"…

    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.

  • Warning Line 28, Column 2574: reference not terminated by REFC delimiter
    …es/?host="+d.hostUrl+"&limit=15&apikey=06de469f576be61d2dcc350e4e602f0a";_curr…

    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.

  • Error Line 28, Column 2574: reference to entity "apikey" for which no system identifier could be generated
    …es/?host="+d.hostUrl+"&limit=15&apikey=06de469f576be61d2dcc350e4e602f0a";_curr…

    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.

  • Info Line 28, Column 2567: entity was defined here
    …/toppages/?host="+d.hostUrl+"&limit=15&apikey=06de469f576be61d2dcc350e4e602f0a…
  • Warning Line 28, Column 3534: character "<" is the first character of a delimiter but occurred as data
    …urrentPageTitle,_currentPageTitleList)<0){_currentNumberOfElements++;_currentP…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 28, Column 4182: character ")" not allowed in attribute specification list
    …("down")}else{if(_currentRank<_oldRank){_currentTrendingList.push("^")}}}}}}h(…
  • Error Line 28, Column 4182: element "_oldRank" undefined
    …("down")}else{if(_currentRank<_oldRank){_currentTrendingList.push("^")}}}}}}h(…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 28, Column 5242: character ";" not allowed in attribute specification list
    …idx=0;idx<_currentPageTitleList.length;idx++){if(_currentTrendingList[idx]=="-…
  • Error Line 28, Column 5242: element "_currentPageTitleList.length" undefined
    …idx=0;idx<_currentPageTitleList.length;idx++){if(_currentTrendingList[idx]=="-…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 28, Column 6873: character "&" is the first character of a delimiter but occurred as data
    ….appendTo("#cell"+idx)}if(_isFirstTime&&_isSecondTime){_isFirstTime=false}else…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 28, Column 6875: cannot generate system identifier for general entity "_isSecondTime"
    …ppendTo("#cell"+idx)}if(_isFirstTime&&_isSecondTime){_isFirstTime=false}else{_…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 28, Column 6875: general entity "_isSecondTime" not defined and no default entity
    …ppendTo("#cell"+idx)}if(_isFirstTime&&_isSecondTime){_isFirstTime=false}else{_…

    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.

  • Warning Line 28, Column 6888: reference not terminated by REFC delimiter
    …l"+idx)}if(_isFirstTime&&_isSecondTime){_isFirstTime=false}else{_isSecondTime=…

    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.

  • Error Line 28, Column 6888: reference to entity "_isSecondTime" for which no system identifier could be generated
    …l"+idx)}if(_isFirstTime&&_isSecondTime){_isFirstTime=false}else{_isSecondTime=…

    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.

  • Info Line 28, Column 6874: entity was defined here
    …appendTo("#cell"+idx)}if(_isFirstTime&&_isSecondTime){_isFirstTime=false}else{…
  • Error Line 28, Column 8602: end tag for "_currentPageTitleList.length" omitted, but OMITTAG NO was specified
    …ntTrendingList=[]}}})(jQuery);</script><script type='text/javascript'>Echo.Bro…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 5213: start tag was here
    …opularPagesWidgetTitle");for(idx=0;idx<_currentPageTitleList.length;idx++){if(…
  • Error Line 28, Column 8602: end tag for "_oldRank" omitted, but OMITTAG NO was specified
    …ntTrendingList=[]}}})(jQuery);</script><script type='text/javascript'>Echo.Bro…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 4173: start tag was here
    …List.push("down")}else{if(_currentRank<_oldRank){_currentTrendingList.push("^"…
  • Error Line 28, Column 8766: character "(" not allowed in attribute specification list
    …emContent=itemContent.replace(/<object(.*?)<\/object>/g,"[video]");itemContent…
  • Error Line 28, Column 8766: document type does not allow element "object" here
    …emContent=itemContent.replace(/<object(.*?)<\/object>/g,"[video]");itemContent…

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

  • Warning Line 28, Column 8771: character "<" is the first character of a delimiter but occurred as data
    …tent=itemContent.replace(/<object(.*?)<\/object>/g,"[video]");itemContent=item…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 28, Column 8835: character "(" not allowed in attribute specification list
    …emContent=itemContent.replace(/<object(.*?)<\/>/g,"[video]");itemContent=itemC…
  • Warning Line 28, Column 8840: character "<" is the first character of a delimiter but occurred as data
    …tent=itemContent.replace(/<object(.*?)<\/>/g,"[video]");itemContent=itemConten…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 28, Column 8898: character "(" not allowed in attribute specification list
    …emContent=itemContent.replace(/<object(.*?)/g,"[video]");itemContent=itemConte…
  • Error Line 28, Column 8954: character "(" not allowed in attribute specification list
    …;itemContent=itemContent.replace(/<img(.*?)<\/img>/g,"(image)");itemContent=it…
  • Error Line 28, Column 8955: end tag for "img" omitted, but OMITTAG NO was specified
    …itemContent=itemContent.replace(/<img(.*?)<\/img>/g,"(image)");itemContent=ite…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 8950: start tag was here
    …o]");itemContent=itemContent.replace(/<img(.*?)<\/img>/g,"(image)");itemConten…
  • Warning Line 28, Column 8959: character "<" is the first character of a delimiter but occurred as data
    …Content=itemContent.replace(/<img(.*?)<\/img>/g,"(image)");itemContent=itemCon…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 28, Column 9017: character "(" not allowed in attribute specification list
    …;itemContent=itemContent.replace(/<img(.*?)\/>/g,"(image)");itemContent=itemCo…
  • Error Line 28, Column 9018: end tag for "img" omitted, but OMITTAG NO was specified
    …itemContent=itemContent.replace(/<img(.*?)\/>/g,"(image)");itemContent=itemCon…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 9013: start tag was here
    …e)");itemContent=itemContent.replace(/<img(.*?)\/>/g,"(image)");itemContent=it…
  • Error Line 28, Column 9076: character "(" not allowed in attribute specification list
    …;itemContent=itemContent.replace(/<img(.*?)/g,"(image)");itemContent=itemConte…
  • Error Line 28, Column 9077: end tag for "img" omitted, but OMITTAG NO was specified
    …itemContent=itemContent.replace(/<img(.*?)/g,"(image)");itemContent=itemConten…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 9072: start tag was here
    …e)");itemContent=itemContent.replace(/<img(.*?)/g,"(image)");itemContent=itemC…
  • Error Line 28, Column 9133: character "(" not allowed in attribute specification list
    …itemContent=itemContent.replace(/<font(.*?)<\/font>/g,"(font)");itemContent=it…
  • Warning Line 28, Column 9138: character "<" is the first character of a delimiter but occurred as data
    …ontent=itemContent.replace(/<font(.*?)<\/font>/g,"(font)");itemContent=itemCon…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 28, Column 9197: character "(" not allowed in attribute specification list
    …itemContent=itemContent.replace(/<font(.*?)\/>/g,"(font)");itemContent=itemCon…
  • Error Line 28, Column 9256: character "(" not allowed in attribute specification list
    …itemContent=itemContent.replace(/<font(.*?)/g,"(font)");itemContent=itemConten…
  • Error Line 28, Column 9313: character "(" not allowed in attribute specification list
    …temContent=itemContent.replace(/<embed(.*?)<\/embed>/g,"(embed)");itemContent=…
  • Error Line 28, Column 9313: element "embed" undefined
    …temContent=itemContent.replace(/<embed(.*?)<\/embed>/g,"(embed)");itemContent=…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 28, Column 9318: character "<" is the first character of a delimiter but occurred as data
    …ntent=itemContent.replace(/<embed(.*?)<\/embed>/g,"(embed)");itemContent=itemC…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 28, Column 9380: character "(" not allowed in attribute specification list
    …temContent=itemContent.replace(/<embed(.*?)\/>/g,"(embed)");itemContent=itemCo…
  • Error Line 28, Column 9380: element "embed" undefined
    …temContent=itemContent.replace(/<embed(.*?)\/>/g,"(embed)");itemContent=itemCo…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 28, Column 9441: character "(" not allowed in attribute specification list
    …temContent=itemContent.replace(/<embed(.*?)/g,"(embed)");itemContent=itemConte…
  • Error Line 28, Column 9441: element "embed" undefined
    …temContent=itemContent.replace(/<embed(.*?)/g,"(embed)");itemContent=itemConte…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 28, Column 9500: character "(" not allowed in attribute specification list
    …emContent=itemContent.replace(/<script(.*?)<\/script>/g,"(script)");itemConten…
  • Warning Line 28, Column 9505: character "<" is the first character of a delimiter but occurred as data
    …tent=itemContent.replace(/<script(.*?)<\/script>/g,"(script)");itemContent=ite…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 28, Column 9570: character "(" not allowed in attribute specification list
    …emContent=itemContent.replace(/<script(.*?)\/>/g,"(script)");itemContent=itemC…
  • Error Line 28, Column 9570: document type does not allow element "script" here
    …emContent=itemContent.replace(/<script(.*?)\/>/g,"(script)");itemContent=itemC…

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

  • Error Line 28, Column 9633: character "(" not allowed in attribute specification list
    …emContent=itemContent.replace(/<script(.*?)/g,"(script)");c.postData.content=i…
  • Error Line 28, Column 9633: document type does not allow element "script" here
    …emContent=itemContent.replace(/<script(.*?)/g,"(script)");c.postData.content=i…

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

  • Error Line 28, Column 10262: end tag for element "div" which is not open
    …le,cComment:commentContent},function(d){})}});</script> </div> </body> </html> 

    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.

  • Error Line 28, Column 10270: end tag for "script" omitted, but OMITTAG NO was specified
    …le,cComment:commentContent},function(d){})}});</script> </div> </body> </html> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 9563: start tag was here
    …t)");itemContent=itemContent.replace(/<script(.*?)\/>/g,"(script)");itemConten…
  • Error Line 28, Column 10270: end tag for "script" omitted, but OMITTAG NO was specified
    …le,cComment:commentContent},function(d){})}});</script> </div> </body> </html> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 9493: start tag was here
    …d)");itemContent=itemContent.replace(/<script(.*?)<\/script>/g,"(script)");ite…
  • Error Line 28, Column 10270: end tag for "embed" omitted, but OMITTAG NO was specified
    …le,cComment:commentContent},function(d){})}});</script> </div> </body> </html> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 9435: start tag was here
    …d)");itemContent=itemContent.replace(/<embed(.*?)/g,"(embed)");itemContent=ite…
  • Error Line 28, Column 10270: end tag for "embed" omitted, but OMITTAG NO was specified
    …le,cComment:commentContent},function(d){})}});</script> </div> </body> </html> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 9374: start tag was here
    …d)");itemContent=itemContent.replace(/<embed(.*?)\/>/g,"(embed)");itemContent=…
  • Error Line 28, Column 10270: end tag for "embed" omitted, but OMITTAG NO was specified
    …le,cComment:commentContent},function(d){})}});</script> </div> </body> </html> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 9307: start tag was here
    …t)");itemContent=itemContent.replace(/<embed(.*?)<\/embed>/g,"(embed)");itemCo…
  • Error Line 28, Column 10270: end tag for "font" omitted, but OMITTAG NO was specified
    …le,cComment:commentContent},function(d){})}});</script> </div> </body> </html> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 9251: start tag was here
    …t)");itemContent=itemContent.replace(/<font(.*?)/g,"(font)");itemContent=itemC…
  • Error Line 28, Column 10270: end tag for "font" omitted, but OMITTAG NO was specified
    …le,cComment:commentContent},function(d){})}});</script> </div> </body> </html> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 9192: start tag was here
    …t)");itemContent=itemContent.replace(/<font(.*?)\/>/g,"(font)");itemContent=it…
  • Error Line 28, Column 10270: end tag for "font" omitted, but OMITTAG NO was specified
    …le,cComment:commentContent},function(d){})}});</script> </div> </body> </html> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 9128: start tag was here
    …e)");itemContent=itemContent.replace(/<font(.*?)<\/font>/g,"(font)");itemConte…
  • Error Line 28, Column 10270: end tag for "object" omitted, but OMITTAG NO was specified
    …le,cComment:commentContent},function(d){})}});</script> </div> </body> </html> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 8891: start tag was here
    …o]");itemContent=itemContent.replace(/<object(.*?)/g,"[video]");itemContent=it…
  • Error Line 28, Column 10270: end tag for "object" omitted, but OMITTAG NO was specified
    …le,cComment:commentContent},function(d){})}});</script> </div> </body> </html> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 8828: start tag was here
    …o]");itemContent=itemContent.replace(/<object(.*?)<\/>/g,"[video]");itemConten…
  • Error Line 28, Column 10270: end tag for "object" omitted, but OMITTAG NO was specified
    …le,cComment:commentContent},function(d){})}});</script> </div> </body> </html> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 8759: start tag was here
    …tent;itemContent=itemContent.replace(/<object(.*?)<\/object>/g,"[video]");item…
  • Error Line 28, Column 10270: end tag for "script" omitted, but OMITTAG NO was specified
    …le,cComment:commentContent},function(d){})}});</script> </div> </body> </html> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 28, Column 8603: start tag was here
    …tTrendingList=[]}}})(jQuery);</script><script type='text/javascript'>Echo.Broa…

Visitor Analysis

Daily Visitor
  • 5.950 visits