NBA LIVE ONLINE - Watch NBA TV Live Streaming Online and NBA League Pass available for FREE NBA Replay. ...

nbaliveonline.tv
  • Domain Name
    nbaliveonline.tv
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #39562
  • Page Size
    76.9 KB
  • Ip Address
    81.17.24.132
  • Heading
    H1: 1, H2: 1, H3: 44, H4: 0, H5: 1, H6: 0
  • Images
    1 GIF, 9 JPG, 0 PNG

Website Meta Analysis

  • Title
    NBA LIVE ONLINE
  • Meta Keyword
    nba, nba stream, nba live, nba live stream, nba live streaming, nba schedule, nba live score, stream, streaming, live, live stream, free nba, nba free live stream, nba live stream free, nba live online, nba games live, watch nba live stream, watch nba games online, live nba games, live nba stream
  • Meta Description
    NBA LIVE ONLINE - Watch NBA TV Live Streaming Online and NBA League Pass available for FREE NBA Replay.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    81.17.24.132
  • Domain Age
    1 Years, 0 Months, 20 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from nbaliveonline.tv.

HTML Analysis

  • server: nginx
  • date: Sun, 10 Feb 2013 05:35:19 GMT
  • content-type: text/html; charset=UTF-8
  • content-length: 11676
  • connection: keep-alive
  • last-modified: Sun, 10 Feb 2013 04:59:34 GMT
  • accept-ranges: bytes
  • cache-control: max-age=3, must-revalidate
  • expires: Sun, 10 Feb 2013 05:35:22 GMT
  • vary: Accept-Encoding,Cookie
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain nbaliveonline.tv

Date Registered: 2012-1-26
Date Modified: 2012-12-18
Expiry Date: 2014-1-26

DNS1: ns1.animewiz.com
DNS2: ns2.animewiz.com

Registrant
Fundacion Private Whois
Domain Administrator
Email: email
Attn: nbaliveonline.tv
Aptds. 0850-00056
Zona 15 Panama
Panama
Tel: +507.65995877

Administrative Contact
Fundacion Private Whois
Domain Administrator
Email: email
Attn: nbaliveonline.tv
Aptds. 0850-00056
Zona 15 Panama
Panama
Tel: +507.65995877

Technical Contact
Fundacion Private Whois
Domain Administrator
Email: email
Attn: nbaliveonline.tv
Aptds. 0850-00056
Zona 15 Panama
Panama
Tel: +507.65995877

Registrar: Internet.bs Corp.
Registrar's Website : http://www.internetbs.net/

DNS Analysis


DNS servers
ns1.animewiz.com [81.17.24.130]
ns2.animewiz.com [81.17.24.131]


DNS Records

Answer records
nbaliveonline.tv MX
preference: 0
exchange: nbaliveonline.tv
14400s
nbaliveonline.tv SOA
server: ns1.animewiz.com
email: kurtjimbo@gmail.com
serial: 2012021200
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
nbaliveonline.tv NS  ns1.animewiz.com 86400s
nbaliveonline.tv NS  ns2.animewiz.com 86400s
nbaliveonline.tv A 81.17.24.132 14400s

Authority records

Additional records
nbaliveonline.tv A 81.17.24.132 14400s
ns1.animewiz.com A 81.17.24.130 14400s
ns2.animewiz.com A 81.17.24.131 14400s

IP 81.17.24.132 Analysis

  • Country Code
    CH
  • Country Code3
    CHE
  • Country Name
    Switzerland
  • City
    EU
  • Continent Code
    47° North
  • Latitude
    8.
  • Longitude
  • No whois ip data for 81.17.24.132

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 211 Errors
  • 142 Warnings
Ratio Text/Html
  • 0.6838682636251635
Message Error
  • Error Line 10, Column 16: there is no attribute "property"
    <meta property="og:title" content="Watch NBA Live Streaming" />

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

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

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

  • Error Line 217, Column 7: required attribute "type" not specified
    <style>

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

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

  • Error Line 217, Column 7: document type does not allow element "style" here
    <style>

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

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

  • Error Line 225, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s='header'><td align='center' colspan=2>NBA Schedule - Feb 9, 2013 - Feb 15, 2…
  • Error Line 234, Column 21: an attribute specification must start with a name or name token
    document.write('<scr'+'ipt src="http://ax-d.pixfuture.net/w/1.0/jstag"><\/scr'+…

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

  • Error Line 234, Column 21: element "scr" undefined
    document.write('<scr'+'ipt src="http://ax-d.pixfuture.net/w/1.0/jstag"><\/scr'+…

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

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 235, Column 9: end tag for "scr" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 234, Column 17: start tag was here
    document.write('<scr'+'ipt src="http://ax-d.pixfuture.net/w/1.0/jstag"><\/scr'+…
  • Error Line 236, Column 23: value of attribute "id" invalid: "5" cannot start a name
    <noscript><iframe id="5093fd44f36e0" name="5093fd44f36e0" src="http://ax-d.pixf…

    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 236, Column 112: cannot generate system identifier for general entity "cb"
    …d.pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" frameborde…

    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 236, Column 112: general entity "cb" not defined and no default entity
    …d.pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" frameborde…

    This is usually a cascading error caused by 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 236, Column 114: reference not terminated by REFC delimiter
    …pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" frameborder=…

    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 236, Column 114: reference to external entity in attribute value
    …pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" frameborder=…

    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 236, Column 114: reference to entity "cb" for which no system identifier could be generated
    …pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" frameborder=…

    This is usually a cascading error caused by 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 236, Column 111: entity was defined here
    …-d.pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" framebord…
  • Warning Line 236, Column 261: reference not terminated by REFC delimiter
    …uture.net/w/1.0/rc?cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    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 236, Column 261: reference to external entity in attribute value
    …uture.net/w/1.0/rc?cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    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 236, Column 261: reference to entity "cb" for which no system identifier could be generated
    …uture.net/w/1.0/rc?cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    This is usually a cascading error caused by 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 236, Column 111: entity was defined here
    …-d.pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" framebord…
  • Warning Line 236, Column 347: cannot generate system identifier for general entity "cs"
    …-d.pixfuture.net/w/1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER…

    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 236, Column 347: general entity "cs" not defined and no default entity
    …-d.pixfuture.net/w/1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER…

    This is usually a cascading error caused by 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 236, Column 349: reference not terminated by REFC delimiter
    ….pixfuture.net/w/1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_H…

    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 236, Column 349: reference to external entity in attribute value
    ….pixfuture.net/w/1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_H…

    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 236, Column 349: reference to entity "cs" for which no system identifier could be generated
    ….pixfuture.net/w/1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_H…

    This is usually a cascading error caused by 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 236, Column 346: entity was defined here
    …x-d.pixfuture.net/w/1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBE…
  • Warning Line 236, Column 366: reference not terminated by REFC delimiter
    …1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_HERE" border="0" 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 236, Column 366: reference to external entity in attribute value
    …1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_HERE" border="0" 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 236, Column 366: reference to entity "cb" for which no system identifier could be generated
    …1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_HERE" border="0" 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 236, Column 111: entity was defined here
    …-d.pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" framebord…
  • Error Line 236, Column 415: end tag for "img" omitted, but OMITTAG NO was specified
    …4f36e0&cb=INSERT_RANDOM_NUMBER_HERE" border="0" alt=""></a></iframe></noscript>

    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 236, Column 290: start tag was here
    …4f36e0&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="http://ax-d.pixfuture.net/w/1.…
  • Error Line 242, Column 21: an attribute specification must start with a name or name token
    document.write('<scr'+'ipt src="http://ax-d.pixfuture.net/w/1.0/jstag"><\/scr'+…

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

  • Error Line 242, Column 21: element "scr" undefined
    document.write('<scr'+'ipt src="http://ax-d.pixfuture.net/w/1.0/jstag"><\/scr'+…

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

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 243, Column 9: end tag for "scr" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 242, Column 17: start tag was here
    document.write('<scr'+'ipt src="http://ax-d.pixfuture.net/w/1.0/jstag"><\/scr'+…
  • Error Line 244, Column 23: value of attribute "id" invalid: "5" cannot start a name
    <noscript><iframe id="5093fd44f36e0" name="5093fd44f36e0" src="http://ax-d.pixf…

    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 244, Column 23: ID "5093fd44f36e0" already defined
    <noscript><iframe id="5093fd44f36e0" name="5093fd44f36e0" src="http://ax-d.pixf…

    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 236, Column 23: ID "5093fd44f36e0" first defined here
    <noscript><iframe id="5093fd44f36e0" name="5093fd44f36e0" src="http://ax-d.pixf…
  • Warning Line 244, Column 114: reference not terminated by REFC delimiter
    …pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" frameborder=…

    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 244, Column 114: reference to external entity in attribute value
    …pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" frameborder=…

    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 244, Column 114: reference to entity "cb" for which no system identifier could be generated
    …pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" frameborder=…

    This is usually a cascading error caused by 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 236, Column 111: entity was defined here
    …-d.pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" framebord…
  • Warning Line 244, Column 261: reference not terminated by REFC delimiter
    …uture.net/w/1.0/rc?cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    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 244, Column 261: reference to external entity in attribute value
    …uture.net/w/1.0/rc?cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    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 244, Column 261: reference to entity "cb" for which no system identifier could be generated
    …uture.net/w/1.0/rc?cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    This is usually a cascading error caused by 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 236, Column 111: entity was defined here
    …-d.pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" framebord…
  • Warning Line 244, Column 349: reference not terminated by REFC delimiter
    ….pixfuture.net/w/1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_H…

    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 244, Column 349: reference to external entity in attribute value
    ….pixfuture.net/w/1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_H…

    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 244, Column 349: reference to entity "cs" for which no system identifier could be generated
    ….pixfuture.net/w/1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_H…

    This is usually a cascading error caused by 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 236, Column 346: entity was defined here
    …x-d.pixfuture.net/w/1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBE…
  • Warning Line 244, Column 366: reference not terminated by REFC delimiter
    …1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_HERE" border="0" 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 244, Column 366: reference to external entity in attribute value
    …1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_HERE" border="0" 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 244, Column 366: reference to entity "cb" for which no system identifier could be generated
    …1.0/ai?auid=311478&cs=5093fd44f36e0&cb=INSERT_RANDOM_NUMBER_HERE" border="0" 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 236, Column 111: entity was defined here
    …-d.pixfuture.net/w/1.0/afr?auid=311478&cb=INSERT_RANDOM_NUMBER_HERE" framebord…
  • Error Line 244, Column 415: end tag for "img" omitted, but OMITTAG NO was specified
    …4f36e0&cb=INSERT_RANDOM_NUMBER_HERE" border="0" alt=""></a></iframe></noscript>

    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 244, Column 290: start tag was here
    …4f36e0&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="http://ax-d.pixfuture.net/w/1.…
  • Error Line 599, Column 21: there is no attribute "FRAMEBORDER"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…

    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 599, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 599, Column 35: there is no attribute "MARGINWIDTH"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…

    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 599, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 599, Column 50: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…

    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 599, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 599, Column 62: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.x…

    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 599, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.x…
  • Error Line 599, Column 71: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.xtendmedia…

    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 599, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.xtendmedia…
  • Error Line 599, Column 82: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.xtendmedia.com/st?ad_…

    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 599, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.xtendmedia.com/st?ad_…
  • Error Line 599, Column 90: there is no attribute "SRC"
    …SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.xtendmedia.com/st?ad_type=ifr…

    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 599, Column 134: cannot generate system identifier for general entity "ad_size"
    …//ad.xtendmedia.com/st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=…

    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 599, Column 134: general entity "ad_size" not defined and no default entity
    …//ad.xtendmedia.com/st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=…

    This is usually a cascading error caused by 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 599, Column 141: reference not terminated by REFC delimiter
    …endmedia.com/st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_U…

    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 599, Column 141: reference to external entity in attribute value
    …endmedia.com/st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_U…

    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 599, Column 141: reference to entity "ad_size" for which no system identifier could be generated
    …endmedia.com/st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_U…

    This is usually a cascading error caused by 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 599, Column 133: entity was defined here
    …://ad.xtendmedia.com/st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url…
  • Warning Line 599, Column 150: cannot generate system identifier for general entity "section"
    …com/st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_URL}"></IF…

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

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

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

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

  • Error Line 599, Column 150: general entity "section" not defined and no default entity
    …com/st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_URL}"></IF…

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

  • Warning Line 599, Column 157: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_URL}"></IFRAME>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 599, Column 157: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_URL}"></IFRAME>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 599, Column 157: reference to entity "section" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_URL}"></IFRAME>

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

  • Info Line 599, Column 149: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_URL}"></I…
  • Warning Line 599, Column 166: cannot generate system identifier for general entity "pub_url"
    …st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_URL}"></IFRAME>

    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 599, Column 166: general entity "pub_url" not defined and no default entity
    …st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_URL}"></IFRAME>

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

  • Warning Line 599, Column 173: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_URL}"></IFRAME>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 599, Column 173: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_URL}"></IFRAME>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 599, Column 173: reference to entity "pub_url" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_URL}"></IFRAME>

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

  • Info Line 599, Column 165: entity was defined here
    …st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_URL}"></IFRAME>
  • Error Line 599, Column 185: element "IFRAME" undefined
    …st?ad_type=iframe&ad_size=300x250&section=2657764&pub_url=${PUB_URL}"></IFRAME>

    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 607, Column 163: there is no attribute "VALUE"
    …<param name="AllowScriptAccess" VALUE="always"/><param name="AllowNetworking" …

    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 607, Column 309: cannot generate system identifier for general entity "a"
    …="flashvars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085…

    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 607, Column 309: general entity "a" not defined and no default entity
    …="flashvars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085…

    This is usually a cascading error caused by 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 607, Column 310: reference not terminated by REFC delimiter
    …"flashvars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F…

    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 607, Column 310: reference to external entity in attribute value
    …"flashvars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F…

    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 607, Column 310: reference to entity "a" for which no system identifier could be generated
    …"flashvars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F…

    This is usually a cascading error caused by 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 607, Column 308: entity was defined here
    …e="flashvars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=0808…
  • Warning Line 607, Column 318: cannot generate system identifier for general entity "b"
    …rs" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F…

    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 607, Column 318: general entity "b" not defined and no default entity
    …rs" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F…

    This is usually a cascading error caused by 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 607, Column 319: reference not terminated by REFC delimiter
    …s" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5…

    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 607, Column 319: reference to external entity in attribute value
    …s" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5…

    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 607, Column 319: reference to entity "b" for which no system identifier could be generated
    …s" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5…

    This is usually a cascading error caused by 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 607, Column 317: entity was defined here
    …ars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70…
  • Warning Line 607, Column 324: cannot generate system identifier for general entity "c"
    …lue="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1…

    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 607, Column 324: general entity "c" not defined and no default entity
    …lue="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1…

    This is usually a cascading error caused by 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 607, Column 325: reference not terminated by REFC delimiter
    …ue="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1E…

    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 607, Column 325: reference to external entity in attribute value
    …ue="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1E…

    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 607, Column 325: reference to entity "c" for which no system identifier could be generated
    …ue="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1E…

    This is usually a cascading error caused by 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 607, Column 323: entity was defined here
    …alue="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D…
  • Warning Line 607, Column 333: cannot generate system identifier for general entity "d"
    …1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=99…

    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 607, Column 333: general entity "d" not defined and no default entity
    …1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=99…

    This is usually a cascading error caused by 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 607, Column 334: reference not terminated by REFC delimiter
    …286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999…

    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 607, Column 334: reference to external entity in attribute value
    …286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999…

    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 607, Column 334: reference to entity "d" for which no system identifier could be generated
    …286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999…

    This is usually a cascading error caused by 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 607, Column 332: entity was defined here
    …=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=9…
  • Warning Line 607, Column 342: cannot generate system identifier for general entity "k"
    …5940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51…

    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 607, Column 342: general entity "k" not defined and no default entity
    …5940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51…

    This is usually a cascading error caused by 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 607, Column 343: reference not terminated by REFC delimiter
    …940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&…

    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 607, Column 343: reference to external entity in attribute value
    …940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&…

    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 607, Column 343: reference to entity "k" for which no system identifier could be generated
    …940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&…

    This is usually a cascading error caused by 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 607, Column 341: entity was defined here
    …75940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=5…
  • Warning Line 607, Column 351: cannot generate system identifier for general entity "l"
    …ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"…

    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 607, Column 351: general entity "l" not defined and no default entity
    …ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"…

    This is usually a cascading error caused by 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 607, Column 352: reference not terminated by REFC delimiter
    …CFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/…

    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 607, Column 352: reference to external entity in attribute value
    …CFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/…

    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 607, Column 352: reference to entity "l" for which no system identifier could be generated
    …CFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/…

    This is usually a cascading error caused by 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 607, Column 350: entity was defined here
    …1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0…
  • Warning Line 607, Column 360: cannot generate system identifier for general entity "m"
    …0&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed …

    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 607, Column 360: general entity "m" not defined and no default entity
    …0&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed …

    This is usually a cascading error caused by 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 607, Column 361: reference not terminated by REFC delimiter
    …&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed i…

    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 607, Column 361: reference to external entity in attribute value
    …&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed i…

    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 607, Column 361: reference to entity "m" for which no system identifier could be generated
    …&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed 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.

  • Info Line 607, Column 359: entity was defined here
    …00&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed…
  • Warning Line 607, Column 369: cannot generate system identifier for general entity "q"
    …9&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1…

    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 607, Column 369: general entity "q" not defined and no default entity
    …9&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1…

    This is usually a cascading error caused by 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 607, Column 370: reference not terminated by REFC delimiter
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_12…

    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 607, Column 370: reference to external entity in attribute value
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_12…

    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 607, Column 370: reference to entity "q" for which no system identifier could be generated
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_12…

    This is usually a cascading error caused by 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 607, Column 368: entity was defined here
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_…
  • Warning Line 607, Column 378: cannot generate system identifier for general entity "r"
    …0&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075…

    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 607, Column 378: general entity "r" not defined and no default entity
    …0&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075…

    This is usually a cascading error caused by 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 607, Column 379: reference not terminated by REFC delimiter
    …&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_12862170759…

    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 607, Column 379: reference to external entity in attribute value
    …&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_12862170759…

    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 607, Column 379: reference to entity "r" for which no system identifier could be generated
    …&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_12862170759…

    This is usually a cascading error caused by 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 607, Column 377: entity was defined here
    …00&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_128621707…
  • Warning Line 607, Column 383: cannot generate system identifier for general entity "s"
    …8085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" …

    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 607, Column 383: general entity "s" not defined and no default entity
    …8085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" …

    This is usually a cascading error caused by 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 607, Column 384: reference not terminated by REFC delimiter
    …085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" 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.

  • Warning Line 607, Column 384: reference to external entity in attribute value
    …085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" s…

    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 607, Column 384: reference to entity "s" for which no system identifier could be generated
    …085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" 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 607, Column 382: entity was defined here
    …08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940"…
  • Warning Line 607, Column 387: cannot generate system identifier for general entity "t"
    …F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" src=…

    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 607, Column 387: general entity "t" not defined and no default entity
    …F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" src=…

    This is usually a cascading error caused by 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 607, Column 388: reference not terminated by REFC delimiter
    …&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" src="…

    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 607, Column 388: reference to external entity in attribute value
    …&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" src="…

    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 607, Column 388: reference to entity "t" for which no system identifier could be generated
    …&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" src="…

    This is usually a cascading error caused by 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 607, Column 386: entity was defined here
    …5F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" src…
  • Error Line 607, Column 403: there is no attribute "id"
    …CFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" src="http://nbalivec…

    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 607, Column 427: there is no attribute "src"
    …0"/><embed id="emb_1286217075940" src="http://nbalivechat1.chatango.com/group"…

    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 607, Column 474: there is no attribute "width"
    …balivechat1.chatango.com/group" width="300" height="500" allowScriptAccess="al…

    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 607, Column 487: there is no attribute "height"
    …hatango.com/group" width="300" height="500" allowScriptAccess="always" allowNe…

    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 607, Column 511: there is no attribute "allowScriptAccess"
    …="300" height="500" allowScriptAccess="always" allowNetworking="all" type="app…

    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 607, Column 536: there is no attribute "allowNetworking"
    …ScriptAccess="always" allowNetworking="all" type="application/x-shockwave-flas…

    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 607, Column 547: there is no attribute "type"
    …s="always" allowNetworking="all" type="application/x-shockwave-flash" allowFul…

    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 607, Column 595: there is no attribute "allowFullScreen"
    …on/x-shockwave-flash" allowFullScreen="true" flashvars="cid=1286217075940&a=D1…

    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 607, Column 612: there is no attribute "flashvars"
    …ash" allowFullScreen="true" flashvars="cid=1286217075940&a=D1ECFD&b=100&c=0000…

    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 607, Column 632: reference not terminated by REFC delimiter
    …="true" flashvars="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F…

    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 607, Column 632: reference to external entity in attribute value
    …="true" flashvars="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F…

    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 607, Column 632: reference to entity "a" for which no system identifier could be generated
    …="true" flashvars="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F…

    This is usually a cascading error caused by 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 607, Column 308: entity was defined here
    …e="flashvars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=0808…
  • Warning Line 607, Column 641: reference not terminated by REFC delimiter
    …lashvars="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5…

    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 607, Column 641: reference to external entity in attribute value
    …lashvars="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5…

    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 607, Column 641: reference to entity "b" for which no system identifier could be generated
    …lashvars="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5…

    This is usually a cascading error caused by 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 607, Column 317: entity was defined here
    …ars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70…
  • Warning Line 607, Column 647: reference not terminated by REFC delimiter
    …rs="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1E…

    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 607, Column 647: reference to external entity in attribute value
    …rs="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1E…

    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 607, Column 647: reference to entity "c" for which no system identifier could be generated
    …rs="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1E…

    This is usually a cascading error caused by 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 607, Column 323: entity was defined here
    …alue="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D…
  • Warning Line 607, Column 656: reference not terminated by REFC delimiter
    …286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999…

    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 607, Column 656: reference to external entity in attribute value
    …286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999…

    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 607, Column 656: reference to entity "d" for which no system identifier could be generated
    …286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999…

    This is usually a cascading error caused by 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 607, Column 332: entity was defined here
    …=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=9…
  • Warning Line 607, Column 665: reference not terminated by REFC delimiter
    …940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&…

    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 607, Column 665: reference to external entity in attribute value
    …940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&…

    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 607, Column 665: reference to entity "k" for which no system identifier could be generated
    …940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&…

    This is usually a cascading error caused by 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 607, Column 341: entity was defined here
    …75940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=5…
  • Warning Line 607, Column 674: reference not terminated by REFC delimiter
    …CFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0">…

    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 607, Column 674: reference to external entity in attribute value
    …CFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0">…

    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 607, Column 674: reference to entity "l" for which no system identifier could be generated
    …CFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0">…

    This is usually a cascading error caused by 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 607, Column 350: entity was defined here
    …1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0…
  • Warning Line 607, Column 683: reference not terminated by REFC delimiter
    …&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed><…

    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 607, Column 683: reference to external entity in attribute value
    …&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed><…

    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 607, Column 683: reference to entity "m" for which no system identifier could be generated
    …&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed><…

    This is usually a cascading error caused by 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 607, Column 359: entity was defined here
    …00&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed…
  • Warning Line 607, Column 692: reference not terminated by REFC delimiter
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>

    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 607, Column 692: reference to external entity in attribute value
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>

    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 607, Column 692: reference to entity "q" for which no system identifier could be generated
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>

    This is usually a cascading error caused by 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 607, Column 368: entity was defined here
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_…
  • Warning Line 607, Column 701: reference not terminated by REFC delimiter
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>

    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 607, Column 701: reference to external entity in attribute value
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>

    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 607, Column 701: reference to entity "r" for which no system identifier could be generated
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>

    This is usually a cascading error caused by 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 607, Column 377: entity was defined here
    …00&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_128621707…
  • Warning Line 607, Column 706: reference not terminated by REFC delimiter
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>

    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 607, Column 706: reference to external entity in attribute value
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>

    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 607, Column 706: reference to entity "s" for which no system identifier could be generated
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>

    This is usually a cascading error caused by 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 607, Column 382: entity was defined here
    …08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940"…
  • Warning Line 607, Column 710: reference not terminated by REFC delimiter
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>

    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 607, Column 710: reference to external entity in attribute value
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>

    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 607, Column 710: reference to entity "t" for which no system identifier could be generated
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>

    This is usually a cascading error caused by 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 607, Column 386: entity was defined here
    …5F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" src…
  • Error Line 607, Column 713: element "embed" undefined
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 612, Column 145: cannot generate system identifier for general entity "pid"
    …/widgets/swfs/standings.swf?sport=nba&pid=espnstandings_1289059330703670022&sh…

    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 612, Column 145: general entity "pid" not defined and no default entity
    …/widgets/swfs/standings.swf?sport=nba&pid=espnstandings_1289059330703670022&sh…

    This is usually a cascading error caused by 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 612, Column 148: reference not terminated by REFC delimiter
    …dgets/swfs/standings.swf?sport=nba&pid=espnstandings_1289059330703670022&share…

    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 612, Column 148: reference to external entity in attribute value
    …dgets/swfs/standings.swf?sport=nba&pid=espnstandings_1289059330703670022&share…

    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 612, Column 148: reference to entity "pid" for which no system identifier could be generated
    …dgets/swfs/standings.swf?sport=nba&pid=espnstandings_1289059330703670022&share…

    This is usually a cascading error caused by 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 612, Column 144: entity was defined here
    …y/widgets/swfs/standings.swf?sport=nba&pid=espnstandings_1289059330703670022&s…
  • Warning Line 612, Column 183: cannot generate system identifier for general entity "share"
    …pid=espnstandings_1289059330703670022&share=embed" allowScriptAccess="always" …

    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 612, Column 183: general entity "share" not defined and no default entity
    …pid=espnstandings_1289059330703670022&share=embed" allowScriptAccess="always" …

    This is usually a cascading error caused by 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 612, Column 188: reference not terminated by REFC delimiter
    …spnstandings_1289059330703670022&share=embed" allowScriptAccess="always" allow…

    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 612, Column 188: reference to external entity in attribute value
    …spnstandings_1289059330703670022&share=embed" allowScriptAccess="always" allow…

    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 612, Column 188: reference to entity "share" for which no system identifier could be generated
    …spnstandings_1289059330703670022&share=embed" allowScriptAccess="always" allow…

    This is usually a cascading error caused by 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 612, Column 182: entity was defined here
    …&pid=espnstandings_1289059330703670022&share=embed" allowScriptAccess="always"…
  • Error Line 612, Column 214: there is no attribute "allowScriptAccess"
    …670022&share=embed" allowScriptAccess="always" allowNetworking="all"><param na…

    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 612, Column 239: there is no attribute "allowNetworking"
    …ScriptAccess="always" allowNetworking="all"><param name="movie" value="http://…

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

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

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

  • Warning Line 612, Column 343: reference not terminated by REFC delimiter
    …dgets/swfs/standings.swf?sport=nba&pid=espnstandings_1289059330703284171&share…

    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 612, Column 343: reference to external entity in attribute value
    …dgets/swfs/standings.swf?sport=nba&pid=espnstandings_1289059330703284171&share…

    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 612, Column 343: reference to entity "pid" for which no system identifier could be generated
    …dgets/swfs/standings.swf?sport=nba&pid=espnstandings_1289059330703284171&share…

    This is usually a cascading error caused by 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 612, Column 144: entity was defined here
    …y/widgets/swfs/standings.swf?sport=nba&pid=espnstandings_1289059330703670022&s…
  • Warning Line 612, Column 383: reference not terminated by REFC delimiter
    …spnstandings_1289059330703284171&share=embed" /><param name="wmode" value="tra…

    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 612, Column 383: reference to external entity in attribute value
    …spnstandings_1289059330703284171&share=embed" /><param name="wmode" value="tra…

    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 612, Column 383: reference to entity "share" for which no system identifier could be generated
    …spnstandings_1289059330703284171&share=embed" /><param name="wmode" value="tra…

    This is usually a cascading error caused by 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 612, Column 182: entity was defined here
    …&pid=espnstandings_1289059330703670022&share=embed" allowScriptAccess="always"…
  • Error Line 617, Column 238: end tag for "param" omitted, but OMITTAG NO was specified
    …_1289321494765783861&amp;share=embed"><param name="movie" value="http://a.espn…

    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 617, Column 137: start tag was here
    …ommunity/widgets/swfs/scoreboard.swf"><param name="flashVars" value="sport=nba…
  • Error Line 617, Column 326: end tag for "param" omitted, but OMITTAG NO was specified
    …mmunity/widgets/swfs/scoreboard.swf" ><param name="wmode" value="transparent">…

    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 617, Column 238: start tag was here
    …_1289321494765783861&amp;share=embed"><param name="movie" value="http://a.espn…
  • Error Line 617, Column 366: end tag for "param" omitted, but OMITTAG NO was specified
    …aram name="wmode" value="transparent"><param name="allowScriptAccess" value="a…

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

  • Info Line 617, Column 326: start tag was here
    …mmunity/widgets/swfs/scoreboard.swf" ><param name="wmode" value="transparent">…
  • Error Line 617, Column 413: end tag for "param" omitted, but OMITTAG NO was specified
    …me="allowScriptAccess" value="always"><param name="allowNetworking" value="all…

    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 617, Column 366: start tag was here
    …aram name="wmode" value="transparent"><param name="allowScriptAccess" value="a…
  • Error Line 617, Column 463: end tag for "param" omitted, but OMITTAG NO was specified
    …ss" value="always"><param name="allowNetworking" value="all"></object></center>

    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 617, Column 413: start tag was here
    …me="allowScriptAccess" value="always"><param name="allowNetworking" value="all…
  • Error Line 620, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 624, Column 86: ID "obj_1286217075940" already defined
    …'<object width="300" height="700" id="obj_1286217075940"><param name="movie" v…

    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 607, Column 38: ID "obj_1286217075940" first defined here
    <object width="300" height="500" id="obj_1286217075940"><param name="movie" val…
  • Error Line 624, Column 104: document type does not allow element "object" here
    …0" height="700" id="obj_1286217075940"><param name="movie" value="http://nhlch…

    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 624, Column 357: reference not terminated by REFC delimiter
    …"flashvars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F…

    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 624, Column 357: reference to external entity in attribute value
    …"flashvars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F…

    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 624, Column 357: reference to entity "a" for which no system identifier could be generated
    …"flashvars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F…

    This is usually a cascading error caused by 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 607, Column 308: entity was defined here
    …e="flashvars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=0808…
  • Warning Line 624, Column 366: reference not terminated by REFC delimiter
    …s" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5…

    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 624, Column 366: reference to external entity in attribute value
    …s" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5…

    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 624, Column 366: reference to entity "b" for which no system identifier could be generated
    …s" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5…

    This is usually a cascading error caused by 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 607, Column 317: entity was defined here
    …ars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70…
  • Warning Line 624, Column 372: reference not terminated by REFC delimiter
    …ue="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1E…

    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 624, Column 372: reference to external entity in attribute value
    …ue="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1E…

    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 624, Column 372: reference to entity "c" for which no system identifier could be generated
    …ue="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1E…

    This is usually a cascading error caused by 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 607, Column 323: entity was defined here
    …alue="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D…
  • Warning Line 624, Column 381: reference not terminated by REFC delimiter
    …286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999…

    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 624, Column 381: reference to external entity in attribute value
    …286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999…

    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 624, Column 381: reference to entity "d" for which no system identifier could be generated
    …286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999…

    This is usually a cascading error caused by 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 607, Column 332: entity was defined here
    …=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=9…
  • Warning Line 624, Column 390: reference not terminated by REFC delimiter
    …940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&…

    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 624, Column 390: reference to external entity in attribute value
    …940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&…

    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 624, Column 390: reference to entity "k" for which no system identifier could be generated
    …940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&…

    This is usually a cascading error caused by 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 607, Column 341: entity was defined here
    …75940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=5…
  • Warning Line 624, Column 399: reference not terminated by REFC delimiter
    …CFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/…

    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 624, Column 399: reference to external entity in attribute value
    …CFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/…

    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 624, Column 399: reference to entity "l" for which no system identifier could be generated
    …CFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/…

    This is usually a cascading error caused by 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 607, Column 350: entity was defined here
    …1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0…
  • Warning Line 624, Column 408: reference not terminated by REFC delimiter
    …&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed i…

    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 624, Column 408: reference to external entity in attribute value
    …&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed i…

    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 624, Column 408: reference to entity "m" for which no system identifier could be generated
    …&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed 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.

  • Info Line 607, Column 359: entity was defined here
    …00&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed…
  • Warning Line 624, Column 417: reference not terminated by REFC delimiter
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_12…

    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 624, Column 417: reference to external entity in attribute value
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_12…

    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 624, Column 417: reference to entity "q" for which no system identifier could be generated
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_12…

    This is usually a cascading error caused by 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 607, Column 368: entity was defined here
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_…
  • Warning Line 624, Column 426: reference not terminated by REFC delimiter
    …&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_12862170759…

    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 624, Column 426: reference to external entity in attribute value
    …&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_12862170759…

    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 624, Column 426: reference to entity "r" for which no system identifier could be generated
    …&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_12862170759…

    This is usually a cascading error caused by 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 607, Column 377: entity was defined here
    …00&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_128621707…
  • Warning Line 624, Column 431: reference not terminated by REFC delimiter
    …085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" 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.

  • Warning Line 624, Column 431: reference to external entity in attribute value
    …085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" s…

    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 624, Column 431: reference to entity "s" for which no system identifier could be generated
    …085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" 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 607, Column 382: entity was defined here
    …08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940"…
  • Warning Line 624, Column 435: reference not terminated by REFC delimiter
    …&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" src="…

    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 624, Column 435: reference to external entity in attribute value
    …&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" src="…

    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 624, Column 435: reference to entity "t" for which no system identifier could be generated
    …&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" src="…

    This is usually a cascading error caused by 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 607, Column 386: entity was defined here
    …5F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" src…
  • Warning Line 624, Column 678: reference not terminated by REFC delimiter
    …="true" flashvars="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F…

    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 624, Column 678: reference to external entity in attribute value
    …="true" flashvars="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F…

    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 624, Column 678: reference to entity "a" for which no system identifier could be generated
    …="true" flashvars="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F…

    This is usually a cascading error caused by 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 607, Column 308: entity was defined here
    …e="flashvars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=0808…
  • Warning Line 624, Column 687: reference not terminated by REFC delimiter
    …lashvars="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5…

    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 624, Column 687: reference to external entity in attribute value
    …lashvars="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5…

    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 624, Column 687: reference to entity "b" for which no system identifier could be generated
    …lashvars="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5…

    This is usually a cascading error caused by 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 607, Column 317: entity was defined here
    …ars" value="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70…
  • Warning Line 624, Column 693: reference not terminated by REFC delimiter
    …rs="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1E…

    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 624, Column 693: reference to external entity in attribute value
    …rs="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1E…

    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 624, Column 693: reference to entity "c" for which no system identifier could be generated
    …rs="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1E…

    This is usually a cascading error caused by 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 607, Column 323: entity was defined here
    …alue="cid=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D…
  • Warning Line 624, Column 702: reference not terminated by REFC delimiter
    …286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999…

    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 624, Column 702: reference to external entity in attribute value
    …286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999…

    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 624, Column 702: reference to entity "d" for which no system identifier could be generated
    …286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999…

    This is usually a cascading error caused by 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 607, Column 332: entity was defined here
    …=1286217075940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=9…
  • Warning Line 624, Column 711: reference not terminated by REFC delimiter
    …940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&…

    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 624, Column 711: reference to external entity in attribute value
    …940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&…

    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 624, Column 711: reference to entity "k" for which no system identifier could be generated
    …940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&…

    This is usually a cascading error caused by 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 607, Column 341: entity was defined here
    …75940&a=D1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=5…
  • Warning Line 624, Column 720: reference not terminated by REFC delimiter
    …CFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0">…

    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 624, Column 720: reference to external entity in attribute value
    …CFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0">…

    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 624, Column 720: reference to entity "l" for which no system identifier could be generated
    …CFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0">…

    This is usually a cascading error caused by 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 607, Column 350: entity was defined here
    …1ECFD&b=100&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0…
  • Warning Line 624, Column 729: reference not terminated by REFC delimiter
    …&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed><…

    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 624, Column 729: reference to external entity in attribute value
    …&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed><…

    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 624, Column 729: reference to entity "m" for which no system identifier could be generated
    …&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed><…

    This is usually a cascading error caused by 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 607, Column 359: entity was defined here
    …00&c=000099&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed…
  • Warning Line 624, Column 738: reference not terminated by REFC delimiter
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>'…

    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 624, Column 738: reference to external entity in attribute value
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>'…

    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 624, Column 738: reference to entity "q" for which no system identifier could be generated
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>'…

    This is usually a cascading error caused by 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 607, Column 368: entity was defined here
    …99&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_…
  • Warning Line 624, Column 747: reference not terminated by REFC delimiter
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>';

    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 624, Column 747: reference to external entity in attribute value
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>';

    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 624, Column 747: reference to entity "r" for which no system identifier could be generated
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>';

    This is usually a cascading error caused by 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 607, Column 377: entity was defined here
    …00&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_128621707…
  • Warning Line 624, Column 752: reference not terminated by REFC delimiter
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>';

    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 624, Column 752: reference to external entity in attribute value
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>';

    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 624, Column 752: reference to entity "s" for which no system identifier could be generated
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>';

    This is usually a cascading error caused by 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 607, Column 382: entity was defined here
    …08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940"…
  • Warning Line 624, Column 756: reference not terminated by REFC delimiter
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>';

    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 624, Column 756: reference to external entity in attribute value
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>';

    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 624, Column 756: reference to entity "t" for which no system identifier could be generated
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>';

    This is usually a cascading error caused by 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 607, Column 386: entity was defined here
    …5F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"/><embed id="emb_1286217075940" src…
  • Error Line 624, Column 759: element "embed" undefined
    …&d=CC0000&k=08085F&l=1B70F5&m=D1ECFD&q=999999&r=51&s=1&t=0"></embed></object>';

    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 628, Column 104: document type does not allow element "object" here
    …0" height="700" id="obj_1289576002984"><param value="http://pinaytambayanchat.…

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

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

  • Error Line 628, Column 839: there is no attribute "allowfullscreen"
    …=100&amp;s=1&amp;t=0" allowfullscreen="true" type="application/x-shockwave-fla…

    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 628, Column 899: there is no attribute "allownetworking"
    …on/x-shockwave-flash" allownetworking="all" allowscriptaccess="always" src="ht…

    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 628, Column 923: there is no attribute "allowscriptaccess"
    …lownetworking="all" allowscriptaccess="always" src="http://pinaytambayanchat.c…

    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 628, Column 1004: element "embed" undefined
    …inaytambayanchat.chatango.com/group" id="emb_1289576002984"></embed></object>';

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 743, Column 119: cannot generate system identifier for general entity "script"
    …/view.aspx?poolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3…

    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 743, Column 119: general entity "script" not defined and no default entity
    …/view.aspx?poolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3…

    This is usually a cascading error caused by 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 743, Column 125: reference not terminated by REFC delimiter
    …aspx?poolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3c/scri…

    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 743, Column 125: reference to entity "script" for which no system identifier could be generated
    …aspx?poolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3c/scri…

    This is usually a cascading error caused by 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 743, Column 118: entity was defined here
    …m/view.aspx?poolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x…
  • Warning Line 743, Column 128: cannot generate system identifier for general entity "rnd"
    …x?poolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3c/script\…

    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 743, Column 128: general entity "rnd" not defined and no default entity
    …x?poolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3c/script\…

    This is usually a cascading error caused by 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 743, Column 131: reference not terminated by REFC delimiter
    …oolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3c/script\x3e…

    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 743, Column 131: reference to entity "rnd" for which no system identifier could be generated
    …oolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3c/script\x3e…

    This is usually a cascading error caused by 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 743, Column 127: entity was defined here
    …px?poolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3c/script…
  • Error Line 748, Column 30: required attribute "type" not specified
    <script language="JavaScript">

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

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

  • Error Line 751, Column 68: required attribute "type" not specified
    <script language="JavaScript" src="http://c4.zedo.com/jsc/c4/fo.js"></script>

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

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

  • Error Line 753, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 754, Column 52: character "?" not allowed in attribute specification list
    …(p,a,c,k,e,r){e=function(c){return(c<a?'':e(parseInt(c/a)))+((c=c%a)>35?String…
  • Error Line 754, Column 52: document type does not allow element "a" here
    …(p,a,c,k,e,r){e=function(c){return(c<a?'':e(parseInt(c/a)))+((c=c%a)>35?String…

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

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

  • Error Line 754, Column 350: there is no attribute "i"
    …c]);return p}('B D(){f.g("T").h="<c i=\'E\' j=\'E\' d=\'3://4.5.6/k.7?e=F&2;8=…

    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 754, Column 350: an attribute value must be a literal unless it contains only name characters
    …c]);return p}('B D(){f.g("T").h="<c i=\'E\' j=\'E\' d=\'3://4.5.6/k.7?e=F&2;8=…

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

  • Error Line 754, Column 358: there is no attribute "j"
    …rn p}('B D(){f.g("T").h="<c i=\'E\' j=\'E\' d=\'3://4.5.6/k.7?e=F&2;8=9\' l=\'…

    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 754, Column 358: an attribute value must be a literal unless it contains only name characters
    …rn p}('B D(){f.g("T").h="<c i=\'E\' j=\'E\' d=\'3://4.5.6/k.7?e=F&2;8=9\' l=\'…

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

  • Error Line 754, Column 366: there is no attribute "d"
    … D(){f.g("T").h="<c i=\'E\' j=\'E\' d=\'3://4.5.6/k.7?e=F&2;8=9\' l=\'0\' m=\'…

    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 754, Column 366: an attribute value must be a literal unless it contains only name characters
    … D(){f.g("T").h="<c i=\'E\' j=\'E\' d=\'3://4.5.6/k.7?e=F&2;8=9\' l=\'0\' m=\'…

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

  • Error Line 754, Column 396: there is no attribute "l"
    …\'E\' d=\'3://4.5.6/k.7?e=F&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3:/…

    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 754, Column 396: an attribute value must be a literal unless it contains only name characters
    …\'E\' d=\'3://4.5.6/k.7?e=F&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3:/…

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

  • Error Line 754, Column 404: there is no attribute "m"
    …\'3://4.5.6/k.7?e=F&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u…

    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 754, Column 404: an attribute value must be a literal unless it contains only name characters
    …\'3://4.5.6/k.7?e=F&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u…

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

  • Error Line 754, Column 412: there is no attribute "p"
    …5.6/k.7?e=F&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=G&2…

    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 754, Column 412: an attribute value must be a literal unless it contains only name characters
    …5.6/k.7?e=F&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=G&2…

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

  • Error Line 754, Column 420: there is no attribute "r"
    …e=F&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=G&2;8=9\' v…

    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 754, Column 420: an attribute value must be a literal unless it contains only name characters
    …e=F&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=G&2;8=9\' v…

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

  • Error Line 754, Column 425: element "c" undefined
    …;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=G&2;8=9\' v=\'w\…

    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 754, Column 431: there is no attribute "t"
    … l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=G&2;8=9\' v=\'w\'><x d…

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

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

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

  • Error Line 754, Column 431: an attribute value must be a literal unless it contains only name characters
    … l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=G&2;8=9\' v=\'w\'><x d…

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

  • Error Line 754, Column 461: there is no attribute "v"
    …\'><a t=\'3://4.5.6/u.7?n=G&2;8=9\' v=\'w\'><x d=\'3://4.5.6/y.7?e=F&2;8=9&2;n…

    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 754, Column 461: an attribute value must be a literal unless it contains only name characters
    …\'><a t=\'3://4.5.6/u.7?n=G&2;8=9\' v=\'w\'><x d=\'3://4.5.6/y.7?e=F&2;8=9&2;n…

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

  • Error Line 754, Column 472: there is no attribute "d"
    …://4.5.6/u.7?n=G&2;8=9\' v=\'w\'><x d=\'3://4.5.6/y.7?e=F&2;8=9&2;n=G\' z=\'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 754, Column 472: an attribute value must be a literal unless it contains only name characters
    …://4.5.6/u.7?n=G&2;8=9\' v=\'w\'><x d=\'3://4.5.6/y.7?e=F&2;8=9&2;n=G\' z=\'0\…

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

  • Error Line 754, Column 508: there is no attribute "z"
    …d=\'3://4.5.6/y.7?e=F&2;8=9&2;n=G\' z=\'0\' A=\'\' /></a></c>";f.g("U").h="<c …

    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 754, Column 508: an attribute value must be a literal unless it contains only name characters
    …d=\'3://4.5.6/y.7?e=F&2;8=9&2;n=G\' z=\'0\' A=\'\' /></a></c>";f.g("U").h="<c …

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

  • Error Line 754, Column 516: there is no attribute "A"
    …4.5.6/y.7?e=F&2;8=9&2;n=G\' z=\'0\' A=\'\' /></a></c>";f.g("U").h="<c i=\'H\' …

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

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

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

  • Error Line 754, Column 516: an attribute value must be a literal unless it contains only name characters
    …4.5.6/y.7?e=F&2;8=9&2;n=G\' z=\'0\' A=\'\' /></a></c>";f.g("U").h="<c i=\'H\' …

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

  • Error Line 754, Column 522: element "x" undefined
    …y.7?e=F&2;8=9&2;n=G\' z=\'0\' A=\'\' /></a></c>";f.g("U").h="<c i=\'H\' j=\'H\…

    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 754, Column 550: an attribute value must be a literal unless it contains only name characters
    …' A=\'\' /></a></c>";f.g("U").h="<c i=\'H\' j=\'H\' d=\'3://4.5.6/k.7?e=I&2;8=…

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

  • Error Line 754, Column 558: an attribute value must be a literal unless it contains only name characters
    … /></a></c>";f.g("U").h="<c i=\'H\' j=\'H\' d=\'3://4.5.6/k.7?e=I&2;8=9\' l=\'…

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

  • Error Line 754, Column 566: an attribute value must be a literal unless it contains only name characters
    …/c>";f.g("U").h="<c i=\'H\' j=\'H\' d=\'3://4.5.6/k.7?e=I&2;8=9\' l=\'0\' m=\'…

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

  • Error Line 754, Column 596: an attribute value must be a literal unless it contains only name characters
    …\'H\' d=\'3://4.5.6/k.7?e=I&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3:/…

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

  • Error Line 754, Column 604: an attribute value must be a literal unless it contains only name characters
    …\'3://4.5.6/k.7?e=I&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u…

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

  • Error Line 754, Column 612: an attribute value must be a literal unless it contains only name characters
    …5.6/k.7?e=I&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=J&2…

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

  • Error Line 754, Column 620: an attribute value must be a literal unless it contains only name characters
    …e=I&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=J&2;8=9\' v…

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

  • Error Line 754, Column 625: element "c" undefined
    …;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=J&2;8=9\' v=\'w\…

    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 754, Column 631: an attribute value must be a literal unless it contains only name characters
    … l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=J&2;8=9\' v=\'w\'><x d…

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

  • Error Line 754, Column 661: an attribute value must be a literal unless it contains only name characters
    …\'><a t=\'3://4.5.6/u.7?n=J&2;8=9\' v=\'w\'><x d=\'3://4.5.6/y.7?e=I&2;8=9&2;n…

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

  • Error Line 754, Column 672: an attribute value must be a literal unless it contains only name characters
    …://4.5.6/u.7?n=J&2;8=9\' v=\'w\'><x d=\'3://4.5.6/y.7?e=I&2;8=9&2;n=J\' z=\'0\…

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

  • Error Line 754, Column 708: an attribute value must be a literal unless it contains only name characters
    …d=\'3://4.5.6/y.7?e=I&2;8=9&2;n=J\' z=\'0\' A=\'\' /></a></c>"}B K(){f.g("V").…

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

  • Error Line 754, Column 716: an attribute value must be a literal unless it contains only name characters
    …4.5.6/y.7?e=I&2;8=9&2;n=J\' z=\'0\' A=\'\' /></a></c>"}B K(){f.g("V").h="<c i=…

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

  • Error Line 754, Column 722: element "x" undefined
    …y.7?e=I&2;8=9&2;n=J\' z=\'0\' A=\'\' /></a></c>"}B K(){f.g("V").h="<c i=\'L\' …

    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 754, Column 756: an attribute value must be a literal unless it contains only name characters
    …\' /></a></c>"}B K(){f.g("V").h="<c i=\'L\' j=\'L\' d=\'3://4.5.6/k.7?e=M&2;8=…

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

  • Error Line 754, Column 764: an attribute value must be a literal unless it contains only name characters
    …></c>"}B K(){f.g("V").h="<c i=\'L\' j=\'L\' d=\'3://4.5.6/k.7?e=M&2;8=9\' l=\'…

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

  • Error Line 754, Column 772: an attribute value must be a literal unless it contains only name characters
    … K(){f.g("V").h="<c i=\'L\' j=\'L\' d=\'3://4.5.6/k.7?e=M&2;8=9\' l=\'0\' m=\'…

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

  • Error Line 754, Column 802: an attribute value must be a literal unless it contains only name characters
    …\'L\' d=\'3://4.5.6/k.7?e=M&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3:/…

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

  • Error Line 754, Column 810: an attribute value must be a literal unless it contains only name characters
    …\'3://4.5.6/k.7?e=M&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u…

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

  • Error Line 754, Column 818: an attribute value must be a literal unless it contains only name characters
    …5.6/k.7?e=M&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=N&2…

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

  • Error Line 754, Column 826: an attribute value must be a literal unless it contains only name characters
    …e=M&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=N&2;8=9\' v…

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

  • Error Line 754, Column 831: element "c" undefined
    …;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=N&2;8=9\' v=\'w\…

    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 754, Column 837: an attribute value must be a literal unless it contains only name characters
    … l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=N&2;8=9\' v=\'w\'><x d…

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

  • Error Line 754, Column 867: an attribute value must be a literal unless it contains only name characters
    …\'><a t=\'3://4.5.6/u.7?n=N&2;8=9\' v=\'w\'><x d=\'3://4.5.6/y.7?e=M&2;8=9&2;n…

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

  • Error Line 754, Column 878: an attribute value must be a literal unless it contains only name characters
    …://4.5.6/u.7?n=N&2;8=9\' v=\'w\'><x d=\'3://4.5.6/y.7?e=M&2;8=9&2;n=N\' z=\'0\…

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

  • Error Line 754, Column 914: an attribute value must be a literal unless it contains only name characters
    …d=\'3://4.5.6/y.7?e=M&2;8=9&2;n=N\' z=\'0\' A=\'\' /></a></c>";f.g("W").h="<c …

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

  • Error Line 754, Column 922: an attribute value must be a literal unless it contains only name characters
    …4.5.6/y.7?e=M&2;8=9&2;n=N\' z=\'0\' A=\'\' /></a></c>";f.g("W").h="<c i=\'O\' …

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

  • Error Line 754, Column 928: element "x" undefined
    …y.7?e=M&2;8=9&2;n=N\' z=\'0\' A=\'\' /></a></c>";f.g("W").h="<c i=\'O\' j=\'O\…

    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 754, Column 956: an attribute value must be a literal unless it contains only name characters
    …' A=\'\' /></a></c>";f.g("W").h="<c i=\'O\' j=\'O\' d=\'3://4.5.6/k.7?e=P&2;8=…

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

  • Error Line 754, Column 964: an attribute value must be a literal unless it contains only name characters
    … /></a></c>";f.g("W").h="<c i=\'O\' j=\'O\' d=\'3://4.5.6/k.7?e=P&2;8=9\' l=\'…

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

  • Error Line 754, Column 972: an attribute value must be a literal unless it contains only name characters
    …/c>";f.g("W").h="<c i=\'O\' j=\'O\' d=\'3://4.5.6/k.7?e=P&2;8=9\' l=\'0\' m=\'…

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

  • Error Line 754, Column 1002: an attribute value must be a literal unless it contains only name characters
    …\'O\' d=\'3://4.5.6/k.7?e=P&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3:/…

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

  • Error Line 754, Column 1010: an attribute value must be a literal unless it contains only name characters
    …\'3://4.5.6/k.7?e=P&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u…

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

  • Error Line 754, Column 1018: an attribute value must be a literal unless it contains only name characters
    …5.6/k.7?e=P&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=Q&2…

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

  • Error Line 754, Column 1026: an attribute value must be a literal unless it contains only name characters
    …e=P&2;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=Q&2;8=9\' v…

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

  • Error Line 754, Column 1031: element "c" undefined
    …;8=9\' l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=Q&2;8=9\' v=\'w\…

    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 754, Column 1037: an attribute value must be a literal unless it contains only name characters
    … l=\'0\' m=\'o\' p=\'q\' r=\'s\'><a t=\'3://4.5.6/u.7?n=Q&2;8=9\' v=\'w\'><x d…

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

  • Error Line 754, Column 1067: an attribute value must be a literal unless it contains only name characters
    …\'><a t=\'3://4.5.6/u.7?n=Q&2;8=9\' v=\'w\'><x d=\'3://4.5.6/y.7?e=P&2;8=9&2;n…

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

  • Error Line 754, Column 1078: an attribute value must be a literal unless it contains only name characters
    …://4.5.6/u.7?n=Q&2;8=9\' v=\'w\'><x d=\'3://4.5.6/y.7?e=P&2;8=9&2;n=Q\' z=\'0\…

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

  • Error Line 754, Column 1114: an attribute value must be a literal unless it contains only name characters
    …d=\'3://4.5.6/y.7?e=P&2;8=9&2;n=Q\' z=\'0\' A=\'\' /></a></c>";R("D()",C(X,Y))…

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

  • Error Line 754, Column 1122: an attribute value must be a literal unless it contains only name characters
    …4.5.6/y.7?e=P&2;8=9&2;n=Q\' z=\'0\' A=\'\' /></a></c>";R("D()",C(X,Y))}B C(a,b…

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

  • Error Line 754, Column 1128: element "x" undefined
    …y.7?e=P&2;8=9&2;n=Q\' z=\'0\' A=\'\' /></a></c>";R("D()",C(X,Y))}B C(a,b){Z S.…

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

    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 754, Column 50: start tag was here
    …on(p,a,c,k,e,r){e=function(c){return(c<a?'':e(parseInt(c/a)))+((c=c%a)>35?Stri…

Visitor Analysis

Daily Visitor
  • 4.433 visits
Daily Visitor