atlanticbb.net has Alexa Rank 55.171 and Google Page Rank is 4

atlanticbb.net
  • Domain Name
    atlanticbb.net
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #55171
  • Page Size
    139.3 KB
  • Ip Address
    64.8.70.102
  • Heading
    H1: 1, H2: 22, H3: 0, H4: 21, H5: 0, H6: 0
  • Images
    0 GIF, 3 JPG, 4 PNG

Website Meta Analysis

  • Title
    Home - Welcome to Atlantic Broadband
  • Meta Keyword
  • Meta Description

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    64.8.70.102
  • Domain Age
    10 Years, 0 Months, 12 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from atlanticbb.net.

HTML Analysis

  • server: nginx
  • date: Mon, 30 Sep 2013 21:05:32 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • cache-control: no-cache, must-revalidate
  • pragma: no-cache
  • p3p: CP="ALL DSP COR TAIa PSAa PSDa IVAa IVDa CONi OUR IND UNI"
  • x-varnish: 243080600
  • age: 0
  • via: 1.1 varnish
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
Registrant:
Atlantic Broadband FInance LLC
1 Batterymarch Park, Atlantic Broadband
Ste 405
Quincy, MA 02169
US
Domain Name: ATLANTICBB.NET

Administrative Contact:
Shea, Rich email
1 Batterymarch Park, Atlantic Broadband
Ste 405
Quincy, MA 02169
US
617 786-8800 x103
Technical Contact:
www.123cheapdomains.com - -, Domain Registrations - email
1032 Irving Street, # 603
Renew / Manage domain at 123CHEAPDOMAINS.COM - Keep for memo
For support, please send email to: email
San Francisco, Ca 94122
US
1-415-682-3859

Registrar: TUCOWS, INC.
Updated: 30-Jun-2011.
Expires: 11-Sep-2012.
Created: 11-Sep-2003.
Name Servers:
NS2.ECHOLABS.NET
NS02.ATLANTICBB.NET 207.255.96.20
NS01.ATLANTICBB.NET 207.255.0.72
NS1.ECHOLABS.NET

Domain Status: ok

DNS Analysis


DNS servers
ns1.echolabs.net [216.52.118.211]
ns2.echolabs.net [216.52.118.212]
ns02.atlanticbb.net [207.255.96.20]
ns01.atlanticbb.net [207.255.0.72]


DNS Records

Answer records
atlanticbb.net SOA
server: ns01.atlanticbb.net
email: dnsadmin@atlanticbb.net
serial: 2013021300
refresh: 1800
retry: 600
expire: 604800
minimum ttl: 3600
300s
atlanticbb.net A 64.8.70.102 300s
atlanticbb.net MX
preference: 0
exchange: mail.atlanticbb.net
300s
atlanticbb.net TXT v=spf1 ip4:216.52.118.192/26 ip4:38.111.141.0/24 a mx ptr ?all 300s
atlanticbb.net NS  ns2.echolabs.net 300s
atlanticbb.net NS  ns02.atlanticbb.net 300s
atlanticbb.net NS  ns01.atlanticbb.net 300s
atlanticbb.net NS  ns1.echolabs.net 300s

Authority records

Additional records
mail.atlanticbb.net A 38.111.141.32 300s
ns01.atlanticbb.net A 207.255.0.72 300s
ns02.atlanticbb.net A 207.255.96.20 300s

IP 64.8.70.102 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 233 Errors
  • 252 Warnings
Ratio Text/Html
  • 0.5499179603685473
Message Error
  • Warning Line 36, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 36, Column 40: cannot generate system identifier for general entity "Syn.ComponentMgr"
    …script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 36, Column 40: general entity "Syn.ComponentMgr" not defined and no default entity
    …script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 36, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 61, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 61, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 61, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Error Line 70, Column 73: there is no attribute "alt"
    …s="on"><a href="http://atlanticbb.net/index.php?tab=Web" alt="Web">Web</a></li>

    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 77, Column 77: there is no attribute "target"
    …rm class="s_input web_q" action="/search/index.php" method="get" target="_top">

    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 95, Column 41: cannot generate system identifier for general entity "context"
    …pan>1. <a href="/search/?q=Weekly+Ads&context=topsearches">Weekly Ads</a></spa…

    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 95, Column 41: general entity "context" not defined and no default entity
    …pan>1. <a href="/search/?q=Weekly+Ads&context=topsearches">Weekly Ads</a></spa…

    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 95, Column 48: reference not terminated by REFC delimiter
    …an>1. <a href="/search/?q=Weekly+Ads&context=topsearches">Weekly Ads</a></span>

    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 95, Column 48: reference to external entity in attribute value
    …an>1. <a href="/search/?q=Weekly+Ads&context=topsearches">Weekly Ads</a></span>

    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 95, Column 48: reference to entity "context" for which no system identifier could be generated
    …an>1. <a href="/search/?q=Weekly+Ads&context=topsearches">Weekly Ads</a></span>

    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 95, Column 40: entity was defined here
    …span>1. <a href="/search/?q=Weekly+Ads&context=topsearches">Weekly Ads</a></sp…
  • Warning Line 97, Column 51: reference not terminated by REFC delimiter
    …<a href="/search/?q=Credit+Repair&context=topsearches">Credit Repair</a></span>

    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 97, Column 51: reference to external entity in attribute value
    …<a href="/search/?q=Credit+Repair&context=topsearches">Credit Repair</a></span>

    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 97, Column 51: reference to entity "context" for which no system identifier could be generated
    …<a href="/search/?q=Credit+Repair&context=topsearches">Credit Repair</a></span>

    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 95, Column 40: entity was defined here
    …span>1. <a href="/search/?q=Weekly+Ads&context=topsearches">Weekly Ads</a></sp…
  • Warning Line 99, Column 51: reference not terminated by REFC delimiter
    …<a href="/search/?q=Pope+Blessing&context=topsearches">Pope Blessing</a></span>

    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 99, Column 51: reference to external entity in attribute value
    …<a href="/search/?q=Pope+Blessing&context=topsearches">Pope Blessing</a></span>

    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 99, Column 51: reference to entity "context" for which no system identifier could be generated
    …<a href="/search/?q=Pope+Blessing&context=topsearches">Pope Blessing</a></span>

    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 95, Column 40: entity was defined here
    …span>1. <a href="/search/?q=Weekly+Ads&context=topsearches">Weekly Ads</a></sp…
  • Warning Line 108, Column 44: character "&" is the first character of a delimiter but occurred as data
    …><script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.ins…

    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 108, Column 62: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 108, Column 62: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Error Line 206, Column 74: there is no attribute "target"
    …//api.nextag.com/serv/ABBISP/buyer/Home.jsp"  target="_blank" class="nav_shop">

    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 229, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 229, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 229, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 229, Column 579: character "&" is the first character of a delimiter but occurred as data
    …><script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.ins…

    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 229, Column 597: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 229, Column 597: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 231, Column 214: character "&" is the first character of a delimiter but occurred as data
    …><script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.ins…

    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 231, Column 232: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 231, Column 232: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 248, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 248, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 248, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 249, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 249, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 249, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Error Line 263, Column 13: value of attribute "id" invalid: "3" cannot start a name
    			<div id="371d75a32b408ec8c261e7378c7a2194_zone-3a-2f-2fSynacor-2fPortal-2fPa…

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

  • Error Line 268, Column 205: syntax of attribute value does not conform to declared value
    …I nightclub fire 10 years later" rel="" title="100 nightclub fire victims reme…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 271, Column 129: syntax of attribute value does not conform to declared value
    …%3E&amp;ps=1011" alt="" class="" rel="">100 nightclub fire victims remembered …

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 281, Column 204: syntax of attribute value does not conform to declared value
    …;#039;s, but no damage reported" rel="" title="Videos capture exploding meteor…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 284, Column 132: syntax of attribute value does not conform to declared value
    …446/" alt="" class="dcc_vidicon" rel="">Videos capture exploding meteor</a></h…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 292, Column 213: syntax of attribute value does not conform to declared value
    …p;#039;s speech on gun violence" rel="" title="Obama gun speech attendee&#039;…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 295, Column 129: syntax of attribute value does not conform to declared value
    …g%3E&amp;ps=931" alt="" class="" rel="">Obama gun speech attendee&#039;s siste…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 305, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 305, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 305, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 305, Column 308: cannot generate system identifier for general entity "content_id"
    …/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_i…

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

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

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

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

  • Error Line 305, Column 308: general entity "content_id" not defined and no default entity
    …/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_i…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 305, Column 318: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_id":"compon…

    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 305, Column 318: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_id":"compon…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 312, Column 127: syntax of attribute value does not conform to declared value
    …psearches&amp;source=DCC" alt="" rel="" title="Hot Searches: What are the most…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 315, Column 142: syntax of attribute value does not conform to declared value
    …&amp;source=DCC" alt="" class="" rel="">Hot Searches: What are the most common…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 325, Column 132: syntax of attribute value does not conform to declared value
    …psearches&amp;source=DCC" alt="" rel="" title="What does cancer do to your bod…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 328, Column 147: syntax of attribute value does not conform to declared value
    …&amp;source=DCC" alt="" class="" rel="">What does cancer do to your body?</a><…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 336, Column 125: syntax of attribute value does not conform to declared value
    …psearches&amp;source=DCC" alt="" rel="" title="Learn more about the symptoms o…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 339, Column 140: syntax of attribute value does not conform to declared value
    …&amp;source=DCC" alt="" class="" rel="">Learn more about the symptoms of cance…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 349, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 349, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 349, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 349, Column 326: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=hot_searches","parent_uri":null,"event_…

    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 349, Column 326: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=hot_searches","parent_uri":null,"event_…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 351, Column 13: value of attribute "id" invalid: "7" cannot start a name
    			<div id="78195e6bc079010609430475f583eaba_zone-3a-2f-2fSynacor-2fPortal-2fPa…

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

  • Error Line 357, Column 154: syntax of attribute value does not conform to declared value
    …894/" alt="" class="dcc_vidicon" rel="">LeAnn Rimes involved in lawsuit</a></s…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 367, Column 161: syntax of attribute value does not conform to declared value
    …463/" alt="" class="dcc_vidicon" rel="">Forest Whitaker accused of shoplifting…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 378, Column 35: syntax of attribute value does not conform to declared value
    " alt="" class="dcc_vidicon" rel="">Miley opens up about love life</a></span>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 387, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 387, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 387, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 387, Column 327: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=2","parent_uri":null,"event_id":"compon…

    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 387, Column 327: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=2","parent_uri":null,"event_id":"compon…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 392, Column 13: value of attribute "id" invalid: "9" cannot start a name
    			<div id="9663d04bf455beb2086a98eda5a44d17_zone-3a-2f-2fSynacor-2fPortal-2fPa…

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

  • Error Line 398, Column 160: syntax of attribute value does not conform to declared value
    …9281" alt="" class="dcc_vidicon" rel="">Man hits baby, uses racial slur on pla…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 408, Column 151: syntax of attribute value does not conform to declared value
    …350/" alt="" class="dcc_vidicon" rel="">Man claims to have second Mona Lisa</a…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 418, Column 149: syntax of attribute value does not conform to declared value
    …%3E&amp;ps=1012" alt="" class="" rel="">Masked intruders raid gold company</a>…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 426, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 426, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 426, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 426, Column 326: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=3","parent_uri":null,"event_id":"compon…

    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 426, Column 326: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=3","parent_uri":null,"event_id":"compon…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 428, Column 13: value of attribute "id" invalid: "2" cannot start a name
    			<div id="2262bae1b24618bb7b9f86f339d997c0_zone-3a-2f-2fSynacor-2fPortal-2fPa…

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

  • Error Line 433, Column 209: syntax of attribute value does not conform to declared value
    …39;s season-opening Daytona 500" rel="" title="Danica Patrick makes Sprint Cup…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 436, Column 125: syntax of attribute value does not conform to declared value
    …%3E&amp;ps=1013" alt="" class="" rel="">Danica Patrick makes Sprint Cup histor…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 446, Column 230: syntax of attribute value does not conform to declared value
    …p;#039;serious charge&amp;#039;" rel="" title="Pistorius&#039; agent cancels f…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 449, Column 126: syntax of attribute value does not conform to declared value
    …%3E&amp;ps=1013" alt="" class="" rel="">Pistorius&#039; agent cancels future r…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 457, Column 185: syntax of attribute value does not conform to declared value
    …s for DUI arrest, vows to learn" rel="" title="Rockies&#039; Todd Helton sorry…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 460, Column 126: syntax of attribute value does not conform to declared value
    …%3E&amp;ps=1013" alt="" class="" rel="">Rockies&#039; Todd Helton sorry for DU…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 470, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 470, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 470, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 470, Column 320: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=4","parent_uri":null,"event_id":"compon…

    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 470, Column 320: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=4","parent_uri":null,"event_id":"compon…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 477, Column 101: syntax of attribute value does not conform to declared value
    …/hulu/asset/syn_35230604" alt="" rel="" title="The pressure builds as hometown…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 480, Column 127: syntax of attribute value does not conform to declared value
    …0604" alt="" class="dcc_vidicon" rel="">The pressure builds as hometown dates …

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 490, Column 102: syntax of attribute value does not conform to declared value
    …/hulu/asset/syn_35230533" alt="" rel="" title="Secret identities are revealed …

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 493, Column 128: syntax of attribute value does not conform to declared value
    …0533" alt="" class="dcc_vidicon" rel="">Secret identities are revealed on &#03…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 501, Column 105: syntax of attribute value does not conform to declared value
    …/hulu/asset/syn_35213793" alt="" rel="" title="&#039;The Carrie Diaries&#039; …

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 504, Column 131: syntax of attribute value does not conform to declared value
    …3793" alt="" class="dcc_vidicon" rel="">&#039;The Carrie Diaries&#039; go to a…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 514, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 514, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 514, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 514, Column 322: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=VAM_THREE_WATCH_TV","parent_uri":null,"…

    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 514, Column 322: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=VAM_THREE_WATCH_TV","parent_uri":null,"…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 516, Column 13: value of attribute "id" invalid: "8" cannot start a name
    			<div id="87165cec7cad098ab7e8409e8ca64b1f_zone-3a-2f-2fSynacor-2fPortal-2fPa…

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

  • Warning Line 526, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 526, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 526, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 526, Column 328: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=synacor_promo_1","parent_uri":null,"eve…

    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 526, Column 328: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=synacor_promo_1","parent_uri":null,"eve…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 528, Column 13: value of attribute "id" invalid: "7" cannot start a name
    			<div id="7dc31f7d485ecfeaa8beee979a22c4d4_zone-3a-2f-2fSynacor-2fPortal-2fPa…

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

  • Warning Line 562, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 562, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 562, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 562, Column 324: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=todays_deals_2","parent_uri":null,"even…

    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 562, Column 324: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=todays_deals_2","parent_uri":null,"even…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 571, Column 17: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3d1" already defined
    							<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 264, Column 14: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3d1" first defined here
    				<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEd…
  • Error Line 571, Column 138: there is no attribute "rel"
    …king_area-3ddcc-26content_id-3d1" rel="component://Synacor/Portal/Components/D…

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

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

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

  • Warning Line 574, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 574, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 574, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 574, Column 237: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_id":"compon…

    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 574, Column 237: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_id":"compon…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 578, Column 17: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3dhot_searches" already defined
    							<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 308, Column 14: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3dhot_searches" first defined here
    				<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEd…
  • Warning Line 581, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 581, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 581, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 581, Column 237: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=hot_searches","parent_uri":null,"event_…

    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 581, Column 237: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=hot_searches","parent_uri":null,"event_…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 584, Column 17: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3d2" already defined
    							<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 352, Column 14: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3d2" first defined here
    				<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEd…
  • Warning Line 587, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 587, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 587, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 587, Column 237: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=2","parent_uri":null,"event_id":"compon…

    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 587, Column 237: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=2","parent_uri":null,"event_id":"compon…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 595, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 595, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 595, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Error Line 598, Column 17: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3d3" already defined
    							<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 393, Column 14: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3d3" first defined here
    				<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEd…
  • Warning Line 601, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 601, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 601, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 601, Column 237: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=3","parent_uri":null,"event_id":"compon…

    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 601, Column 237: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=3","parent_uri":null,"event_id":"compon…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 604, Column 17: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3d4" already defined
    							<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 429, Column 14: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3d4" first defined here
    				<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEd…
  • Warning Line 607, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 607, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 607, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 607, Column 237: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=4","parent_uri":null,"event_id":"compon…

    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 607, Column 237: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=4","parent_uri":null,"event_id":"compon…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 610, Column 17: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3dVAM_THREE_WATCH_TV" already defined
    							<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 473, Column 14: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3dVAM_THREE_WATCH_TV" first defined here
    				<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEd…
  • Warning Line 613, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 613, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 613, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 613, Column 237: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=VAM_THREE_WATCH_TV","parent_uri":null,"…

    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 613, Column 237: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=VAM_THREE_WATCH_TV","parent_uri":null,"…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 616, Column 17: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3dsynacor_promo_1" already defined
    							<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 517, Column 14: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3dsynacor_promo_1" first defined here
    				<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEd…
  • Warning Line 619, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 619, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 619, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 619, Column 237: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=synacor_promo_1","parent_uri":null,"eve…

    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 619, Column 237: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=synacor_promo_1","parent_uri":null,"eve…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 622, Column 17: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3dtodays_deals_2" already defined
    							<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 529, Column 14: ID "component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEditorial-2f-3ftracking_area-3ddcc-26content_id-3dtodays_deals_2" first defined here
    				<div id="component-3a-2f-2fSynacor-2fPortal-2fComponents-2fDcc-2fSlide-2fEd…
  • Warning Line 625, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 625, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 625, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 625, Column 237: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=todays_deals_2","parent_uri":null,"even…

    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 625, Column 237: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=todays_deals_2","parent_uri":null,"even…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 640, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 640, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 640, Column 229: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=1":{"uri":"component:\/\/Synacor\/Porta…

    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 640, Column 229: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=1":{"uri":"component:\/\/Synacor\/Porta…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 336: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=1","hash":"371d75a32b408ec8c261e7378c7a…

    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 640, Column 336: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=1","hash":"371d75a32b408ec8c261e7378c7a…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 544: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=hot_searches":{"uri":"component:\/\/Syn…

    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 640, Column 544: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=hot_searches":{"uri":"component:\/\/Syn…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 662: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=hot_searches","hash":"db2ee0c09867789f1…

    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 640, Column 662: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=hot_searches","hash":"db2ee0c09867789f1…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 881: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=2":{"uri":"component:\/\/Synacor\/Porta…

    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 640, Column 881: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=2":{"uri":"component:\/\/Synacor\/Porta…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 988: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=2","hash":"78195e6bc079010609430475f583…

    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 640, Column 988: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=2","hash":"78195e6bc079010609430475f583…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 1509: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=3":{"uri":"component:\/\/Synacor\/Porta…

    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 640, Column 1509: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=3":{"uri":"component:\/\/Synacor\/Porta…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 1616: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=3","hash":"9663d04bf455beb2086a98eda5a4…

    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 640, Column 1616: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=3","hash":"9663d04bf455beb2086a98eda5a4…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 1824: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=4":{"uri":"component:\/\/Synacor\/Porta…

    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 640, Column 1824: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=4":{"uri":"component:\/\/Synacor\/Porta…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 1931: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=4","hash":"2262bae1b24618bb7b9f86f339d9…

    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 640, Column 1931: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=4","hash":"2262bae1b24618bb7b9f86f339d9…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 2139: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=VAM_THREE_WATCH_TV":{"uri":"component:\…

    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 640, Column 2139: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=VAM_THREE_WATCH_TV":{"uri":"component:\…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 2263: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=VAM_THREE_WATCH_TV","hash":"b5fcf2bfecf…

    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 640, Column 2263: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=VAM_THREE_WATCH_TV","hash":"b5fcf2bfecf…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 2488: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=synacor_promo_1":{"uri":"component:\/\/…

    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 640, Column 2488: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=synacor_promo_1":{"uri":"component:\/\/…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 2609: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=synacor_promo_1","hash":"87165cec7cad09…

    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 640, Column 2609: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=synacor_promo_1","hash":"87165cec7cad09…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 2831: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=todays_deals_2":{"uri":"component:\/\/S…

    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 640, Column 2831: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=todays_deals_2":{"uri":"component:\/\/S…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 2951: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=todays_deals_2","hash":"7dc31f7d485ecfe…

    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 640, Column 2951: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=todays_deals_2","hash":"7dc31f7d485ecfe…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 640, Column 3205: reference not terminated by REFC delimiter
    …itorial\/?tracking_area=dcc&content_id=1","starting_slide_index":0,"autoplay":…

    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 640, Column 3205: reference to entity "content_id" for which no system identifier could be generated
    …itorial\/?tracking_area=dcc&content_id=1","starting_slide_index":0,"autoplay":…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Error Line 689, Column 744: document type does not allow element "pre" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …er Green)"><pre class="scroll_loader" ><!-- <img src="http://web.synacor.com/a…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 751, Column 10: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    						<li><a href="http://atlanticbb.net/news/political.php" alt="">Political</…

    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 755, Column 23: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    						<li class="last"><a href="http://atlanticbb.net/news/entertainment.php" a…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 758, Column 8: end tag for "li" omitted, but OMITTAG NO was specified
    			</ul>

    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 755, Column 7: start tag was here
    						<li class="last"><a href="http://atlanticbb.net/news/entertainment.php" a…
  • Error Line 758, Column 8: end tag for "li" omitted, but OMITTAG NO was specified
    			</ul>

    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 751, Column 7: start tag was here
    						<li><a href="http://atlanticbb.net/news/political.php" alt="">Political</…
  • Error Line 758, Column 8: end tag for "li" omitted, but OMITTAG NO was specified
    			</ul>

    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 747, Column 7: start tag was here
    						<li><a href="http://atlanticbb.net/news/world.php" alt="">World</a>
  • Warning Line 764, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 764, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 764, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 769, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 769, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 769, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Error Line 786, Column 9: end tag for element "th" which is not open
    				</th>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 797, Column 102: cannot generate system identifier for general entity "Ticker"
    …x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=DJ:DJI">

    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 797, Column 102: general entity "Ticker" not defined and no default entity
    …x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=DJ:DJI">

    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 797, Column 108: reference not terminated by REFC delimiter
    …x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=DJ:DJI">

    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 797, Column 108: reference to external entity in attribute value
    …x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=DJ:DJI">

    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 797, Column 108: reference to entity "Ticker" for which no system identifier could be generated
    …x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=DJ:DJI">

    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 797, Column 101: entity was defined here
    …x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=DJ:DJI">
  • Warning Line 809, Column 108: reference not terminated by REFC delimiter
    …t/x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=$SPX">

    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 108: reference to external entity in attribute value
    …t/x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=$SPX">

    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 108: reference to entity "Ticker" for which no system identifier could be generated
    …t/x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=$SPX">

    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 797, Column 101: entity was defined here
    …x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=DJ:DJI">
  • Warning Line 821, Column 108: reference not terminated by REFC delimiter
    …/x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=$COMP">

    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 821, Column 108: reference to external entity in attribute value
    …/x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=$COMP">

    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 821, Column 108: reference to entity "Ticker" for which no system identifier could be generated
    …/x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=$COMP">

    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 797, Column 101: entity was defined here
    …x.php?u=http://studio-5.financialcontent.com/synacor?Page=QUOTE&Ticker=DJ:DJI">
  • Error Line 839, Column 197: duplicate specification of attribute "class"
    …ponent-3a-2f-2fSynacor-2fPortal-2fComponents-2fMarketwatch-2f" class="current">

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

  • Error Line 875, Column 154: required attribute "action" not specified
    …-2fLeft-2f-7ccomponent-3a-2f-2fSynacor-2fPortal-2fComponents-2fMarketwatch-2f">

    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 946, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 946, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 946, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 970, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 970, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 970, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 970, Column 273: reference not terminated by REFC delimiter
    …/?tracking_area=watercooler&content_id=WC_1&position=1","parent_uri":null,"eve…

    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 970, Column 273: reference to entity "content_id" for which no system identifier could be generated
    …/?tracking_area=watercooler&content_id=WC_1&position=1","parent_uri":null,"eve…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 970, Column 279: cannot generate system identifier for general entity "position"
    …king_area=watercooler&content_id=WC_1&position=1","parent_uri":null,"event_id"…

    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 970, Column 279: general entity "position" not defined and no default entity
    …king_area=watercooler&content_id=WC_1&position=1","parent_uri":null,"event_id"…

    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 970, Column 287: reference not terminated by REFC delimiter
    …a=watercooler&content_id=WC_1&position=1","parent_uri":null,"event_id":"compon…

    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 970, Column 287: reference to entity "position" for which no system identifier could be generated
    …a=watercooler&content_id=WC_1&position=1","parent_uri":null,"event_id":"compon…

    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 970, Column 278: entity was defined here
    …cking_area=watercooler&content_id=WC_1&position=1","parent_uri":null,"event_id…
  • Warning Line 977, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 977, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 977, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 977, Column 273: reference not terminated by REFC delimiter
    …/?tracking_area=watercooler&content_id=WC_2&position=2","parent_uri":null,"eve…

    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 977, Column 273: reference to entity "content_id" for which no system identifier could be generated
    …/?tracking_area=watercooler&content_id=WC_2&position=2","parent_uri":null,"eve…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 977, Column 287: reference not terminated by REFC delimiter
    …a=watercooler&content_id=WC_2&position=2","parent_uri":null,"event_id":"compon…

    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 977, Column 287: reference to entity "position" for which no system identifier could be generated
    …a=watercooler&content_id=WC_2&position=2","parent_uri":null,"event_id":"compon…

    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 970, Column 278: entity was defined here
    …cking_area=watercooler&content_id=WC_1&position=1","parent_uri":null,"event_id…
  • Warning Line 987, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 987, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 987, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 987, Column 273: reference not terminated by REFC delimiter
    …/?tracking_area=watercooler&content_id=WC_3&position=3","parent_uri":null,"eve…

    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 987, Column 273: reference to entity "content_id" for which no system identifier could be generated
    …/?tracking_area=watercooler&content_id=WC_3&position=3","parent_uri":null,"eve…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 987, Column 287: reference not terminated by REFC delimiter
    …a=watercooler&content_id=WC_3&position=3","parent_uri":null,"event_id":"compon…

    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 987, Column 287: reference to entity "position" for which no system identifier could be generated
    …a=watercooler&content_id=WC_3&position=3","parent_uri":null,"event_id":"compon…

    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 970, Column 278: entity was defined here
    …cking_area=watercooler&content_id=WC_1&position=1","parent_uri":null,"event_id…
  • Warning Line 994, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 994, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 994, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 994, Column 273: reference not terminated by REFC delimiter
    …/?tracking_area=watercooler&content_id=WC_4&position=4","parent_uri":null,"eve…

    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 994, Column 273: reference to entity "content_id" for which no system identifier could be generated
    …/?tracking_area=watercooler&content_id=WC_4&position=4","parent_uri":null,"eve…

    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 305, Column 307: entity was defined here
    …\/Slide\/Editorial\/?tracking_area=dcc&content_id=1","parent_uri":null,"event_…
  • Warning Line 994, Column 287: reference not terminated by REFC delimiter
    …a=watercooler&content_id=WC_4&position=4","parent_uri":null,"event_id":"compon…

    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 994, Column 287: reference to entity "position" for which no system identifier could be generated
    …a=watercooler&content_id=WC_4&position=4","parent_uri":null,"event_id":"compon…

    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 970, Column 278: entity was defined here
    …cking_area=watercooler&content_id=WC_1&position=1","parent_uri":null,"event_id…
  • Warning Line 1004, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1004, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1004, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 1015, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1015, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1015, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 1015, Column 187: cannot generate system identifier for general entity "width"
    …n.com\/Scripts\/PlayerSeed.js?sid=825&width=300&height=260&colorPallet=#FFEB00…

    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 1015, Column 187: general entity "width" not defined and no default entity
    …n.com\/Scripts\/PlayerSeed.js?sid=825&width=300&height=260&colorPallet=#FFEB00…

    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 1015, Column 192: reference not terminated by REFC delimiter
    …\/Scripts\/PlayerSeed.js?sid=825&width=300&height=260&colorPallet=#FFEB00&rela…

    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 1015, Column 192: reference to entity "width" for which no system identifier could be generated
    …\/Scripts\/PlayerSeed.js?sid=825&width=300&height=260&colorPallet=#FFEB00&rela…

    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 1015, Column 186: entity was defined here
    …in.com\/Scripts\/PlayerSeed.js?sid=825&width=300&height=260&colorPallet=#FFEB0…
  • Warning Line 1015, Column 197: cannot generate system identifier for general entity "height"
    …ipts\/PlayerSeed.js?sid=825&width=300&height=260&colorPallet=#FFEB00&relatedBo…

    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 1015, Column 197: general entity "height" not defined and no default entity
    …ipts\/PlayerSeed.js?sid=825&width=300&height=260&colorPallet=#FFEB00&relatedBo…

    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 1015, Column 203: reference not terminated by REFC delimiter
    …PlayerSeed.js?sid=825&width=300&height=260&colorPallet=#FFEB00&relatedBottomHe…

    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 1015, Column 203: reference to entity "height" for which no system identifier could be generated
    …PlayerSeed.js?sid=825&width=300&height=260&colorPallet=#FFEB00&relatedBottomHe…

    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 1015, Column 196: entity was defined here
    …ripts\/PlayerSeed.js?sid=825&width=300&height=260&colorPallet=#FFEB00&relatedB…
  • Warning Line 1015, Column 208: cannot generate system identifier for general entity "colorPallet"
    …rSeed.js?sid=825&width=300&height=260&colorPallet=#FFEB00&relatedBottomHeight=…

    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 1015, Column 208: general entity "colorPallet" not defined and no default entity
    …rSeed.js?sid=825&width=300&height=260&colorPallet=#FFEB00&relatedBottomHeight=…

    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 1015, Column 219: reference not terminated by REFC delimiter
    …d=825&width=300&height=260&colorPallet=#FFEB00&relatedBottomHeight=60&hasCompa…

    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 1015, Column 219: reference to entity "colorPallet" for which no system identifier could be generated
    …d=825&width=300&height=260&colorPallet=#FFEB00&relatedBottomHeight=60&hasCompa…

    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 1015, Column 207: entity was defined here
    …erSeed.js?sid=825&width=300&height=260&colorPallet=#FFEB00&relatedBottomHeight…
  • Warning Line 1015, Column 228: cannot generate system identifier for general entity "relatedBottomHeight"
    …th=300&height=260&colorPallet=#FFEB00&relatedBottomHeight=60&hasCompanion=true…

    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 1015, Column 228: general entity "relatedBottomHeight" not defined and no default entity
    …th=300&height=260&colorPallet=#FFEB00&relatedBottomHeight=60&hasCompanion=true…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 1015, Column 247: reference not terminated by REFC delimiter
    …olorPallet=#FFEB00&relatedBottomHeight=60&hasCompanion=true&companionPos=botto…

    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 1015, Column 247: reference to entity "relatedBottomHeight" for which no system identifier could be generated
    …olorPallet=#FFEB00&relatedBottomHeight=60&hasCompanion=true&companionPos=botto…

    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 1015, Column 227: entity was defined here
    …dth=300&height=260&colorPallet=#FFEB00&relatedBottomHeight=60&hasCompanion=tru…
  • Warning Line 1015, Column 251: cannot generate system identifier for general entity "hasCompanion"
    …Pallet=#FFEB00&relatedBottomHeight=60&hasCompanion=true&companionPos=bottom&pl…

    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 1015, Column 251: general entity "hasCompanion" not defined and no default entity
    …Pallet=#FFEB00&relatedBottomHeight=60&hasCompanion=true&companionPos=bottom&pl…

    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 1015, Column 263: reference not terminated by REFC delimiter
    …00&relatedBottomHeight=60&hasCompanion=true&companionPos=bottom&playerActions=…

    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 1015, Column 263: reference to entity "hasCompanion" for which no system identifier could be generated
    …00&relatedBottomHeight=60&hasCompanion=true&companionPos=bottom&playerActions=…

    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 1015, Column 250: entity was defined here
    …rPallet=#FFEB00&relatedBottomHeight=60&hasCompanion=true&companionPos=bottom&p…
  • Warning Line 1015, Column 269: cannot generate system identifier for general entity "companionPos"
    …atedBottomHeight=60&hasCompanion=true&companionPos=bottom&playerActions=696&re…

    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 1015, Column 269: general entity "companionPos" not defined and no default entity
    …atedBottomHeight=60&hasCompanion=true&companionPos=bottom&playerActions=696&re…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 1015, Column 281: reference not terminated by REFC delimiter
    …ight=60&hasCompanion=true&companionPos=bottom&playerActions=696&relatedMode=2&…

    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 1015, Column 281: reference to entity "companionPos" for which no system identifier could be generated
    …ight=60&hasCompanion=true&companionPos=bottom&playerActions=696&relatedMode=2&…

    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 1015, Column 268: entity was defined here
    …latedBottomHeight=60&hasCompanion=true&companionPos=bottom&playerActions=696&r…
  • Warning Line 1015, Column 289: cannot generate system identifier for general entity "playerActions"
    …hasCompanion=true&companionPos=bottom&playerActions=696&relatedMode=2&videoCon…

    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 1015, Column 289: general entity "playerActions" not defined and no default entity
    …hasCompanion=true&companionPos=bottom&playerActions=696&relatedMode=2&videoCon…

    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 1015, Column 302: reference not terminated by REFC delimiter
    …true&companionPos=bottom&playerActions=696&relatedMode=2&videoControlDisplayCo…

    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 1015, Column 302: reference to entity "playerActions" for which no system identifier could be generated
    …true&companionPos=bottom&playerActions=696&relatedMode=2&videoControlDisplayCo…

    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 1015, Column 288: entity was defined here
    …&hasCompanion=true&companionPos=bottom&playerActions=696&relatedMode=2&videoCo…
  • Warning Line 1015, Column 307: cannot generate system identifier for general entity "relatedMode"
    …companionPos=bottom&playerActions=696&relatedMode=2&videoControlDisplayColor=#…

    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 1015, Column 307: general entity "relatedMode" not defined and no default entity
    …companionPos=bottom&playerActions=696&relatedMode=2&videoControlDisplayColor=#…

    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 1015, Column 318: reference not terminated by REFC delimiter
    …s=bottom&playerActions=696&relatedMode=2&videoControlDisplayColor=#191919&sequ…

    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 1015, Column 318: reference to entity "relatedMode" for which no system identifier could be generated
    …s=bottom&playerActions=696&relatedMode=2&videoControlDisplayColor=#191919&sequ…

    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 1015, Column 306: entity was defined here
    …&companionPos=bottom&playerActions=696&relatedMode=2&videoControlDisplayColor=…
  • Warning Line 1015, Column 321: cannot generate system identifier for general entity "videoControlDisplayColor"
    …ottom&playerActions=696&relatedMode=2&videoControlDisplayColor=#191919&sequent…

    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 1015, Column 321: general entity "videoControlDisplayColor" not defined and no default entity
    …ottom&playerActions=696&relatedMode=2&videoControlDisplayColor=#191919&sequent…

    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 1015, Column 345: reference not terminated by REFC delimiter
    …relatedMode=2&videoControlDisplayColor=#191919&sequential=1&shuffle=0&autoStar…

    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 1015, Column 345: reference to entity "videoControlDisplayColor" for which no system identifier could be generated
    …relatedMode=2&videoControlDisplayColor=#191919&sequential=1&shuffle=0&autoStar…

    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 1015, Column 320: entity was defined here
    …bottom&playerActions=696&relatedMode=2&videoControlDisplayColor=#191919&sequen…
  • Warning Line 1015, Column 354: cannot generate system identifier for general entity "sequential"
    …de=2&videoControlDisplayColor=#191919&sequential=1&shuffle=0&autoStart=false",…

    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 1015, Column 354: general entity "sequential" not defined and no default entity
    …de=2&videoControlDisplayColor=#191919&sequential=1&shuffle=0&autoStart=false",…

    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 1015, Column 364: reference not terminated by REFC delimiter
    …ControlDisplayColor=#191919&sequential=1&shuffle=0&autoStart=false","proxy_dw"…

    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 1015, Column 364: reference to entity "sequential" for which no system identifier could be generated
    …ControlDisplayColor=#191919&sequential=1&shuffle=0&autoStart=false","proxy_dw"…

    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 1015, Column 353: entity was defined here
    …ode=2&videoControlDisplayColor=#191919&sequential=1&shuffle=0&autoStart=false"…
  • Warning Line 1015, Column 367: cannot generate system identifier for general entity "shuffle"
    …trolDisplayColor=#191919&sequential=1&shuffle=0&autoStart=false","proxy_dw":fa…

    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 1015, Column 367: general entity "shuffle" not defined and no default entity
    …trolDisplayColor=#191919&sequential=1&shuffle=0&autoStart=false","proxy_dw":fa…

    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 1015, Column 374: reference not terminated by REFC delimiter
    …playColor=#191919&sequential=1&shuffle=0&autoStart=false","proxy_dw":false,"de…

    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 1015, Column 374: reference to entity "shuffle" for which no system identifier could be generated
    …playColor=#191919&sequential=1&shuffle=0&autoStart=false","proxy_dw":false,"de…

    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 1015, Column 366: entity was defined here
    …ntrolDisplayColor=#191919&sequential=1&shuffle=0&autoStart=false","proxy_dw":f…
  • Warning Line 1015, Column 377: cannot generate system identifier for general entity "autoStart"
    …yColor=#191919&sequential=1&shuffle=0&autoStart=false","proxy_dw":false,"defer…

    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 1015, Column 377: general entity "autoStart" not defined and no default entity
    …yColor=#191919&sequential=1&shuffle=0&autoStart=false","proxy_dw":false,"defer…

    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 1015, Column 386: reference not terminated by REFC delimiter
    …91919&sequential=1&shuffle=0&autoStart=false","proxy_dw":false,"defer":true,"s…

    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 1015, Column 386: reference to entity "autoStart" for which no system identifier could be generated
    …91919&sequential=1&shuffle=0&autoStart=false","proxy_dw":false,"defer":true,"s…

    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 1015, Column 376: entity was defined here
    …ayColor=#191919&sequential=1&shuffle=0&autoStart=false","proxy_dw":false,"defe…
  • Warning Line 1027, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1027, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1027, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Error Line 1048, Column 51: there is no attribute "href"
    …ass="services_tab services_left" href="#" rel="component://Synacor/Portal/Comp…

    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 1056, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1056, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1056, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 1144, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1144, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1144, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Error Line 1164, Column 21: there is no attribute "frameborder"
            frameborder="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 1165, Column 19: there is no attribute "scrolling"
            scrolling="no" 

    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 1166, Column 15: there is no attribute "width"
            width="300" 

    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 1167, Column 16: there is no attribute "height"
            height="250" 

    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 1168, Column 22: there is no attribute "marginheight"
            marginheight="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 1169, Column 27: there is no attribute "allowtransparency"
            allowtransparency="true" 

    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 1170, Column 21: there is no attribute "marginwidth"
            marginwidth="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 1171, Column 13: there is no attribute "src"
            src="http://atlanticbb.net/ads/displayad.php?name=home_main_atf_300x250…

    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 1171, Column 85: element "iframe" undefined
    … src="http://atlanticbb.net/ads/displayad.php?name=home_main_atf_300x250_tag"> 

    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 1172, Column 20: end tag for "noscript" which is not finished
    </iframe></noscript>

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

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

  • Warning Line 1271, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1271, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1271, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Error Line 1302, Column 82: end tag for "img" omitted, but OMITTAG NO was specified
    …<img alt="[Video]" src="http://images.synacor.com/clientimages/69162/6316.png">

    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 3: start tag was here
    		<img alt="[Video]" src="http://images.synacor.com/clientimages/69162/6316.png…
  • Warning Line 1318, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1318, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1318, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Error Line 1330, Column 164: document type does not allow element "pre" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …e-factory"><pre class="scroll_loader" ><!-- <img src="http://web.synacor.com/a…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1335, Column 148: document type does not allow element "pre" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …ines-shop"><pre class="scroll_loader" ><!-- <img src="http://web.synacor.com/a…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1340, Column 140: document type does not allow element "pre" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …card-game"><pre class="scroll_loader" ><!-- <img src="http://web.synacor.com/a…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1350, Column 145: document type does not allow element "pre" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …ne-hearts"><pre class="scroll_loader" ><!-- <img src="http://web.synacor.com/a…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 1364, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1364, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1364, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 1364, Column 290: cannot generate system identifier for general entity "content_type"
    …g\/?content_id=mochi_valentine-hearts&content_type=zhakaas&instanceId=1","pare…

    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 1364, Column 290: general entity "content_type" not defined and no default entity
    …g\/?content_id=mochi_valentine-hearts&content_type=zhakaas&instanceId=1","pare…

    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 1364, Column 302: reference not terminated by REFC delimiter
    …id=mochi_valentine-hearts&content_type=zhakaas&instanceId=1","parent_uri":null…

    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 1364, Column 302: reference to entity "content_type" for which no system identifier could be generated
    …id=mochi_valentine-hearts&content_type=zhakaas&instanceId=1","parent_uri":null…

    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 1364, Column 289: entity was defined here
    …ng\/?content_id=mochi_valentine-hearts&content_type=zhakaas&instanceId=1","par…
  • Warning Line 1364, Column 311: cannot generate system identifier for general entity "instanceId"
    …valentine-hearts&content_type=zhakaas&instanceId=1","parent_uri":null,"event_i…

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

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

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

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

  • Error Line 1364, Column 311: general entity "instanceId" not defined and no default entity
    …valentine-hearts&content_type=zhakaas&instanceId=1","parent_uri":null,"event_i…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 1364, Column 321: reference not terminated by REFC delimiter
    …hearts&content_type=zhakaas&instanceId=1","parent_uri":null,"event_id":"compon…

    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 1364, Column 321: reference to entity "instanceId" for which no system identifier could be generated
    …hearts&content_type=zhakaas&instanceId=1","parent_uri":null,"event_id":"compon…

    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 1364, Column 310: entity was defined here
    …_valentine-hearts&content_type=zhakaas&instanceId=1","parent_uri":null,"event_…
  • Error Line 1373, Column 141: document type does not allow element "pre" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …-vs-birds"><pre class="scroll_loader" ><!-- <img src="http://web.synacor.com/a…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 1387, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1387, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1387, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 1387, Column 298: reference not terminated by REFC delimiter
    …t_id=mochi_tommy-vs-birds&content_type=zhakaas&instanceId=1","parent_uri":null…

    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 1387, Column 298: reference to entity "content_type" for which no system identifier could be generated
    …t_id=mochi_tommy-vs-birds&content_type=zhakaas&instanceId=1","parent_uri":null…

    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 1364, Column 289: entity was defined here
    …ng\/?content_id=mochi_valentine-hearts&content_type=zhakaas&instanceId=1","par…
  • Warning Line 1387, Column 317: reference not terminated by REFC delimiter
    …-birds&content_type=zhakaas&instanceId=1","parent_uri":null,"event_id":"compon…

    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 1387, Column 317: reference to entity "instanceId" for which no system identifier could be generated
    …-birds&content_type=zhakaas&instanceId=1","parent_uri":null,"event_id":"compon…

    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 1364, Column 310: entity was defined here
    …_valentine-hearts&content_type=zhakaas&instanceId=1","parent_uri":null,"event_…
  • Error Line 1396, Column 145: document type does not allow element "pre" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …g-girls-2"><pre class="scroll_loader" ><!-- <img src="http://web.synacor.com/a…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 1410, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1410, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1410, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 1410, Column 302: reference not terminated by REFC delimiter
    …id=mochi_charming-girls-2&content_type=zhakaas&instanceId=1","parent_uri":null…

    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 1410, Column 302: reference to entity "content_type" for which no system identifier could be generated
    …id=mochi_charming-girls-2&content_type=zhakaas&instanceId=1","parent_uri":null…

    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 1364, Column 289: entity was defined here
    …ng\/?content_id=mochi_valentine-hearts&content_type=zhakaas&instanceId=1","par…
  • Warning Line 1410, Column 321: reference not terminated by REFC delimiter
    …irls-2&content_type=zhakaas&instanceId=1","parent_uri":null,"event_id":"compon…

    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 1410, Column 321: reference to entity "instanceId" for which no system identifier could be generated
    …irls-2&content_type=zhakaas&instanceId=1","parent_uri":null,"event_id":"compon…

    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 1364, Column 310: entity was defined here
    …_valentine-hearts&content_type=zhakaas&instanceId=1","parent_uri":null,"event_…
  • Error Line 1419, Column 147: document type does not allow element "pre" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …valentine"><pre class="scroll_loader" ><!-- <img src="http://web.synacor.com/a…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 1433, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1433, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1433, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 1433, Column 304: reference not terminated by REFC delimiter
    …d=mochi_meet-my-valentine&content_type=zhakaas&instanceId=1","parent_uri":null…

    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 1433, Column 304: reference to entity "content_type" for which no system identifier could be generated
    …d=mochi_meet-my-valentine&content_type=zhakaas&instanceId=1","parent_uri":null…

    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 1364, Column 289: entity was defined here
    …ng\/?content_id=mochi_valentine-hearts&content_type=zhakaas&instanceId=1","par…
  • Warning Line 1433, Column 323: reference not terminated by REFC delimiter
    …entine&content_type=zhakaas&instanceId=1","parent_uri":null,"event_id":"compon…

    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 1433, Column 323: reference to entity "instanceId" for which no system identifier could be generated
    …entine&content_type=zhakaas&instanceId=1","parent_uri":null,"event_id":"compon…

    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 1364, Column 310: entity was defined here
    …_valentine-hearts&content_type=zhakaas&instanceId=1","parent_uri":null,"event_…
  • Warning Line 1448, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1448, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1448, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Error Line 1474, Column 89: element "iframe" undefined
    …="http://www.atlanticbb.net/ads/displayad.php?name=home_main_btf_300x250_tag"> 

    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 1475, Column 20: end tag for "noscript" which is not finished
    </iframe></noscript>

    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 1514, Column 89: element "iframe" undefined
    …="http://www.atlanticbb.net/ads/displayad.php?name=footer_ros_btf_728x90_tag"> 

    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 1515, Column 20: end tag for "noscript" which is not finished
    </iframe></noscript>

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

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

  • Warning Line 1531, Column 69: character "&" is the first character of a delimiter but occurred as data
    …                             	<a href="/movies_channel/">Movies & Showtimes</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1538, Column 32: character "&" is the first character of a delimiter but occurred as data
    					<a href="/local/">Traffic & Directions</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1542, Column 42: character "&" is the first character of a delimiter but occurred as data
    					<a  href="/travel_channel/">Travels & Deals</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1562, Column 11: "t" is not a member of a group specified for any attribute
    					<a t href="/news/">News</a>
  • Warning Line 1568, Column 24: character "&" is the first character of a delimiter but occurred as data
    					<a href="/tv/">TV & Video</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1593, Column 17: character "&" is the first character of a delimiter but occurred as data
    			<h2>Products & Services</h2>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1606, Column 81: cannot generate system identifier for general entity "page"
    …tp://www.atlanticbb.com/wfboth.asp?site=digital&page=2">Product Information</a>

    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 1606, Column 81: general entity "page" not defined and no default entity
    …tp://www.atlanticbb.com/wfboth.asp?site=digital&page=2">Product Information</a>

    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 1606, Column 85: reference not terminated by REFC delimiter
    …tp://www.atlanticbb.com/wfboth.asp?site=digital&page=2">Product Information</a>

    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 1606, Column 85: reference to external entity in attribute value
    …tp://www.atlanticbb.com/wfboth.asp?site=digital&page=2">Product Information</a>

    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 1606, Column 85: reference to entity "page" for which no system identifier could be generated
    …tp://www.atlanticbb.com/wfboth.asp?site=digital&page=2">Product Information</a>

    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 1606, Column 80: entity was defined here
    …tp://www.atlanticbb.com/wfboth.asp?site=digital&page=2">Product Information</a>
  • Warning Line 1610, Column 93: cannot generate system identifier for general entity "GrpId"
    …nticbb.com/CustomerSelection.asp?site=atlantic&GrpId=1/">Order New Services</a>

    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 1610, Column 93: general entity "GrpId" not defined and no default entity
    …nticbb.com/CustomerSelection.asp?site=atlantic&GrpId=1/">Order New Services</a>

    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 1610, Column 98: reference not terminated by REFC delimiter
    …nticbb.com/CustomerSelection.asp?site=atlantic&GrpId=1/">Order New Services</a>

    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 1610, Column 98: reference to external entity in attribute value
    …nticbb.com/CustomerSelection.asp?site=atlantic&GrpId=1/">Order New Services</a>

    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 1610, Column 98: reference to entity "GrpId" for which no system identifier could be generated
    …nticbb.com/CustomerSelection.asp?site=atlantic&GrpId=1/">Order New Services</a>

    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 1610, Column 92: entity was defined here
    …nticbb.com/CustomerSelection.asp?site=atlantic&GrpId=1/">Order New Services</a>
  • Warning Line 1623, Column 90: reference not terminated by REFC delimiter
    …://www.atlanticbb.com/pa/wfCCare.asp?site=atlantic&page=2">Customer Support</a>

    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 1623, Column 90: reference to external entity in attribute value
    …://www.atlanticbb.com/pa/wfCCare.asp?site=atlantic&page=2">Customer Support</a>

    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 1623, Column 90: reference to entity "page" for which no system identifier could be generated
    …://www.atlanticbb.com/pa/wfCCare.asp?site=atlantic&page=2">Customer Support</a>

    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 1606, Column 80: entity was defined here
    …tp://www.atlanticbb.com/wfboth.asp?site=digital&page=2">Product Information</a>
  • Warning Line 1629, Column 106: cannot generate system identifier for general entity "customize_from"
    …on/index.php?user_action=edit_profile&customize_from=myaccount_menu">Edit Prof…

    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 1629, Column 106: general entity "customize_from" not defined and no default entity
    …on/index.php?user_action=edit_profile&customize_from=myaccount_menu">Edit Prof…

    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 1629, Column 120: reference not terminated by REFC delimiter
    …ex.php?user_action=edit_profile&customize_from=myaccount_menu">Edit Profile</a>

    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 1629, Column 120: reference to external entity in attribute value
    …ex.php?user_action=edit_profile&customize_from=myaccount_menu">Edit Profile</a>

    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 1629, Column 120: reference to entity "customize_from" for which no system identifier could be generated
    …ex.php?user_action=edit_profile&customize_from=myaccount_menu">Edit Profile</a>

    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 1629, Column 105: entity was defined here
    …ion/index.php?user_action=edit_profile&customize_from=myaccount_menu">Edit Pro…
  • Warning Line 1632, Column 84: reference not terminated by REFC delimiter
    … href="http://www.atlanticbb.com/wfcontactus.asp?site=a&page=26">Contact Us</a>

    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 1632, Column 84: reference to external entity in attribute value
    … href="http://www.atlanticbb.com/wfcontactus.asp?site=a&page=26">Contact Us</a>

    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 1632, Column 84: reference to entity "page" for which no system identifier could be generated
    … href="http://www.atlanticbb.com/wfcontactus.asp?site=a&page=26">Contact Us</a>

    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 1606, Column 80: entity was defined here
    …tp://www.atlanticbb.com/wfboth.asp?site=digital&page=2">Product Information</a>
  • Warning Line 1644, Column 97: reference not terminated by REFC delimiter
    …p?user_action=downloads&customize_from=home" title="Downloads & Plus-ins">Down…

    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 1644, Column 97: reference to external entity in attribute value
    …p?user_action=downloads&customize_from=home" title="Downloads & Plus-ins">Down…

    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 1644, Column 97: reference to entity "customize_from" for which no system identifier could be generated
    …p?user_action=downloads&customize_from=home" title="Downloads & Plus-ins">Down…

    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 1629, Column 105: entity was defined here
    …ion/index.php?user_action=edit_profile&customize_from=myaccount_menu">Edit Pro…
  • Warning Line 1644, Column 121: character "&" is the first character of a delimiter but occurred as data
    …oads&customize_from=home" title="Downloads & Plus-ins">Downloads & Plus-ins</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1644, Column 143: character "&" is the first character of a delimiter but occurred as data
    …oads&customize_from=home" title="Downloads & Plus-ins">Downloads & Plus-ins</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1657, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1657, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1657, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 1658, Column 52: cannot generate system identifier for general entity "cj"
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 52: general entity "cj" not defined and no default entity
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 54: reference not terminated by REFC delimiter
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 54: reference to external entity in attribute value
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 54: reference to entity "cj" for which no system identifier could be generated
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 51: entity was defined here
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />
  • Warning Line 1658, Column 57: cannot generate system identifier for general entity "c1"
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 57: general entity "c1" not defined and no default entity
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 59: reference not terminated by REFC delimiter
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 59: reference to external entity in attribute value
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 59: reference to entity "c1" for which no system identifier could be generated
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 56: entity was defined here
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />
  • Warning Line 1658, Column 62: cannot generate system identifier for general entity "c2"
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 62: general entity "c2" not defined and no default entity
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 64: reference not terminated by REFC delimiter
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 64: reference to external entity in attribute value
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 64: reference to entity "c2" for which no system identifier could be generated
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 61: entity was defined here
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />
  • Error Line 1658, Column 75: required attribute "alt" not specified
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1658, Column 75: document type does not allow element "img" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    	<img src="http://b.scorecardresearch.com/p?cv=2.0&cj=1&c1=2&c2=6036266" />

    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 1659, Column 11: end tag for "noscript" which is not finished
    </noscript>

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

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

  • Warning Line 1660, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1660, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1660, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Error Line 1665, Column 31: document type does not allow element "script" here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 1665, Column 38: character "&" is the first character of a delimiter but occurred as data
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…

    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 1665, Column 56: reference not terminated by REFC delimiter
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 1665, Column 56: reference to entity "Syn.ComponentMgr" for which no system identifier could be generated
    …t/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.instantiate({"class_n…

    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 36, Column 39: entity was defined here
    <script type="text/javascript">if(Syn&&Syn.ComponentMgr){Syn.ComponentMgr.insta…
  • Warning Line 881, Column 20: reference to non-existent ID "symbol"
    							<label for="symbol">

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 918, Column 17: reference to non-existent ID "Ticker"
    				<label for="Ticker">

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

Visitor Analysis

Daily Visitor
  • 2.567 visits