wtov9.com

WTOV9 | Steubenville-Wheeling News, Weather, Video and Sports | Ohio Valley News | ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    wtov9.com
  • Favicon
  • Alexa Rank
    #73124
  • Google Page Rank
    PR 5
  • Ip Address
    66.6.152.59
  • Page Size
    134.1 KB
  • Images
    1 GIF, 53 JPG, 2 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    14 30 10 7 0 1

Website Meta Analysis



  • Title
    WTOV9 | Steubenville-Wheeling News, Weather, Video and Sports... | www.wtov9.com
  • Meta Keyword
  • Meta Description
    WTOV9 | Steubenville-Wheeling News, Weather, Video and Sports | Ohio Valley News |

Technical Analysis



  • Webserver
    Apache/2.2.3 (CentOS)
  • Ip Address
    66.6.152.59
  • Domain Age
    11 Years, 11 Months, 7 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache/2.2.3 (CentOS)
  • x-object-id: 91
  • x-bettercache-proxy: false
  • x-object-type: sections.homepage
  • last-modified: Mon, 08 Jul 2013 11:29:14 GMT
  • content-type: text/html; charset=utf-8
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 26317
  • cache-control: max-age=34, post-check=34, pre-check=60
  • date: Mon, 08 Jul 2013 11:30:34 GMT
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for wtov9.com

DNS Analysis


DNS servers
ns1.cmgdigital.com [66.6.152.88]
ns2.cmgdigital.com [66.6.152.89]
ns3.cmgdigital.com [66.6.152.93]


DNS Records

Answer records
wtov9.com NS  ns1.cmgdigital.com 60s
wtov9.com NS  ns2.cmgdigital.com 60s
wtov9.com NS  ns3.cmgdigital.com 60s
wtov9.com A 66.6.152.59 60s
wtov9.com MX
preference: 0
exchange: mx1.coxnewspapers.com
60s
wtov9.com SOA
server: ns1.cmgdigital.com
email: hostmaster@cimedia.com
serial: 2013021900
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
60s

Authority records

Additional records
ns1.cmgdigital.com A 66.6.152.88 60s
ns2.cmgdigital.com A 66.6.152.89 60s
ns3.cmgdigital.com A 66.6.152.93 60s
mx1.coxnewspapers.com A 66.6.147.156 360s

IP 66.6.152.59 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Atlanta
  • Continent Code
    30328
  • Latitude
    404
  • Longitude
    524
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 66.6.152.59"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=66.6.152.59?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 66.6.144.0 - 66.6.159.255
    CIDR: 66.6.144.0/20
    OriginAS:
    NetName: COX-ENTERPRISES
    NetHandle: NET-66-6-144-0-1
    Parent: NET-66-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2004-02-10
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-66-6-144-0-1

    OrgName: Cox Enterprises Inc
    OrgId: COXENT
    Address: 6205 Peachtree Dunwoody Road
    City: Atlanta
    StateProv: GA
    PostalCode: 30328
    Country: US
    RegDate: 1999-06-04
    Updated: 2011-10-20
    Ref: http://whois.arin.net/rest/org/COXENT

    OrgNOCHandle: CNOC17-ARIN
    OrgNOCName: CEI Network Operations Center
    OrgNOCPhone: +1-678-645-4357
    OrgNOCEmail: domaintech@coxinc.com
    OrgNOCRef: http://whois.arin.net/rest/poc/CNOC17-ARIN

    OrgTechHandle: TNS1-ARIN
    OrgTechName: Savas, Theodore Nicholas
    OrgTechPhone: +1-678-645-0101
    OrgTechEmail: ted.savas@coxinc.com
    OrgTechRef: http://whois.arin.net/rest/poc/TNS1-ARIN

    OrgAbuseHandle: CNOC17-ARIN
    OrgAbuseName: CEI Network Operations Center
    OrgAbusePhone: +1-678-645-4357
    OrgAbuseEmail: domaintech@coxinc.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/CNOC17-ARIN

    RTechHandle: JJB33-ARIN
    RTechName: Blank, John Joseph
    RTechPhone: +1-678-645-0505
    RTechEmail: john.blank@coxinc.com
    RTechRef: http://whois.arin.net/rest/poc/JJB33-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 189 Errors
  • 32 Warnings
Ratio Text/Html
  • 0.6179275501587025
Message Error
  • Error Line 1, Column 306: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    …en"><![endif]--><!--[if gt IE 9]><!--><html lang="en"><!--<![endif]--><head><s…

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 1, Column 996: there is no attribute "property"
    …"keywords" content=""/><meta property="og:title" content="WTOV9 | Steubenville…

    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.

  • Warning Line 161, Column 36: character "&" is the first character of a delimiter but occurred as data
            url = url.replace(/\?next=?&/, '?').replace(/&next=?&/, '&').replace(/[…

    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 161, Column 55: cannot generate system identifier for general entity "next"
    …l.replace(/\?next=?&/, '?').replace(/&next=?&/, '&').replace(/[?&]next=?$/, ''…

    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 161, Column 55: general entity "next" not defined and no default entity
    …l.replace(/\?next=?&/, '?').replace(/&next=?&/, '&').replace(/[?&]next=?$/, ''…

    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 161, Column 59: reference not terminated by REFC delimiter
    …place(/\?next=?&/, '?').replace(/&next=?&/, '&').replace(/[?&]next=?$/, '').re…

    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 161, Column 59: reference to entity "next" for which no system identifier could be generated
    …place(/\?next=?&/, '?').replace(/&next=?&/, '&').replace(/[?&]next=?$/, '').re…

    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 161, Column 54: entity was defined here
    …rl.replace(/\?next=?&/, '?').replace(/&next=?&/, '&').replace(/[?&]next=?$/, '…
  • Warning Line 161, Column 61: character "&" is the first character of a delimiter but occurred as data
    …ace(/\?next=?&/, '?').replace(/&next=?&/, '&').replace(/[?&]next=?$/, '').repl…

    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 161, Column 66: character "&" is the first character of a delimiter but occurred as data
    …\?next=?&/, '?').replace(/&next=?&/, '&').replace(/[?&]next=?$/, '').replace(/…

    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 161, Column 81: character "&" is the first character of a delimiter but occurred as data
    …).replace(/&next=?&/, '&').replace(/[?&]next=?$/, '').replace(/[?&]next=?#/, '…

    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 161, Column 108: character "&" is the first character of a delimiter but occurred as data
    …eplace(/&next=?&/, '&').replace(/[?&]next=?$/, '').replace(/[?&]next=?#/, '#');

    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 167, Column 46: character "&" is the first character of a delimiter but occurred as data
            var connector = (url.match(/\?/)) ? "&" : "?";

    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 174, Column 27: character "&" is the first character of a delimiter but occurred as data
            var m = RegExp('[?&]' + name + '=([^&^#]*)').exec(url);

    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 174, Column 45: character "&" is the first character of a delimiter but occurred as data
            var m = RegExp('[?&]' + name + '=([^&^#]*)').exec(url);

    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 175, Column 18: character "&" is the first character of a delimiter but occurred as data
            return m && decodeURIComponent(m[1].replace(/\+/g, ' '));

    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 175, Column 19: character "&" is the first character of a delimiter but occurred as data
            return m && decodeURIComponent(m[1].replace(/\+/g, ' '));

    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 368, Column 59: document type does not allow element "div" here; assuming missing "object" start-tag
    …ass="cmCol9 cmFirst cmLast cmClearfix"><div class="cmPencilAd"><!-- pencil ad …
  • Error Line 368, Column 410: end tag for element "div" which is not open
    …v><!-- end cmHeaderWrap block --></div><!-- begin cmSubHeaderWrap block> --><d…

    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 390, Column 247: there is no attribute "data-vr-zone"
    …ect"><div class="cmCol6" data-vr-zone="Third Party Tease 72504"><div id="write…

    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 392, Column 89: "data-vr-contentbox" is not a member of a group specified for any attribute
    …lse, "html": " <div data-vr-contentbox></div> ", "id": "writecapture78170561",…
  • Error Line 392, Column 89: document type does not allow element "div" here
    …lse, "html": " <div data-vr-contentbox></div> ", "id": "writecapture78170561",…

    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 395, Column 89: "data-vr-contentbox" is not a member of a group specified for any attribute
    …lse, "html": " <div data-vr-contentbox><span></span></div> ", "id": "writecapt…
  • Error Line 395, Column 89: document type does not allow element "div" here
    …lse, "html": " <div data-vr-contentbox><span></span></div> ", "id": "writecapt…

    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 396, Column 287: "data-vr-contentbox" is not a member of a group specified for any attribute
    …Nav cmClearfix"><li data-vr-contentbox><a href="#cm39924Tab01" onclick="javasc…
  • Error Line 396, Column 448: "data-vr-contentbox" is not a member of a group specified for any attribute
    …al News</a></li><li data-vr-contentbox><a href="#cm39924Tab02" onclick="javasc…
  • Error Line 396, Column 606: "data-vr-contentbox" is not a member of a group specified for any attribute
    …Weather</a></li><li data-vr-contentbox><a href="#cm39924Tab03" onclick="javasc…
  • Error Line 396, Column 778: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ld News</a></li><li data-vr-contentbox><a href="#cm39924Tab04" onclick="javasc…
  • Error Line 396, Column 935: "data-vr-contentbox" is not a member of a group specified for any attribute
    …>Sports</a></li><li data-vr-contentbox><a href="#cm39924Tab06" onclick="javasc…
  • Error Line 396, Column 1237: "data-vr-contentbox" is not a member of a group specified for any attribute
    …Content cmClearfix" data-vr-contentbox><div class="cmCol4" data-vr-zone="Autom…
  • Error Line 396, Column 1495: "data-vr-contentbox" is not a member of a group specified for any attribute
    …l4 cmTeasePhotoTop" data-vr-contentbox><!-- requires javascript/jquery.ui.dial…
  • Error Line 419, Column 294: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/news…
  • Error Line 419, Column 460: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/news…
  • Error Line 419, Column 689: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/news…
  • Error Line 419, Column 893: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/news…
  • Error Line 419, Column 1109: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/news…
  • Error Line 419, Column 1313: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/news…
  • Error Line 419, Column 1521: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/news…
  • Error Line 419, Column 2142: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/s/news/lo…
  • Error Line 419, Column 2317: "data-vr-contentbox" is not a member of a group specified for any attribute
    …Content cmClearfix" data-vr-contentbox><div class="cmCol4" data-vr-zone="Photo…
  • Error Line 419, Column 2443: "data-vr-contentbox" is not a member of a group specified for any attribute
    …l4 cmTeasePhotoTop" data-vr-contentbox><!-- requires javascript/jquery.ui.dial…
  • Error Line 420, Column 359: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/photo/wea…
  • Error Line 421, Column 73: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/photo/wea…
  • Error Line 422, Column 73: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/photo/wea…
  • Error Line 423, Column 73: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/photo/wea…
  • Error Line 424, Column 73: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/s/weather…
  • Error Line 424, Column 233: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/gallery/w…
  • Error Line 424, Column 389: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/weather/4…
  • Error Line 424, Column 532: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/s/weather…
  • Error Line 424, Column 685: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/s/weather…
  • Error Line 424, Column 843: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/weblogs/s…
  • Error Line 424, Column 1253: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/s/weather…
  • Error Line 424, Column 1441: "data-vr-contentbox" is not a member of a group specified for any attribute
    …Content cmClearfix" data-vr-contentbox><div class="cmCol4" data-vr-zone="Manua…
  • Error Line 424, Column 1644: "data-vr-contentbox" is not a member of a group specified for any attribute
    …l4 cmTeasePhotoTop" data-vr-contentbox><!-- requires javascript/jquery.ui.dial…
  • Error Line 447, Column 293: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/hea…
  • Error Line 447, Column 503: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/top…
  • Error Line 447, Column 715: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/cri…
  • Error Line 447, Column 922: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/cri…
  • Error Line 447, Column 1133: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/cri…
  • Error Line 447, Column 1333: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/top…
  • Error Line 447, Column 1531: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/ent…
  • Error Line 447, Column 2127: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/s/news/na…
  • Warning Line 447, Column 2194: character "&" is the first character of a delimiter but occurred as data
    …m/s/news/nation-world/">More National & World Headlines</a></li></ul></div></d…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 447, Column 2316: "data-vr-contentbox" is not a member of a group specified for any attribute
    …Content cmClearfix" data-vr-contentbox><div class="cmCol4" data-vr-zone="Autom…
  • Error Line 447, Column 2566: "data-vr-contentbox" is not a member of a group specified for any attribute
    …l4 cmTeasePhotoTop" data-vr-contentbox><!-- requires javascript/jquery.ui.dial…
  • Error Line 452, Column 314: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/spor…
  • Error Line 452, Column 508: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/spor…
  • Error Line 452, Column 694: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/spor…
  • Error Line 452, Column 889: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/spor…
  • Error Line 452, Column 1049: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/ap/s…
  • Error Line 452, Column 1265: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/ap/s…
  • Error Line 452, Column 1480: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/spor…
  • Error Line 452, Column 2111: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/s/sports/…
  • Error Line 452, Column 2279: "data-vr-contentbox" is not a member of a group specified for any attribute
    …Content cmClearfix" data-vr-contentbox><div class="cmCol3" data-vr-zone="Manua…
  • Error Line 452, Column 2482: "data-vr-contentbox" is not a member of a group specified for any attribute
    …l3 cmTeasePhotoTop" data-vr-contentbox><!-- requires javascript/jquery.ui.dial…
  • Error Line 465, Column 376: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/top…
  • Error Line 465, Column 592: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/sou…
  • Error Line 465, Column 796: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/news/busi…
  • Error Line 465, Column 1048: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/top…
  • Error Line 465, Column 1256: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/ent…
  • Error Line 465, Column 1455: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/videos/ne…
  • Error Line 466, Column 73: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/videos/ne…
  • Error Line 467, Column 73: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/videos/te…
  • Error Line 468, Column 73: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/videos/ne…
  • Error Line 469, Column 516: there is no attribute "data-numtoshow"
    …="cmRotator cmRotate4" data-numtoshow="4"><ul class="cmRotatorControls"><li cl…

    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 469, Column 884: "data-vr-contentbox" is not a member of a group specified for any attribute
    …"cmRotatorList"><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 469, Column 1409: "data-vr-contentbox" is not a member of a group specified for any attribute
    …r 9</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 469, Column 1875: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ast</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 469, Column 2398: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ies</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 469, Column 2921: "data-vr-contentbox" is not a member of a group specified for any attribute
    …res</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 469, Column 3759: there is no attribute "autocomplete"
    …ss="cmWeatherSearchForm" autocomplete="off"><p><input type="text" name="q" val…

    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 470, Column 16: there is no attribute "onBlur"
            onBlur="if(this.value==''){this.value='Enter ZIP or City, State';}"

    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 471, Column 17: there is no attribute "onFocus"
            onFocus="if(this.value=='Enter ZIP or City, State'){this.value='';}" />…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 472, Column 243: "data-vr-contentbox" is not a member of a group specified for any attribute
    …mTease cmTeaseCol6" data-vr-contentbox><div class="oembed oembed-video provide…
  • Error Line 568, Column 195: "data-vr-contentbox" is not a member of a group specified for any attribute
    …l2 cmTeasePhotoTop" data-vr-contentbox><h2><a href="http://www.wtov9.com/news/…
  • Error Line 573, Column 460: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ol2 cmTeasePhotoNo" data-vr-contentbox><h2><a href="http://share.wtov9.com/">I…
  • Error Line 575, Column 89: "data-vr-contentbox" is not a member of a group specified for any attribute
    …lse, "html": " <div data-vr-contentbox>$BEGINSCRIPT type='text/javascript' src…
  • Error Line 575, Column 89: document type does not allow element "div" here
    …lse, "html": " <div data-vr-contentbox>$BEGINSCRIPT 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).

  • Error Line 575, Column 296: document type does not allow element "link" here
    …ss' rel='stylesheet' type='text/css' />$NEWLINE\t<a href='http://api.celljourn…

    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 575, Column 376: cannot generate system identifier for general entity "partitionId"
    …ist.com/Media/ShowUpload?portalId=184&partitionId=219&channelId=6686&tags=&req…

    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 575, Column 376: general entity "partitionId" not defined and no default entity
    …ist.com/Media/ShowUpload?portalId=184&partitionId=219&channelId=6686&tags=&req…

    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 575, Column 387: reference not terminated by REFC delimiter
    …ia/ShowUpload?portalId=184&partitionId=219&channelId=6686&tags=&required=t,d,k…

    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 575, Column 387: reference to external entity in attribute value
    …ia/ShowUpload?portalId=184&partitionId=219&channelId=6686&tags=&required=t,d,k…

    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 575, Column 387: reference to entity "partitionId" for which no system identifier could be generated
    …ia/ShowUpload?portalId=184&partitionId=219&channelId=6686&tags=&required=t,d,k…

    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 575, Column 375: entity was defined here
    …list.com/Media/ShowUpload?portalId=184&partitionId=219&channelId=6686&tags=&re…
  • Warning Line 575, Column 392: cannot generate system identifier for general entity "channelId"
    …owUpload?portalId=184&partitionId=219&channelId=6686&tags=&required=t,d,k&keep…

    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 575, Column 392: general entity "channelId" not defined and no default entity
    …owUpload?portalId=184&partitionId=219&channelId=6686&tags=&required=t,d,k&keep…

    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 575, Column 401: reference not terminated by REFC delimiter
    …portalId=184&partitionId=219&channelId=6686&tags=&required=t,d,k&keepThis=true…

    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 575, Column 401: reference to external entity in attribute value
    …portalId=184&partitionId=219&channelId=6686&tags=&required=t,d,k&keepThis=true…

    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 575, Column 401: reference to entity "channelId" for which no system identifier could be generated
    …portalId=184&partitionId=219&channelId=6686&tags=&required=t,d,k&keepThis=true…

    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 575, Column 391: entity was defined here
    …howUpload?portalId=184&partitionId=219&channelId=6686&tags=&required=t,d,k&kee…
  • Warning Line 575, Column 407: cannot generate system identifier for general entity "tags"
    …Id=184&partitionId=219&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_if…

    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 575, Column 407: general entity "tags" not defined and no default entity
    …Id=184&partitionId=219&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_if…

    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 575, Column 411: reference not terminated by REFC delimiter
    …84&partitionId=219&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe…

    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 575, Column 411: reference to external entity in attribute value
    …84&partitionId=219&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe…

    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 575, Column 411: reference to entity "tags" for which no system identifier could be generated
    …84&partitionId=219&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe…

    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 575, Column 406: entity was defined here
    …lId=184&partitionId=219&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_i…
  • Warning Line 575, Column 413: cannot generate system identifier for general entity "required"
    …&partitionId=219&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe=t…

    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 575, Column 413: general entity "required" not defined and no default entity
    …&partitionId=219&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe=t…

    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 575, Column 421: reference not terminated by REFC delimiter
    …onId=219&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe=true&heig…

    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 575, Column 421: reference to external entity in attribute value
    …onId=219&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe=true&heig…

    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 575, Column 421: reference to entity "required" for which no system identifier could be generated
    …onId=219&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe=true&heig…

    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 575, Column 412: entity was defined here
    …4&partitionId=219&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe=…
  • Warning Line 575, Column 428: cannot generate system identifier for general entity "keepThis"
    …9&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe=true&height=260&…

    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 575, Column 428: general entity "keepThis" not defined and no default entity
    …9&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe=true&height=260&…

    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 575, Column 436: reference not terminated by REFC delimiter
    …lId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe=true&height=260&width=42…

    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 575, Column 436: reference to external entity in attribute value
    …lId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe=true&height=260&width=42…

    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 575, Column 436: reference to entity "keepThis" for which no system identifier could be generated
    …lId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe=true&height=260&width=42…

    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 575, Column 427: entity was defined here
    …19&channelId=6686&tags=&required=t,d,k&keepThis=true&TB_iframe=true&height=260…
  • Warning Line 575, Column 442: cannot generate system identifier for general entity "TB_iframe"
    …86&tags=&required=t,d,k&keepThis=true&TB_iframe=true&height=260&width=420' tit…

    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 575, Column 442: general entity "TB_iframe" not defined and no default entity
    …86&tags=&required=t,d,k&keepThis=true&TB_iframe=true&height=260&width=420' tit…

    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 575, Column 451: reference not terminated by REFC delimiter
    …required=t,d,k&keepThis=true&TB_iframe=true&height=260&width=420' title='Uploa…

    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 575, Column 451: reference to external entity in attribute value
    …required=t,d,k&keepThis=true&TB_iframe=true&height=260&width=420' title='Uploa…

    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 575, Column 451: reference to entity "TB_iframe" for which no system identifier could be generated
    …required=t,d,k&keepThis=true&TB_iframe=true&height=260&width=420' title='Uploa…

    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 575, Column 441: entity was defined here
    …686&tags=&required=t,d,k&keepThis=true&TB_iframe=true&height=260&width=420' ti…
  • Warning Line 575, Column 457: cannot generate system identifier for general entity "height"
    …ed=t,d,k&keepThis=true&TB_iframe=true&height=260&width=420' title='Upload File…

    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 575, Column 457: general entity "height" not defined and no default entity
    …ed=t,d,k&keepThis=true&TB_iframe=true&height=260&width=420' title='Upload File…

    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 575, Column 463: reference not terminated by REFC delimiter
    …,k&keepThis=true&TB_iframe=true&height=260&width=420' title='Upload File' clas…

    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 575, Column 463: reference to external entity in attribute value
    …,k&keepThis=true&TB_iframe=true&height=260&width=420' title='Upload File' clas…

    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 575, Column 463: reference to entity "height" for which no system identifier could be generated
    …,k&keepThis=true&TB_iframe=true&height=260&width=420' title='Upload File' clas…

    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 575, Column 456: entity was defined here
    …red=t,d,k&keepThis=true&TB_iframe=true&height=260&width=420' title='Upload Fil…
  • Warning Line 575, Column 468: cannot generate system identifier for general entity "width"
    …epThis=true&TB_iframe=true&height=260&width=420' title='Upload File' class='th…

    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 575, Column 468: general entity "width" not defined and no default entity
    …epThis=true&TB_iframe=true&height=260&width=420' title='Upload File' class='th…

    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 575, Column 473: reference not terminated by REFC delimiter
    …s=true&TB_iframe=true&height=260&width=420' title='Upload File' class='thickbo…

    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 575, Column 473: reference to external entity in attribute value
    …s=true&TB_iframe=true&height=260&width=420' title='Upload File' class='thickbo…

    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 575, Column 473: reference to entity "width" for which no system identifier could be generated
    …s=true&TB_iframe=true&height=260&width=420' title='Upload File' class='thickbo…

    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 575, Column 467: entity was defined here
    …eepThis=true&TB_iframe=true&height=260&width=420' title='Upload File' class='t…
  • Error Line 576, Column 691: "data-vr-contentbox" is not a member of a group specified for any attribute
    …"cmRotatorList"><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 1332: "data-vr-contentbox" is not a member of a group specified for any attribute
    …iew</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 1917: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ch?</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 2502: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ch?</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 3075: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ter</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 3786: "data-vr-contentbox" is not a member of a group specified for any attribute
    …nce</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 4468: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ery</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 5146: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ion</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 5702: "data-vr-contentbox" is not a member of a group specified for any attribute
    …7 P</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 6380: "data-vr-contentbox" is not a member of a group specified for any attribute
    …hts</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 7090: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ool</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 7711: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ers</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 8384: "data-vr-contentbox" is not a member of a group specified for any attribute
    …rty</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 9083: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ans</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 9657: "data-vr-contentbox" is not a member of a group specified for any attribute
    …013</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 10353: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ine</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 10971: "data-vr-contentbox" is not a member of a group specified for any attribute
    …tue</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 11605: "data-vr-contentbox" is not a member of a group specified for any attribute
    …and</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 12247: "data-vr-contentbox" is not a member of a group specified for any attribute
    …urt</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 12920: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ght</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 13564: "data-vr-contentbox" is not a member of a group specified for any attribute
    …er?</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 14174: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ls?</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 14816: "data-vr-contentbox" is not a member of a group specified for any attribute
    …mph</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 15458: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ome</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 16455: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/leg…
  • Error Line 576, Column 16670: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/ene…
  • Error Line 576, Column 16880: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/cri…
  • Error Line 576, Column 17087: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/cri…
  • Error Line 576, Column 17298: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/cri…
  • Error Line 576, Column 17859: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/rel…
  • Error Line 576, Column 18073: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/top…
  • Error Line 576, Column 18262: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/rel…
  • Error Line 576, Column 18475: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/def…
  • Error Line 576, Column 18687: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/ene…
  • Error Line 576, Column 19257: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/cri…
  • Error Line 576, Column 19458: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/top…
  • Error Line 576, Column 19666: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/top…
  • Error Line 576, Column 19879: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/soc…
  • Error Line 576, Column 20086: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wtov9.com/ap/ap/top…
  • Error Line 576, Column 20916: "data-vr-contentbox" is not a member of a group specified for any attribute
    …"cmRotatorList"><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 21537: "data-vr-contentbox" is not a member of a group specified for any attribute
    …rce</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 22041: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ays</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 22521: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ies</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 23219: "data-vr-contentbox" is not a member of a group specified for any attribute
    …12)</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 23712: "data-vr-contentbox" is not a member of a group specified for any attribute
    …012</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 24256: "data-vr-contentbox" is not a member of a group specified for any attribute
    …eup</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 24932: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ved</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 25477: "data-vr-contentbox" is not a member of a group specified for any attribute
    …end</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 26044: "data-vr-contentbox" is not a member of a group specified for any attribute
    …exy</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 26778: "data-vr-contentbox" is not a member of a group specified for any attribute
    …l2 cmTeasePhotoTop" data-vr-contentbox><h2><a href="http://www.wtov9.com/s/lot…
  • Error Line 576, Column 27794: "data-vr-contentbox" is not a member of a group specified for any attribute
    …"cmRotatorList"><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 28212: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ule</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 28687: "data-vr-contentbox" is not a member of a group specified for any attribute
    …len</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 29177: "data-vr-contentbox" is not a member of a group specified for any attribute
    …hil</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 29650: "data-vr-contentbox" is not a member of a group specified for any attribute
    …tie</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 30091: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ood</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 30677: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ael</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 31208: "data-vr-contentbox" is not a member of a group specified for any attribute
    …all</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 576, Column 31886: "data-vr-contentbox" is not a member of a group specified for any attribute
    …mTease cmTeaseCol6" data-vr-contentbox><div class="oembed oembed-video provide…
  • Error Line 632, Column 256: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wftv.com/news/news/…
  • Error Line 632, Column 479: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wpxi.com/news/news/…
  • Error Line 632, Column 722: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.wsbtv.com/gallery/n…
  • Error Line 632, Column 956: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.kirotv.com/gallery/…
  • Error Line 632, Column 1159: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.whiotv.com/news/new…
  • Error Line 632, Column 1440: there is no attribute "data-href"
    …r"><div class="fb-like-box" data-href="http://www.facebook.com/WTOV9" data-wid…

    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 632, Column 1483: there is no attribute "data-width"
    …://www.facebook.com/WTOV9" data-width="293" data-height="255" data-show-faces=…

    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 632, Column 1501: there is no attribute "data-height"
    …m/WTOV9" data-width="293" data-height="255" data-show-faces="true" data-stream…

    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 632, Column 1523: there is no attribute "data-show-faces"
    …93" data-height="255" data-show-faces="true" data-stream="false" data-header="…

    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 632, Column 1542: there is no attribute "data-stream"
    …5" data-show-faces="true" data-stream="false" data-header="false"></div></div>…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 632, Column 1562: there is no attribute "data-header"
    …true" data-stream="false" data-header="false"></div></div><div class="cmModule…

    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 696, Column 1032: literal is missing closing delimiter
    …d radar">Weather</a></li><li><a href="/s/sports/ title="Steelers and Penns and…

    Did you forget to close a (double) quote mark?

  • Error Line 701, Column 163: end tag for element "div" which is not open
    …<div class="cmClear">&nbsp;</div></div></div><!-- begin cmFooterContainer bloc…

    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 701, Column 169: end tag for element "div" which is not open
    …lass="cmClear">&nbsp;</div></div></div><!-- begin cmFooterContainer block --><…

    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 701, Column 388: there is no attribute "onClick"
    …%2F" class="cmMobileSiteLink" onClick="s.tl(this,'o','view mobile - bottom');"…

    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 701, Column 431: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …(this,'o','view mobile - bottom');"><p><span>View mobile site</span></p></a></…

    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 701, Column 611: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …eturn=%2F" class="cmMobileSiteLink"><p><span>View mobile site</span></p></a></…

    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 705, Column 47: character "&" is the first character of a delimiter but occurred as data
    …erAgentPttn.test(navigator.userAgent) && !mobBlacklistPttn.test(location.pathn…

    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 705, Column 48: character "&" is the first character of a delimiter but occurred as data
    …rAgentPttn.test(navigator.userAgent) && !mobBlacklistPttn.test(location.pathna…

    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 898, Column 68: there is no attribute "data-capturescreen"
    …       <a href="#" data-capturescreen="forgotPassword" id="forgotPasswordLink"…

    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 902, Column 107: there is no attribute "data-cancelcapturereturnexperience"
    …#" data-cancelcapturereturnexperience="true">Use another account</a></div></di…

    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 908, Column 81: ID "forgotPasswordLink" already defined
    …ta-capturescreen="forgotPassword" id="forgotPasswordLink">Forgot your password…

    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 898, Column 89: ID "forgotPasswordLink" first defined here
    …ta-capturescreen="forgotPassword" id="forgotPasswordLink">Forgot your password…
  • Error Line 976, Column 409: ID "forgotPasswordSuccess" already defined
    …></div><div style="display:none;" id="forgotPasswordSuccess"><div class="captu…

    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 976, Column 56: ID "forgotPasswordSuccess" first defined here
    …></div><div style="display:none;" id="forgotPasswordSuccess"><div class="captu…
  • Error Line 995, Column 942: end tag for element "body" which is not open
    …DHgTVEYBIQZNEgYXNw1cExtTARc=",0,5,new Date().getTime()])</script></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 995, Column 949: end tag for "object" omitted, but OMITTAG NO was specified
    …DHgTVEYBIQZNEgYXNw1cExtTARc=",0,5,new Date().getTime()])</script></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 368, Column 14: start tag was here
        </script><div class="cmCol9 cmFirst cmLast cmClearfix"><div class="cmPencil…
  • Error Line 995, Column 949: end tag for "head" omitted, but OMITTAG NO was specified
    …DHgTVEYBIQZNEgYXNw1cExtTARc=",0,5,new Date().getTime()])</script></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 1, Column 338: start tag was here
    …><!--><html lang="en"><!--<![endif]--><head><script type="text/javascript">var…
  • Error Line 995, Column 949: end tag for "html" which is not finished
    …DHgTVEYBIQZNEgYXNw1cExtTARc=",0,5,new Date().getTime()])</script></body></html>

    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.

Visitor Analysis

Daily Visitor
  • 1.155 visits