Download videos from social websites...Save, get internet video ...

force-download.net
  • Domain Name
    force-download.net
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #20695
  • Page Size
    12.4 KB
  • Ip Address
    188.165.51.246
  • Heading
    H1: 1, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    3 GIF, 0 JPG, 5 PNG

Website Meta Analysis

  • Title
    Force Download - Download, copy, save video, DailyMotion, Metacafe, Wideo, Kewego, Abrutis.com, IFilm
  • Meta Keyword
    force download, forcedl, download , download dailymotion, get vidoe, save video, get dailymotion, save dailymotion, downloading, dowload, save, donwload, video, videos, dowload video tube, keepvid, keep vid
  • Meta Description
    Download videos from social websites...Save, get internet video

Technical Analysis

  • Webserver
    nginx/0.7.67
  • Ip Address
    188.165.51.246
  • Domain Age
    3 Years, 7 Months, 14 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from force-download.net.

HTML Analysis

  • server: nginx/0.7.67
  • date: Wed, 26 Jun 2013 23:53:05 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.3.3-7+squeeze13
  • 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-encoding: gzip
  • vary: Accept-Encoding
  • content-length: 4382
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: force-download.net

Registrant:
Mézy Florian
force-download.net, office #1684399
c/o OwO, BP80157
59053, Roubaix Cedex 1
FR
+33.899498765
email

Administrative Contact:
Mézy Florian
force-download.net, office #1684399
c/o OwO, BP80157
59053, Roubaix Cedex 1
FR
+33.899498765
email

Technical Contact:
Mézy Florian
force-download.net, office #1684399
c/o OwO, BP80157
59053, Roubaix Cedex 1
FR
+33.899498765
email

Billing Contact:
Mézy Florian
force-download.net, office #1684399
c/o OwO, BP80157
59053, Roubaix Cedex 1
FR
+33.899498765
email

Registrar of Record: OVH.
Record last updated on 2012-09-17.
Record expires on 2013-10-31.
Record created on 2009-10-31.

DNS Analysis


DNS servers
dns14.ovh.net [213.251.188.133]
ns14.ovh.net [213.251.128.133]


DNS Records

Answer records
force-download.net SOA
server: dns14.ovh.net
email: tech@ovh.net
serial: 2010080700
refresh: 86400
retry: 3600
expire: 3600000
minimum ttl: 86400
86400s
force-download.net NS  ns14.ovh.net 86400s
force-download.net NS  dns14.ovh.net 86400s
force-download.net MX
preference: 1
exchange: redirect.ovh.net
86400s
force-download.net A 188.165.51.246 86400s

Authority records

Additional records

IP 188.165.51.246 Analysis

  • Country Code
    FR
  • Country Code3
    FRA
  • Country Name
    France
  • City
    EU
  • Continent Code
    46° North
  • Latitude
    2.
  • Longitude
  • No whois ip data for 188.165.51.246

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 77 Errors
  • 40 Warnings
Ratio Text/Html
  • 0.6627423279177458
Message Error
  • Error Line 95, Column 21: syntax of attribute value does not conform to declared value
            <div align="" class="bandeTitre1" style="font-weight:normal">

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

  • Error Line 95, Column 21: value of attribute "ALIGN" cannot be ""; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY"
            <div align="" class="bandeTitre1" style="font-weight:normal">

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

  • Error Line 104, Column 222: an attribute specification must start with a name or name token
    …&nbsp; <a href='/myspace/password.php'" style="text-decoration:underline">Pass…

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

  • Warning Line 130, Column 7: NET-enabling start-tag requires SHORTTAG YES
    			<br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 136, Column 8: end tag for "UL" which is not finished
    			</ul>

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

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

  • Error Line 139, Column 387: there is no attribute "ALLOWTRANSPARENCY"
    …en; width:140px; height:500px;padding:0px;" allowTransparency="true"></iframe>	

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

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

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

  • Warning Line 148, Column 122: NET-enabling start-tag requires SHORTTAG YES
    …e_title.gif" alt="Download Dailymotion and Youtube into MP3, AVI, MP4..."><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 149, Column 234: NET-enabling start-tag requires SHORTTAG YES
    …deo_url.focus()' style="color:#000000"> below </a> then click " Go ".<br/><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 149, Column 239: NET-enabling start-tag requires SHORTTAG YES
    …deo_url.focus()' style="color:#000000"> below </a> then click " Go ".<br/><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 150, Column 97: NET-enabling start-tag requires SHORTTAG YES
    …fault/images/en/converti_title.gif" alt="convert dailymotion and youtube"><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 151, Column 75: NET-enabling start-tag requires SHORTTAG YES
    …u can convert videos to any format : MOV, MP4, MPEG, WMV, MP3, WMA...<br/><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 151, Column 80: NET-enabling start-tag requires SHORTTAG YES
    …u can convert videos to any format : MOV, MP4, MPEG, WMV, MP3, WMA...<br/><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 152, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …e/default/images/en/cherche_title.gif" alt="video dailymotion et youtube"><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 153, Column 232: NET-enabling start-tag requires SHORTTAG YES
    …eos </a>: seeking visualizes and download the videos with one click.<br/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 162, Column 44: NET-enabling start-tag requires SHORTTAG YES
    <input type="hidden" value="en" name="lang"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 163, Column 115: NET-enabling start-tag requires SHORTTAG YES
    …here (<a href='/help_download_youtube.php' style='color:white'>help</a>) :<br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 164, Column 138: NET-enabling start-tag requires SHORTTAG YES
    …r:1px solid #000000" type="text" name="video_url" maxlength="400" size="100" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 165, Column 125: NET-enabling start-tag requires SHORTTAG YES
    …EDEDED; border:1px solid #000000; font-weight:bold;" type="submit" value="GO"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 167, Column 10: NET-enabling start-tag requires SHORTTAG YES
    </div><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 169, Column 5: NET-enabling start-tag requires SHORTTAG YES
    	<br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 172, Column 73: NET-enabling start-tag requires SHORTTAG YES
    	<param name="movie" value="http://force-download-en.chatango.com/group"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 173, Column 41: NET-enabling start-tag requires SHORTTAG YES
    	<param name="wmode" value="transparent"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 174, Column 48: NET-enabling start-tag requires SHORTTAG YES
    	<param name="AllowScriptAccess" VALUE="always"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 175, Column 43: NET-enabling start-tag requires SHORTTAG YES
    	<param name="AllowNetworking" VALUE="all"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 176, Column 44: NET-enabling start-tag requires SHORTTAG YES
    	<param name="AllowFullScreen" VALUE="true"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 177, Column 51: cannot generate system identifier for general entity "a"
    …="flashvars" value="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333…

    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 177, Column 51: general entity "a" not defined and no default entity
    …="flashvars" value="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333…

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

  • Error Line 177, Column 52: reference to entity "a" for which no system identifier could be generated
    …"flashvars" value="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&…

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

  • Info Line 177, Column 50: entity was defined here
    …e="flashvars" value="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=33333…
  • Warning Line 177, Column 60: cannot generate system identifier for general entity "b"
    …rs" value="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333…

    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 177, Column 60: general entity "b" not defined and no default entity
    …rs" value="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333…

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

  • Error Line 177, Column 61: reference to entity "b" for which no system identifier could be generated
    …s" value="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&…

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

  • Info Line 177, Column 59: entity was defined here
    …ars" value="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=33333…
  • Warning Line 177, Column 65: cannot generate system identifier for general entity "c"
    …alue="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=00…

    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 177, Column 65: general entity "c" not defined and no default entity
    …alue="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=00…

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

  • Error Line 177, Column 66: reference to entity "c" for which no system identifier could be generated
    …lue="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=009…

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

  • Info Line 177, Column 64: entity was defined here
    …value="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0…
  • Warning Line 177, Column 74: cannot generate system identifier for general entity "d"
    …=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=00…

    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 177, Column 74: general entity "d" not defined and no default entity
    …=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=00…

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

  • Error Line 177, Column 75: reference to entity "d" for which no system identifier could be generated
    …1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=009…

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

  • Info Line 177, Column 73: entity was defined here
    …d=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0…
  • Warning Line 177, Column 83: cannot generate system identifier for general entity "g"
    …32453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=00…

    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 177, Column 83: general entity "g" not defined and no default entity
    …32453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=00…

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

  • Error Line 177, Column 84: reference to entity "g" for which no system identifier could be generated
    …2453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=009…

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

  • Info Line 177, Column 82: entity was defined here
    …732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0…
  • Warning Line 177, Column 92: cannot generate system identifier for general entity "j"
    …fffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FF…

    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 177, Column 92: general entity "j" not defined and no default entity
    …fffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FF…

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

  • Error Line 177, Column 93: reference to entity "j" for which no system identifier could be generated
    …ffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFF…

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

  • Info Line 177, Column 91: entity was defined here
    …ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=F…
  • Warning Line 177, Column 101: cannot generate system identifier for general entity "k"
    …4&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&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 177, Column 101: general entity "k" not defined and no default entity
    …4&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&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.

  • Error Line 177, Column 102: reference to entity "k" for which no system identifier could be generated
    …&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&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 177, Column 100: entity was defined here
    …54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1…
  • Warning Line 177, Column 110: cannot generate system identifier for general entity "l"
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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 177, Column 110: general entity "l" not defined and no default entity
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Error Line 177, Column 111: reference to entity "l" for which no system identifier could be generated
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Info Line 177, Column 109: entity was defined here
    …FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1"…
  • Warning Line 177, Column 119: cannot generate system identifier for general entity "m"
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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 177, Column 119: general entity "m" not defined and no default entity
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Error Line 177, Column 120: reference to entity "m" for which no system identifier could be generated
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Info Line 177, Column 118: entity was defined here
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1"/>
  • Warning Line 177, Column 128: cannot generate system identifier for general entity "n"
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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 177, Column 128: general entity "n" not defined and no default entity
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Error Line 177, Column 129: reference to entity "n" for which no system identifier could be generated
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Info Line 177, Column 127: entity was defined here
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1"/>
  • Warning Line 177, Column 137: cannot generate system identifier for general entity "s"
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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 177, Column 137: general entity "s" not defined and no default entity
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Error Line 177, Column 138: reference to entity "s" for which no system identifier could be generated
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Info Line 177, Column 136: entity was defined here
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1"/>
  • Warning Line 177, Column 141: cannot generate system identifier for general entity "t"
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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 177, Column 141: general entity "t" not defined and no default entity
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Error Line 177, Column 142: reference to entity "t" for which no system identifier could be generated
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Info Line 177, Column 140: entity was defined here
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1"/>
  • Warning Line 177, Column 145: cannot generate system identifier for general entity "w"
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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 177, Column 145: general entity "w" not defined and no default entity
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Error Line 177, Column 146: reference to entity "w" for which no system identifier could be generated
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Info Line 177, Column 144: entity was defined here
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1"/>
  • Warning Line 177, Column 149: NET-enabling start-tag requires SHORTTAG YES
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 178, Column 13: there is no attribute "ID"
    	<embed 	id="emb_1253048732453" 	src="http://force-download-en.chatango.com/gro…

    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 178, Column 38: there is no attribute "SRC"
    	<embed 	id="emb_1253048732453" 	src="http://force-download-en.chatango.com/gro…

    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 178, Column 90: there is no attribute "WIDTH"
    …download-en.chatango.com/group" width="700" height="430" wmode="transparent" a…

    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 178, Column 103: there is no attribute "HEIGHT"
    …hatango.com/group" width="700" height="430" wmode="transparent" allowScriptAcc…

    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 178, Column 115: there is no attribute "WMODE"
    …group" width="700" height="430" wmode="transparent" allowScriptAccess="always"…

    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 178, Column 147: there is no attribute "ALLOWSCRIPTACCESS"
    …wmode="transparent" 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 178, Column 172: 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 178, Column 183: there is no attribute "TYPE"
    …s="always" allowNetworking="all" type="application/x-shockwave-flash" allowFul…

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

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

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

  • Error Line 178, Column 231: there is no attribute "ALLOWFULLSCREEN"
    …on/x-shockwave-flash" allowFullScreen="true" flashvars="cid=1208086612250&a=ff…

    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 178, Column 248: there is no attribute "FLASHVARS"
    …ash" allowFullScreen="true" flashvars="cid=1208086612250&a=ffffff&b=54&c=0099F…

    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 178, Column 268: reference to entity "a" for which no system identifier could be generated
    …="true" flashvars="cid=1208086612250&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&…

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

  • Info Line 177, Column 50: entity was defined here
    …e="flashvars" value="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=33333…
  • Error Line 178, Column 277: reference to entity "b" for which no system identifier could be generated
    …lashvars="cid=1208086612250&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&…

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

  • Info Line 177, Column 59: entity was defined here
    …ars" value="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=33333…
  • Error Line 178, Column 282: reference to entity "c" for which no system identifier could be generated
    …ars="cid=1208086612250&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=009…

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

  • Info Line 177, Column 64: entity was defined here
    …value="cid=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0…
  • Error Line 178, Column 291: reference to entity "d" for which no system identifier could be generated
    …1208086612250&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=009…

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

  • Info Line 177, Column 73: entity was defined here
    …d=1253048732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0…
  • Error Line 178, Column 300: reference to entity "g" for which no system identifier could be generated
    …2250&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=009…

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

  • Info Line 177, Column 82: entity was defined here
    …732453&a=ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0…
  • Error Line 178, Column 309: reference to entity "j" for which no system identifier could be generated
    …ffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFF…

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

  • Info Line 177, Column 91: entity was defined here
    …ffffff&b=54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=F…
  • Error Line 178, Column 318: reference to entity "k" for which no system identifier could be generated
    …&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&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 177, Column 100: entity was defined here
    …54&c=0099FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1…
  • Error Line 178, Column 327: reference to entity "l" for which no system identifier could be generated
    …FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Info Line 177, Column 109: entity was defined here
    …FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1"…
  • Error Line 178, Column 336: reference to entity "m" for which no system identifier could be generated
    …FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Info Line 177, Column 118: entity was defined here
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1"/>
  • Error Line 178, Column 345: reference to entity "n" for which no system identifier could be generated
    …FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Info Line 177, Column 127: entity was defined here
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1"/>
  • Error Line 178, Column 354: reference to entity "s" for which no system identifier could be generated
    …FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Info Line 177, Column 136: entity was defined here
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1"/>
  • Error Line 178, Column 358: reference to entity "t" for which no system identifier could be generated
    …FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Info Line 177, Column 140: entity was defined here
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1"/>
  • Error Line 178, Column 362: reference to entity "w" for which no system identifier could be generated
    …FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=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.

  • Info Line 177, Column 144: entity was defined here
    …F&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1"/>
  • Error Line 178, Column 365: element "EMBED" undefined
    …FF&d=0099FF&g=333333&j=333333&k=0099FF&l=0099FF&m=0099FF&n=FFFFFF&s=1&t=0&w=1">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 194, Column 6: NET-enabling start-tag requires SHORTTAG YES
    		<br/><br/><br/><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 194, Column 11: NET-enabling start-tag requires SHORTTAG YES
    		<br/><br/><br/><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 194, Column 16: NET-enabling start-tag requires SHORTTAG YES
    		<br/><br/><br/><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 194, Column 21: NET-enabling start-tag requires SHORTTAG YES
    		<br/><br/><br/><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 196, Column 8: NET-enabling start-tag requires SHORTTAG YES
    				<br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 201, Column 6: NET-enabling start-tag requires SHORTTAG YES
    		<br/><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 201, Column 11: NET-enabling start-tag requires SHORTTAG YES
    		<br/><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 207, Column 7: required attribute "TYPE" not specified
    <style>#ShareMe{top: 10%;width:60px;padding-right:10px;right: 0 !important;over…

    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 207, Column 7: document type does not allow element "STYLE" here
    <style>#ShareMe{top: 10%;width:60px;padding-right:10px;right: 0 !important;over…

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

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

  • Error Line 207, Column 780: ID "E" already defined
    …arency="true"></iframe></div><div id="e"><script type="text/javascript" src="h…

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

  • Info Line 207, Column 412: ID "E" first defined here
    …x;}</style><div id="ShareMe"><div id="e"><iframe style="height:63px; border:no…
  • Error Line 207, Column 882: there is no attribute "SIZE"
    …/plusone.js"></script><g:plusone size="tall" href="www.force-download.net"></g…

    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 207, Column 894: there is no attribute "HREF"
    …></script><g:plusone size="tall" href="www.force-download.net"></g:plusone></d…

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

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

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

  • Error Line 207, Column 918: element "G:PLUSONE" undefined
    …e="tall" href="www.force-download.net"></g:plusone></div><div id="e"><script s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 207, Column 946: ID "E" already defined
    …nload.net"></g:plusone></div><div id="e"><script src="http://www.stumbleupon.c…

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

  • Info Line 207, Column 412: ID "E" first defined here
    …x;}</style><div id="ShareMe"><div id="e"><iframe style="height:63px; border:no…
  • Error Line 207, Column 1038: required attribute "TYPE" not specified
    ….php?s=5&amp;r=www.force-download.net"></script></div><div id="e"><script type…

    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 207, Column 1063: ID "E" already defined
    …download.net"></script></div><div id="e"><script type="text/javascript">reddit…

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

  • Info Line 207, Column 412: ID "E" first defined here
    …x;}</style><div id="ShareMe"><div id="e"><iframe style="height:63px; border:no…
  • Error Line 207, Column 1252: ID "E" already defined
    …n/button2.js"></script></div><div id="e"><script type="text/javascript" src="h…

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

  • Info Line 207, Column 412: ID "E" first defined here
    …x;}</style><div id="ShareMe"><div id="e"><iframe style="height:63px; border:no…
  • Error Line 207, Column 1484: ID "E" already defined
    …->Save on Delicious</a></div><div id="e"><iframe src="http://getmailcounter.co…

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

  • Info Line 207, Column 412: ID "E" first defined here
    …x;}</style><div id="ShareMe"><div id="e"><iframe style="height:63px; border:no…
  • Warning Line 207, Column 1566: cannot generate system identifier for general entity "title"
    …ilcounter/?url=www.force-download.net&title=www.force-download.net" height="64…

    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 207, Column 1566: general entity "title" not defined and no default entity
    …ilcounter/?url=www.force-download.net&title=www.force-download.net" height="64…

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

  • Error Line 207, Column 1571: reference to entity "title" for which no system identifier could be generated
    …nter/?url=www.force-download.net&title=www.force-download.net" height="64" wid…

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

  • Info Line 207, Column 1565: entity was defined here
    …ailcounter/?url=www.force-download.net&title=www.force-download.net" height="6…
  • Error Line 207, Column 1674: ID "E" already defined
    …crolling="no"></iframe></div><div id="e"><a href="http://twitter.com/share" cl…

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

  • Info Line 207, Column 412: ID "E" first defined here
    …x;}</style><div id="ShareMe"><div id="e"><iframe style="height:63px; border:no…
  • Error Line 207, Column 1752: there is no attribute "DATA-COUNT"
    …ass="twitter-share-button" data-count="vertical" data-url="www.force-download.…

    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 207, Column 1772: there is no attribute "DATA-URL"
    …utton" data-count="vertical" data-url="www.force-download.net">Tweet</a><scrip…

    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 207, Column 1906: ID "E" already defined
    …m/widgets.js"></script></div><div id="e"><script type="text/javascript" src="h…

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

  • Info Line 207, Column 412: ID "E" first defined here
    …x;}</style><div id="ShareMe"><div id="e"><iframe style="height:63px; border:no…
  • Error Line 207, Column 2027: there is no attribute "DATA-COUNTER"
    …><script type="in/share" data-counter="top" data-url="www.force-download.net">…

    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 207, Column 2042: there is no attribute "DATA-URL"
    …in/share" data-counter="top" data-url="www.force-download.net"></script></div>…

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

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

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

  • Error Line 215, 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 218, Column 68: required attribute "TYPE" not specified
    … src="http://d2.zedo.com/jsc/d2/fo.js"></script>	<script type="text/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>.

Visitor Analysis

Daily Visitor
  • 8.517 visits
Daily Visitor