FreeTvAll provides free Internet Live TV channels. Watch Free TV & Live Tv Stations from around the world on your computer, free Live Streaming from Anywhere ...

freetvall.com
  • Domain Name
    freetvall.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #31233
  • Page Size
    22.6 KB
  • Ip Address
    94.102.51.83
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 6 JPG, 7 PNG

Website Meta Analysis

  • Title
    FreeTvAll.com - Watch Free All Live Tv Channels Online Anywhere - Watch and Broadcast Live Tv Channels Online on Internet (Powered by FreeTvAll)
  • Meta Keyword
    tv online, live tv, freetvall, free satellite tv, live cricket, live sports, online tv stream, free tv online, live streaming, live tv, tv live
  • Meta Description
    FreeTvAll provides free Internet Live TV channels. Watch Free TV & Live Tv Stations from around the world on your computer, free Live Streaming from Anywhere

Technical Analysis

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

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

HTML Analysis

  • date: Tue, 30 Jul 2013 13:13:53 GMT
  • server: Apache/2.2.23 (CentOS)
  • x-powered-by: PHP/5.2.17
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
NOTICE AND TERMS OF USE: You are not authorized to access or query our WHOIS
database through the use of high-volume, automated, electronic processes. The
Data in our WHOIS database is provided for information purposes only, and to
assist persons in obtaining information about or related to a domain name
registration record. We do not guarantee its accuracy. By submitting a WHOIS
query, you agree to abide by the following terms of use: You agree that you may
use this Data only for lawful purposes and that under no circumstances will you
use this Data to: (1) allow, enable, or otherwise support the transmission of
mass unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes that
apply to us (or our computer systems). The compilation, repackaging,
dissemination or other use of this Data is expressly prohibited without our
prior written consent. We reserve the right to terminate your access to the
WHOIS database at our sole discretion, including without limitation, for
excessive querying of the WHOIS database or for failure to otherwise abide by
this policy. We reserve the right to modify these terms at any time.

Domains - cheap, easy, and secure at NameSilo.com

http://www.namesilo.com


Domain Name: freetvall.com
Created On: 2010-10-21
Expiration Date: 2013-10-21
Name Server: ns1.freetvall.com
Name Server: ns2.freetvall.com
Name Server: ns3.freetvall.com
Name Server: ns4.freetvall.com
Name Server: ns5.freetvall.com
Name Server: ns6.freetvall.com
Registrant Name: Mail Rejected See PrivacyGuardian.org
Registrant Organization: PrivacyGuardian.org
Registrant Street1: 1928 E. Highland Ave. Ste F104
Registrant Street2: PMB# 255
Registrant Street3: NOTE - All Postal Mails Rejected - visit PrivacyGuardian.org
Registrant City: Phoenix
Registrant State/Province: Arizona
Registrant Postal Code: 85016
Registrant Country: US
Registrant Phone: 347-871-7726
Registrant Fax:
Registrant Email: email
Admin Name: Mail Rejected See PrivacyGuardian.org
Admin Organization: PrivacyGuardian.org
Admin Street1: 1928 E. Highland Ave. Ste F104
Admin Street2: PMB# 255
Admin Street3: NOTE - All Postal Mails Rejected - visit PrivacyGuardian.org
Admin City: Phoenix
Admin State/Province: Arizona
Admin Postal Code: 85016
Admin Country: US
Admin Phone: 347-871-7726
Admin Fax:
Admin Email: email
Billing Name: Mail Rejected See PrivacyGuardian.org
Billing Organization: PrivacyGuardian.org
Billing Street1: 1928 E. Highland Ave. Ste F104
Billing Street2: PMB# 255
Billing Street3: NOTE - All Postal Mails Rejected - visit PrivacyGuardian.org
Billing City: Phoenix
Billing State/Province: Arizona
Billing Postal Code: 85016
Billing Country: US
Billing Phone: 347-871-7726
Billing Fax:
Billing Email: email
Tech Name: Mail Rejected See PrivacyGuardian.org
Tech Organization: PrivacyGuardian.org
Tech Street1: 1928 E. Highland Ave. Ste F104
Tech Street2: PMB# 255
Tech Street3: NOTE - All Postal Mails Rejected - visit PrivacyGuardian.org
Tech City: Phoenix
Tech State/Province: Arizona
Tech Postal Code: 85016
Tech Country: US
Tech Phone: 347-871-7726
Tech Fax:
Tech Email: email

Register your domain now at www.NameSilo.com - Domains. Cheap, Fast and Secure


DNS Analysis


DNS servers
lara.ns.cloudflare.com [173.245.58.128]
lee.ns.cloudflare.com [173.245.59.129]


DNS Records

Answer records
freetvall.com NS  lee.ns.cloudflare.com 86400s
freetvall.com A 141.101.116.28 300s
freetvall.com MX
preference: 10
exchange: mail.freetvall.com
300s
freetvall.com SOA
server: lara.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2013012513
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s
freetvall.com TXT v=spf1 a mx ~all 300s
freetvall.com NS  lara.ns.cloudflare.com 86400s
freetvall.com A 141.101.117.28 300s

Authority records

Additional records
mail.freetvall.com A 46.246.93.212 300s

IP 94.102.51.83 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 93 Errors
  • 56 Warnings
Ratio Text/Html
  • 0.6658015399255991
Message Error
  • Error Line 9, Column 67: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="shortcut icon" href="http://freetvall.com/favicon.ico">

    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 9, Column 1: start tag was here
    <link rel="shortcut icon" href="http://freetvall.com/favicon.ico">
  • Error Line 68, Column 73: required attribute "type" not specified
    …l.com/js/embed_video_mod/functions.js"></script>    	    	<!-- ClipBucket Edit…

    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 192, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <script language=JavaScript> 
  • Error Line 192, Column 28: required attribute "type" not specified
    <script language=JavaScript> 

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

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

  • Warning Line 196, Column 5: S separator in comment declaration
    <!-- var message="Function Disabled!"; -->

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

  • Error Line 196, Column 6: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!-- var message="Function Disabled!"; -->
  • Info Line 193, Column 1: comment declaration started here
    <!--
  • Warning Line 200, Column 43: character "&" is the first character of a delimiter but occurred as data
    (document.layers||(document.getElementById&&!document.all)) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 200, Column 44: character "&" is the first character of a delimiter but occurred as data
    (document.layers||(document.getElementById&&!document.all)) {

    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 220, Column 42: document type does not allow element "div" here; assuming missing "object" start-tag
    …tyle><div class="w2bslikebox" style=""><div><iframe src="http://www.facebook.c…
  • Error Line 220, Column 345: duplicate specification of attribute "scrolling"
    …olling="no" frameborder="0" scrolling="no" style="border: medium none; overflo…

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

  • Error Line 223, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

    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 220, Column 9: start tag was here
    </style><div class="w2bslikebox" style=""><div><iframe src="http://www.facebook…
  • Error Line 254, Column 488: end tag for "img" omitted, but OMITTAG NO was specified
    …Live Tv Channels Online on Internet  (Powered by FreeTvAll)"  class="logo"></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 254, Column 36: start tag was here
        <a href="http://freetvall.com"><img src="http://freetvall.com/styles/cbv2ne…
  • Warning Line 324, Column 59: cannot generate system identifier for general entity "ad_size"
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=4121187&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 324, Column 59: general entity "ad_size" not defined and no default entity
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=4121187&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 324, Column 66: reference not terminated by REFC delimiter
    …dmanager.com/st?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_UR…

    If you meant to include an entity that starts with "&", then you should terminate it 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 324, Column 66: reference to external entity in attribute value
    …dmanager.com/st?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_UR…

    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 324, Column 66: reference to entity "ad_size" for which no system identifier could be generated
    …dmanager.com/st?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_UR…

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

  • Info Line 324, Column 58: entity was defined here
    …/ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=…
  • Warning Line 324, Column 74: cannot generate system identifier for general entity "section"
    ….com/st?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_URL}" heig…

    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 324, Column 74: general entity "section" not defined and no default entity
    ….com/st?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_URL}" heig…

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

  • Warning Line 324, Column 81: reference not terminated by REFC delimiter
    …?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_URL}" height="90"…

    If you meant to include an entity that starts with "&", then you should terminate it 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 324, Column 81: reference to external entity in attribute value
    …?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_URL}" height="90"…

    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 324, Column 81: reference to entity "section" for which no system identifier could be generated
    …?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_URL}" height="90"…

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

  • Info Line 324, Column 73: entity was defined here
    …r.com/st?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_URL}" hei…
  • Warning Line 324, Column 90: cannot generate system identifier for general entity "pub_url"
    …iframe&ad_size=728x90&section=4121187&pub_url=${PUB_URL}" height="90" width="7…

    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 324, Column 90: general entity "pub_url" not defined and no default entity
    …iframe&ad_size=728x90&section=4121187&pub_url=${PUB_URL}" height="90" width="7…

    This is usually a cascading error caused by 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 324, Column 97: reference not terminated by REFC delimiter
    …ad_size=728x90&section=4121187&pub_url=${PUB_URL}" height="90" width="728" scr…

    If you meant to include an entity that starts with "&", then you should terminate it 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 324, Column 97: reference to external entity in attribute value
    …ad_size=728x90&section=4121187&pub_url=${PUB_URL}" height="90" width="728" scr…

    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 324, Column 97: reference to entity "pub_url" for which no system identifier could be generated
    …ad_size=728x90&section=4121187&pub_url=${PUB_URL}" height="90" width="728" scr…

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

  • Info Line 324, Column 89: entity was defined here
    …=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_URL}" height="90" width="…
  • Error Line 334, Column 83: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …dia Flash Player 7 or higher. <a href=http://www.macromedia.com/go/getflash/>G…
  • Error Line 334, Column 89: NET-enabling start-tag not immediately followed by null end-tag
    …ash Player 7 or higher. <a href=http://www.macromedia.com/go/getflash/>Get Fla…

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

  • Error Line 334, Column 134: end tag for element "a" which is not open
    …layer 7 or higher. <a href=http://www.macromedia.com/go/getflash/>Get Flash</a>

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

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

  • Error Line 336, 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 337, Column 28: there is no attribute "src"
    	var EmbedCode="<embed src=\"http://freetvall.com/player/jw_player_5/player3.SW…

    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 337, Column 28: an attribute value must be a literal unless it contains only name characters
    	var EmbedCode="<embed src=\"http://freetvall.com/player/jw_player_5/player3.SW…

    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 337, Column 254: there is no attribute "quality"
    …or=FFFFFF&lightcolor=66FF66\" quality=\"high\" pluginspage=\"http://www.macrom…

    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 337, Column 254: an attribute value must be a literal unless it contains only name characters
    …or=FFFFFF&lightcolor=66FF66\" quality=\"high\" pluginspage=\"http://www.macrom…

    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 337, Column 275: there is no attribute "pluginspage"
    …66FF66\" quality=\"high\" pluginspage=\"http://www.macromedia.com/go/getflashp…

    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 337, Column 275: an attribute value must be a literal unless it contains only name characters
    …66FF66\" quality=\"high\" pluginspage=\"http://www.macromedia.com/go/getflashp…

    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 337, Column 329: there is no attribute "align"
    …romedia.com/go/getflashplayer\" align=\"middle\" allowFullScreen=\"true\" type…

    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 337, Column 329: an attribute value must be a literal unless it contains only name characters
    …romedia.com/go/getflashplayer\" align=\"middle\" allowFullScreen=\"true\" type…

    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 337, Column 356: there is no attribute "allowFullScreen"
    …er\" align=\"middle\" allowFullScreen=\"true\" type=\"application/x-shockwave-…

    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 337, Column 356: an attribute value must be a literal unless it contains only name characters
    …er\" align=\"middle\" allowFullScreen=\"true\" type=\"application/x-shockwave-…

    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 337, Column 370: there is no attribute "type"
    …iddle\" allowFullScreen=\"true\" type=\"application/x-shockwave-flash\" width=…

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

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

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

  • Error Line 337, Column 370: an attribute value must be a literal unless it contains only name characters
    …iddle\" allowFullScreen=\"true\" type=\"application/x-shockwave-flash\" width=…

    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 337, Column 410: there is no attribute "width"
    … type=\"application/x-shockwave-flash\" width=\"440\" height=\"250\"></embed>";

    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 337, Column 410: an attribute value must be a literal unless it contains only name characters
    … type=\"application/x-shockwave-flash\" width=\"440\" height=\"250\"></embed>";

    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 337, Column 425: there is no attribute "height"
    … type=\"application/x-shockwave-flash\" width=\"440\" height=\"250\"></embed>";

    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 337, Column 425: an attribute value must be a literal unless it contains only name characters
    … type=\"application/x-shockwave-flash\" width=\"440\" height=\"250\"></embed>";

    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 337, Column 432: element "embed" undefined
    … type=\"application/x-shockwave-flash\" width=\"440\" height=\"250\"></embed>";

    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 355, Column 102: required attribute "alt" not specified
    …all.com/files/thumbs/131230068750f1b.jpg" width="64" height="42" border="0"  />

    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 362, Column 104: required attribute "alt" not specified
    …l.com/files/thumbs/1354817457a0b8c-1.jpg" width="64" height="42" border="0"  />

    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 369, Column 102: required attribute "alt" not specified
    …all.com/files/thumbs/128777004993255.jpg" width="64" height="42" border="0"  />

    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 376, Column 102: required attribute "alt" not specified
    …all.com/files/thumbs/1288439139eb041.gif" width="64" height="42" border="0"  />

    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 383, Column 104: required attribute "alt" not specified
    …l.com/files/thumbs/1291549090f9b3e-1.jpg" width="64" height="42" border="0"  />

    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 393, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <center><li><a href="http://cricket-tv.net/" target="_blank">

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

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

  • Error Line 394, Column 156: required attribute "alt" not specified
    … class="thumbImg thumbImgSize" title="Free Games All" /><br /></li></center>   

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

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

  • Error Line 394, Column 167: end tag for "a" omitted, but OMITTAG NO was specified
    … class="thumbImg thumbImgSize" title="Free Games All" /><br /></li></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 393, Column 13: start tag was here
    <center><li><a href="http://cricket-tv.net/" target="_blank">
  • Warning Line 423, Column 87: reference not terminated by REFC delimiter
    …dmanager.com/st?ad_type=iframe&ad_size=300x250&section=4121187&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 423, Column 87: reference to external entity in attribute value
    …dmanager.com/st?ad_type=iframe&ad_size=300x250&section=4121187&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 423, Column 87: reference to entity "ad_size" for which no system identifier could be generated
    …dmanager.com/st?ad_type=iframe&ad_size=300x250&section=4121187&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 324, Column 58: entity was defined here
    …/ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=…
  • Warning Line 423, Column 103: reference not terminated by REFC delimiter
    …ad_type=iframe&ad_size=300x250&section=4121187&pub_url=${PUB_URL}" height="250…

    If you meant to include an entity that starts with "&", then you should terminate it 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 423, Column 103: reference to external entity in attribute value
    …ad_type=iframe&ad_size=300x250&section=4121187&pub_url=${PUB_URL}" height="250…

    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 423, Column 103: reference to entity "section" for which no system identifier could be generated
    …ad_type=iframe&ad_size=300x250&section=4121187&pub_url=${PUB_URL}" height="250…

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

  • Info Line 324, Column 73: entity was defined here
    …r.com/st?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_URL}" hei…
  • Warning Line 423, Column 119: reference not terminated by REFC delimiter
    …d_size=300x250&section=4121187&pub_url=${PUB_URL}" height="250" width="300" sc…

    If you meant to include an entity that starts with "&", then you should terminate it 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 423, Column 119: reference to external entity in attribute value
    …d_size=300x250&section=4121187&pub_url=${PUB_URL}" height="250" width="300" sc…

    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 423, Column 119: reference to entity "pub_url" for which no system identifier could be generated
    …d_size=300x250&section=4121187&pub_url=${PUB_URL}" height="250" width="300" sc…

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

  • Info Line 324, Column 89: entity was defined here
    …=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_URL}" height="90" width="…
  • Warning Line 446, Column 66: cannot generate system identifier for general entity "url"
    … href="http://digg.com/submit?phase=2&url=http://freetvall.com&title="><img sr…

    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 446, Column 66: general entity "url" not defined and no default entity
    … href="http://digg.com/submit?phase=2&url=http://freetvall.com&title="><img sr…

    This is usually a cascading error caused by 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 446, Column 69: reference not terminated by REFC delimiter
    …ef="http://digg.com/submit?phase=2&url=http://freetvall.com&title="><img 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 446, Column 69: reference to external entity in attribute value
    …ef="http://digg.com/submit?phase=2&url=http://freetvall.com&title="><img 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 446, Column 69: reference to entity "url" for which no system identifier could be generated
    …ef="http://digg.com/submit?phase=2&url=http://freetvall.com&title="><img 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 446, Column 65: entity was defined here
    …a href="http://digg.com/submit?phase=2&url=http://freetvall.com&title="><img s…
  • Warning Line 446, Column 91: cannot generate system identifier for general entity "title"
    …bmit?phase=2&url=http://freetvall.com&title="><img src="http://freetvall.com/p…

    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 446, Column 91: general entity "title" not defined and no default entity
    …bmit?phase=2&url=http://freetvall.com&title="><img src="http://freetvall.com/p…

    This is usually a cascading error caused by 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 446, Column 96: reference not terminated by REFC delimiter
    …phase=2&url=http://freetvall.com&title="><img src="http://freetvall.com/plugin…

    If you meant to include an entity that starts with "&", then you should terminate it 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 446, Column 96: reference to external entity in attribute value
    …phase=2&url=http://freetvall.com&title="><img src="http://freetvall.com/plugin…

    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 446, Column 96: reference to entity "title" for which no system identifier could be generated
    …phase=2&url=http://freetvall.com&title="><img src="http://freetvall.com/plugin…

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

  • Info Line 446, Column 90: entity was defined here
    …ubmit?phase=2&url=http://freetvall.com&title="><img src="http://freetvall.com/…
  • Error Line 446, Column 189: required attribute "alt" not specified
    …ages/social_icons/digg.png" border="0"></a> <a href="http://del.icio.us/post?u…

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

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

  • Error Line 446, Column 193: end tag for "img" omitted, but OMITTAG NO was specified
    …/social_icons/digg.png" border="0"></a> <a href="http://del.icio.us/post?url=h…

    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 446, Column 99: start tag was here
    …se=2&url=http://freetvall.com&title="><img src="http://freetvall.com/plugins/c…
  • Warning Line 446, Column 258: reference not terminated by REFC delimiter
    …us/post?url=http://freetvall.com&title="><img src="http://freetvall.com/plugin…

    If you meant to include an entity that starts with "&", then you should terminate it 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 446, Column 258: reference to external entity in attribute value
    …us/post?url=http://freetvall.com&title="><img src="http://freetvall.com/plugin…

    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 446, Column 258: reference to entity "title" for which no system identifier could be generated
    …us/post?url=http://freetvall.com&title="><img src="http://freetvall.com/plugin…

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

  • Info Line 446, Column 90: entity was defined here
    …ubmit?phase=2&url=http://freetvall.com&title="><img src="http://freetvall.com/…
  • Error Line 446, Column 356: required attribute "alt" not specified
    …social_icons/delicious.png" border="0"></a> <a href="http://www.stumbleupon.co…

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

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

  • Error Line 446, Column 360: end tag for "img" omitted, but OMITTAG NO was specified
    …al_icons/delicious.png" border="0"></a> <a href="http://www.stumbleupon.com/su…

    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 446, Column 261: start tag was here
    …post?url=http://freetvall.com&title="><img src="http://freetvall.com/plugins/c…
  • Warning Line 446, Column 435: reference not terminated by REFC delimiter
    …/submit?url=http://freetvall.com&title="><img src="http://freetvall.com/plugin…

    If you meant to include an entity that starts with "&", then you should terminate it 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 446, Column 435: reference to external entity in attribute value
    …/submit?url=http://freetvall.com&title="><img src="http://freetvall.com/plugin…

    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 446, Column 435: reference to entity "title" for which no system identifier could be generated
    …/submit?url=http://freetvall.com&title="><img src="http://freetvall.com/plugin…

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

  • Info Line 446, Column 90: entity was defined here
    …ubmit?phase=2&url=http://freetvall.com&title="><img src="http://freetvall.com/…
  • Error Line 446, Column 535: required attribute "alt" not specified
    …cial_icons/stumbleupon.png" border="0"></a> <a href="http://reddit.com/submit?…

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

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

  • Error Line 446, Column 539: end tag for "img" omitted, but OMITTAG NO was specified
    …_icons/stumbleupon.png" border="0"></a> <a href="http://reddit.com/submit?url=…

    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 446, Column 438: start tag was here
    …bmit?url=http://freetvall.com&title="><img src="http://freetvall.com/plugins/c…
  • Warning Line 446, Column 605: reference not terminated by REFC delimiter
    …/submit?url=http://freetvall.com&title="><img src="http://freetvall.com/plugin…

    If you meant to include an entity that starts with "&", then you should terminate it 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 446, Column 605: reference to external entity in attribute value
    …/submit?url=http://freetvall.com&title="><img src="http://freetvall.com/plugin…

    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 446, Column 605: reference to entity "title" for which no system identifier could be generated
    …/submit?url=http://freetvall.com&title="><img src="http://freetvall.com/plugin…

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

  • Info Line 446, Column 90: entity was defined here
    …ubmit?phase=2&url=http://freetvall.com&title="><img src="http://freetvall.com/…
  • Error Line 446, Column 700: required attribute "alt" not specified
    …es/social_icons/reddit.png" border="0"></a> <a href="http://technorati.com/cos…

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

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

  • Error Line 446, Column 704: end tag for "img" omitted, but OMITTAG NO was specified
    …ocial_icons/reddit.png" border="0"></a> <a href="http://technorati.com/cosmos/…

    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 446, Column 608: start tag was here
    …bmit?url=http://freetvall.com&title="><img src="http://freetvall.com/plugins/c…
  • Error Line 446, Column 878: required attribute "alt" not specified
    …ocial_icons/technorati.png" border="0"></a> <a href="http://www.facebook.com/s…

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

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

  • Error Line 446, Column 882: end tag for "img" omitted, but OMITTAG NO was specified
    …l_icons/technorati.png" border="0"></a> <a href="http://www.facebook.com/share…

    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 446, Column 782: start tag was here
    …search.html?url=http://freetvall.com"><img src="http://freetvall.com/plugins/c…
  • Error Line 446, Column 1045: required attribute "alt" not specified
    …om/plugins/cb_modules/images/social_icons/facebook.png" border="0"></a> </div> 

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

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

  • Error Line 446, Column 1049: end tag for "img" omitted, but OMITTAG NO was specified
    …om/plugins/cb_modules/images/social_icons/facebook.png" border="0"></a> </div> 

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

  • Info Line 446, Column 951: start tag was here
    …com/share.php?u=http://freetvall.com"><img src="http://freetvall.com/plugins/c…
  • Error Line 448, Column 168: 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 448, Column 314: cannot generate system identifier for general entity "a"
    …="flashvars" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=66666…

    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 448, Column 314: general entity "a" not defined and no default entity
    …="flashvars" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=66666…

    This is usually a cascading error caused by 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 448, Column 315: reference not terminated by REFC delimiter
    …"flashvars" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 315: reference to external entity in attribute value
    …"flashvars" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666…

    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 448, Column 315: reference to entity "a" for which no system identifier could be generated
    …"flashvars" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666…

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

  • Info Line 448, Column 313: entity was defined here
    …e="flashvars" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=6666…
  • Warning Line 448, Column 323: cannot generate system identifier for general entity "b"
    …rs" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=99999…

    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 448, Column 323: general entity "b" not defined and no default entity
    …rs" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=99999…

    This is usually a cascading error caused by 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 448, Column 324: reference not terminated by REFC delimiter
    …s" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 324: reference to external entity in attribute value
    …s" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999…

    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 448, Column 324: reference to entity "b" for which no system identifier could be generated
    …s" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999…

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

  • Info Line 448, Column 322: entity was defined here
    …ars" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=9999…
  • Warning Line 448, Column 329: cannot generate system identifier for general entity "c"
    …lue="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=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 448, Column 329: general entity "c" not defined and no default entity
    …lue="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=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 448, Column 330: reference not terminated by REFC delimiter
    …ue="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 330: reference to external entity in attribute value
    …ue="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t…

    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 448, Column 330: reference to entity "c" for which no system identifier could be generated
    …ue="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t…

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

  • Info Line 448, Column 328: entity was defined here
    …alue="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1…
  • Warning Line 448, Column 338: cannot generate system identifier for general entity "d"
    …1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><em…

    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 448, Column 338: general entity "d" not defined and no default entity
    …1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><em…

    This is usually a cascading error caused by 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 448, Column 339: reference not terminated by REFC delimiter
    …313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><emb…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 339: reference to external entity in attribute value
    …313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><emb…

    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 448, Column 339: reference to entity "d" for which no system identifier could be generated
    …313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><emb…

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

  • Info Line 448, Column 337: entity was defined here
    …=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><e…
  • Warning Line 448, Column 347: cannot generate system identifier for general entity "k"
    …1443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="e…

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

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

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

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

  • Error Line 448, Column 347: general entity "k" not defined and no default entity
    …1443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="e…

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

  • Warning Line 448, Column 348: reference not terminated by REFC delimiter
    …443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="em…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 348: reference to external entity in attribute value
    …443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="em…

    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 448, Column 348: reference to entity "k" for which no system identifier could be generated
    …443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="em…

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

  • Info Line 448, Column 346: entity was defined here
    …81443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="…
  • Warning Line 448, Column 356: cannot generate system identifier for general entity "l"
    …3333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_131314…

    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 448, Column 356: general entity "l" not defined and no default entity
    …3333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_131314…

    This is usually a cascading error caused by 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 448, Column 357: reference not terminated by REFC delimiter
    …333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 357: reference to external entity in attribute value
    …333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148…

    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 448, Column 357: reference to entity "l" for which no system identifier could be generated
    …333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148…

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

  • Info Line 448, Column 355: entity was defined here
    …33333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_13131…
  • Warning Line 448, Column 365: cannot generate system identifier for general entity "s"
    …0&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443" …

    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 448, Column 365: general entity "s" not defined and no default entity
    …0&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443" …

    This is usually a cascading error caused by 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 448, Column 366: reference not terminated by REFC delimiter
    …&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443" 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 448, Column 366: reference to external entity in attribute value
    …&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443" 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 448, Column 366: reference to entity "s" for which no system identifier could be generated
    …&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443" 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 448, Column 364: entity was defined here
    …00&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443"…
  • Warning Line 448, Column 369: cannot generate system identifier for general entity "t"
    …FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443" 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 448, Column 369: general entity "t" not defined and no default entity
    …FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443" 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 448, Column 370: reference not terminated by REFC delimiter
    …FFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443" 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 448, Column 370: reference to external entity in attribute value
    …FFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443" 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 448, Column 370: reference to entity "t" for which no system identifier could be generated
    …FFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443" 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 448, Column 368: entity was defined here
    …=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443" src…
  • Error Line 448, Column 385: there is no attribute "id"
    …k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443" src="http://freetval…

    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 448, Column 490: there is no attribute "allowScriptAccess"
    …="300" height="370" 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 448, Column 515: 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 448, Column 591: there is no attribute "flashvars"
    …ash" allowFullScreen="true" flashvars="cid=1313148781443&a=333333&b=100&c=FFFF…

    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 448, Column 611: reference not terminated by REFC delimiter
    …="true" flashvars="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 611: reference to external entity in attribute value
    …="true" flashvars="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666…

    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 448, Column 611: reference to entity "a" for which no system identifier could be generated
    …="true" flashvars="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666…

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

  • Info Line 448, Column 313: entity was defined here
    …e="flashvars" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=6666…
  • Warning Line 448, Column 620: reference not terminated by REFC delimiter
    …lashvars="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 620: reference to external entity in attribute value
    …lashvars="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999…

    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 448, Column 620: reference to entity "b" for which no system identifier could be generated
    …lashvars="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999…

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

  • Info Line 448, Column 322: entity was defined here
    …ars" value="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=9999…
  • Warning Line 448, Column 626: reference not terminated by REFC delimiter
    …rs="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 626: reference to external entity in attribute value
    …rs="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t…

    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 448, Column 626: reference to entity "c" for which no system identifier could be generated
    …rs="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t…

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

  • Info Line 448, Column 328: entity was defined here
    …alue="cid=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1…
  • Warning Line 448, Column 635: reference not terminated by REFC delimiter
    …313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></emb…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 635: reference to external entity in attribute value
    …313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></emb…

    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 448, Column 635: reference to entity "d" for which no system identifier could be generated
    …313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></emb…

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

  • Info Line 448, Column 337: entity was defined here
    …=1313148781443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><e…
  • Warning Line 448, Column 644: reference not terminated by REFC delimiter
    …443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></embed></obje…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 644: reference to external entity in attribute value
    …443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></embed></obje…

    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 448, Column 644: reference to entity "k" for which no system identifier could be generated
    …443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></embed></obje…

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

  • Info Line 448, Column 346: entity was defined here
    …81443&a=333333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="…
  • Warning Line 448, Column 653: reference not terminated by REFC delimiter
    …333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></embed></object></cent…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 653: reference to external entity in attribute value
    …333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></embed></object></cent…

    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 448, Column 653: reference to entity "l" for which no system identifier could be generated
    …333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></embed></object></cent…

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

  • Info Line 448, Column 355: entity was defined here
    …33333&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_13131…
  • Warning Line 448, Column 662: reference not terminated by REFC delimiter
    …3&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></embed></object></center>

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 662: reference to external entity in attribute value
    …3&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></embed></object></center>

    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 448, Column 662: reference to entity "s" for which no system identifier could be generated
    …3&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></embed></object></center>

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

  • Info Line 448, Column 364: entity was defined here
    …00&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443"…
  • Warning Line 448, Column 666: reference not terminated by REFC delimiter
    …3&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></embed></object></center>

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 666: reference to external entity in attribute value
    …3&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></embed></object></center>

    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 448, Column 666: reference to entity "t" for which no system identifier could be generated
    …3&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></embed></object></center>

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

  • Info Line 448, Column 368: entity was defined here
    …=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"/><embed id="emb_1313148781443" src…
  • Error Line 448, Column 669: element "embed" undefined
    …3&b=100&c=FFFFFF&d=FFFFFF&k=666666&l=999999&s=1&t=0"></embed></object></center>

    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 451, Column 198: required attribute "alt" not specified
    …HLpDLwSU/Tf2c3vpeMhI/AAAAAAAAAKk/SbaEX5p84-w/s400/facebook.jpg" border="0"></a>

    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 451, Column 202: end tag for "img" omitted, but OMITTAG NO was specified
    …HLpDLwSU/Tf2c3vpeMhI/AAAAAAAAAKk/SbaEX5p84-w/s400/facebook.jpg" border="0"></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 451, Column 85: start tag was here
    …-All/159843554041190" target="_blank"><img src="http://4.bp.blogspot.com/-yC6H…
  • Warning Line 454, Column 66: reference not terminated by REFC delimiter
    …dmanager.com/st?ad_type=iframe&ad_size=300x250&section=4121187&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 454, Column 66: reference to external entity in attribute value
    …dmanager.com/st?ad_type=iframe&ad_size=300x250&section=4121187&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 454, Column 66: reference to entity "ad_size" for which no system identifier could be generated
    …dmanager.com/st?ad_type=iframe&ad_size=300x250&section=4121187&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 324, Column 58: entity was defined here
    …/ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=…
  • Warning Line 454, Column 82: reference not terminated by REFC delimiter
    …ad_type=iframe&ad_size=300x250&section=4121187&pub_url=${PUB_URL}" height="250…

    If you meant to include an entity that starts with "&", then you should terminate it 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 454, Column 82: reference to external entity in attribute value
    …ad_type=iframe&ad_size=300x250&section=4121187&pub_url=${PUB_URL}" height="250…

    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 454, Column 82: reference to entity "section" for which no system identifier could be generated
    …ad_type=iframe&ad_size=300x250&section=4121187&pub_url=${PUB_URL}" height="250…

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

  • Info Line 324, Column 73: entity was defined here
    …r.com/st?ad_type=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_URL}" hei…
  • Warning Line 454, Column 98: reference not terminated by REFC delimiter
    …d_size=300x250&section=4121187&pub_url=${PUB_URL}" height="250" width="300" sc…

    If you meant to include an entity that starts with "&", then you should terminate it 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 454, Column 98: reference to external entity in attribute value
    …d_size=300x250&section=4121187&pub_url=${PUB_URL}" height="250" width="300" sc…

    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 454, Column 98: reference to entity "pub_url" for which no system identifier could be generated
    …d_size=300x250&section=4121187&pub_url=${PUB_URL}" height="250" width="300" sc…

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

  • Info Line 324, Column 89: entity was defined here
    …=iframe&ad_size=728x90&section=4121187&pub_url=${PUB_URL}" height="90" width="…
  • Error Line 505, Column 48: there is no attribute "alt"
    …><a href="http://www.histats.com" alt="counter customizable free hit" target="…

    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 505, Column 115: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …t" target="_blank" ><div id="histatsC"><img border="0" src="http://s4is.histat…

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

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

  • Warning Line 505, Column 188: character "&" is the first character of a delimiter but occurred as data
    …er="0" src="http://s4is.histats.com/stats/i/1288534.gif?1288534&103"></div></a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 505, Column 193: required attribute "alt" not specified
    …er="0" src="http://s4is.histats.com/stats/i/1288534.gif?1288534&103"></div></a>

    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 505, Column 199: end tag for "img" omitted, but OMITTAG NO was specified
    …er="0" src="http://s4is.histats.com/stats/i/1288534.gif?1288534&103"></div></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 505, Column 116: start tag was here
    …" target="_blank" ><div id="histatsC"><img border="0" src="http://s4is.histats…
  • Error Line 541, Column 229: there is no attribute "data-cfemail"
    …re.com/email-protection" data-cfemail="63051106061715020f0f23040e020a0f4d000c0…

    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 548, Column 4: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li><a href='http://time4tv.com/' title='Live Sports Channels' target="_blank">…

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

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

  • Error Line 548, Column 112: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …lank">Live Sports Channels</a></li><li><a href='http://www.extrafreetv.com/' t…

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

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

  • Error Line 548, Column 228: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …lank">Watch Free Tv Online</a></li><li><a href='http://www.a1livetv.com/' titl…

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

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

  • Error Line 548, Column 333: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …="_blank">Live Tv Channels</a></li><li><a href='http://liveallchannel.com/' ti…

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

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

  • Error Line 548, Column 438: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …t="_blank">Watch Online Tv</a></li><li><a href="http://www.freegamesall.com/" …

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

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

  • Error Line 549, Column 158: required attribute "alt" not specified
    …thumbImgSize" title="Free Games All" /><br /></li><li><a href="http://cricket-…

    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 549, Column 169: end tag for "a" omitted, but OMITTAG NO was specified
    …Size" title="Free Games All" /><br /></li><li><a href="http://cricket-tv.net/">

    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 548, Column 439: start tag was here
    …="_blank">Watch Online Tv</a></li><li><a href="http://www.freegamesall.com/" t…
  • Error Line 549, Column 173: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …Size" title="Free Games All" /><br /></li><li><a href="http://cricket-tv.net/">

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

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

  • Error Line 550, Column 181: required attribute "alt" not specified
    …Img thumbImgSize" title="Click Here to Watch Live Cricket Online" /><br /></li>

    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 550, Column 192: end tag for "a" omitted, but OMITTAG NO was specified
    …Img thumbImgSize" title="Click Here to Watch Live Cricket Online" /><br /></li>

    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 549, Column 174: start tag was here
    …Size" title="Free Games All" /><br /></li><li><a href="http://cricket-tv.net/">

Visitor Analysis

Daily Visitor
  • 4.550 visits