WHIO TV 7 is Dayton, Ohio's home for local news, weather and traffic reports, lottery results, and University of Dayton sports coverage. ...

whiotv.com
  • Domain Name
    whiotv.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #39480
  • Page Size
    152.4 KB
  • Ip Address
    66.6.152.59
  • Heading
    H1: 14, H2: 22, H3: 4, H4: 8, H5: 2, H6: 0
  • Images
    1 GIF, 42 JPG, 4 PNG

Website Meta Analysis

  • Title
    Dayton, Ohio Network News, Weather, Traffic, Sports - WHIOTV | www.whiotv.com
  • Meta Keyword
  • Meta Description
    WHIO TV 7 is Dayton, Ohio's home for local news, weather and traffic reports, lottery results, and University of Dayton sports coverage.

Technical Analysis

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

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

HTML Analysis

  • server: Apache/2.2.3 (CentOS)
  • x-object-id: 89
  • x-bettercache-proxy: false
  • x-object-type: sections.homepage
  • last-modified: Thu, 08 Aug 2013 17:32:28 GMT
  • content-type: text/html; charset=utf-8
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 29178
  • cache-control: max-age=25, post-check=25, pre-check=60
  • date: Thu, 08 Aug 2013 17:32:57 GMT
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Corporation Service Company(c) (CSC) The Trusted Partner of More than 50% of the 100 Best Global Brands.
Contact us to learn more about our enterprise solutions for Global Domain Name Registration and Management, Trademark Research and Watching, Brand, Logo and Auction Monitoring, as well SSL Certificate Services and DNS Hosting.
NOTICE: You are not authorized to access or query our WHOIS database through the use of high-volume, automated, electronic processes or for the purpose or purposes of using the data in any manner that violates these terms of use. The Data in the CSC WHOIS database is provided by CSC for information purposes only, and to assist persons in obtaining information about or related to a domain name registration record. CSC does not guarantee its accuracy. By submitting a WHOIS query, you agree to abide by the following terms of use: you agree that you may use this Data only for lawful purposes and that under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, e-mail, telephone, or facsimile; or (2) enable high volume, automated, electronic processes that apply to CSC (or its computer systems). CSC reserves the right to terminate your access to the WHOIS database in its sole discretion for any violations by you of these terms of use. CSC reserves the right to modify these terms at any tim

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
whiotv.com NS  ns3.cmgdigital.com 60s
whiotv.com NS  ns1.cmgdigital.com 60s
whiotv.com NS  ns2.cmgdigital.com 60s
whiotv.com A 66.6.152.59 60s
whiotv.com MX
preference: 10
exchange: mx1.coxtv.com
60s
whiotv.com SOA
server: ns1.cmgdigital.com
email: hostmaster@cimedia.com
serial: 2013012900
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

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

    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

    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

    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
  • 180 Errors
  • 25 Warnings
Ratio Text/Html
  • 0.47396387503685566
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 986: there is no attribute "property"
    …"keywords" content=""/><meta property="og:title" content="Dayton, Ohio Network…

    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 166, 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 166, 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 166, 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 166, 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 166, 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 166, Column 54: entity was defined here
    …rl.replace(/\?next=?&/, '?').replace(/&next=?&/, '&').replace(/[?&]next=?$/, '…
  • Warning Line 166, 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 166, 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 166, 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 166, 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 172, 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 179, 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 179, 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 180, 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 180, 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 399, 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 399, 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 400, Column 247: there is no attribute "data-vr-zone"
    …ect"><div class="cmCol6" data-vr-zone="Third Party Tease 70119"></div><div cla…

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

    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 403, Column 190: "data-vr-contentbox" is not a member of a group specified for any attribute
    …TeaseHorizList"><li data-vr-contentbox><a href="http://share.whiotv.com/">iWit…
  • Error Line 403, Column 266: "data-vr-contentbox" is not a member of a group specified for any attribute
    …itness7</a></li><li data-vr-contentbox><a href="http://www.whiotv.com/photo/we…
  • Error Line 403, Column 400: "data-vr-contentbox" is not a member of a group specified for any attribute
    …orecast</a></li><li data-vr-contentbox><a href="http://www.whiotv.com/s/traffi…
  • Error Line 403, Column 482: "data-vr-contentbox" is not a member of a group specified for any attribute
    …Traffic</a></li><li data-vr-contentbox><a href="http://www.whiotv.com/s/sports…
  • Error Line 403, Column 562: "data-vr-contentbox" is not a member of a group specified for any attribute
    …>Sports</a></li><li data-vr-contentbox><a href="http://www.whiotv.com/pumppatr…
  • Error Line 403, Column 675: "data-vr-contentbox" is not a member of a group specified for any attribute
    …"cmHozListLastItem" data-vr-contentbox><a href="http://www.whiotv.com/web-link…
  • Error Line 403, Column 1025: "data-vr-contentbox" is not a member of a group specified for any attribute
    …Nav cmClearfix"><li data-vr-contentbox><a href="#cm64979Tab01" onclick="javasc…
  • Error Line 403, Column 1186: "data-vr-contentbox" is not a member of a group specified for any attribute
    …al News</a></li><li data-vr-contentbox><a href="#cm64979Tab03" onclick="javasc…
  • Error Line 403, Column 1352: "data-vr-contentbox" is not a member of a group specified for any attribute
    …Traffic</a></li><li data-vr-contentbox><a href="#cm64979Tab04" onclick="javasc…
  • Error Line 403, Column 1512: "data-vr-contentbox" is not a member of a group specified for any attribute
    …itness7</a></li><li data-vr-contentbox><a href="#cm64979Tab05" onclick="javasc…
  • Error Line 403, Column 1675: "data-vr-contentbox" is not a member of a group specified for any attribute
    …istible</a></li><li data-vr-contentbox><a href="#cm64979Tab06" onclick="javasc…
  • Error Line 403, Column 1831: "data-vr-contentbox" is not a member of a group specified for any attribute
    …">Video</a></li><li data-vr-contentbox><a href="#cm64979Tab07" onclick="javasc…
  • Error Line 403, Column 2131: "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 403, Column 2334: "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 408, Column 300: "data-vr-contentbox" is not a member of a group specified for any attribute
    …earfix cmTeaseCol3" data-vr-contentbox><!-- requires javascript/jquery.ui.dial…
  • Error Line 408, Column 1350: "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 408, Column 1544: "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 408, Column 1726: "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 408, Column 1927: "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 408, Column 2110: "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 408, Column 2312: "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 408, Column 2516: "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 408, Column 2752: "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 408, Column 2958: "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 408, Column 3333: "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="Third…
  • Error Line 410, Column 89: "data-vr-contentbox" is not a member of a group specified for any attribute
    …lse, "html": " <div data-vr-contentbox><img src=\" http://media.cmgdigital.com…
  • Error Line 410, Column 89: document type does not allow element "div" here
    …lse, "html": " <div data-vr-contentbox><img src=\" http://media.cmgdigital.com…

    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 410, Column 99: an attribute value must be a literal unless it contains only name characters
    …": " <div data-vr-contentbox><img src=\" http://media.cmgdigital.com/shared/im…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 410, Column 108: NET-enabling start-tag not immediately followed by null end-tag
    … data-vr-contentbox><img src=\" http://media.cmgdigital.com/shared/img/photos/…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 410, Column 108: "http:" is not a member of a group specified for any attribute
    … data-vr-contentbox><img src=\" http://media.cmgdigital.com/shared/img/photos/…
  • Error Line 410, Column 108: required attribute "alt" not specified
    … data-vr-contentbox><img src=\" http://media.cmgdigital.com/shared/img/photos/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 410, Column 108: end tag for "img" omitted, but OMITTAG NO was specified
    … data-vr-contentbox><img src=\" http://media.cmgdigital.com/shared/img/photos/…

    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 410, Column 90: start tag was here
    …se, "html": " <div data-vr-contentbox><img src=\" http://media.cmgdigital.com/…
  • Error Line 410, Column 309: end tag for "br" omitted, but OMITTAG NO was specified
    …in:0 auto;width:275px;\"/>$NEWLINE<br>$NEWLINE<p style=\"padding-bottom:1em;\"…

    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 410, Column 305: start tag was here
    …margin:0 auto;width:275px;\"/>$NEWLINE<br>$NEWLINE<p style=\"padding-bottom:1e…
  • Error Line 410, Column 326: an attribute value must be a literal unless it contains only name characters
    …75px;\"/>$NEWLINE<br>$NEWLINE<p style=\"padding-bottom:1em;\">Introducing WHIO…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 410, Column 576: an attribute value must be a literal unless it contains only name characters
    …otos from iWitness7 and more! <a href=\"http://www.whiotv.com/news/marketing/f…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 410, Column 661: an attribute value must be a literal unless it contains only name characters
    …al-weather-app/nTyfb/?65cpbB\" target=\"_blank\">Read more about the app.</a>$…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 410, Column 661: character "\" is not allowed in the value of attribute "target"
    …al-weather-app/nTyfb/?65cpbB\" target=\"_blank\">Read more about the app.</a>$…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 410, Column 718: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …e about the app.</a>$NEWLINE$NEWLINE<p><h2><strong><a href=\"https://itunes.ap…

    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 410, Column 722: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …out the app.</a>$NEWLINE$NEWLINE<p><h2><strong><a href=\"https://itunes.apple.…

    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 410, Column 739: an attribute value must be a literal unless it contains only name characters
    …NEWLINE$NEWLINE<p><h2><strong><a href=\"https://itunes.apple.com/us/app/id5863…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 410, Column 794: an attribute value must be a literal unless it contains only name characters
    …apple.com/us/app/id586377264\" target=\"_blank\">Download App</a> | <a href=\"…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 410, Column 794: character "\" is not allowed in the value of attribute "target"
    …apple.com/us/app/id586377264\" target=\"_blank\">Download App</a> | <a href=\"…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 410, Column 832: an attribute value must be a literal unless it contains only name characters
    …\"_blank\">Download App</a> | <a href=\"http://www.whiotv.com/videos/news/free…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 410, Column 975: end tag for "p" omitted, but OMITTAG NO was specified
    …tures!</a></strong></h2> $NEWLINE</div> ", "id": "writecapture16956810", "widg…

    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 410, Column 716: start tag was here
    …ore about the app.</a>$NEWLINE$NEWLINE<p><h2><strong><a href=\"https://itunes.…
  • Error Line 410, Column 975: end tag for "p" omitted, but OMITTAG NO was specified
    …tures!</a></strong></h2> $NEWLINE</div> ", "id": "writecapture16956810", "widg…

    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 410, Column 317: start tag was here
    …o;width:275px;\"/>$NEWLINE<br>$NEWLINE<p style=\"padding-bottom:1em;\">Introdu…
  • Error Line 411, Column 141: "data-vr-contentbox" is not a member of a group specified for any attribute
    …3 cmTeasePhotoLeft" data-vr-contentbox><!-- requires javascript/jquery.ui.dial…
  • Error Line 411, Column 1206: "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/s/weathe…
  • Error Line 411, Column 1340: "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/weather/…
  • Error Line 411, Column 1483: "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/s/traffi…
  • Error Line 411, Column 1613: "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/s/weathe…
  • Error Line 411, Column 1762: "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/weatherv…
  • Error Line 411, Column 1887: "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/videos/w…
  • Error Line 412, Column 161: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ol3 cmTeasePhotoNo" data-vr-contentbox><h2><a href="http://www.whiotv.com/s/tr…
  • Error Line 412, Column 541: "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="Link …
  • Error Line 412, Column 666: "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 429, Column 298: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://signin.cmgdigital.com/l…
  • Error Line 429, Column 526: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://share.whiotv.com/">Uplo…
  • Error Line 429, Column 644: "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/gallery/…
  • Error Line 430, 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.whiotv.com/gallery/…
  • Error Line 431, 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.whiotv.com/gallery/…
  • Error Line 432, 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.whiotv.com/gallery/…
  • Error Line 433, 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.whiotv.com/iw7conte…
  • Error Line 433, Column 318: "data-vr-contentbox" is not a member of a group specified for any attribute
    …3 cmTeasePhotoLeft" data-vr-contentbox><!-- requires javascript/jquery.ui.dial…
  • Error Line 433, Column 1208: "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 433, Column 1411: "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 451, Column 286: "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/videos/n…
  • Error Line 452, 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.whiotv.com/videos/e…
  • Error Line 453, 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.whiotv.com/videos/n…
  • Error Line 454, 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.whiotv.com/ap/ap/fi…
  • Error Line 454, Column 298: "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/gallery/…
  • Error Line 455, 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.whiotv.com/ap/ap/tr…
  • Error Line 455, 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.whiotv.com/gallery/…
  • Error Line 456, 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.whiotv.com/ap/ap/us…
  • Error Line 456, Column 278: "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/ap/ap/en…
  • Error Line 456, Column 640: "data-vr-contentbox" is not a member of a group specified for any attribute
    …Content cmClearfix" data-vr-contentbox><div class="cmCol6" data-vr-zone="Autom…
  • Error Line 456, Column 860: 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 456, Column 1228: "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 456, Column 1924: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ity</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 456, Column 2617: "data-vr-contentbox" is not a member of a group specified for any attribute
    …bar</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 456, Column 3306: "data-vr-contentbox" is not a member of a group specified for any attribute
    …uck</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 456, Column 4024: "data-vr-contentbox" is not a member of a group specified for any attribute
    …nty</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 456, Column 4752: "data-vr-contentbox" is not a member of a group specified for any attribute
    …art</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 456, Column 5391: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ney</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 456, Column 6080: "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 456, Column 6869: "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 456, Column 7687: "data-vr-contentbox" is not a member of a group specified for any attribute
    …uts</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 456, Column 8444: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ows</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 456, Column 9118: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ing</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 456, Column 10076: "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/videos/a…
  • Error Line 457, 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.whiotv.com/videos/a…
  • Error Line 458, 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.whiotv.com/videos/a…
  • Error Line 459, 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.whiotv.com/videos/a…
  • Error Line 460, Column 117: "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 460, Column 320: "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 473, Column 484: "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/ap/ap/ki…
  • Error Line 473, Column 691: "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/ap/ap/en…
  • Error Line 473, Column 908: "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/ap/ap/en…
  • Error Line 473, Column 1128: "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/ap/ap/en…
  • Error Line 473, Column 1345: "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/ap/ap/en…
  • Error Line 473, Column 1565: "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/ap/ap/en…
  • Error Line 473, Column 1787: "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/ap/ap/en…
  • Error Line 473, Column 2003: "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/ap/ap/ca…
  • Error Line 473, Column 2454: "data-vr-contentbox" is not a member of a group specified for any attribute
    …3 cmTeasePhotoLeft" data-vr-contentbox><!-- requires javascript/jquery.ui.dial…
  • Error Line 478, Column 383: "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/ap/ap/in…
  • Error Line 478, Column 593: "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/ap/ap/in…
  • Error Line 478, Column 805: "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/ap/ap/ed…
  • Error Line 478, Column 1021: "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/ap/ap/cr…
  • Error Line 478, Column 1598: "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/ap/ap/pe…
  • Error Line 478, Column 1816: "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/ap/ap/ae…
  • Error Line 478, Column 2034: "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/ap/ap/ca…
  • Error Line 478, Column 2244: "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/ap/ap/au…
  • Error Line 478, Column 2669: "data-vr-contentbox" is not a member of a group specified for any attribute
    …l2 cmTeasePhotoTop" data-vr-contentbox><!-- requires javascript/jquery.ui.dial…
  • Error Line 478, Column 3687: "data-vr-contentbox" is not a member of a group specified for any attribute
    …mTease cmTeaseCol4" data-vr-contentbox><div class="oembed oembed-video provide…
  • Error Line 488, Column 215: "data-vr-contentbox" is not a member of a group specified for any attribute
    …l2 cmTeasePhotoTop" data-vr-contentbox><!-- requires javascript/jquery.ui.dial…
  • Error Line 488, Column 1330: "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/ap/ap/to…
  • Error Line 488, Column 1539: "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/ap/ap/wa…
  • Error Line 488, Column 1757: "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/ap/ap/to…
  • Error Line 488, Column 2556: "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 488, Column 3160: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ngs</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 3885: "data-vr-contentbox" is not a member of a group specified for any attribute
    …als</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 4468: "data-vr-contentbox" is not a member of a group specified for any attribute
    …nts</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 5132: "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 488, Column 5723: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ame</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 6264: "data-vr-contentbox" is not a member of a group specified for any attribute
    …pse</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 6963: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ask</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 7607: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ish</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 8261: "data-vr-contentbox" is not a member of a group specified for any attribute
    …rks</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 8975: "data-vr-contentbox" is not a member of a group specified for any attribute
    …OTU</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 9671: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ing</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 10300: "data-vr-contentbox" is not a member of a group specified for any attribute
    …era</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 11004: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ons</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 11693: "data-vr-contentbox" is not a member of a group specified for any attribute
    …cer</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 12322: "data-vr-contentbox" is not a member of a group specified for any attribute
    …...</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 13016: "data-vr-contentbox" is not a member of a group specified for any attribute
    …cer</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 13777: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ng"</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 14473: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ton</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 15152: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ves</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 15843: "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 488, Column 16473: "data-vr-contentbox" is not a member of a group specified for any attribute
    …unt</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 17167: "data-vr-contentbox" is not a member of a group specified for any attribute
    … up</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 17888: "data-vr-contentbox" is not a member of a group specified for any attribute
    …eud</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 19244: "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 488, Column 19963: "data-vr-contentbox" is not a member of a group specified for any attribute
    …now</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 20579: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ngs</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 21148: "data-vr-contentbox" is not a member of a group specified for any attribute
    ….S.</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 21773: "data-vr-contentbox" is not a member of a group specified for any attribute
    …on?</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 22465: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ces</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 23182: "data-vr-contentbox" is not a member of a group specified for any attribute
    …rms</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 23870: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ked</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 24459: "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 488, Column 25082: "data-vr-contentbox" is not a member of a group specified for any attribute
    …eek</a></p></li><li data-vr-contentbox><div class="cmTeaseListItemPhoto"><a hr…
  • Error Line 488, Column 25924: "data-vr-contentbox" is not a member of a group specified for any attribute
    …l2 cmTeasePhotoTop" data-vr-contentbox><!-- requires javascript/jquery.ui.dial…
  • Error Line 488, Column 26937: "data-vr-contentbox" is not a member of a group specified for any attribute
    …l2 cmTeasePhotoTop" data-vr-contentbox><!-- requires javascript/jquery.ui.dial…
  • Error Line 490, Column 88: "data-vr-contentbox" is not a member of a group specified for any attribute
    …rue, "html": " <div data-vr-contentbox><!-- MODIFIED by Gerald Fullam 2012-06-…
  • Error Line 490, Column 88: document type does not allow element "div" here
    …rue, "html": " <div data-vr-contentbox><!-- MODIFIED by Gerald Fullam 2012-06-…

    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 490, Column 7367: character "&" is the first character of a delimiter but occurred as data
    …\"An evening with local artists, wine & cheese\",$NEWLINE start: \"2013/02/06\…

    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 490, Column 11718: character "&" is the first character of a delimiter but occurred as data
    …wn\",$NEWLINE text: \"Art, Live Music & Food at Free Event Friday\",$NEWLINE s…

    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 490, Column 16545: character "&" is the first character of a delimiter but occurred as data
    …ins\",$NEWLINE text: \"Grab your kids & enjoy Mary Poppins on stage\",$NEWLINE…

    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 490, Column 17236: character "&" is the first character of a delimiter but occurred as data
    …NEWLINE text: \"Furniture, Mattresses & more for less!\",$NEWLINE start: \"201…

    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 494, Column 393: there is no attribute "data-feature-on"
    … style="display:none" data-feature-on="janrain" class="sprite iconMobile"><a h…

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

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

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

  • Error Line 494, Column 575: there is no attribute "data-feature-off"
    …style="display:none" data-feature-off="janrain" class="sprite iconMobile"><a h…

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

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

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

  • Error Line 496, Column 89: "data-vr-contentbox" is not a member of a group specified for any attribute
    …lse, "html": " <div data-vr-contentbox><a href=\"http://www.whiotv.com/news/ma…
  • Error Line 496, Column 89: document type does not allow element "div" here
    …lse, "html": " <div data-vr-contentbox><a href=\"http://www.whiotv.com/news/ma…

    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 496, Column 98: an attribute value must be a literal unless it contains only name characters
    …l": " <div data-vr-contentbox><a href=\"http://www.whiotv.com/news/marketing/f…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 496, Column 185: an attribute value must be a literal unless it contains only name characters
    …-weather-app/nTyfb/?65cpbB\"><img src=\"http://media.cmgdigital.com/shared/img…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 496, Column 288: an attribute value must be a literal unless it contains only name characters
    …WHIOWeatherAppBanner600x220.png\" alt=\"WHIO Weather App\" title=\"iPad App\" …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 496, Column 303: "Weather" is not a member of a group specified for any attribute
    …anner600x220.png\" alt=\"WHIO Weather App\" title=\"iPad App\" style=\"display…
  • Error Line 496, Column 306: "App" is not a member of a group specified for any attribute
    …er600x220.png\" alt=\"WHIO Weather App\" title=\"iPad App\" style=\"display:bl…
  • Error Line 496, Column 315: an attribute value must be a literal unless it contains only name characters
    ….png\" alt=\"WHIO Weather App\" title=\"iPad App\" style=\"display:block;margi…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 496, Column 325: "App" is not a member of a group specified for any attribute
    …=\"WHIO Weather App\" title=\"iPad App\" style=\"display:block;margin:0 auto;w…
  • Error Line 496, Column 334: an attribute value must be a literal unless it contains only name characters
    …eather App\" title=\"iPad App\" style=\"display:block;margin:0 auto;width:275p…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 496, Column 363: "auto" is not a member of a group specified for any attribute
    …\" style=\"display:block;margin:0 auto;width:275px;\"/></a>$NEWLINE<br>$NEWLIN…
  • Error Line 496, Column 383: end tag for "img" omitted, but OMITTAG NO was specified
    …lock;margin:0 auto;width:275px;\"/></a>$NEWLINE<br>$NEWLINE$NEWLINE<center><p>…

    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 496, Column 176: start tag was here
    …ree-local-weather-app/nTyfb/?65cpbB\"><img src=\"http://media.cmgdigital.com/s…
  • Error Line 496, Column 396: end tag for "br" omitted, but OMITTAG NO was specified
    … auto;width:275px;\"/></a>$NEWLINE<br>$NEWLINE$NEWLINE<center><p><h3><strong><…

    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 496, Column 392: start tag was here
    …in:0 auto;width:275px;\"/></a>$NEWLINE<br>$NEWLINE$NEWLINE<center><p><h3><stro…
  • Error Line 496, Column 426: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …LINE<br>$NEWLINE$NEWLINE<center><p><h3><strong><a href=\"https://itunes.apple.…

    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 496, Column 443: an attribute value must be a literal unless it contains only name characters
    …NEWLINE<center><p><h3><strong><a href=\"https://itunes.apple.com/us/app/id5863…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 496, Column 498: an attribute value must be a literal unless it contains only name characters
    …apple.com/us/app/id586377264\" target=\"_blank\">Download the WHIO Weather App…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 496, Column 498: character "\" is not allowed in the value of attribute "target"
    …apple.com/us/app/id586377264\" target=\"_blank\">Download the WHIO Weather App…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 496, Column 564: end tag for "p" omitted, but OMITTAG NO was specified
    … Weather App</a></strong></h3></center>$NEWLINE$NEWLINE<center><b><a href=\"ht…

    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 496, Column 420: start tag was here
    …a>$NEWLINE<br>$NEWLINE$NEWLINE<center><p><h3><strong><a href=\"https://itunes.…
  • Error Line 496, Column 600: an attribute value must be a literal unless it contains only name characters
    …er>$NEWLINE$NEWLINE<center><b><a href=\"http://www.whiotv.com/videos/news/free…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 499, Column 88: "data-vr-contentbox" is not a member of a group specified for any attribute
    …rue, "html": " <div data-vr-contentbox><style type=\"text/css\">$NEWLINE#cbTop…
  • Error Line 499, Column 88: document type does not allow element "div" here
    …rue, "html": " <div data-vr-contentbox><style type=\"text/css\">$NEWLINE#cbTop…

    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 499, Column 101: an attribute value must be a literal unless it contains only name characters
    …" <div data-vr-contentbox><style type=\"text/css\">$NEWLINE#cbTopWidget { widt…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 499, Column 113: document type does not allow element "style" here
    …vr-contentbox><style type=\"text/css\">$NEWLINE#cbTopWidget { width: 300px; }$…

    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 499, Column 403: an attribute value must be a literal unless it contains only name characters
    …WLINE}$NEWLINE</style>$NEWLINE<div id=\"cbTopWidget\"></div>$NEWLINE$BEGINSCRI…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 499, Column 403: character "\" is not allowed in the value of attribute "id"
    …WLINE}$NEWLINE</style>$NEWLINE<div id=\"cbTopWidget\"></div>$NEWLINE$BEGINSCRI…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 500, Column 175: "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/gallery/ap…
  • Error Line 500, Column 373: "data-vr-contentbox" is not a member of a group specified for any attribute
    …ite iconListBullet" data-vr-contentbox><a href="http://www.daytondailynews.com…
  • Error Line 500, Column 585: "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 500, Column 792: "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/gallery/…
  • Error Line 500, Column 1005: "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 500, Column 1229: there is no attribute "data-href"
    …r"><div class="fb-like-box" data-href="http://www.facebook.com/whiotv" data-wi…

    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 500, Column 1273: there is no attribute "data-width"
    …//www.facebook.com/whiotv" 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 500, Column 1291: there is no attribute "data-height"
    …/whiotv" 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 500, Column 1313: 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 500, Column 1332: 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 500, Column 1352: 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 502, Column 88: "data-vr-contentbox" is not a member of a group specified for any attribute
    …rue, "html": " <div data-vr-contentbox><a class=\"twitter-timeline\"  href=\"h…
  • Error Line 502, Column 88: document type does not allow element "div" here
    …rue, "html": " <div data-vr-contentbox><a class=\"twitter-timeline\"  href=\"h…

    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 502, Column 98: an attribute value must be a literal unless it contains only name characters
    …": " <div data-vr-contentbox><a class=\"twitter-timeline\"  href=\"https://twi…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 502, Column 125: an attribute value must be a literal unless it contains only name characters
    …x><a class=\"twitter-timeline\"  href=\"https://twitter.com/search?q=%40stormc…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 502, Column 189: there is no attribute "data-widget-id"
    …ch?q=%40stormcenter7\" data-widget-id=\"297008938627514368\" data-theme=\"ligh…

    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 502, Column 189: an attribute value must be a literal unless it contains only name characters
    …ch?q=%40stormcenter7\" data-widget-id=\"297008938627514368\" data-theme=\"ligh…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 502, Column 223: there is no attribute "data-theme"
    …-id=\"297008938627514368\" data-theme=\"light\" data-link-color=\"#036DBE\"  d…

    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 502, Column 223: an attribute value must be a literal unless it contains only name characters
    …-id=\"297008938627514368\" data-theme=\"light\" data-link-color=\"#036DBE\"  d…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 502, Column 249: there is no attribute "data-link-color"
    … data-theme=\"light\" data-link-color=\"#036DBE\"  data-related=\"whiotv, touc…

    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 502, Column 249: an attribute value must be a literal unless it contains only name characters
    … data-theme=\"light\" data-link-color=\"#036DBE\"  data-related=\"whiotv, touc…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 502, Column 275: there is no attribute "data-related"
    …-link-color=\"#036DBE\"  data-related=\"whiotv, touchdown7,whioradio\" data-ar…

    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 502, Column 275: an attribute value must be a literal unless it contains only name characters
    …-link-color=\"#036DBE\"  data-related=\"whiotv, touchdown7,whioradio\" data-ar…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 502, Column 295: "touchdown7" is not a member of a group specified for any attribute
    …E\"  data-related=\"whiotv, touchdown7,whioradio\" data-aria-polite=\"polite\"…
  • Error Line 502, Column 325: there is no attribute "data-aria-polite"
    …uchdown7,whioradio\" data-aria-polite=\"polite\" width=\"300\" height=\"200\" …

    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 502, Column 325: an attribute value must be a literal unless it contains only name characters
    …uchdown7,whioradio\" data-aria-polite=\"polite\" width=\"300\" height=\"200\" …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 502, Column 342: there is no attribute "width"
    …o\" data-aria-polite=\"polite\" width=\"300\" height=\"200\" lang=\"EN\">Tweet…

    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 502, Column 342: an attribute value must be a literal unless it contains only name characters
    …o\" data-aria-polite=\"polite\" width=\"300\" height=\"200\" lang=\"EN\">Tweet…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 502, Column 357: there is no attribute "height"
    …olite=\"polite\" width=\"300\" height=\"200\" lang=\"EN\">Tweets about \"@stor…

    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 502, Column 357: an attribute value must be a literal unless it contains only name characters
    …olite=\"polite\" width=\"300\" height=\"200\" lang=\"EN\">Tweets about \"@stor…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 502, Column 370: an attribute value must be a literal unless it contains only name characters
    …e\" width=\"300\" height=\"200\" lang=\"EN\">Tweets about \"@stormcenter7\"</a…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 502, Column 370: character "\" is not allowed in the value of attribute "lang"
    …e\" width=\"300\" height=\"200\" lang=\"EN\">Tweets about \"@stormcenter7\"</a…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 505, Column 89: "data-vr-contentbox" is not a member of a group specified for any attribute
    …lse, "html": " <div data-vr-contentbox><iframe src='http://share.whiotv.com/Wi…
  • Error Line 505, Column 89: document type does not allow element "div" here
    …lse, "html": " <div data-vr-contentbox><iframe src='http://share.whiotv.com/Wi…

    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 505, Column 170: cannot generate system identifier for general entity "callback"
    …ts/Slideshow.aspx?type=recently-added&callback=?&h=300&w=300&baseTag=base_slid…

    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 505, Column 170: general entity "callback" not defined and no default entity
    …ts/Slideshow.aspx?type=recently-added&callback=?&h=300&w=300&baseTag=base_slid…

    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 505, Column 178: reference not terminated by REFC delimiter
    …show.aspx?type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' m…

    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 505, Column 178: reference to external entity in attribute value
    …show.aspx?type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' m…

    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 505, Column 178: reference to entity "callback" for which no system identifier could be generated
    …show.aspx?type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' m…

    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 505, Column 169: entity was defined here
    …ets/Slideshow.aspx?type=recently-added&callback=?&h=300&w=300&baseTag=base_sli…
  • Warning Line 505, Column 181: cannot generate system identifier for general entity "h"
    …w.aspx?type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' marg…

    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 505, Column 181: general entity "h" not defined and no default entity
    …w.aspx?type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' marg…

    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 505, Column 182: reference not terminated by REFC delimiter
    ….aspx?type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' margi…

    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 505, Column 182: reference to external entity in attribute value
    ….aspx?type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' margi…

    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 505, Column 182: reference to entity "h" for which no system identifier could be generated
    ….aspx?type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' margi…

    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 505, Column 180: entity was defined here
    …ow.aspx?type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' mar…
  • Warning Line 505, Column 187: cannot generate system identifier for general entity "w"
    …?type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' marginwidt…

    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 505, Column 187: general entity "w" not defined and no default entity
    …?type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' marginwidt…

    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 505, Column 188: reference not terminated by REFC delimiter
    …type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' marginwidth…

    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 505, Column 188: reference to external entity in attribute value
    …type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' marginwidth…

    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 505, Column 188: reference to entity "w" for which no system identifier could be generated
    …type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' marginwidth…

    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 505, Column 186: entity was defined here
    …x?type=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' marginwid…
  • Warning Line 505, Column 193: cannot generate system identifier for general entity "baseTag"
    …recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' marginwidth='0px…

    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 505, Column 193: general entity "baseTag" not defined and no default entity
    …recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' marginwidth='0px…

    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 505, Column 200: reference not terminated by REFC delimiter
    …y-added&callback=?&h=300&w=300&baseTag=base_slide_300' marginwidth='0px' margi…

    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 505, Column 200: reference to external entity in attribute value
    …y-added&callback=?&h=300&w=300&baseTag=base_slide_300' marginwidth='0px' margi…

    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 505, Column 200: reference to entity "baseTag" for which no system identifier could be generated
    …y-added&callback=?&h=300&w=300&baseTag=base_slide_300' marginwidth='0px' margi…

    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 505, Column 192: entity was defined here
    …=recently-added&callback=?&h=300&w=300&baseTag=base_slide_300' marginwidth='0p…
  • Error Line 505, Column 261: there is no attribute "border"
    …width='0px' marginheight='0px' border='0' width='300' height='300' scrolling='…

    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 506, Column 537: character "&" is the first character of a delimiter but occurred as data
    …/" title="U.S. and world news">Nation & World News</a></li><li><a href="/s/new…

    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 506, Column 633: character "&" is the first character of a delimiter but occurred as data
    … title="Ohio and regional news">State & Regional News</a></li><li><a href="/s/…

    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 506, Column 732: character "&" is the first character of a delimiter but occurred as data
    …ent/" title="political news">Politics & Government News</a></li><li><a href="/…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 511, 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 511, 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 511, Column 389: 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 511, Column 432: 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 511, Column 613: 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 515, 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 515, 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 708, 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 712, 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 718, 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 708, Column 89: ID "forgotPasswordLink" first defined here
    …ta-capturescreen="forgotPassword" id="forgotPasswordLink">Forgot your password…
  • Error Line 786, 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 786, Column 56: ID "forgotPasswordSuccess" first defined here
    …></div><div style="display:none;" id="forgotPasswordSuccess"><div class="captu…
  • Error Line 805, Column 943: end tag for element "body" which is not open
    …HgTVEYBIQZNEgYXNw1cExtTARc=",0,10,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 805, Column 950: end tag for "object" omitted, but OMITTAG NO was specified
    …HgTVEYBIQZNEgYXNw1cExtTARc=",0,10,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 399, Column 14: start tag was here
        </script><div class="cmCol9 cmFirst cmLast cmClearfix"><div class="cmPencil…
  • Error Line 805, Column 950: end tag for "head" omitted, but OMITTAG NO was specified
    …HgTVEYBIQZNEgYXNw1cExtTARc=",0,10,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 805, Column 950: end tag for "html" which is not finished
    …HgTVEYBIQZNEgYXNw1cExtTARc=",0,10,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
  • 3.733 visits