gratisnovelas.com

En GratisNovelas.Com podras ver telenovelas online gratis, telenovelas completas, ver novelas completas, telenovelas completas, y tambien podras encontrar una amplia coleccion de telenovelas de todo genero, telenovelas en vivo ...

Display Widget for this domain on your website. Click Here
This data was last updated from 09-07-2013 02:41:33  (update).

Overview Info

  • Domain Name
    gratisnovelas.com
  • Favicon
  • Alexa Rank
    #30272
  • Google Page Rank
    PR 1
  • Ip Address
    50.63.153.121
  • Page Size
    72.9 KB
  • Images
    0 GIF, 62 JPG, 2 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 0 0 0 0

Website Meta Analysis



  • Title
    ver telenovelas gratis online capitulos completos descargar
  • Meta Keyword
    ver telenovelas gratis, telenovelas completas gratis, telenovelas online gratis, ver telenovelas gratis, mirar telenovelas gratis, ver telenovelas capitulos completos, ver gratis telenovelas, telenovelas de televisa, ver, capitulo, telenovela, en vivo, capitulos
  • Meta Description
    En GratisNovelas.Com podras ver telenovelas online gratis, telenovelas completas, ver novelas completas, telenovelas completas, y tambien podras encontrar una amplia coleccion de telenovelas de todo genero, telenovelas en vivo

Technical Analysis



  • Webserver
    Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • Ip Address
    50.63.153.121
  • Domain Age
    1 Years, 2 Months, 15 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 09 Jul 2013 14:41:29 GMT
  • server: Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • x-powered-by: PHP/5.3.16
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for gratisnovelas.com

DNS Analysis


DNS servers
ns1.activatuprograma.com [50.63.153.121]
ns2.activatuprograma.com [50.63.153.121]


DNS Records

Answer records
gratisnovelas.com MX
preference: 0
exchange: gratisnovelas.com
14400s
gratisnovelas.com SOA
server: ns1.activatuprograma.com
email: guillermo_sg_12@hotmail.com
serial: 2012091103
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
gratisnovelas.com NS  ns1.activatuprograma.com 86400s
gratisnovelas.com NS  ns2.activatuprograma.com 86400s
gratisnovelas.com A 50.63.153.121 14400s

Authority records

Additional records
gratisnovelas.com A 50.63.153.121 14400s
ns1.activatuprograma.com A 50.63.153.121 14400s
ns2.activatuprograma.com A 50.63.153.121 14400s

IP 50.63.153.121 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Scottsdale
  • Continent Code
    85260
  • Latitude
    480
  • Longitude
    753
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 50.63.153.121"
    #
    # Use "?" to get help.
    #

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

    NetRange: 50.62.0.0 - 50.63.255.255
    CIDR: 50.62.0.0/15
    OriginAS: AS26496
    NetName: GO-DADDY-COM-LLC
    NetHandle: NET-50-62-0-0-1
    Parent: NET-50-0-0-0-0
    NetType: Direct Allocation
    Comment: Please send abuse complaints to abuse@godaddy.com
    RegDate: 2011-02-02
    Updated: 2012-02-24
    Ref: http://whois.arin.net/rest/net/NET-50-62-0-0-1

    OrgName: GoDaddy.com, LLC
    OrgId: GODAD
    Address: 14455 N Hayden Road
    Address: Suite 226
    City: Scottsdale
    StateProv: AZ
    PostalCode: 85260
    Country: US
    RegDate: 2007-06-01
    Updated: 2012-03-15
    Comment: Please send abuse complaints to abuse@godaddy.com
    Ref: http://whois.arin.net/rest/org/GODAD

    OrgAbuseHandle: ABUSE51-ARIN
    OrgAbuseName: Abuse Department
    OrgAbusePhone: +1-480-624-2505
    OrgAbuseEmail: abuse@godaddy.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE51-ARIN

    OrgTechHandle: NOC124-ARIN
    OrgTechName: Network Operations Center
    OrgTechPhone: +1-480-505-8809
    OrgTechEmail: noc@godaddy.com
    OrgTechRef: http://whois.arin.net/rest/poc/NOC124-ARIN

    OrgNOCHandle: NOC124-ARIN
    OrgNOCName: Network Operations Center
    OrgNOCPhone: +1-480-505-8809
    OrgNOCEmail: noc@godaddy.com
    OrgNOCRef: http://whois.arin.net/rest/poc/NOC124-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 93 Errors
  • 76 Warnings
Ratio Text/Html
  • 0.7460017680623644
Message Error
  • Error Line 6, Column 263: end tag for "meta" omitted, but OMITTAG NO was specified
    …ntrar una amplia coleccion de telenovelas de todo genero, telenovelas en vivo">

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

  • Info Line 6, Column 1: start tag was here
    <meta name="description" content="En GratisNovelas.Com podras ver telenovelas o…
  • Error Line 7, Column 296: end tag for "meta" omitted, but OMITTAG NO was specified
    …velas, telenovelas de televisa, ver, capitulo, telenovela, en vivo, capitulos">

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

  • Info Line 7, Column 1: start tag was here
    <meta name="keywords" content="ver telenovelas gratis, telenovelas completas gr…
  • Error Line 23, Column 16: there is no attribute "property"
    <meta property="og:image" content="http://gratisnovelas.com/img/logo.png"/>

    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 28, Column 250: character "&" is the first character of a delimiter but occurred as data
    …imer:c,load:f};try{var g=null;a.chrome&&a.chrome.csi&&(g=Math.floor(a.chrome.c…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 28, Column 252: cannot generate system identifier for general entity "a.chrome.csi"
    …er:c,load:f};try{var g=null;a.chrome&&a.chrome.csi&&(g=Math.floor(a.chrome.csi…

    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 28, Column 252: general entity "a.chrome.csi" not defined and no default entity
    …er:c,load:f};try{var g=null;a.chrome&&a.chrome.csi&&(g=Math.floor(a.chrome.csi…

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

  • Warning Line 28, Column 264: reference not terminated by REFC delimiter
    …;try{var g=null;a.chrome&&a.chrome.csi&&(g=Math.floor(a.chrome.csi().pageT));n…

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

  • Error Line 28, Column 264: reference to entity "a.chrome.csi" for which no system identifier could be generated
    …;try{var g=null;a.chrome&&a.chrome.csi&&(g=Math.floor(a.chrome.csi().pageT));n…

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

  • Info Line 28, Column 251: entity was defined here
    …mer:c,load:f};try{var g=null;a.chrome&&a.chrome.csi&&(g=Math.floor(a.chrome.cs…
  • Warning Line 28, Column 264: character "&" is the first character of a delimiter but occurred as data
    …;try{var g=null;a.chrome&&a.chrome.csi&&(g=Math.floor(a.chrome.csi().pageT));n…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 28, Column 265: character "&" is the first character of a delimiter but occurred as data
    …try{var g=null;a.chrome&&a.chrome.csi&&(g=Math.floor(a.chrome.csi().pageT));nu…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 28, Column 310: character "&" is the first character of a delimiter but occurred as data
    …h.floor(a.chrome.csi().pageT));null==g&&a.gtbExternal&&(g=a.gtbExternal.pageT(…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 28, Column 312: cannot generate system identifier for general entity "a.gtbExternal"
    …floor(a.chrome.csi().pageT));null==g&&a.gtbExternal&&(g=a.gtbExternal.pageT())…

    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 28, Column 312: general entity "a.gtbExternal" not defined and no default entity
    …floor(a.chrome.csi().pageT));null==g&&a.gtbExternal&&(g=a.gtbExternal.pageT())…

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

  • Warning Line 28, Column 325: reference not terminated by REFC delimiter
    …e.csi().pageT));null==g&&a.gtbExternal&&(g=a.gtbExternal.pageT());null==g&&a.e…

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

  • Error Line 28, Column 325: reference to entity "a.gtbExternal" for which no system identifier could be generated
    …e.csi().pageT));null==g&&a.gtbExternal&&(g=a.gtbExternal.pageT());null==g&&a.e…

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

  • Info Line 28, Column 311: entity was defined here
    ….floor(a.chrome.csi().pageT));null==g&&a.gtbExternal&&(g=a.gtbExternal.pageT()…
  • Warning Line 28, Column 325: character "&" is the first character of a delimiter but occurred as data
    …e.csi().pageT));null==g&&a.gtbExternal&&(g=a.gtbExternal.pageT());null==g&&a.e…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 28, Column 326: character "&" is the first character of a delimiter but occurred as data
    ….csi().pageT));null==g&&a.gtbExternal&&(g=a.gtbExternal.pageT());null==g&&a.ex…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 28, Column 360: character "&" is the first character of a delimiter but occurred as data
    …nal&&(g=a.gtbExternal.pageT());null==g&&a.external&&(g=a.external.pageT);g&&(a…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 28, Column 362: cannot generate system identifier for general entity "a.external"
    …l&&(g=a.gtbExternal.pageT());null==g&&a.external&&(g=a.external.pageT);g&&(a.j…

    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 28, Column 362: general entity "a.external" not defined and no default entity
    …l&&(g=a.gtbExternal.pageT());null==g&&a.external&&(g=a.external.pageT);g&&(a.j…

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

  • Warning Line 28, Column 372: reference not terminated by REFC delimiter
    …bExternal.pageT());null==g&&a.external&&(g=a.external.pageT);g&&(a.jstiming.pt…

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

  • Error Line 28, Column 372: reference to entity "a.external" for which no system identifier could be generated
    …bExternal.pageT());null==g&&a.external&&(g=a.external.pageT);g&&(a.jstiming.pt…

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

  • Info Line 28, Column 361: entity was defined here
    …al&&(g=a.gtbExternal.pageT());null==g&&a.external&&(g=a.external.pageT);g&&(a.…
  • Warning Line 28, Column 372: character "&" is the first character of a delimiter but occurred as data
    …bExternal.pageT());null==g&&a.external&&(g=a.external.pageT);g&&(a.jstiming.pt…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 28, Column 373: character "&" is the first character of a delimiter but occurred as data
    …External.pageT());null==g&&a.external&&(g=a.external.pageT);g&&(a.jstiming.pt=…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 28, Column 396: character "&" is the first character of a delimiter but occurred as data
    …=g&&a.external&&(g=a.external.pageT);g&&(a.jstiming.pt=g)}catch(h){};a.tickAbo…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 28, Column 397: character "&" is the first character of a delimiter but occurred as data
    …g&&a.external&&(g=a.external.pageT);g&&(a.jstiming.pt=g)}catch(h){};a.tickAbov…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 28, Column 534: character "&" is the first character of a delimiter but occurred as data
    …Top;while(b=b.offsetParent)}b=e;750>=b&&a.jstiming.load.tick("aft")};var j=!1;…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 28, Column 536: cannot generate system identifier for general entity "a.jstiming.load.tick"
    …p;while(b=b.offsetParent)}b=e;750>=b&&a.jstiming.load.tick("aft")};var j=!1;fu…

    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 28, Column 536: general entity "a.jstiming.load.tick" not defined and no default entity
    …p;while(b=b.offsetParent)}b=e;750>=b&&a.jstiming.load.tick("aft")};var j=!1;fu…

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

  • Warning Line 28, Column 556: reference not terminated by REFC delimiter
    …rent)}b=e;750>=b&&a.jstiming.load.tick("aft")};var j=!1;function k(){j||(j=!0,…

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

  • Error Line 28, Column 556: reference to entity "a.jstiming.load.tick" for which no system identifier could be generated
    …rent)}b=e;750>=b&&a.jstiming.load.tick("aft")};var j=!1;function k(){j||(j=!0,…

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

  • Info Line 28, Column 535: entity was defined here
    …op;while(b=b.offsetParent)}b=e;750>=b&&a.jstiming.load.tick("aft")};var j=!1;f…
  • Error Line 46, Column 120: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"
    …otion/790.php" width="728" height="90" frameborder="0" scrolling="No"></iframe>

    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 48, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 45, Column 1: start tag was here
    <div class="a728"> 
  • Error Line 48, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 41, Column 1: start tag was here
    <div class="header">
  • Error Line 48, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 40, Column 1: start tag was here
    <div id="header">
  • Error Line 49, Column 6: end tag for element "div" which is not open
    </div> 

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

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

  • Error Line 51, Column 6: end tag for element "div" which is not open
    </div>

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

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

  • Error Line 52, Column 6: end tag for element "div" which is not open
    </div>

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

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

  • Error Line 54, Column 16: document type does not allow element "div" here
    <div id="barra">

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

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

  • Warning Line 69, Column 5: S separator in comment declaration
    <!-- FIN BUSCADOR --> 

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

  • Error Line 69, Column 6: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!-- FIN BUSCADOR --> 
  • Info Line 64, Column 1: comment declaration started here
    <!-- INICIO BUSCADOR
  • Error Line 72, Column 19: document type does not allow element "div" here
    <div id="alfabeto">

    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 73, Column 10: ID "nav" already defined
    <div id="nav"> 

    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 55, Column 10: ID "nav" first defined here
    <div id="nav"> 
  • Error Line 74, Column 9: ID "catnav" already defined
    <ul id="catnav" class="dropdown dropdown-horizontal">

    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 56, Column 9: ID "catnav" first defined here
    <ul id="catnav" class="dropdown dropdown-horizontal">
  • Error Line 104, Column 21: document type does not allow element "div" here
    <div id="contenedor">

    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 749, Column 182: there is no attribute "allowTransparency"
    … overflow:hidden; width:720px; height:90px;" allowTransparency="true"></iframe>

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

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

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

  • Error Line 771, Column 25: document type does not allow element "div" here
    <div id="cuerpo-derecha">

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

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

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

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

  • Warning Line 783, Column 315: cannot generate system identifier for general entity "b"
    …="flashvars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=…

    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 783, Column 315: general entity "b" not defined and no default entity
    …="flashvars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=…

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

  • Warning Line 783, Column 316: reference not terminated by REFC delimiter
    …"flashvars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=3…

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

  • Warning Line 783, Column 316: reference to external entity in attribute value
    …"flashvars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=3…

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

  • Error Line 783, Column 316: reference to entity "b" for which no system identifier could be generated
    …"flashvars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=3…

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

  • Info Line 783, Column 314: entity was defined here
    …e="flashvars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j…
  • Warning Line 783, Column 321: cannot generate system identifier for general entity "c"
    …hvars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&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 783, Column 321: general entity "c" not defined and no default entity
    …hvars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&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.

  • Warning Line 783, Column 322: reference not terminated by REFC delimiter
    …vars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&…

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

  • Warning Line 783, Column 322: reference to external entity in attribute value
    …vars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&…

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

  • Error Line 783, Column 322: reference to entity "c" for which no system identifier could be generated
    …vars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&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 783, Column 320: entity was defined here
    …shvars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=33333…
  • Warning Line 783, Column 330: cannot generate system identifier for general entity "d"
    …lue="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666…

    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 783, Column 330: general entity "d" not defined and no default entity
    …lue="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666…

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

  • Warning Line 783, Column 331: reference not terminated by REFC delimiter
    …ue="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&…

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

  • Warning Line 783, Column 331: reference to external entity in attribute value
    …ue="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&…

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

  • Error Line 783, Column 331: reference to entity "d" for which no system identifier could be generated
    …ue="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&…

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

  • Info Line 783, Column 329: entity was defined here
    …alue="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=66666…
  • Warning Line 783, Column 339: cannot generate system identifier for general entity "f"
    …1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC…

    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 783, Column 339: general entity "f" not defined and no default entity
    …1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC…

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

  • Warning Line 783, Column 340: reference not terminated by REFC delimiter
    …336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&…

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

  • Warning Line 783, Column 340: reference to external entity in attribute value
    …336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&…

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

  • Error Line 783, Column 340: reference to entity "f" for which no system identifier could be generated
    …336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&…

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

  • Info Line 783, Column 338: entity was defined here
    …=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00C…
  • Warning Line 783, Column 344: cannot generate system identifier for general entity "g"
    …71779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&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 783, Column 344: general entity "g" not defined and no default entity
    …71779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&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.

  • Warning Line 783, Column 345: reference not terminated by REFC delimiter
    …1779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFF…

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

  • Warning Line 783, Column 345: reference to external entity in attribute value
    …1779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFF…

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

  • Error Line 783, Column 345: reference to entity "g" for which no system identifier could be generated
    …1779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&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 783, Column 343: entity was defined here
    …971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=F…
  • Warning Line 783, Column 353: cannot generate system identifier for general entity "j"
    …b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&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 783, Column 353: general entity "j" not defined and no default entity
    …b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&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.

  • Warning Line 783, Column 354: reference not terminated by REFC delimiter
    …=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/…

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

  • Warning Line 783, Column 354: reference to external entity in attribute value
    …=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/…

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

  • Error Line 783, Column 354: reference to entity "j" for which no system identifier could be generated
    …=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&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.

  • Info Line 783, Column 352: entity was defined here
    …&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1…
  • Warning Line 783, Column 362: cannot generate system identifier for general entity "k"
    …C00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed …

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

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

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

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

  • Error Line 783, Column 362: general entity "k" not defined and no default entity
    …C00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed …

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

  • Warning Line 783, Column 363: reference not terminated by REFC delimiter
    …00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed i…

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

  • Warning Line 783, Column 363: reference to external entity in attribute value
    …00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed i…

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

  • Error Line 783, Column 363: reference to entity "k" for which no system identifier could be generated
    …00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed i…

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

  • Info Line 783, Column 361: entity was defined here
    …CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed…
  • Warning Line 783, Column 371: cannot generate system identifier for general entity "m"
    …66666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_1…

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

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

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

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

  • Error Line 783, Column 371: general entity "m" not defined and no default entity
    …66666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_1…

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

  • Warning Line 783, Column 372: reference not terminated by REFC delimiter
    …6666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_13…

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

  • Warning Line 783, Column 372: reference to external entity in attribute value
    …6666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_13…

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

  • Error Line 783, Column 372: reference to entity "m" for which no system identifier could be generated
    …6666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_13…

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

  • Info Line 783, Column 370: entity was defined here
    …666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_…
  • Warning Line 783, Column 380: cannot generate system identifier for general entity "n"
    …6&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_1336971779…

    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 783, Column 380: general entity "n" not defined and no default entity
    …6&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_1336971779…

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

  • Warning Line 783, Column 381: reference not terminated by REFC delimiter
    …&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_13369717794…

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

  • Warning Line 783, Column 381: reference to external entity in attribute value
    …&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_13369717794…

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

  • Error Line 783, Column 381: reference to entity "n" for which no system identifier could be generated
    …&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_13369717794…

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

  • Info Line 783, Column 379: entity was defined here
    …46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_133697177…
  • Warning Line 783, Column 389: cannot generate system identifier for general entity "s"
    …C&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_1336971779477" src=…

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

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

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

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

  • Error Line 783, Column 389: general entity "s" not defined and no default entity
    …C&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_1336971779477" src=…

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

  • Warning Line 783, Column 390: reference not terminated by REFC delimiter
    …&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_1336971779477" src="…

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

  • Warning Line 783, Column 390: reference to external entity in attribute value
    …&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_1336971779477" src="…

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

  • Error Line 783, Column 390: reference to entity "s" for which no system identifier could be generated
    …&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_1336971779477" src="…

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

  • Info Line 783, Column 388: entity was defined here
    …CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_1336971779477" src…
  • Error Line 783, Column 405: there is no attribute "id"
    …666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_1336971779477" src="http://gratisno…

    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 783, Column 429: there is no attribute "src"
    …1"/><embed id="emb_1336971779477" src="http://gratisnovelas-chat.chatango.com/…

    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 783, Column 482: there is no attribute "width"
    …ovelas-chat.chatango.com/group" width="250" height="400" allowScriptAccess="al…

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

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

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

  • Error Line 783, Column 495: there is no attribute "height"
    …hatango.com/group" width="250" height="400" allowScriptAccess="always" allowNe…

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

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

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

  • Error Line 783, Column 519: there is no attribute "allowScriptAccess"
    …="250" height="400" 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 783, Column 544: 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 783, Column 555: 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 783, Column 603: there is no attribute "allowFullScreen"
    …on/x-shockwave-flash" allowFullScreen="true" flashvars="cid=1336971779477&b=10…

    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 783, Column 620: there is no attribute "flashvars"
    …ash" allowFullScreen="true" flashvars="cid=1336971779477&b=100&c=CC00CC&d=6666…

    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 783, Column 640: reference not terminated by REFC delimiter
    …="true" flashvars="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=3…

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

  • Warning Line 783, Column 640: reference to external entity in attribute value
    …="true" flashvars="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=3…

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

  • Error Line 783, Column 640: reference to entity "b" for which no system identifier could be generated
    …="true" flashvars="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=3…

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

  • Info Line 783, Column 314: entity was defined here
    …e="flashvars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j…
  • Warning Line 783, Column 646: reference not terminated by REFC delimiter
    …" flashvars="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&…

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

  • Warning Line 783, Column 646: reference to external entity in attribute value
    …" flashvars="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&…

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

  • Error Line 783, Column 646: reference to entity "c" for which no system identifier could be generated
    …" flashvars="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&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 783, Column 320: entity was defined here
    …shvars" value="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=33333…
  • Warning Line 783, Column 655: reference not terminated by REFC delimiter
    …rs="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&…

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

  • Warning Line 783, Column 655: reference to external entity in attribute value
    …rs="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&…

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

  • Error Line 783, Column 655: reference to entity "d" for which no system identifier could be generated
    …rs="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&…

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

  • Info Line 783, Column 329: entity was defined here
    …alue="cid=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=66666…
  • Warning Line 783, Column 664: reference not terminated by REFC delimiter
    …336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&…

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

  • Warning Line 783, Column 664: reference to external entity in attribute value
    …336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&…

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

  • Error Line 783, Column 664: reference to entity "f" for which no system identifier could be generated
    …336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&…

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

  • Info Line 783, Column 338: entity was defined here
    …=1336971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00C…
  • Warning Line 783, Column 669: reference not terminated by REFC delimiter
    …1779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFF…

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

  • Warning Line 783, Column 669: reference to external entity in attribute value
    …1779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFF…

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

  • Error Line 783, Column 669: reference to entity "g" for which no system identifier could be generated
    …1779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&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 783, Column 343: entity was defined here
    …971779477&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=F…
  • Warning Line 783, Column 678: reference not terminated by REFC delimiter
    …=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1">…

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

  • Warning Line 783, Column 678: reference to external entity in attribute value
    …=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1">…

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

  • Error Line 783, Column 678: reference to entity "j" for which no system identifier could be generated
    …=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&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.

  • Info Line 783, Column 352: entity was defined here
    …&b=100&c=CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1…
  • Warning Line 783, Column 687: reference not terminated by REFC delimiter
    …00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"></embed><…

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

  • Warning Line 783, Column 687: reference to external entity in attribute value
    …00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"></embed><…

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

  • Error Line 783, Column 687: reference to entity "k" for which no system identifier could be generated
    …00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"></embed><…

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

  • Info Line 783, Column 361: entity was defined here
    …CC00CC&d=666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed…
  • Warning Line 783, Column 696: reference not terminated by REFC delimiter
    …6666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"></embed></object> …

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

  • Warning Line 783, Column 696: reference to external entity in attribute value
    …6666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"></embed></object> …

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

  • Error Line 783, Column 696: reference to entity "m" for which no system identifier could be generated
    …6666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"></embed></object> …

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

  • Info Line 783, Column 370: entity was defined here
    …666666&f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_…
  • Warning Line 783, Column 705: reference not terminated by REFC delimiter
    …f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"></embed></object> </div>

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

  • Warning Line 783, Column 705: reference to external entity in attribute value
    …f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"></embed></object> </div>

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

  • Error Line 783, Column 705: reference to entity "n" for which no system identifier could be generated
    …f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"></embed></object> </div>

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

  • Info Line 783, Column 379: entity was defined here
    …46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_133697177…
  • Warning Line 783, Column 714: reference not terminated by REFC delimiter
    …f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"></embed></object> </div>

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

  • Warning Line 783, Column 714: reference to external entity in attribute value
    …f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"></embed></object> </div>

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

  • Error Line 783, Column 714: reference to entity "s" for which no system identifier could be generated
    …f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"></embed></object> </div>

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

  • Info Line 783, Column 388: entity was defined here
    …CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"/><embed id="emb_1336971779477" src…
  • Error Line 783, Column 717: element "embed" undefined
    …f=46&g=CC00CC&j=333333&k=666666&m=CC00CC&n=FFFFFF&s=1"></embed></object> </div>

    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 786, Column 10: ID "categoria-titulo" already defined
    <div id="categoria-titulo">Facebook</div>

    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 773, Column 10: ID "categoria-titulo" first defined here
    <div id="categoria-titulo">Telenovelas Completas [FIN]</div>
  • Error Line 791, Column 10: ID "categoria-titulo" already defined
    <div id="categoria-titulo">Tags Mas Buscados:</div>

    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 773, Column 10: ID "categoria-titulo" first defined here
    <div id="categoria-titulo">Telenovelas Completas [FIN]</div>
  • Error Line 797, Column 10: ID "categoria-titulo" already defined
    <div id="categoria-titulo">Nueva Telenovela</div>

    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 773, Column 10: ID "categoria-titulo" first defined here
    <div id="categoria-titulo">Telenovelas Completas [FIN]</div>
  • Error Line 803, Column 10: ID "categoria-titulo" already defined
    <div id="categoria-titulo">Ultimo video</div>

    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 773, Column 10: ID "categoria-titulo" first defined here
    <div id="categoria-titulo">Telenovelas Completas [FIN]</div>
  • Error Line 808, Column 10: ID "categoria-titulo" already defined
    <div id="categoria-titulo">Avances</div>

    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 773, Column 10: ID "categoria-titulo" first defined here
    <div id="categoria-titulo">Telenovelas Completas [FIN]</div>
  • Error Line 814, Column 17: document type does not allow element "div" here
    <div id="footer">

    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 816, Column 8: element "string" undefined
    <string>Telenovelas Online</string>, <string>Telenovelas Mexicanas</string>, <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 816, Column 45: element "string" undefined
    …g>Telenovelas Online</string>, <string>Telenovelas Mexicanas</string>, <string…

    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 816, Column 85: element "string" undefined
    …elenovelas Mexicanas</string>, <string>Telenovelas Españolas</string>, <string…

    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 816, Column 125: element "string" undefined
    …elenovelas Españolas</string>, <string>Telenovelas Argentinas</string>, <strin…

    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 816, Column 166: element "string" undefined
    …lenovelas Argentinas</string>, <string>Ver telenovelas gratis</string>, <strin…

    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 816, Column 207: element "string" undefined
    …r telenovelas gratis</string>, <string>Telenovelas Colombianas</string> @GRATI…

    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 820, Column 117: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"
    …atomy/790.php" width="728" height="90" frameborder="0" scrolling="No"></iframe>

    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 823, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

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

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

  • Warning Line 830, Column 29: character "&" is the first character of a delimiter but occurred as data
    return (document.compatMode && document.compatMode!="BackCompat")? document.doc…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 830, Column 30: character "&" is the first character of a delimiter but occurred as data
    return (document.compatMode && document.compatMode!="BackCompat")? document.doc…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 901, Column 76: document type does not allow element "div" here
    <div style='display: scroll; position: fixed; bottom: 350px; right: 150px;'>

    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 904, Column 215: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"
    …flech" alt="Cerrar" title="Cerrar" width="24" align="absmiddle" height="24" /> 

    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 906, Column 379: there is no attribute "allowtransparency"
    … overflow:hidden; width:100px; height:65px;" allowtransparency="true"></iframe>

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

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

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

  • Error Line 909, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    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 921, Column 40: document type does not allow element "script" here
    </script><script type='text/javascript'>

    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 928, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    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 932, Column 89: document type does not allow element "script" here
    …javascript" src="http://resources.infolinks.com/js/infolinks_main.js"></script>

    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 933, Column 68: required attribute "type" not specified
    		<script src="http://cf.ads.kontextua.com/container/tags/13885.js"></script>

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

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

  • Error Line 933, Column 68: document type does not allow element "script" here
    		<script src="http://cf.ads.kontextua.com/container/tags/13885.js"></script>

    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 936, Column 7: end tag for element "body" which is not open
    </body>

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

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

Visitor Analysis

Daily Visitor
  • 6.767 visits

In Page Analysis