Breaking news, weather, top stories, plus local photos and video for Syracuse and Central New York from NewsChannel 9 WSYR. ...

9wsyr.com
  • Domain Name
    9wsyr.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #37616
  • Page Size
    151.9 KB
  • Ip Address
    206.53.213.32
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    25 GIF, 85 JPG, 24 PNG

Website Meta Analysis

  • Title
    Home - NewsChannel 9 WSYR
  • Meta Keyword
    Syracuse Weather WSYR TV Live Doppler 9news WIXT CNY Central New York Snow Onondaga County Your Stories Storm Team Carrie Lazarus Rod Wood Family Healthcast Friday Night Fever Oswego Lake-Effect
  • Meta Description
    Breaking news, weather, top stories, plus local photos and video for Syracuse and Central New York from NewsChannel 9 WSYR.

Technical Analysis

  • Webserver
    PWS/8.0.16
  • Ip Address
    206.53.213.32
  • Domain Age
    8 Years, 6 Months, 5 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 16 Aug 2013 09:08:22 GMT
  • server: PWS/8.0.16
  • x-px: rf-ms h0-s65.p3-dfw ( h0-s8.p3-dfw), ht h0-s8.p3-dfw.cdngp.net
  • cache-control: max-age=120
  • expires: Fri, 16 Aug 2013 09:09:00 GMT
  • age: 82
  • content-length: 27968
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • px-uncompress-origin: 142651
  • x-served-by: WEBC2N1
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
DNS Hostmaster
Clear Channel Identity, Inc.
20880 Stone Oak Parkway
San Antonio TX 78258
US
email +1.2102535000 Fax: +1.2102535013

Domain Name: 9wsyr.com

Registrar Name: Markmonitor.com
Registrar Whois: whois.markmonitor.com
Registrar Homepage: http://www.markmonitor.com

Administrative Contact:
DNS Hostmaster
Clear Channel Identity, Inc.
20880 Stone Oak Parkway
San Antonio TX 78258
US
email +1.2102535000 Fax: +1.2102535013
Technical Contact, Zone Contact:
DNS Hostmaster
Clear Channel Identity, Inc.
20880 Stone Oak Parkway
San Antonio TX 78258
US
email +1.2102535000 Fax: +1.2102535013

Created on..............: 2005-01-25.
Expires on..............: 2013-01-25.
Record last updated on..: 2012-02-09.

Domain servers in listed order:

dns1.clearchannel.com
ns2.clearchannel.com
ns1.clearchannel.com
dns2.clearchannel.com

DNS Analysis


DNS servers
ns2.nexstarbroadcasting.com
ns1.nexstarbroadcasting.com


DNS Records

Answer records
9wsyr.com SOA
server: ns1.nexstarbroadcasting.com
email: hostmaster@ns1.nexstarbroadcasting.com
serial: 2012120345
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
3600s
9wsyr.com NS  ns2.nexstarbroadcasting.com 3600s
9wsyr.com NS  ns1.nexstarbroadcasting.com 3600s
9wsyr.com A 206.53.213.32 3600s
9wsyr.com MX
preference: 20
exchange: mx2.nexstar.tv
3600s
9wsyr.com MX
preference: 10
exchange: mx1.nexstar.tv
3600s
9wsyr.com TXT v=spf1 include:spf.idmemail.net include:nptv.idmemail.net ~all 3600s

Authority records

Additional records
ns1.nexstarbroadcasting.com A 72.249.102.9 3600s
ns2.nexstarbroadcasting.com A 70.42.108.9 3600s
mx1.nexstar.tv A 70.42.108.21 30s
mx2.nexstar.tv A 72.249.102.21 30s

IP 206.53.213.32 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    San Antonio
  • Continent Code
    78258
  • Latitude
    210
  • Longitude
    641
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 206.53.213.32"
    #
    # Use "?" to get help.
    #

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

    NetRange: 206.53.208.0 - 206.53.223.255
    CIDR: 206.53.208.0/20
    OriginAS:
    NetName: CLEAR-CHANNEL-BLOCK-1
    NetHandle: NET-206-53-208-0-1
    Parent: NET-206-0-0-0-0
    NetType: Direct Assignment
    RegDate: 2004-10-04
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-206-53-208-0-1

    OrgName: Clear Channel Communications, Inc.
    OrgId: CCC-111
    Address: Clear Channel
    Address: 20880 Stone Oak Parkway
    City: San Antonio
    StateProv: TX
    PostalCode: 78258
    Country: US
    RegDate: 1998-12-11
    Updated: 2011-09-24
    Ref: http://whois.arin.net/rest/org/CCC-111

    OrgAbuseHandle: MOORE7-ARIN
    OrgAbuseName: Moore, Rick
    OrgAbusePhone: +1-210-253-5310
    OrgAbuseEmail: rickmoore@clearchannel.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/MOORE7-ARIN

    OrgTechHandle: MOORE7-ARIN
    OrgTechName: Moore, Rick
    OrgTechPhone: +1-210-253-5310
    OrgTechEmail: rickmoore@clearchannel.com
    OrgTechRef: http://whois.arin.net/rest/poc/MOORE7-ARIN

    RTechHandle: MOORE7-ARIN
    RTechName: Moore, Rick
    RTechPhone: +1-210-253-5310
    RTechEmail: rickmoore@clearchannel.com
    RTechRef: http://whois.arin.net/rest/poc/MOORE7-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
  • 362 Errors
  • 293 Warnings
Ratio Text/Html
  • 0.6966816420183946
Message Error
  • Error Line 66, Column 8: required attribute "type" not specified
    <script>

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

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

  • Warning Line 75, Column 49: cannot generate system identifier for general entity "c2"
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 49: general entity "c2" not defined and no default entity
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 51: reference not terminated by REFC delimiter
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 51: reference to external entity in attribute value
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 51: reference to entity "c2" for which no system identifier could be generated
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 48: entity was defined here
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>
  • Warning Line 75, Column 61: cannot generate system identifier for general entity "cv"
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 61: general entity "cv" not defined and no default entity
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 63: reference not terminated by REFC delimiter
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 63: reference to external entity in attribute value
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 63: reference to entity "cv" for which no system identifier could be generated
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 60: entity was defined here
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>
  • Warning Line 75, Column 68: cannot generate system identifier for general entity "cj"
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 68: general entity "cj" not defined and no default entity
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 70: reference not terminated by REFC delimiter
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 70: reference to external entity in attribute value
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 70: reference to entity "cj" for which no system identifier could be generated
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 75, Column 67: entity was defined here
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>
  • Error Line 75, Column 75: required attribute "alt" not specified
    …c='http://b.scorecardresearch.com/p?c1=2&c2=14054738&cv=2.0&cj=1' /></noscript>

    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 142, Column 7: required attribute "type" not specified
    <style>

    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 142, Column 7: document type does not allow element "style" here
    <style>

    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 148, Column 25: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div class="dowloadsbar">

    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 158, Column 29: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<div id="WelcomeControl">

    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 167, Column 253: required attribute "alt" not specified
    …tes/wsyr/images/transparent.gif" border="0" height="100" width="235"></a></div>

    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 167, Column 257: end tag for "img" omitted, but OMITTAG NO was specified
    …tes/wsyr/images/transparent.gif" border="0" height="100" width="235"></a></div>

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

  • Info Line 167, Column 135: start tag was here
    …><a href="/default.aspx?=viaMasthead"><img style="width: 235px; height: 100px;…
  • Error Line 186, Column 22: an attribute specification must start with a name or name token
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 186, Column 22: element "scr" undefined
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 186, Column 128: character "<" is the first character of a delimiter but occurred as data
    …src="http://w11.localadbuy.com/banners/idm-ajtg.js"><' + '/' + 'scr' + 'ipt>');

    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 188, Column 9: end tag for "scr" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 186, Column 18: start tag was here
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…
  • Error Line 205, Column 177: there is no attribute "onChange"
    … class="GoogleSearchBarDrop" onChange="document.getElementById('ctl00_ctl00_ct…

    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 206, Column 28: there is no attribute "imgUrl"
    	<option value="70" imgUrl="http://www.9wsyr.com//images/transparent.gif">Searc…

    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 217, Column 128: required attribute "alt" not specified
    …ar___PoweredBy" src="/images/transparent.gif" style="border-width:0px;" /></td>

    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 226, Column 1262: required attribute "alt" not specified
    …><img src="/sites/wsyr/images/f.png" /></a></li><li><a id="TopNavID-I1-N12" hr…

    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 226, Column 1376: required attribute "alt" not specified
    …/twitter.com/newschannel9"><img src="/sites/wsyr/images/t.png" /></a></li></ul>

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

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

  • Warning Line 228, Column 352: character "&" is the first character of a delimiter but occurred as data
    …w.9wsyr.com/content/links.aspx">Links & Reminders</a></li><li><a id="TopNavID-…

    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 228, Column 793: character "&" is the first character of a delimiter but occurred as data
    …ntent/lostpets/default.aspx">Pet Lost & Found</a></li><li><a id="TopNavID-I2-N…

    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 228, Column 905: character "&" is the first character of a delimiter but occurred as data
    …ent/news/gas_prices/default.aspx">Gas & Energy Prices</a></li><li><a id="TopNa…

    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 228, Column 4358: character "&" is the first character of a delimiter but occurred as data
    …gc/cat/oaa_calendar/default.aspx">Out & About Calendar</a></li><li><a class="H…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 228, Column 6211: required attribute "alt" not specified
    …<img src="/images/common/camera.jpg" /> Photos</a><ul class="Hidden"><li><a id…

    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 238, Column 22: an attribute specification must start with a name or name token
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 238, Column 22: element "scr" undefined
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 238, Column 128: character "<" is the first character of a delimiter but occurred as data
    …src="http://w11.localadbuy.com/banners/idm-ajtg.js"><' + '/' + 'scr' + 'ipt>');

    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 240, Column 9: end tag for "scr" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 238, Column 18: start tag was here
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…
  • Error Line 315, Column 23: document type does not allow element "style" here
    <style type="text/css">

    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 429, Column 49: required attribute "alt" not specified
    				Loading ... <img src="/images/spinner.gif" />

    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 433, Column 197: there is no attribute "rotatorWidth"
    …l00p" class="boxRotator" rotatorWidth="673" totalSlideCount="10" teaseImageHei…

    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 433, Column 219: there is no attribute "totalSlideCount"
    …r" rotatorWidth="673" totalSlideCount="10" teaseImageHeight="100" teaseButtonW…

    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 433, Column 241: there is no attribute "teaseImageHeight"
    …totalSlideCount="10" teaseImageHeight="100" teaseButtonWidth="125" teaseCount=…

    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 433, Column 264: there is no attribute "teaseButtonWidth"
    …aseImageHeight="100" teaseButtonWidth="125" teaseCount="5" slideEaseFunc="ease…

    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 433, Column 281: there is no attribute "teaseCount"
    …00" teaseButtonWidth="125" teaseCount="5" slideEaseFunc="easeOutQuad" slideEas…

    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 433, Column 299: there is no attribute "slideEaseFunc"
    …th="125" teaseCount="5" slideEaseFunc="easeOutQuad" slideEaseTime="0" teaseEas…

    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 433, Column 327: there is no attribute "slideEaseTime"
    …eEaseFunc="easeOutQuad" slideEaseTime="0" teaseEaseFunc="easeOutQuad" teaseEas…

    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 433, Column 345: there is no attribute "teaseEaseFunc"
    …Quad" slideEaseTime="0" teaseEaseFunc="easeOutQuad" teaseEaseTime="650" slideI…

    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 433, Column 373: there is no attribute "teaseEaseTime"
    …eEaseFunc="easeOutQuad" teaseEaseTime="650" slideInterval="10000" style="width…

    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 433, Column 393: there is no attribute "slideInterval"
    …ad" teaseEaseTime="650" slideInterval="10000" style="width:673px; height:435px…

    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 434, Column 45: there is no attribute "action"
    …		<div class="rotatorViewerView" action="0" style="width:673px; height:285px;">

    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 438, Column 408: required attribute "alt" not specified
    …-969c-e278d4a1d08e/FeatureImage.jpg" /></a></div><div><div class="rotatorSumma…

    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 440, Column 407: required attribute "alt" not specified
    …2/11/00/14/wkmriqxexkxdcbygvlnl.jpg" /></a></div><div><div class="rotatorSumma…

    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 442, Column 437: required attribute "alt" not specified
    …-b8c0-6bb129c1ef3b/FeatureImage.jpg" /></a></div><div><div class="rotatorSumma…

    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 444, Column 415: required attribute "alt" not specified
    …-92bc-cda998e5c74f/FeatureImage.jpg" /></a></div><div><div class="rotatorSumma…

    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 446, Column 429: required attribute "alt" not specified
    …-8ed7-c20c0abbee8e/FeatureImage.jpg" /></a></div><div><div class="rotatorSumma…

    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 448, Column 368: required attribute "alt" not specified
    …-927a-b3f257b9e3d0/FeatureImage.jpg" /></a></div><div><div class="rotatorSumma…

    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 450, Column 461: required attribute "alt" not specified
    …-a5a7-2651fdadb3a8/FeatureImage.jpg" /></a></div><div><div class="rotatorSumma…

    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 452, Column 421: required attribute "alt" not specified
    …-876d-9e91c88ffed7/FeatureImage.gif" /></a></div><div><div class="rotatorSumma…

    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 454, Column 422: required attribute "alt" not specified
    …-a967-dbe975b19877/FeatureImage.jpg" /></a></div><div><div class="rotatorSumma…

    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 456, Column 420: required attribute "alt" not specified
    …-92bc-cda998e5c74f/FeatureImage.jpg" /></a></div><div><div class="rotatorSumma…

    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 460, Column 140: there is no attribute "page"
    …ft" style="height:150px;"></a><div class="rotatorTeaseView" page="0" slide="0">

    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 460, Column 150: there is no attribute "slide"
    …ft" style="height:150px;"></a><div class="rotatorTeaseView" page="0" slide="0">

    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 463, Column 51: duplicate specification of attribute "class"
    … class="rotatorTeaseli current" class="rotatorTeaseli" style="width:125;height…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 463, Column 352: required attribute "alt" not specified
    …dline.jpg" class="rotatorTeaseImage" /></span><span class="rotatorTeaseText">W…

    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 463, Column 784: required attribute "alt" not specified
    …gvlnl.jpg" class="rotatorTeaseImage" /></span><span class="rotatorTeaseText">P…

    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 463, Column 1189: required attribute "alt" not specified
    …dline.jpg" class="rotatorTeaseImage" /></span><span class="rotatorTeaseText">N…

    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 463, Column 1617: required attribute "alt" not specified
    …dline.jpg" class="rotatorTeaseImage" /></span><span class="rotatorTeaseText">M…

    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 463, Column 2031: required attribute "alt" not specified
    …dline.jpg" class="rotatorTeaseImage" /></span><span class="rotatorTeaseText">O…

    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 463, Column 2443: required attribute "alt" not specified
    …dline.jpg" class="rotatorTeaseImage" /></span><span class="rotatorTeaseText">P…

    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 463, Column 2865: required attribute "alt" not specified
    …dline.jpg" class="rotatorTeaseImage" /></span><span class="rotatorTeaseText">S…

    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 463, Column 3286: required attribute "alt" not specified
    …Image.gif" class="rotatorTeaseImage" /></span><span class="rotatorTeaseText">N…

    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 463, Column 3704: required attribute "alt" not specified
    …dline.jpg" class="rotatorTeaseImage" /></span><span class="rotatorTeaseText">L…

    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 463, Column 4122: required attribute "alt" not specified
    …dline.jpg" class="rotatorTeaseImage" /></span><span class="rotatorTeaseText">B…

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

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

  • Warning Line 494, Column 7: S separator in comment declaration
    <!---- Code for Live Stream Alert Bar ---->

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

  • Error Line 494, Column 8: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!---- Code for Live Stream Alert Bar ---->
  • Info Line 494, Column 1: comment declaration started here
    <!---- Code for Live Stream Alert Bar ---->
  • Error Line 505, Column 5: end tag for "ul" which is not finished
    </ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 513, Column 103: there is no attribute "scr"
    …m/syracuse/wsyr/" id="Link1"><img scr="http://www.9wsyr.com/sites/wsyr/images/…

    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 513, Column 223: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …me="Rotating1" id="Rotating1" style="border:none" width=220 height=60></a></td>
  • Error Line 513, Column 234: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …me="Rotating1" id="Rotating1" style="border:none" width=220 height=60></a></td>
  • Error Line 513, Column 236: required attribute "src" not specified
    …me="Rotating1" id="Rotating1" style="border:none" width=220 height=60></a></td>

    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 513, Column 236: required attribute "alt" not specified
    …me="Rotating1" id="Rotating1" style="border:none" width=220 height=60></a></td>

    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 513, Column 240: end tag for "img" omitted, but OMITTAG NO was specified
    …me="Rotating1" id="Rotating1" style="border:none" width=220 height=60></a></td>

    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 513, Column 94: start tag was here
    …oupigg.com/syracuse/wsyr/" id="Link1"><img scr="http://www.9wsyr.com/sites/wsy…
  • Error Line 515, Column 156: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …me="Rotating2" id="Rotating2" style="border:none" width=220 height=60></a></td>
  • Error Line 515, Column 167: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …me="Rotating2" id="Rotating2" style="border:none" width=220 height=60></a></td>
  • Error Line 515, Column 169: required attribute "src" not specified
    …me="Rotating2" id="Rotating2" style="border:none" width=220 height=60></a></td>

    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 515, Column 169: required attribute "alt" not specified
    …me="Rotating2" id="Rotating2" style="border:none" width=220 height=60></a></td>

    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 515, Column 173: end tag for "img" omitted, but OMITTAG NO was specified
    …me="Rotating2" id="Rotating2" style="border:none" width=220 height=60></a></td>

    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 515, Column 32: start tag was here
        <td><a href="#" id="Link2"><img scr="http://www.9wsyr.com/sites/wsyr/images…
  • Error Line 521, Column 22: an attribute specification must start with a name or name token
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 521, Column 22: element "scr" undefined
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 521, Column 128: character "<" is the first character of a delimiter but occurred as data
    …src="http://w11.localadbuy.com/banners/idm-ajtg.js"><' + '/' + 'scr' + 'ipt>');

    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 523, Column 9: end tag for "scr" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 521, Column 18: start tag was here
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…
  • Error Line 532, Column 32: required attribute "type" not specified
      <script language="JavaScript">

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

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

  • Warning Line 541, Column 83: cannot generate system identifier for general entity "LID"
    …dgestreetdiscountdeals.9wsyr.com/engine/Welcome.aspx?contestid=59881&LID=2585",

    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 541, Column 83: general entity "LID" not defined and no default entity
    …dgestreetdiscountdeals.9wsyr.com/engine/Welcome.aspx?contestid=59881&LID=2585",

    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 541, Column 86: reference not terminated by REFC delimiter
    …dgestreetdiscountdeals.9wsyr.com/engine/Welcome.aspx?contestid=59881&LID=2585",

    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 541, Column 86: reference to entity "LID" for which no system identifier could be generated
    …dgestreetdiscountdeals.9wsyr.com/engine/Welcome.aspx?contestid=59881&LID=2585",

    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 541, Column 82: entity was defined here
    …dgestreetdiscountdeals.9wsyr.com/engine/Welcome.aspx?contestid=59881&LID=2585",
  • Warning Line 542, Column 85: reference not terminated by REFC delimiter
    …dgestreetdiscountdeals.9wsyr.com/engine/Welcome.aspx?contestid=59881&LID=2585",

    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 542, Column 85: reference to entity "LID" for which no system identifier could be generated
    …dgestreetdiscountdeals.9wsyr.com/engine/Welcome.aspx?contestid=59881&LID=2585",

    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 541, Column 82: entity was defined here
    …dgestreetdiscountdeals.9wsyr.com/engine/Welcome.aspx?contestid=59881&LID=2585",
  • Warning Line 543, Column 60: cannot generate system identifier for general entity "market"
    	"http://www.seekitlocal.com/default.aspx?l=Syracuse%2c+NY&market=555");

    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 543, Column 60: general entity "market" not defined and no default entity
    	"http://www.seekitlocal.com/default.aspx?l=Syracuse%2c+NY&market=555");

    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 543, Column 66: reference not terminated by REFC delimiter
    	"http://www.seekitlocal.com/default.aspx?l=Syracuse%2c+NY&market=555");

    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 543, Column 66: reference to entity "market" for which no system identifier could be generated
    	"http://www.seekitlocal.com/default.aspx?l=Syracuse%2c+NY&market=555");

    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 543, Column 59: entity was defined here
    	"http://www.seekitlocal.com/default.aspx?l=Syracuse%2c+NY&market=555");
  • Warning Line 579, Column 51: cannot generate system identifier for general entity "utm_id"
    	("http://www.goforgreater.org?utm_campaign=10082&utm_id=10082",

    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 579, Column 51: general entity "utm_id" not defined and no default entity
    	("http://www.goforgreater.org?utm_campaign=10082&utm_id=10082",

    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 579, Column 57: reference not terminated by REFC delimiter
    	("http://www.goforgreater.org?utm_campaign=10082&utm_id=10082",

    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 579, Column 57: reference to entity "utm_id" for which no system identifier could be generated
    	("http://www.goforgreater.org?utm_campaign=10082&utm_id=10082",

    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 579, Column 50: entity was defined here
    	("http://www.goforgreater.org?utm_campaign=10082&utm_id=10082",
  • Error Line 633, Column 49: required attribute "alt" not specified
    				Loading ... <img src="/images/spinner.gif" />

    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 640, Column 62: there is no attribute "data-totalpages"
    … style="width:670px;" data-totalpages="7" data-page="1" data-scrollpixel="670"…

    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 640, Column 76: there is no attribute "data-page"
    … style="width:670px;" data-totalpages="7" data-page="1" data-scrollpixel="670">

    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 640, Column 97: there is no attribute "data-scrollpixel"
    … style="width:670px;" data-totalpages="7" data-page="1" data-scrollpixel="670">

    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 648, Column 101: cannot generate system identifier for general entity "navCatId"
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">

    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 648, Column 101: general entity "navCatId" not defined and no default entity
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">

    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 648, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">

    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 648, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">

    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 648, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 649, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/175/2013/02/11/00/14/tpkrxmwlkmgfgtfmchgv.jpg" />

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

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

  • Warning Line 653, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">

    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 653, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">

    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 653, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 661, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935829&navCatId=20694">

    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 661, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935829&navCatId=20694">

    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 661, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935829&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 662, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/175/2013/02/10/13/07/hbmdcvywnapkrwxdvpzv.jpg" />

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

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

  • Warning Line 666, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935829&navCatId=20694">

    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 666, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935829&navCatId=20694">

    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 666, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935829&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 674, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935535&navCatId=20694">

    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 674, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935535&navCatId=20694">

    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 674, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935535&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 675, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/175/2013/02/10/00/19/cluwziztovbuytvmilop.jpg" />

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

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

  • Warning Line 679, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935535&navCatId=20694">

    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 679, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935535&navCatId=20694">

    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 679, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935535&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 687, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935531&navCatId=20694">

    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 687, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935531&navCatId=20694">

    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 687, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935531&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 688, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/10/00/17/gdacucifpjnjugdnerdn.jpg" />

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

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

  • Warning Line 692, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935531&navCatId=20694">

    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 692, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935531&navCatId=20694">

    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 692, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935531&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 700, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935524&navCatId=20694">

    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 700, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935524&navCatId=20694">

    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 700, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935524&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 701, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/10/00/14/bkpxjhbahbhersdehxgh.jpg" />

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

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

  • Warning Line 705, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935524&navCatId=20694">

    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 705, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935524&navCatId=20694">

    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 705, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935524&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 713, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935335&navCatId=20694">

    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 713, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935335&navCatId=20694">

    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 713, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935335&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 714, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/175/2013/02/09/13/06/fgrjvoljqqadtedtwgtj.jpg" />

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

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

  • Warning Line 718, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935335&navCatId=20694">

    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 718, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935335&navCatId=20694">

    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 718, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935335&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 726, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935117&navCatId=20694">

    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 726, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935117&navCatId=20694">

    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 726, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935117&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 727, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/09/04/27/svvpebtpllqafqrjqlvs.jpg" />

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

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

  • Warning Line 731, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935117&navCatId=20694">

    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 731, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935117&navCatId=20694">

    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 731, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935117&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 739, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935110&navCatId=20694">

    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 739, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935110&navCatId=20694">

    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 739, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935110&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 740, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/175/2013/02/09/04/24/mmyblloozcojpfoqvucf.jpg" />

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

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

  • Warning Line 744, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935110&navCatId=20694">

    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 744, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935110&navCatId=20694">

    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 744, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935110&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 752, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935111&navCatId=20694">

    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 752, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935111&navCatId=20694">

    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 752, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935111&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 753, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/09/04/24/xyoduykxdibefbvwwkbb.jpg" />

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

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

  • Warning Line 757, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935111&navCatId=20694">

    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 757, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935111&navCatId=20694">

    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 757, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3935111&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 765, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934635&navCatId=20694">

    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 765, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934635&navCatId=20694">

    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 765, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934635&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 766, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/23/31/hfmrwjjvdcijicyfxyye.jpg" />

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

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

  • Warning Line 770, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934635&navCatId=20694">

    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 770, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934635&navCatId=20694">

    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 770, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934635&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 778, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934639&navCatId=20694">

    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 778, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934639&navCatId=20694">

    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 778, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934639&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 779, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/175/2013/02/08/23/33/dpnmprhivhupxykbbxmb.jpg" />

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

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

  • Warning Line 783, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934639&navCatId=20694">

    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 783, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934639&navCatId=20694">

    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 783, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934639&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 791, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934558&navCatId=20694">

    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 791, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934558&navCatId=20694">

    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 791, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934558&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 792, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/175/2013/02/08/23/06/yapkawwjwfxgokuwmdsz.jpg" />

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

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

  • Warning Line 796, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934558&navCatId=20694">

    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 796, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934558&navCatId=20694">

    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 796, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934558&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 804, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934527&navCatId=20694">

    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 804, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934527&navCatId=20694">

    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 804, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934527&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 805, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/22/50/odhgcctiookkjzhtobzo.jpg" />

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

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

  • Warning Line 809, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934527&navCatId=20694">

    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 809, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934527&navCatId=20694">

    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 809, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934527&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 817, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934494&navCatId=20694">

    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 817, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934494&navCatId=20694">

    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 817, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934494&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 818, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/175/2013/02/08/22/26/pplyxumsctmmaohhuzik.jpg" />

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

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

  • Warning Line 822, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934494&navCatId=20694">

    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 822, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934494&navCatId=20694">

    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 822, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934494&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 830, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934490&navCatId=20694">

    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 830, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934490&navCatId=20694">

    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 830, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934490&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 831, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/22/23/nubpubtkdfzkhnncujql.jpg" />

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

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

  • Warning Line 835, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934490&navCatId=20694">

    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 835, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934490&navCatId=20694">

    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 835, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934490&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 843, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934410&navCatId=20694">

    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 843, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934410&navCatId=20694">

    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 843, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934410&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 844, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/175/2013/02/08/21/28/zeyzwbmpwbveidjmcikv.jpg" />

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

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

  • Warning Line 848, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934410&navCatId=20694">

    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 848, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934410&navCatId=20694">

    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 848, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934410&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 856, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934205&navCatId=20694">

    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 856, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934205&navCatId=20694">

    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 856, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934205&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 857, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/17/45/wkhxaqtszoqriejwnxrj.jpg" />

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

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

  • Warning Line 861, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934205&navCatId=20694">

    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 861, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934205&navCatId=20694">

    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 861, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934205&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 869, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934187&navCatId=20694">

    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 869, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934187&navCatId=20694">

    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 869, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934187&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 870, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/17/32/qcibefgxtqhidxtsvmvq.jpg" />

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

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

  • Warning Line 874, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934187&navCatId=20694">

    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 874, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934187&navCatId=20694">

    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 874, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934187&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 882, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934135&navCatId=20694">

    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 882, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934135&navCatId=20694">

    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 882, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934135&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 883, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/16/57/uksgempivvsltomwypnq.jpg" />

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

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

  • Warning Line 887, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934135&navCatId=20694">

    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 887, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934135&navCatId=20694">

    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 887, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934135&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 895, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934391&navCatId=20694">

    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 895, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934391&navCatId=20694">

    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 895, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934391&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 896, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/21/11/mffqanqpohlakcarjwfv.jpg" />

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

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

  • Warning Line 900, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934391&navCatId=20694">

    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 900, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934391&navCatId=20694">

    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 900, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934391&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 908, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934076&navCatId=20694">

    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 908, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934076&navCatId=20694">

    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 908, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934076&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 909, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/16/14/dpvryiyjjbnaqzgqymuo.jpg" />

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

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

  • Warning Line 913, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934076&navCatId=20694">

    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 913, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934076&navCatId=20694">

    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 913, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3934076&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 921, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933774&navCatId=20694">

    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 921, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933774&navCatId=20694">

    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 921, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933774&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 922, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/12/12/amctqttcsdkqmilijuhq.jpg" />

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

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

  • Warning Line 926, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933774&navCatId=20694">

    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 926, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933774&navCatId=20694">

    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 926, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933774&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 934, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933776&navCatId=20694">

    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 934, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933776&navCatId=20694">

    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 934, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933776&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 935, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/175/2013/02/08/12/14/naonlczoxdkkxillaebp.jpg" />

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

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

  • Warning Line 939, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933776&navCatId=20694">

    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 939, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933776&navCatId=20694">

    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 939, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933776&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 940, Column 39: character "&" is the first character of a delimiter but occurred as data
    								What's in Store: Kinney Drugs & Amazing Deals 02-08-13

    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 947, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933770&navCatId=20694">

    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 947, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933770&navCatId=20694">

    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 947, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933770&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 948, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/12/03/lleyvkctucsjgdvihabc.jpg" />

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

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

  • Warning Line 952, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933770&navCatId=20694">

    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 952, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933770&navCatId=20694">

    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 952, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933770&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 953, Column 34: character "&" is the first character of a delimiter but occurred as data
    								The School Buzz: "Beauty & the Beast 02-08-13

    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 960, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933760&navCatId=20694">

    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 960, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933760&navCatId=20694">

    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 960, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933760&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 961, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/175/2013/02/08/11/45/eswgebnpucwujgfeqmhx.jpg" />

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

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

  • Warning Line 965, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933760&navCatId=20694">

    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 965, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933760&navCatId=20694">

    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 965, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933760&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 973, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933752&navCatId=20694">

    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 973, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933752&navCatId=20694">

    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 973, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933752&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 974, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/11/28/czfznccqfjncxdnbwkkb.jpg" />

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

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

  • Warning Line 978, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933752&navCatId=20694">

    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 978, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933752&navCatId=20694">

    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 978, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933752&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 986, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933749&navCatId=20694">

    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 986, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933749&navCatId=20694">

    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 986, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933749&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 987, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/11/23/sfbilppjjxmsutpszust.jpg" />

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

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

  • Warning Line 991, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933749&navCatId=20694">

    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 991, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933749&navCatId=20694">

    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 991, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933749&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 999, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933748&navCatId=20694">

    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 999, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933748&navCatId=20694">

    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 999, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933748&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 1000, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/175/2013/02/08/11/21/ejiiyzdmqqlcgfadrqoa.jpg" />

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

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

  • Warning Line 1004, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933748&navCatId=20694">

    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 1004, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933748&navCatId=20694">

    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 1004, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933748&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 1012, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933742&navCatId=20694">

    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 1012, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933742&navCatId=20694">

    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 1012, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933742&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 1013, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/10/54/fcbjnyfgypgvplzwmrqj.jpg" />

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

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

  • Warning Line 1017, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933742&navCatId=20694">

    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 1017, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933742&navCatId=20694">

    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 1017, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933742&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 1025, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933741&navCatId=20694">

    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 1025, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933741&navCatId=20694">

    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 1025, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933741&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 1026, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/157/2013/02/08/10/51/gkbiktlwbkcdyjeimqhe.jpg" />

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

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

  • Warning Line 1030, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933741&navCatId=20694">

    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 1030, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933741&navCatId=20694">

    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 1030, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933741&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Warning Line 1038, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933481&navCatId=20694">

    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 1038, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933481&navCatId=20694">

    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 1038, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933481&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 1039, Column 140: required attribute "alt" not specified
    …te.com/zStorage/clipsyndicate/175/2013/02/08/04/28/ddtsjsrwoinuftojrcqc.jpg" />

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

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

  • Warning Line 1043, Column 109: reference not terminated by REFC delimiter
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933481&navCatId=20694">

    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 1043, Column 109: reference to external entity in attribute value
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933481&navCatId=20694">

    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 1043, Column 109: reference to entity "navCatId" for which no system identifier could be generated
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3933481&navCatId=20694">

    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 648, Column 100: entity was defined here
    …f="http://www.9wsyr.com/mediacenter/local.aspx?videoId=3936051&navCatId=20694">
  • Error Line 1077, Column 275: required attribute "alt" not specified
    …g" width="100" class="HeadlineImage" /></a></td><td class="HeadlineRight"><a h…

    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 1078, Column 83: element "nobr" undefined
    …Valentines Day rush on Thursday. <nobr><img src="/images/videobullet.gif" alt=…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1078, Column 146: value of attribute "align" cannot be "baseline"; must be one of "top", "middle", "bottom", "left", "right"
    …ullet.gif" alt="Video" align="baseline" /> <a href="/mediacenter/local.aspx?vi…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 1112, Column 282: required attribute "alt" not specified
    …" height="100" class="HeadlineImage" /></a></td><td class="HeadlineRight"><a h…

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

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

  • Warning Line 1118, Column 770: cannot generate system identifier for general entity "R"
    …">Cicero man waiting for guaranteed money from H&R Block: Your Stories</a></li>

    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 1118, Column 770: general entity "R" not defined and no default entity
    …">Cicero man waiting for guaranteed money from H&R Block: Your Stories</a></li>

    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 1118, Column 771: reference not terminated by REFC delimiter
    …">Cicero man waiting for guaranteed money from H&R Block: Your Stories</a></li>

    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 1118, Column 771: reference to entity "R" for which no system identifier could be generated
    …">Cicero man waiting for guaranteed money from H&R Block: Your Stories</a></li>

    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 1118, Column 769: entity was defined here
    …">Cicero man waiting for guaranteed money from H&R Block: Your Stories</a></li>
  • Error Line 1172, Column 69: required attribute "alt" not specified
    <img src="/images/buttons/next-lg-gray.gif" width="24" height="31" />

    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 1205, Column 281: required attribute "alt" not specified
    …" height="100" class="HeadlineImage" /></a></td><td class="HeadlineRight"><a h…

    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 1239, Column 249: required attribute "alt" not specified
    …" height="100" class="HeadlineImage" /></a></td><td class="HeadlineRight"><a h…

    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 1277, Column 269: required attribute "alt" not specified
    …" height="100" class="HeadlineImage" /></a></td><td class="HeadlineRight"><a h…

    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 1283, Column 269: value of attribute "align" cannot be "baseline"; must be one of "top", "middle", "bottom", "left", "right"
    …ullet.gif" alt="Video" align="baseline" /> <a href="/mediacenter/local.aspx?vi…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 1283, Column 592: value of attribute "align" cannot be "baseline"; must be one of "top", "middle", "bottom", "left", "right"
    …ullet.gif" alt="Video" align="baseline" /> <a href="/mediacenter/local.aspx?vi…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 1283, Column 976: value of attribute "align" cannot be "baseline"; must be one of "top", "middle", "bottom", "left", "right"
    …ullet.gif" alt="Video" align="baseline" /> <a href="/mediacenter/local.aspx?vi…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 1302, Column 22: an attribute specification must start with a name or name token
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 1302, Column 22: element "scr" undefined
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1302, Column 128: character "<" is the first character of a delimiter but occurred as data
    …src="http://w11.localadbuy.com/banners/idm-ajtg.js"><' + '/' + 'scr' + 'ipt>');

    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 1304, Column 9: end tag for "scr" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 1302, Column 18: start tag was here
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…
  • Error Line 1342, Column 49: required attribute "alt" not specified
    				Loading ... <img src="/images/spinner.gif" />

    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 1346, Column 335: there is no attribute "allowTransparency"
    … overflow:hidden; width:325px; height:62px;" allowTransparency="true"></iframe>

    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 1377, Column 241: required attribute "alt" not specified
    …" height="100" class="HeadlineImage" /></a></td><td class="HeadlineRight"><a h…

    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 1407, Column 49: required attribute "alt" not specified
    				Loading ... <img src="/images/spinner.gif" />

    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 1420, Column 115: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …llspacing="0" style="border-collapse: collapse" width="100%" bgcolor="#e4e4ee">

    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 1427, Column 93: required attribute "alt" not specified
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>

    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 1427, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>

    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 1427, Column 1: start tag was here
    <img border="0" src="http://www.centralmediaserver.com/transparent.gif" width="…
  • Error Line 1427, Column 98: end tag for "br" omitted, but OMITTAG NO was specified
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>

    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 1427, Column 94: start tag was here
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>
  • Error Line 1429, Column 115: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …llspacing="0" style="border-collapse: collapse" width="100%" bgcolor="#e4e4ee">

    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 1436, Column 93: required attribute "alt" not specified
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>

    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 1436, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>

    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 1436, Column 1: start tag was here
    <img border="0" src="http://www.centralmediaserver.com/transparent.gif" width="…
  • Error Line 1436, Column 98: end tag for "br" omitted, but OMITTAG NO was specified
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>

    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 1436, Column 94: start tag was here
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>
  • Error Line 1438, Column 115: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …llspacing="0" style="border-collapse: collapse" width="100%" bgcolor="#e4e4ee">

    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 1445, Column 93: required attribute "alt" not specified
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>

    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 1445, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>

    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 1445, Column 1: start tag was here
    <img border="0" src="http://www.centralmediaserver.com/transparent.gif" width="…
  • Error Line 1445, Column 98: end tag for "br" omitted, but OMITTAG NO was specified
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>

    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 1445, Column 94: start tag was here
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>
  • Error Line 1447, Column 115: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …llspacing="0" style="border-collapse: collapse" width="100%" bgcolor="#e4e4ee">

    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 1454, Column 93: required attribute "alt" not specified
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>

    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 1454, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>

    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 1454, Column 1: start tag was here
    <img border="0" src="http://www.centralmediaserver.com/transparent.gif" width="…
  • Error Line 1454, Column 98: end tag for "br" omitted, but OMITTAG NO was specified
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>

    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 1454, Column 94: start tag was here
    …c="http://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br>
  • Error Line 1456, Column 115: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …llspacing="0" style="border-collapse: collapse" width="100%" bgcolor="#e4e4ee">

    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 1463, Column 93: required attribute "alt" not specified
    …://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br></span>

    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 1463, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
    …://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br></span>

    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 1463, Column 1: start tag was here
    <img border="0" src="http://www.centralmediaserver.com/transparent.gif" width="…
  • Error Line 1463, Column 104: end tag for "br" omitted, but OMITTAG NO was specified
    …://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br></span>

    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 1463, Column 94: start tag was here
    …://www.centralmediaserver.com/transparent.gif" width="1" height="2"><br></span>
  • Error Line 1464, Column 82: required attribute "alt" not specified
    …g border="0" src="/sites/wsyr/images/transparent.gif" width="1" height="5"><br>

    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 1464, Column 83: end tag for "img" omitted, but OMITTAG NO was specified
    …g border="0" src="/sites/wsyr/images/transparent.gif" width="1" height="5"><br>

    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 1464, Column 5: start tag was here
        <img border="0" src="/sites/wsyr/images/transparent.gif" width="1" height="…
  • Error Line 1464, Column 87: end tag for "br" omitted, but OMITTAG NO was specified
    …g border="0" src="/sites/wsyr/images/transparent.gif" width="1" height="5"><br>

    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 1464, Column 83: start tag was here
    …g border="0" src="/sites/wsyr/images/transparent.gif" width="1" height="5"><br>
  • Error Line 1491, Column 157: required attribute "alt" not specified
    …img border="0" src="/sites/wsyr/images/traffic/traffic-caricon.jpg"></a></span>

    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 1491, Column 161: end tag for "img" omitted, but OMITTAG NO was specified
    …img border="0" src="/sites/wsyr/images/traffic/traffic-caricon.jpg"></a></span>

    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 1491, Column 89: start tag was here
    …x 0;"><a href="/traffic/default.aspx"><img border="0" src="/sites/wsyr/images/…
  • Error Line 1498, Column 159: required attribute "alt" not specified
    …g border="0" src="/sites/wsyr/images/traffic/traffic-videoicon.jpg"></a></span>

    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 1498, Column 163: end tag for "img" omitted, but OMITTAG NO was specified
    …g border="0" src="/sites/wsyr/images/traffic/traffic-videoicon.jpg"></a></span>

    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 1498, Column 89: start tag was here
    …x 0;"><a href="/traffic/default.aspx"><img border="0" src="/sites/wsyr/images/…
  • Error Line 1505, Column 162: required attribute "alt" not specified
    …g border="0" src="/sites/wsyr/images/traffic/traffic-alerticon.jpg"></a></span>

    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 1505, Column 166: end tag for "img" omitted, but OMITTAG NO was specified
    …g border="0" src="/sites/wsyr/images/traffic/traffic-alerticon.jpg"></a></span>

    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 1505, Column 92: start tag was here
    …0pt;"><a href="/traffic/default.aspx"><img border="0" src="/sites/wsyr/images/…
  • Error Line 1522, Column 7: required attribute "type" not specified
    <style>

    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 1522, Column 7: document type does not allow element "style" here
    <style>

    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 1542, Column 172: required attribute "alt" not specified
    …es/wsyr/images/transparent.gif" width="145" height="50" border="0" /></a></div>

    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 1545, Column 147: required attribute "alt" not specified
    …es/wsyr/images/transparent.gif" width="145" height="50" border="0" /></a></div>

    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 1552, Column 73: required attribute "type" not specified
    …29-b085-4328-a0db-f59aae57ce84"><style>.dopplerone {display: none !important;}…

    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 1552, Column 73: document type does not allow element "style" here
    …29-b085-4328-a0db-f59aae57ce84"><style>.dopplerone {display: none !important;}…

    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 1564, Column 49: required attribute "alt" not specified
    				Loading ... <img src="/images/spinner.gif" />

    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 1571, Column 142: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"
    …/files/cctvi_weather/conditions/38-white-md.jpg" align="absmiddle"/></div></td>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 1571, Column 144: required attribute "alt" not specified
    …/files/cctvi_weather/conditions/38-white-md.jpg" align="absmiddle"/></div></td>

    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 1579, Column 116: required attribute "alt" not specified
    …/media/files/cctvi_weather/wsyr/Radar_DMA/1157.jpg" width="295" /></a></center>

    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 1587, Column 94: required attribute "alt" not specified
    … width="14" src="http://www.centralmediaserver.com/wixt/videobullet-old.gif" />

    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 1615, Column 49: required attribute "alt" not specified
    				Loading ... <img src="/images/spinner.gif" />

    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 1622, Column 142: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"
    …/files/cctvi_weather/conditions/38-white-md.jpg" align="absmiddle"/></div></td>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 1622, Column 144: required attribute "alt" not specified
    …/files/cctvi_weather/conditions/38-white-md.jpg" align="absmiddle"/></div></td>

    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 1630, Column 122: required attribute "alt" not specified
    …/cctvi_weather/wsyr/daypart_planner/1828.jpg" width="295" /></a></center>      

    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 1651, Column 22: an attribute specification must start with a name or name token
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 1651, Column 22: element "scr" undefined
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1651, Column 128: character "<" is the first character of a delimiter but occurred as data
    …src="http://w11.localadbuy.com/banners/idm-ajtg.js"><' + '/' + 'scr' + 'ipt>');

    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 1653, Column 9: end tag for "scr" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 1651, Column 18: start tag was here
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…
  • Error Line 1684, Column 110: required attribute "alt" not specified
    …efault.aspx"><img src="/sites/wsyr/images/stayconnected/mobile.jpg" /></a></td>

    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 1685, Column 110: required attribute "alt" not specified
    …/default.aspx"><img src="/sites/wsyr/images/stayconnected/text.jpg" /></a></td>

    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 1686, Column 104: required attribute "alt" not specified
    …default.aspx"><img src="/sites/wsyr/images/stayconnected/email.jpg" /></a></td>

    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 1687, Column 118: required attribute "alt" not specified
    …sChannel9"><img src="/sites/wsyr/images/stayconnected/facebook.jpg" /></a></td>

    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 1688, Column 116: required attribute "alt" not specified
    …wsChannel9"><img src="/sites/wsyr/images/stayconnected/twitter.jpg" /></a></td>

    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 1689, Column 110: required attribute "alt" not specified
    …fault.aspx"><img src="/sites/wsyr/images/stayconnected/contact.jpg" /></a></td>

    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 1692, Column 105: required attribute "alt" not specified
    …efault.aspx"><img src="/sites/wsyr/images/stayconnected/videos.jpg" /></a></td>

    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 1693, Column 121: required attribute "alt" not specified
    ….aspx"><img src="/sites/wsyr/images/stayconnected/bridgestreet.jpg" /></a></td>

    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 1694, Column 111: required attribute "alt" not specified
    …photos.aspx"><img src="/sites/wsyr/images/stayconnected/photos.jpg" /></a></td>

    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 1695, Column 116: required attribute "alt" not specified
    …ault.aspx"><img src="/sites/wsyr/images/stayconnected/calendar.jpg" /></a></td>

    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 1696, Column 109: required attribute "alt" not specified
    …/default.aspx"><img src="/sites/wsyr/images/stayconnected/bios.jpg" /></a></td>

    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 1697, Column 102: required attribute "alt" not specified
    …s/default.aspx"><img src="/sites/wsyr/images/stayconnected/rss.jpg" /></a></td>

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

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

  • Warning Line 1722, Column 62: cannot generate system identifier for general entity "height"
    …nts.9wsyr.com/widget-loader?width=290&height=445" type="text/javascript" id="e…

    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 1722, Column 62: general entity "height" not defined and no default entity
    …nts.9wsyr.com/widget-loader?width=290&height=445" type="text/javascript" id="e…

    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 1722, Column 68: reference not terminated by REFC delimiter
    …syr.com/widget-loader?width=290&height=445" type="text/javascript" id="eventfu…

    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 1722, Column 68: reference to external entity in attribute value
    …syr.com/widget-loader?width=290&height=445" type="text/javascript" id="eventfu…

    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 1722, Column 68: reference to entity "height" for which no system identifier could be generated
    …syr.com/widget-loader?width=290&height=445" type="text/javascript" id="eventfu…

    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 1722, Column 61: entity was defined here
    …ents.9wsyr.com/widget-loader?width=290&height=445" type="text/javascript" id="…
  • Error Line 1734, Column 22: an attribute specification must start with a name or name token
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 1734, Column 22: element "scr" undefined
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1734, Column 128: character "<" is the first character of a delimiter but occurred as data
    …src="http://w11.localadbuy.com/banners/idm-ajtg.js"><' + '/' + 'scr' + 'ipt>');

    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 1736, Column 9: end tag for "scr" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 1734, Column 18: start tag was here
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…
  • Error Line 1745, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><table cellpadding="0" cellspacing="0" border="0">

    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 1745, Column 1: start tag was here
    <br><table cellpadding="0" cellspacing="0" border="0">
  • Error Line 1747, Column 125: end tag for "br" omitted, but OMITTAG NO was specified
    …file/WSYR-TV" target="_blank">Click here for WSYR-TV online Public File</a><br>

    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 1747, Column 121: start tag was here
    …file/WSYR-TV" target="_blank">Click here for WSYR-TV online Public File</a><br>
  • Error Line 1748, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 1748, Column 1: start tag was here
    <br>
  • Error Line 1751, Column 82: end tag for "br" omitted, but OMITTAG NO was specified
    …r content related issues or assistance for those with disabilities contact:<br>

    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 1751, Column 78: start tag was here
    …r content related issues or assistance for those with disabilities contact:<br>
  • Error Line 1762, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
    </tbody></table><br>

    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 1762, Column 17: start tag was here
    </tbody></table><br>
  • Error Line 1779, Column 22: an attribute specification must start with a name or name token
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 1779, Column 22: element "scr" undefined
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1779, Column 128: character "<" is the first character of a delimiter but occurred as data
    …src="http://w11.localadbuy.com/banners/idm-ajtg.js"><' + '/' + 'scr' + 'ipt>');

    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 1781, Column 9: end tag for "scr" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 1779, Column 18: start tag was here
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…
  • Error Line 1788, Column 172: end tag for "img" omitted, but OMITTAG NO was specified
    … alt="Inergize Digital" border="0"></a>  This site is hosted and managed by <a…

    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 1788, Column 61: start tag was here
    ….inergizedigital.com" target="_blank"><img src="/images/inergize_logo_copyrigh…
  • Error Line 1811, Column 128: required attribute "alt" not specified
    …ar___PoweredBy" src="/images/transparent.gif" style="border-width:0px;" /></td>

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

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

  • Warning Line 1861, Column 142: reference not terminated by REFC delimiter
    …dgestreetdiscountdeals.9wsyr.com/engine/Welcome.aspx?contestid=59881&LID=2558" 

    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 1861, Column 142: reference to external entity in attribute value
    …dgestreetdiscountdeals.9wsyr.com/engine/Welcome.aspx?contestid=59881&LID=2558" 

    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 1861, Column 142: reference to entity "LID" for which no system identifier could be generated
    …dgestreetdiscountdeals.9wsyr.com/engine/Welcome.aspx?contestid=59881&LID=2558" 

    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 541, Column 82: entity was defined here
    …dgestreetdiscountdeals.9wsyr.com/engine/Welcome.aspx?contestid=59881&LID=2585",
  • Warning Line 1865, Column 121: reference not terminated by REFC delimiter
    ….seekitlocal.com/default.aspx?l=Syracuse,+NY&market=555">Seek It Local</a></td>

    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 1865, Column 121: reference to external entity in attribute value
    ….seekitlocal.com/default.aspx?l=Syracuse,+NY&market=555">Seek It Local</a></td>

    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 1865, Column 121: reference to entity "market" for which no system identifier could be generated
    ….seekitlocal.com/default.aspx?l=Syracuse,+NY&market=555">Seek It Local</a></td>

    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 543, Column 59: entity was defined here
    	"http://www.seekitlocal.com/default.aspx?l=Syracuse%2c+NY&market=555");
  • Error Line 1999, Column 90: required attribute "alt" not specified
    …	<td valign="top"><img src="/sites/wsyr/content/legal/nexstar_logo.png" /></td>

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

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

  • Warning Line 2010, Column 215: character "&" is the first character of a delimiter but occurred as data
    …> | <a href="/content/legal/default.aspx">Copyright & Trademark Notice</a></td>

    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 2022, Column 22: an attribute specification must start with a name or name token
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 2022, Column 22: element "scr" undefined
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 2022, Column 128: character "<" is the first character of a delimiter but occurred as data
    …src="http://w11.localadbuy.com/banners/idm-ajtg.js"><' + '/' + 'scr' + 'ipt>');

    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 2024, Column 9: end tag for "scr" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 2022, Column 18: start tag was here
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…
  • Error Line 2050, Column 22: an attribute specification must start with a name or name token
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 2050, Column 22: element "scr" undefined
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 2050, Column 128: character "<" is the first character of a delimiter but occurred as data
    …src="http://w11.localadbuy.com/banners/idm-ajtg.js"><' + '/' + 'scr' + 'ipt>');

    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 2052, Column 9: end tag for "scr" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 2050, Column 18: start tag was here
    	document.write('<scr' + 'ipt type="text/javascript" language="JavaScript" src=…

Visitor Analysis

Daily Visitor
  • 2.917 visits