WXYZ 7 Action News is Detroit's breaking news, weather forecast and sports leader. Channel 7 is Detroit's ABC TV station -- On-air, online at WXYZ.com and always Taking Action for You. ...

wxyz.com
  • Domain Name
    wxyz.com
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #31012
  • Page Size
    130.4 KB
  • Ip Address
    204.154.142.84
  • Heading
    H1: 0, H2: 33, H3: 2, H4: 3, H5: 0, H6: 0
  • Images
    2 GIF, 50 JPG, 23 PNG

Website Meta Analysis

  • Title
    WXYZ.COM | Detroit, Michigan Local News, Weather, Sports from 7 Action News and WXYZ-TV Channel 7
  • Meta Keyword
    detroit, news, local, michigan, weather, sports, wxyz, tv, channel 7, homepage, click, lions, tigers, red wings, pistons, forecast, snow, Detroit Michigan WXYZ-TV Channel 7 Breaking News Weather ABC
  • Meta Description
    WXYZ 7 Action News is Detroit's breaking news, weather forecast and sports leader. Channel 7 is Detroit's ABC TV station -- On-air, online at WXYZ.com and always Taking Action for You.

Technical Analysis

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

Hyper Text Transfer Protocol (HTTP) header show data header response from wxyz.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: "cdc7589e"
  • content-type: text/html;charset=utf-8
  • content-length: 22724
  • vary: Accept-Encoding
  • date: Fri, 27 Sep 2013 15:23:15 GMT
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for wxyz.com

DNS Analysis


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


DNS Records

Answer records
wxyz.com SOA
server: ns1.scripps.com
email: hostmaster@scripps.com
serial: 2013010401
refresh: 7200
retry: 3600
expire: 604800
minimum ttl: 3600
3600s
wxyz.com NS  ns1.scripps.com 3600s
wxyz.com NS  ns2.scripps.com 3600s
wxyz.com A 204.154.142.84 3600s
wxyz.com MX
preference: 10
exchange: wxyz-com.mail.eo.outlook.com
3600s
wxyz.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
  • 203 Errors
  • 62 Warnings
Ratio Text/Html
  • 0.6851803303247069
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 937: end tag for "meta" omitted, but OMITTAG NO was specified
    …om and always Taking Action for You."><meta name="Keywords" content="detroit, …

    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 717: start tag was here
    …a http-equiv='expires' content='-1' /><meta name="Description" content="WXYZ 7…
  • Error Line 1, Column 1168: end tag for "meta" omitted, but OMITTAG NO was specified
    … Channel 7 Breaking News Weather ABC"><meta http-equiv='refresh' content='600'…

    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 937: start tag was here
    …om and always Taking Action for You."><meta name="Keywords" content="detroit, …
  • Error Line 1, Column 1209: end tag for "meta" omitted, but OMITTAG NO was specified
    …ta http-equiv='refresh' content='600'><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 1168: start tag was here
    … Channel 7 Breaking News Weather ABC"><meta http-equiv='refresh' content='600'…
  • Warning Line 1, Column 1305: cannot generate system identifier for general entity "obfType"
    …me' href='/feeds/rssFeed?siteId=10017&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 1305: general entity "obfType" not defined and no default entity
    …me' href='/feeds/rssFeed?siteId=10017&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 1312: reference not terminated by REFC delimiter
    …f='/feeds/rssFeed?siteId=10017&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 1312: reference to external entity in attribute value
    …f='/feeds/rssFeed?siteId=10017&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 1312: reference to entity "obfType" for which no system identifier could be generated
    …f='/feeds/rssFeed?siteId=10017&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 1304: entity was defined here
    …ome' href='/feeds/rssFeed?siteId=10017&obfType=RSS_FEED&categoryId=10000'/><li…
  • Warning Line 1, Column 1322: cannot generate system identifier for general entity "categoryId"
    …rssFeed?siteId=10017&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 1322: general entity "categoryId" not defined and no default entity
    …rssFeed?siteId=10017&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 1332: reference not terminated by REFC delimiter
    …teId=10017&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 1332: reference to external entity in attribute value
    …teId=10017&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 1332: reference to entity "categoryId" for which no system identifier could be generated
    …teId=10017&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 1321: entity was defined here
    …/rssFeed?siteId=10017&obfType=RSS_FEED&categoryId=10000'/><link rel='shortcut …
  • Error Line 1, Column 1749: 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 3306: S separator in comment declaration
    …annel 7 is Detroit's ABC TV station -- On-air, online at WXYZ.com and always T…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1, Column 3307: invalid comment declaration: found name start character outside comment but inside comment declaration
    …nnel 7 is Detroit's ABC TV station -- On-air, online at WXYZ.com and always Ta…
  • Info Line 1, Column 2704: comment declaration started here
    …-- /h --> <!-- used for Google CSE --><!--<PageMap><DataObject type="Date"><At…
  • Error Line 1, Column 3308: character data is not allowed here
    …nel 7 is Detroit's ABC TV station -- On-air, online at WXYZ.com and always Tak…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 1, Column 3386: there is no attribute "name"
    …ing Action for You."/><Attribute name="Keywords" value="detroit, news, local, …

    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 3403: there is no attribute "value"
    …u."/><Attribute name="Keywords" value="detroit, news, local, michigan, weather…

    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 3542: element "Attribute" undefined
    …, red wings, pistons, forecast, snow"/><Attribute name="ModDate" value="201302…

    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 3595: element "Attribute" undefined
    …e="ModDate" value="20130211 09:53:26"/><Attribute name="PubDate" value="201001…

    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 3648: element "Attribute" undefined
    …e="PubDate" value="20100126 03:00:32"/></DataObject></PageMap>--> </head> <bod…

    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 3661: end tag for element "DataObject" which is not open
    …alue="20100126 03:00:32"/></DataObject></PageMap>--> </head> <body> <div id="m…

    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 3671: end tag for element "PageMap" which is not open
    …0126 03:00:32"/></DataObject></PageMap>--> </head> <body> <div id="mfl"> <!-- …

    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 3672: character data is not allowed here
    …126 03:00:32"/></DataObject></PageMap>--> </head> <body> <div id="mfl"> <!-- l…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 1, Column 4276: character "&" is the first character of a delimiter but occurred as data
    …stration.aspx?contestid=17895'>Alerts & Email</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 4359: character "&" is the first character of a delimiter but occurred as data
    ….com/subindex/about_us/mobile'>Mobile & Apps</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 5267: 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 5270: 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 5271: 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 5467: 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 5467: 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 5863: delimiter "'" invalid: only S separators and TAGC allowed here
    …0000 + '" type="text/javascript"></scr' + 'ipt>'; document.write('<div class="…
  • Error Line 1, Column 5912: 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 5951: 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 5891: start tag was here
    …ipt"></scr' + 'ipt>'; document.write('<div class="moduleAd">'); document.write…
  • Error Line 1, Column 6027: 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 5952: start tag was here
    …); document.write(ads[tile]);</script><script language="JavaScript" type="text…
  • Error Line 1, Column 6027: 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 4837: start tag was here
    …l class='searchbar line fontStyle31'> <li><script language="JavaScript" type="…
  • Error Line 1, Column 6027: 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 4797: start tag was here
    …itlaw.tv'>DetroitLaw.tv</a></li></ul> <ul class='searchbar line fontStyle31'> …
  • Error Line 1, Column 6052: 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 6061: 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 6121: 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 6126: 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 6324: 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 6414: 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 6551: 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 6472: start tag was here
    …on value="web">Web</option> </select> <input type="button" value="  GO>> " alt…
  • Error Line 1, Column 6930: end tag for element "ul" which is not open
    …d="fwl_wxyz";/*]]>*/</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 8669: character "&" is the first character of a delimiter but occurred as data
    …xyz.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 9069: 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 10810: character "&" is the first character of a delimiter but occurred as data
    …m/subindex/news/science_tech'>SCIENCE & TECH</a></li></ul></li> <li><a href='h…

    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 13626: character "&" is the first character of a delimiter but occurred as data
    …affairs/brightest_and_best'>BRIGHTEST & BEST</a></li></ul></li></ul> <script t…

    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 14356: 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 14359: 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 14360: 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 14636: 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 14636: 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 15057: delimiter "'" invalid: only S separators and TAGC allowed here
    …0000 + '" type="text/javascript"></scr' + 'ipt>'; document.write(ads[tile]); i…
  • Error Line 1, Column 15124: 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 15512: there is no attribute "url"
    …/school_closings' class='closing' url='http://www.wxyz.com/subindex/weather/sc…

    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 15754: there is no attribute "ttl"
    …ass='refresh'><div id='nwsAlerts' ttl='1' url='/refreshmodule/0/57955001'><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 15762: there is no attribute "url"
    …resh'><div id='nwsAlerts' ttl='1' url='/refreshmodule/0/57955001'><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 15864: 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.wxyz.com/subindex/w…

    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 17973: there is no attribute "refid"
    …al court'>Read More</a></li><li refid='wxyz-8240655' url='http://www.wxyz.com/…

    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 17992: there is no attribute "url"
    …</a></li><li refid='wxyz-8240655' url='http://www.wxyz.com/dpp/news/local_news…

    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 30437: 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 30448: 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 31610: 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 32340: 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 33151: 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 33915: 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 34703: end tag for "ul" which is not finished
    …;</p> <ul class='article-options'></ul></div></li></ul></div> <div  class='rig…

    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 36325: end tag for "ul" which is not finished
    …y</a> <ul class='article-options'></ul></li> <li><a href='http://www.wxyz.com/…

    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 37379: end tag for "ul" which is not finished
    …?</a> <ul class='article-options'></ul></li> <li><a href='http://www.wxyz.com/…

    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 38459: end tag for "ul" which is not finished
    …r</a> <ul class='article-options'></ul></li> <li><a href='http://www.wxyz.com/…

    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 39109: end tag for "ul" which is not finished
    …e</a> <ul class='article-options'></ul></li> <li><a href='http://www.wxyz.com/…

    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 39310: end tag for "ul" which is not finished
    …y</a> <ul class='article-options'></ul></li> <li><a href='http://www.wxyz.com/…

    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 39527: end tag for "ul" which is not finished
    …s</a> <ul class='article-options'></ul></li> <li><a href='http://www.wxyz.com/…

    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 39752: end tag for "ul" which is not finished
    …s</a> <ul class='article-options'></ul></li> <li><a href='http://www.wxyz.com/…

    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 39970: end tag for "ul" which is not finished
    …e</a> <ul class='article-options'></ul></li> <li><a href='http://www.wxyz.com/…

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

  • Error Line 1, Column 41806: value of attribute "id" invalid: "8" cannot start a name
    …v  class='br'></div> </div> <div  id='83677845-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.

  • Warning Line 1, Column 43360: reference not terminated by REFC delimiter
    … Oakland County</a> </span><span>&nbsp</span></td></tr><tr style='width:100%;'…

    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 43602: reference not terminated by REFC delimiter
    …> Macomb County</a> </span><span>&nbsp</span></td><td width='30%'><span style=…

    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 44053: reference not terminated by REFC delimiter
    …St Clair County</a> </span><span>&nbsp</span></td></tr><tr style='width:100%;'…

    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 44295: reference not terminated by REFC delimiter
    …> Monroe County</a> </span><span>&nbsp</span></td><td width='30%'><span style=…

    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 44516: reference not terminated by REFC delimiter
    …vingston County</a> </span><span>&nbsp</span></td></tbody></table></div></div>…

    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 1, Column 44535: end tag for "tr" omitted, but OMITTAG NO was specified
    … </span><span>&nbsp</span></td></tbody></table></div></div></div> <div  class=…

    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 44070: start tag was here
    …a> </span><span>&nbsp</span></td></tr><tr style='width:100%;'><td width='30%'>…
  • Warning Line 1, Column 45104: 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 45107: 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 45108: 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 45384: 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 45384: 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 45805: delimiter "'" invalid: only S separators and TAGC allowed here
    …0000 + '" type="text/javascript"></scr' + 'ipt>'; document.write(ads[tile]); i…
  • Error Line 1, Column 45872: 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 46024: ID "m83487041" already defined
    …id='m83487041' class='mod'> <div  id='m83487041' 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 45990: ID "m83487041" first defined here
    … </div> <div  class='col3'> <div  id='m83487041' class='mod'> <div  id='m83487…
  • Error Line 1, Column 46277: value of attribute "id" invalid: "8" cannot start a name
    …v  class='br'></div> </div> <div  id='83487041-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 46394: 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 41923: ID "search-results" first defined here
    …l' style='display: block;'> <div  id='search-results' class='content' style='h…
  • Error Line 1, Column 46471: document type does not allow element "style" here
    …height:35px'><p><style type="text/css"></style><iframe frameborder="0" id="wat…

    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 46872: ID "m57955019" already defined
    …id='m57955019' class='mod'> <div  id='m57955019' class='module wex3'> <div  cl…

    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 46838: ID "m57955019" first defined here
    … </div></div> </div> </div> <div  id='m57955019' class='mod'> <div  id='m57955…
  • Error Line 1, Column 48063: ID "m87176690" already defined
    …id='m87176690' class='mod'> <div  id='m87176690' 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 48029: ID "m87176690" first defined here
    …> </div></div></div> </div> <div  id='m87176690' class='mod'> <div  id='m87176…
  • Error Line 1, Column 48822: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ck for peak wind gusts</a> </h2> <p><p> <font color="black" face="Tahoma" size…

    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 1, Column 49956: 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 49959: 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 49960: 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 50236: 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 50236: 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 50692: delimiter "'" invalid: only S separators and TAGC allowed here
    …0000 + '" type="text/javascript"></scr' + 'ipt>'; document.write(ads[tile]); i…
  • Error Line 1, Column 50759: 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 50961: ID "m83518508" already defined
    …id='m83518508' class='mod'> <div  id='m83518508' 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 1, Column 50927: ID "m83518508" first defined here
    …nt</div></div></div> </div> <div  id='m83518508' class='mod'> <div  id='m83518…
  • Error Line 1, Column 51212: value of attribute "id" invalid: "8" cannot start a name
    …v  class='br'></div> </div> <div  id='83518508-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 51329: ID "search-results" already defined
    …l' style='display: block;'> <div  id='search-results' class='content'><p><img …

    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 41923: ID "search-results" first defined here
    …l' style='display: block;'> <div  id='search-results' class='content' style='h…
  • Error Line 1, Column 52263: ID "m57954991" already defined
    …id='m57954991' class='mod'> <div  id='m57954991' 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 52229: ID "m57954991" first defined here
    … </div></div> </div> </div> <div  id='m57954991' class='mod'> <div  id='m57954…
  • Error Line 1, Column 53052: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ERAGE: Kilpatrick case</a> </h2> <p><p>Kwame Kilpatrick and his father, Bernar…

    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 53269: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <a href='http://www.wxyz.com…

    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 53729: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … Day: Tips and treats!</a> </h2> <p><p>Looking to surprise your sweetie with t…

    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 53940: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <a href='http://www.wxyz.com…

    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 54534: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …oadcasting scholarship</a> </h2> <p><p>Are you a college student currently pur…

    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 54906: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> </ol> </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.

  • Error Line 1, Column 54997: ID "m81227522" already defined
    …id='m81227522' class='mod'> <div  id='m81227522' 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 54963: ID "m81227522" first defined here
    … </div></div> </div> </div> <div  id='m81227522' class='mod'> <div  id='m81227…
  • Error Line 1, Column 55252: value of attribute "id" invalid: "8" cannot start a name
    …v  class='br'></div> </div> <div  id='81227522-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 55369: 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 41923: ID "search-results" first defined here
    …l' style='display: block;'> <div  id='search-results' class='content' style='h…
  • Error Line 1, Column 56375: ID "m57954995" already defined
    …id='m57954995' class='mod'> <div  id='m57954995' 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 1, Column 56341: ID "m57954995" first defined here
    … </div></div> </div> </div> <div  id='m57954995' class='mod'> <div  id='m57954…
  • Error Line 1, Column 56638: value of attribute "id" invalid: "5" cannot start a name
    …v  class='br'></div> </div> <div  id='57954995-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 56755: ID "search-results" already defined
    …l' style='display: block;'> <div  id='search-results' class='content'><p><ifra…

    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 41923: ID "search-results" first defined here
    …l' style='display: block;'> <div  id='search-results' class='content' style='h…
  • Error Line 1, Column 56847: there is no attribute "allowtransparency"
    …no" frameborder="0" allowtransparency="true" style="border: medium none; overf…

    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 58300: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … sued in federal court</a> </h2> <p><p>Wayne County Circuit Court Judge Wade M…

    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 59275: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … on "Kilpatrick, Inc."</a> </h2> <p><p> <strong>BLOG:</strong> Follow along wi…

    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 60194: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ts set to begin Monday</a> </h2> <p><p>Could five months of testimony all come…

    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 60308: end tag for "ul" which is not finished
    …/div> <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 1, Column 61279: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …>Adopt a Detroit park!</a> </h2> <p><p>Last week Detroit City Council failed t…

    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 61530: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <a href='http://detroit2020.…

    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 61974: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …al Detroit 2020 Awards</a> </h2> <p><p>Do you know someone who’s really making…

    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 62096: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <a href='http://detroit2020.…

    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 62621: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …, lifetime of teaching</a> </h2> <p><p>Our Detroit 2020 Person of the Week is …

    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 62790: end tag for "ul" which is not finished
    …/div> <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 1, Column 63871: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …impson sharing&hellip;</a> </h2> <p><p>JESSICA SIMPSON has been giving her bes…

    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 64078: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <a href='http://www.wxyz.com…

    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 64673: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … was soaked by&hellip;</a> </h2> <p><p>VANESSA HUDGENS got a soaking while sho…

    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 64887: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <a href='http://www.wxyz.com…

    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 65452: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ked red carpet&hellip;</a> </h2> <p><p>JULIANNE HOUGH has been fighting sickne…

    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 65666: end tag for "ul" which is not finished
    …/div> <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.

  • Warning Line 1, Column 66054: character "&" is the first character of a delimiter but occurred as data
    …  class="module-bg"><h4>Entertainment & Life</h4> <div  class=''> <div  class=…

    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 66940: 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>Bob Seger & The Silver Bullet Band have…

    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 1, Column 66951: character "&" is the first character of a delimiter but occurred as data
    …span class='description'><p>Bob Seger & The Silver Bullet Band have added a De…

    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 67594: 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>Are you looking for any of the contests…

    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 68498: 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>The ninth annual Motown Winter Blast is…

    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 69291: 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>Henry Ford West Bloomfield Hospital sho…

    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 70019: 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>For more than 15 years Peter Nielsen ha…

    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 70736: 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> <span style="font-size: 12px;">Are wed…

    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 71328: 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>Detroit is a region left behind by the …

    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 72024: 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>Find out about businesses and products …

    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 72640: 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>What's your sign? Get the latest horosc…

    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 72795: 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 1, Column 73536: 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 73539: 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 73540: 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 73816: 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 73816: 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 74251: delimiter "'" invalid: only S separators and TAGC allowed here
    …0000 + '" type="text/javascript"></scr' + 'ipt>'; document.write(ads[tile]); i…
  • Error Line 1, Column 74318: 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 75314: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …, MSU No. 8 in AP poll</a> </h2> <p><p>Michigan drops one spot to fourth in 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 1, Column 75556: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <a href='http://www.wxyz.com…

    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 76116: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …n: Tigers open Tuesday</a> </h2> <p><p>Baseball is almost back. The Detroit Ti…

    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 77081: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … Classic for Verlander</a> </h2> <p><p>When Justin Verlander arrived to Joker …

    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 77322: end tag for "ul" which is not finished
    …/div> <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 1, Column 78420: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …arships at 5-years-old</a> </h2> <p><p>If you’ve been waiting for your child t…

    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 79248: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …your digital afterlife</a> </h2> <p><p>You've probably heard about the importa…

    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 80092: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …Year; Find your zodiac</a> </h2> <p><p>Sunday marks the first day of the Chine…

    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 80284: end tag for "ul" which is not finished
    …/div> <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 1, Column 81359: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … down on car seat laws</a> </h2> <p><p>Michigan lawmakers may no longer let dr…

    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 81509: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <a href='http://www.wxyz.com…

    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 82078: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …Year; Find your zodiac</a> </h2> <p><p>Sunday marks the first day of the Chine…

    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 82270: end tag for "ul" which is not finished
    …/div> <ul class='article-options'></ul></li> <li> <a href='http://www.wxyz.com…

    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 82807: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …gists prepare for snow</a> </h2> <p><p>Take a look behind the scenes as the 7 …

    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 83029: end tag for "ul" which is not finished
    …/div> <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 1, Column 84149: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …arships at 5-years-old</a> </h2> <p><p>If you’ve been waiting for your child t…

    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 85025: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …r: Retire successfully</a> </h2> <p><p>Retirement may be in the distant future…

    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 85813: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …Makeover: Sneaky scams</a> </h2> <p><p>Four ways sneaky scammers are trying 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 86382: ID "m57954993" already defined
    …id='m57954993' class='mod'> <div  id='m57954993' 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 86348: ID "m57954993" first defined here
    …'></div> <div  class="ftr"> <div  id='m57954993' class='mod'> <div  id='m57954…
  • Error Line 1, Column 86648: value of attribute "id" invalid: "5" cannot start a name
    …v  class='br'></div> </div> <div  id='57954993-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 86765: 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 41923: ID "search-results" first defined here
    …l' style='display: block;'> <div  id='search-results' class='content' style='h…
  • Error Line 1, Column 86911: document type does not allow element "link" here
    …ss" rel="stylesheet" type="text/css" /></div><table border="0" cellpadding="0"…

    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 88613: there is no attribute "href"
    …td>--><td width="10%"><g:plusone href="http://www.wxyz.com" size="medium"></g:…

    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 88640: there is no attribute "size"
    …usone href="http://www.wxyz.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 1, Column 88648: element "g:plusone" undefined
    …ef="http://www.wxyz.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 7, Column 58: there is no attribute "property"
    …><meta content="80221381134" property="fb:admins"> <script type="text/javascri…

    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 7, Column 69: document type does not allow element "meta" here
    …ent="80221381134" property="fb:admins"> <script type="text/javascript">/*<![CD…

    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 7, Column 70: end tag for "meta" omitted, but OMITTAG NO was specified
    …nt="80221381134" property="fb:admins"> <script type="text/javascript">/*<![CDA…

    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 7, Column 21: start tag was here
      //]]> </script><p><meta content="80221381134" property="fb:admins"> <script t…
  • Error Line 7, Column 1709: end tag for element "meta" which is not open
    …le.com/js/plusone.js"></script> </meta></p><!-- ******************** BEGIN IPA…

    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 7, Column 1884: 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 7, Column 4127: 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 7, Column 4130: 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 7, Column 4131: 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 7, Column 4407: 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 7, Column 4407: 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 7, Column 4841: delimiter "'" invalid: only S separators and TAGC allowed here
    …0000 + '" type="text/javascript"></scr' + 'ipt>'; document.write(ads[tile]); i…
  • Error Line 7, Column 4908: 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 7, Column 5566: element "nobr" undefined
    …opy;2012 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 7, Column 6140: 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 11, Column 164: required attribute "type" not specified
    …code_scripps_new2.js"></script> <style>#mfl #m57954992{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 11, Column 164: document type does not allow element "style" here
    …code_scripps_new2.js"></script> <style>#mfl #m57954992{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).

  • Error Line 11, Column 3608: character "(" not allowed in attribute specification list
    …emContent=itemContent.replace(/<object(.*?)<\/object>/g,"[video]");itemContent…
  • Error Line 11, Column 3608: 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 11, Column 3613: 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 11, Column 3677: character "(" not allowed in attribute specification list
    …emContent=itemContent.replace(/<object(.*?)<\/>/g,"[video]");itemContent=itemC…
  • Warning Line 11, Column 3682: 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 11, Column 3740: character "(" not allowed in attribute specification list
    …emContent=itemContent.replace(/<object(.*?)/g,"[video]");itemContent=itemConte…
  • Error Line 11, Column 3796: character "(" not allowed in attribute specification list
    …;itemContent=itemContent.replace(/<img(.*?)<\/img>/g,"(image)");itemContent=it…
  • Error Line 11, Column 3797: 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 11, Column 3792: start tag was here
    …o]");itemContent=itemContent.replace(/<img(.*?)<\/img>/g,"(image)");itemConten…
  • Warning Line 11, Column 3801: 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 11, Column 3859: character "(" not allowed in attribute specification list
    …;itemContent=itemContent.replace(/<img(.*?)\/>/g,"(image)");itemContent=itemCo…
  • Error Line 11, Column 3860: 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 11, Column 3855: start tag was here
    …e)");itemContent=itemContent.replace(/<img(.*?)\/>/g,"(image)");itemContent=it…
  • Error Line 11, Column 3918: character "(" not allowed in attribute specification list
    …;itemContent=itemContent.replace(/<img(.*?)/g,"(image)");itemContent=itemConte…
  • Error Line 11, Column 3919: 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 11, Column 3914: start tag was here
    …e)");itemContent=itemContent.replace(/<img(.*?)/g,"(image)");itemContent=itemC…
  • Error Line 11, Column 3975: character "(" not allowed in attribute specification list
    …itemContent=itemContent.replace(/<font(.*?)<\/font>/g,"(font)");itemContent=it…
  • Warning Line 11, Column 3980: 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 11, Column 4039: character "(" not allowed in attribute specification list
    …itemContent=itemContent.replace(/<font(.*?)\/>/g,"(font)");itemContent=itemCon…
  • Error Line 11, Column 4098: character "(" not allowed in attribute specification list
    …itemContent=itemContent.replace(/<font(.*?)/g,"(font)");itemContent=itemConten…
  • Error Line 11, Column 4155: character "(" not allowed in attribute specification list
    …temContent=itemContent.replace(/<embed(.*?)<\/embed>/g,"(embed)");itemContent=…
  • Error Line 11, Column 4155: 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 11, Column 4160: 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 11, Column 4222: character "(" not allowed in attribute specification list
    …temContent=itemContent.replace(/<embed(.*?)\/>/g,"(embed)");itemContent=itemCo…
  • Error Line 11, Column 4222: 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 11, Column 4283: character "(" not allowed in attribute specification list
    …temContent=itemContent.replace(/<embed(.*?)/g,"(embed)");itemContent=itemConte…
  • Error Line 11, Column 4283: 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 11, Column 4342: character "(" not allowed in attribute specification list
    …emContent=itemContent.replace(/<script(.*?)<\/script>/g,"(script)");itemConten…
  • Warning Line 11, Column 4347: 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 11, Column 4412: character "(" not allowed in attribute specification list
    …emContent=itemContent.replace(/<script(.*?)\/>/g,"(script)");itemContent=itemC…
  • Error Line 11, Column 4412: 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 11, Column 4475: character "(" not allowed in attribute specification list
    …emContent=itemContent.replace(/<script(.*?)/g,"(script)");c.postData.content=i…
  • Error Line 11, Column 4475: 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 11, Column 5255: character ";" not allowed in attribute specification list
    …(c.entries);for(i=0;i<c.entries.length;i++){if(c.entries[i].object.content.mat…
  • Error Line 11, Column 5255: element "c.entries.length" undefined
    …(c.entries);for(i=0;i<c.entries.length;i++){if(c.entries[i].object.content.mat…

    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 11, Column 5527: end tag for "c.entries.length" omitted, but OMITTAG NO was specified
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 5238: start tag was here
    … "+b);console.log(c.entries);for(i=0;i<c.entries.length;i++){if(c.entries[i].o…
  • Error Line 11, Column 5534: end tag for element "div" which is not open
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 5542: end tag for "script" omitted, but OMITTAG NO was specified
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 4405: start tag was here
    …t)");itemContent=itemContent.replace(/<script(.*?)\/>/g,"(script)");itemConten…
  • Error Line 11, Column 5542: end tag for "script" omitted, but OMITTAG NO was specified
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 4335: start tag was here
    …d)");itemContent=itemContent.replace(/<script(.*?)<\/script>/g,"(script)");ite…
  • Error Line 11, Column 5542: end tag for "embed" omitted, but OMITTAG NO was specified
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 4277: start tag was here
    …d)");itemContent=itemContent.replace(/<embed(.*?)/g,"(embed)");itemContent=ite…
  • Error Line 11, Column 5542: end tag for "embed" omitted, but OMITTAG NO was specified
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 4216: start tag was here
    …d)");itemContent=itemContent.replace(/<embed(.*?)\/>/g,"(embed)");itemContent=…
  • Error Line 11, Column 5542: end tag for "embed" omitted, but OMITTAG NO was specified
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 4149: start tag was here
    …t)");itemContent=itemContent.replace(/<embed(.*?)<\/embed>/g,"(embed)");itemCo…
  • Error Line 11, Column 5542: end tag for "font" omitted, but OMITTAG NO was specified
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 4093: start tag was here
    …t)");itemContent=itemContent.replace(/<font(.*?)/g,"(font)");itemContent=itemC…
  • Error Line 11, Column 5542: end tag for "font" omitted, but OMITTAG NO was specified
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 4034: start tag was here
    …t)");itemContent=itemContent.replace(/<font(.*?)\/>/g,"(font)");itemContent=it…
  • Error Line 11, Column 5542: end tag for "font" omitted, but OMITTAG NO was specified
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 3970: start tag was here
    …e)");itemContent=itemContent.replace(/<font(.*?)<\/font>/g,"(font)");itemConte…
  • Error Line 11, Column 5542: end tag for "object" omitted, but OMITTAG NO was specified
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 3733: start tag was here
    …o]");itemContent=itemContent.replace(/<object(.*?)/g,"[video]");itemContent=it…
  • Error Line 11, Column 5542: end tag for "object" omitted, but OMITTAG NO was specified
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 3670: start tag was here
    …o]");itemContent=itemContent.replace(/<object(.*?)<\/>/g,"[video]");itemConten…
  • Error Line 11, Column 5542: end tag for "object" omitted, but OMITTAG NO was specified
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 3601: start tag was here
    …tent;itemContent=itemContent.replace(/<object(.*?)<\/object>/g,"[video]");item…
  • Error Line 11, Column 5542: end tag for "script" omitted, but OMITTAG NO was specified
    …g(c.entries[i].object.content)}}})}catch(e){};</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 11, Column 3441: start tag was here
    …t-weight","bold");break}})});</script><script type='text/javascript'>try{Echo.…

Visitor Analysis

Daily Visitor
  • 8.167 visits