Anime, Series y Peliculas en Linea en Alta Calidad y sin Restricciones, completamente gratis ...

mundonlinetv.com
  • Domain Name
    mundonlinetv.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #83481
  • Page Size
    117.2 KB
  • Ip Address
    108.162.198.91
  • Heading
    H1: 38, H2: 7, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 50 JPG, 6 PNG

Website Meta Analysis

  • Title
    Anime|Mundo Online
  • Meta Keyword
    anime, anime online, todos los animes, naruto shippuden, bleach, one piece, animeid, animeflv, todoanimes, ao no exorcist
  • Meta Description
    Anime, Series y Peliculas en Linea en Alta Calidad y sin Restricciones, completamente gratis

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.198.91
  • Domain Age
    1 Years, 11 Months, 0 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: cloudflare-nginx
  • date: Thu, 28 Feb 2013 18:57:11 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.3.21
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • cf-ray: 47fd4eab19b043d
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for mundonlinetv.com

IP 108.162.198.91 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 178 Errors
  • 54 Warnings
Ratio Text/Html
  • 0.7758624998958585
Message Error
  • Error Line 5, Column 16: there is no attribute "property"
    <meta property="og:title" content="Anime" />

    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 17, Column 51: end tag for "link" omitted, but OMITTAG NO was specified
    <link href='/img/favicon.ico' rel='shortcut icon'>

    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 17, Column 1: start tag was here
    <link href='/img/favicon.ico' rel='shortcut icon'>
  • Error Line 18, Column 7: end tag for element "link" which is not open
    </link>

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

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

  • Warning Line 31, Column 98: cannot generate system identifier for general entity "id"
    …"no" src="/java/play.php?mf='+video+'&id=2513&sub=,ES&sub_pre=ES" frameborder=…

    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 31, Column 98: general entity "id" not defined and no default entity
    …"no" src="/java/play.php?mf='+video+'&id=2513&sub=,ES&sub_pre=ES" frameborder=…

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

  • Warning Line 31, Column 100: reference not terminated by REFC delimiter
    …o" src="/java/play.php?mf='+video+'&id=2513&sub=,ES&sub_pre=ES" frameborder="0…

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

  • Warning Line 31, Column 100: reference to external entity in attribute value
    …o" src="/java/play.php?mf='+video+'&id=2513&sub=,ES&sub_pre=ES" frameborder="0…

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

  • Error Line 31, Column 100: reference to entity "id" for which no system identifier could be generated
    …o" src="/java/play.php?mf='+video+'&id=2513&sub=,ES&sub_pre=ES" frameborder="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 31, Column 97: entity was defined here
    …="no" src="/java/play.php?mf='+video+'&id=2513&sub=,ES&sub_pre=ES" frameborder…
  • Warning Line 31, Column 109: reference not terminated by REFC delimiter
    …java/play.php?mf='+video+'&id=2513&sub=,ES&sub_pre=ES" frameborder="0" allowfu…

    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 31, Column 114: cannot generate system identifier for general entity "sub_pre"
    …play.php?mf='+video+'&id=2513&sub=,ES&sub_pre=ES" frameborder="0" allowfullscr…

    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 31, Column 114: general entity "sub_pre" not defined and no default entity
    …play.php?mf='+video+'&id=2513&sub=,ES&sub_pre=ES" frameborder="0" allowfullscr…

    This is usually a cascading error caused by 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 31, Column 121: reference not terminated by REFC delimiter
    …p?mf='+video+'&id=2513&sub=,ES&sub_pre=ES" frameborder="0" allowfullscreen></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 31, Column 121: reference to external entity in attribute value
    …p?mf='+video+'&id=2513&sub=,ES&sub_pre=ES" frameborder="0" allowfullscreen></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 31, Column 121: reference to entity "sub_pre" for which no system identifier could be generated
    …p?mf='+video+'&id=2513&sub=,ES&sub_pre=ES" frameborder="0" allowfullscreen></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 31, Column 113: entity was defined here
    …/play.php?mf='+video+'&id=2513&sub=,ES&sub_pre=ES" frameborder="0" allowfullsc…
  • Error Line 31, Column 157: "allowfullscreen" is not a member of a group specified for any attribute
    …deo+'&id=2513&sub=,ES&sub_pre=ES" frameborder="0" allowfullscreen></iframe>');}
  • Error Line 31, Column 157: document type does not allow element "iframe" here
    …deo+'&id=2513&sub=,ES&sub_pre=ES" frameborder="0" allowfullscreen></iframe>');}

    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 36, Column 126: document type does not allow element "iframe" here
    …src="/server/java/play.php?1f='+video+'" width="640" height="412"></iframe>');}

    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 41, Column 127: document type does not allow element "iframe" here
    …rc="/server/stream/mp4.php?sh='+video+'" width="640" height="412"></iframe>');}

    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 46, Column 127: document type does not allow element "iframe" here
    …rc="/server/stream/flv.php?sh='+video+'" width="640" height="412"></iframe>');}

    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 51, Column 127: document type does not allow element "iframe" here
    …rc="/server/stream/mp41.php?s='+video+'" width="640" height="412"></iframe>');}

    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 56, Column 127: document type does not allow element "iframe" here
    …rc="/server/stream/flv1.php?s='+video+'" width="640" height="412"></iframe>');}

    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 61, Column 129: document type does not allow element "iframe" here
    …="/server/stream/videox.php?x='+video+'" width="640" height="412"></iframe>');}

    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 66, Column 126: document type does not allow element "iframe" here
    …src="/server/stream/yr.php?yr='+video+'" width="640" height="412"></iframe>');}

    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 71, Column 127: document type does not allow element "iframe" here
    …rc="/server/java/play.php?180='+video+'" width="640" height="412"></iframe>');}

    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 76, Column 131: document type does not allow element "iframe" here
    …/server/gkplugins/play.php?pk='+video+'" width="640" height="412"></iframe>');}

    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 81, Column 131: document type does not allow element "iframe" here
    …/server/gkplugins/play.php?zp='+video+'" width="640" height="412"></iframe>');}

    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 86, Column 127: document type does not allow element "iframe" here
    …rc="/server/stream/play.php?x='+video+'" width="640" height="412"></iframe>');}

    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 91, Column 46: there is no attribute "type"
    …t.write('<iframe src="'+video+'" type="text/html" allowfullscreen="true" frame…

    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 91, Column 74: there is no attribute "allowfullscreen"
    …o+'" type="text/html" allowfullscreen="true" frameborder="0" height="412" scro…

    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 91, Column 136: document type does not allow element "iframe" here
    …en="true" frameborder="0" height="412" scrolling="no" width="640"></iframe>');}

    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 96, Column 99: cannot generate system identifier for general entity "reproductor"
    …src="/server/yahoo.php?vidatraslapc=1&reproductor='+video+'" width="640" heigh…

    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 96, Column 99: general entity "reproductor" not defined and no default entity
    …src="/server/yahoo.php?vidatraslapc=1&reproductor='+video+'" width="640" heigh…

    This is usually a cascading error caused by 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 96, Column 110: reference not terminated by REFC delimiter
    …r/yahoo.php?vidatraslapc=1&reproductor='+video+'" width="640" height="380"></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 96, Column 110: reference to external entity in attribute value
    …r/yahoo.php?vidatraslapc=1&reproductor='+video+'" width="640" height="380"></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 96, Column 110: reference to entity "reproductor" for which no system identifier could be generated
    …r/yahoo.php?vidatraslapc=1&reproductor='+video+'" width="640" height="380"></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 96, Column 98: entity was defined here
    … src="/server/yahoo.php?vidatraslapc=1&reproductor='+video+'" width="640" heig…
  • Error Line 96, Column 146: document type does not allow element "iframe" here
    …hp?vidatraslapc=1&reproductor='+video+'" width="640" height="380"></iframe>');}

    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 101, Column 112: reference not terminated by REFC delimiter
    …youtube.php?vidatraslapc=1&reproductor=http://www.youtube.com/watch?v='+video+…

    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 101, Column 112: reference to external entity in attribute value
    …youtube.php?vidatraslapc=1&reproductor=http://www.youtube.com/watch?v='+video+…

    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 101, Column 112: reference to entity "reproductor" for which no system identifier could be generated
    …youtube.php?vidatraslapc=1&reproductor=http://www.youtube.com/watch?v='+video+…

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

  • Info Line 96, Column 98: entity was defined here
    … src="/server/yahoo.php?vidatraslapc=1&reproductor='+video+'" width="640" heig…
  • Error Line 101, Column 179: document type does not allow element "iframe" here
    …ttp://www.youtube.com/watch?v='+video+'" width="640" height="412"></iframe>');}

    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 106, Column 30: there is no attribute "width"
    document.write('<embed width="640" height="360" allowfullscreen="true" src="htt…

    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 106, Column 43: there is no attribute "height"
    …ment.write('<embed width="640" height="360" allowfullscreen="true" src="http:/…

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

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

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

  • Error Line 106, Column 65: there is no attribute "allowfullscreen"
    …th="640" height="360" allowfullscreen="true" src="http://www.vxv.com/styles/la…

    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 106, Column 76: there is no attribute "src"
    …ight="360" allowfullscreen="true" src="http://www.vxv.com/styles/layout/swf/pl…

    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 106, Column 179: cannot generate system identifier for general entity "streamer"
    …w.vxv.com/styles/default/conf/vxv.xml&streamer=rtmp://stream.vxv.com/vod/vxv&f…

    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 106, Column 179: general entity "streamer" not defined and no default entity
    …w.vxv.com/styles/default/conf/vxv.xml&streamer=rtmp://stream.vxv.com/vod/vxv&f…

    This is usually a cascading error caused by 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 106, Column 187: reference not terminated by REFC delimiter
    …m/styles/default/conf/vxv.xml&streamer=rtmp://stream.vxv.com/vod/vxv&file=flv:…

    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 106, Column 187: reference to external entity in attribute value
    …m/styles/default/conf/vxv.xml&streamer=rtmp://stream.vxv.com/vod/vxv&file=flv:…

    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 106, Column 187: reference to entity "streamer" for which no system identifier could be generated
    …m/styles/default/conf/vxv.xml&streamer=rtmp://stream.vxv.com/vod/vxv&file=flv:…

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

  • Info Line 106, Column 178: entity was defined here
    …ww.vxv.com/styles/default/conf/vxv.xml&streamer=rtmp://stream.vxv.com/vod/vxv&…
  • Warning Line 106, Column 218: cannot generate system identifier for general entity "file"
    …treamer=rtmp://stream.vxv.com/vod/vxv&file=flv:vod/data/media/'+video+'&image=…

    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 106, Column 218: general entity "file" not defined and no default entity
    …treamer=rtmp://stream.vxv.com/vod/vxv&file=flv:vod/data/media/'+video+'&image=…

    This is usually a cascading error caused by 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 106, Column 222: reference not terminated by REFC delimiter
    …mer=rtmp://stream.vxv.com/vod/vxv&file=flv:vod/data/media/'+video+'&image=http…

    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 106, Column 222: reference to external entity in attribute value
    …mer=rtmp://stream.vxv.com/vod/vxv&file=flv:vod/data/media/'+video+'&image=http…

    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 106, Column 222: reference to entity "file" for which no system identifier could be generated
    …mer=rtmp://stream.vxv.com/vod/vxv&file=flv:vod/data/media/'+video+'&image=http…

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

  • Info Line 106, Column 217: entity was defined here
    …streamer=rtmp://stream.vxv.com/vod/vxv&file=flv:vod/data/media/'+video+'&image…
  • Warning Line 106, Column 257: reference not terminated by REFC delimiter
    …ile=flv:vod/data/media/'+video+'&image=https://lh6.googleusercontent.com/-pbQS…

    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 106, Column 381: cannot generate system identifier for general entity "backcolor"
    …35/portada%2520firefox%2520chrome.jpg&backcolor=000000&frontcolor=FFFFFF&light…

    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 106, Column 381: general entity "backcolor" not defined and no default entity
    …35/portada%2520firefox%2520chrome.jpg&backcolor=000000&frontcolor=FFFFFF&light…

    This is usually a cascading error caused by 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 106, Column 390: reference not terminated by REFC delimiter
    …a%2520firefox%2520chrome.jpg&backcolor=000000&frontcolor=FFFFFF&lightcolor=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 106, Column 390: reference to external entity in attribute value
    …a%2520firefox%2520chrome.jpg&backcolor=000000&frontcolor=FFFFFF&lightcolor=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 106, Column 390: reference to entity "backcolor" for which no system identifier could be generated
    …a%2520firefox%2520chrome.jpg&backcolor=000000&frontcolor=FFFFFF&lightcolor=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 106, Column 380: entity was defined here
    …635/portada%2520firefox%2520chrome.jpg&backcolor=000000&frontcolor=FFFFFF&ligh…
  • Warning Line 106, Column 398: cannot generate system identifier for general entity "frontcolor"
    …refox%2520chrome.jpg&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&scre…

    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 106, Column 398: general entity "frontcolor" not defined and no default entity
    …refox%2520chrome.jpg&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&scre…

    This is usually a cascading error caused by 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 106, Column 408: reference not terminated by REFC delimiter
    …chrome.jpg&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=00…

    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 106, Column 408: reference to external entity in attribute value
    …chrome.jpg&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=00…

    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 106, Column 408: reference to entity "frontcolor" for which no system identifier could be generated
    …chrome.jpg&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=00…

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

  • Info Line 106, Column 397: entity was defined here
    …irefox%2520chrome.jpg&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&scr…
  • Warning Line 106, Column 416: cannot generate system identifier for general entity "lightcolor"
    …pg&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=000000"/>'…

    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 106, Column 416: general entity "lightcolor" not defined and no default entity
    …pg&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=000000"/>'…

    This is usually a cascading error caused by 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 106, Column 426: reference not terminated by REFC delimiter
    …&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=000000"/>');}

    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 106, Column 426: reference to external entity in attribute value
    …&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=000000"/>');}

    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 106, Column 426: reference to entity "lightcolor" for which no system identifier could be generated
    …&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=000000"/>');}

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

  • Info Line 106, Column 415: entity was defined here
    …jpg&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=000000"/>…
  • Warning Line 106, Column 434: cannot generate system identifier for general entity "screencolor"
    …&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=000000"/>');}

    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 106, Column 434: general entity "screencolor" not defined and no default entity
    …&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=000000"/>');}

    This is usually a cascading error caused by 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 106, Column 445: reference not terminated by REFC delimiter
    …&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=000000"/>');}

    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 106, Column 445: reference to external entity in attribute value
    …&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=000000"/>');}

    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 106, Column 445: reference to entity "screencolor" for which no system identifier could be generated
    …&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=000000"/>');}

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

  • Info Line 106, Column 433: entity was defined here
    …&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=000000"/>');}
  • Error Line 106, Column 454: element "embed" undefined
    …&backcolor=000000&frontcolor=FFFFFF&lightcolor=FFFFFF&screencolor=000000"/>');}

    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 111, Column 131: document type does not allow element "iframe" here
    …/server/stream/twitvid.php?tw='+video+'" width="640" height="412"></iframe>');}

    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 116, Column 132: document type does not allow element "iframe" here
    …server/stream/twitvid.php?tw2='+video+'" width="640" height="412"></iframe>');}

    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 121, Column 175: document type does not allow element "iframe" here
    …dia/embed.aspx/m='+video+',t=1,mt=video" width="640" height="380"></iframe>');}

    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 126, Column 65: there is no attribute "allownetworking"
    …th="640" height="380" allownetworking="internal" allowfullscreen="true" wmode=…

    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 126, Column 105: there is no attribute "wmode"
    …nternal" allowfullscreen="true" wmode="transparent" type="application/x-shockw…

    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 126, Column 124: there is no attribute "type"
    …creen="true" wmode="transparent" type="application/x-shockwave-flash" src="htt…

    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 126, Column 195: element "embed" undefined
    …pe="application/x-shockwave-flash" src="http://video.rutube.ru/'+video+'"/>');}

    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 131, Column 204: document type does not allow element "iframe" here
    …en="true" frameborder="0" height="380" scrolling="no" width="640"></iframe>');}

    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 137, Column 128: reference not terminated by REFC delimiter
    …acebook.php?vidatraslapc=1&reproductor='+video+'&megavideo='+megavideo+'" widt…

    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 137, Column 128: reference to external entity in attribute value
    …acebook.php?vidatraslapc=1&reproductor='+video+'&megavideo='+megavideo+'" widt…

    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 137, Column 128: reference to entity "reproductor" for which no system identifier could be generated
    …acebook.php?vidatraslapc=1&reproductor='+video+'&megavideo='+megavideo+'" widt…

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

  • Info Line 96, Column 98: entity was defined here
    … src="/server/yahoo.php?vidatraslapc=1&reproductor='+video+'" width="640" heig…
  • Warning Line 137, Column 139: cannot generate system identifier for general entity "megavideo"
    …?vidatraslapc=1&reproductor='+video+'&megavideo='+megavideo+'" width="640" hei…

    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 137, Column 139: general entity "megavideo" not defined and no default entity
    …?vidatraslapc=1&reproductor='+video+'&megavideo='+megavideo+'" width="640" hei…

    This is usually a cascading error caused by 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 137, Column 148: reference not terminated by REFC delimiter
    …lapc=1&reproductor='+video+'&megavideo='+megavideo+'" width="640" height="412"…

    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 137, Column 148: reference to external entity in attribute value
    …lapc=1&reproductor='+video+'&megavideo='+megavideo+'" width="640" height="412"…

    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 137, Column 148: reference to entity "megavideo" for which no system identifier could be generated
    …lapc=1&reproductor='+video+'&megavideo='+megavideo+'" width="640" height="412"…

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

  • Info Line 137, Column 138: entity was defined here
    …p?vidatraslapc=1&reproductor='+video+'&megavideo='+megavideo+'" width="640" he…
  • Error Line 137, Column 188: document type does not allow element "iframe" here
    …uctor='+video+'&megavideo='+megavideo+'" width="640" height="412"></iframe>');}

    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 169, Column 23: document type does not allow element "style" here
    <style type='text/css'>

    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 174, Column 524: required attribute "alt" not specified
    …AAFTM/d6jD5rQAxAc/s1600/install.jpg" /></a></div><div style="float:left;margin…

    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 174, Column 835: required attribute "alt" not specified
    …AAAAAFTA/etNLe5K4mEM/s400/cerravlc.jpg" /></a></div></div></div><!-- Header -->

    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 184, Column 147: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …09864&amp;type=1&amp;relevant_count=1"><img border="0" src="/img/cabezera/head…

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

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

  • Error Line 184, Column 198: required attribute "alt" not specified
    …1&amp;relevant_count=1"><img border="0" src="/img/cabezera/header36.jpg" /></a>

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

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

  • Error Line 206, Column 469: there is no attribute "allowTransparency"
    …block;float:left;margin:3px;margin-top:6px;" 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 244, Column 150: there is no attribute "border"
    …" name="Pub160" scrolling="no" border="0" frameborder="0" height="600"></ifram…

    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 268, Column 16: document type does not allow element "html" here
              <html>

    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 268, Column 11: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
              <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 271, Column 78: required attribute "type" not specified
    …src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.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 272, Column 52: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <script src="/barra/jquery.galleryview-1.1.js"type=text/javascript></script>
  • Error Line 272, Column 57: NET-enabling start-tag not immediately followed by null end-tag
    <script src="/barra/jquery.galleryview-1.1.js"type=text/javascript></script>

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

  • Error Line 272, Column 76: end tag for element "script" which is not open
    <script src="/barra/jquery.galleryview-1.1.js"type=text/javascript></script>

    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 273, Column 49: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <script src="/barra/jquery.timers-1.1.2.js"type=text/javascript></script>
  • Error Line 273, Column 54: NET-enabling start-tag not immediately followed by null end-tag
    <script src="/barra/jquery.timers-1.1.2.js"type=text/javascript></script>

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

  • Error Line 273, Column 73: end tag for element "script" which is not open
    <script src="/barra/jquery.timers-1.1.2.js"type=text/javascript></script>

    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 310, Column 12: there is no attribute "class"
    <DIV class=galleryview id=photos align=center>

    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 310, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <DIV class=galleryview id=photos align=center>
  • Error Line 310, Column 27: there is no attribute "id"
    <DIV class=galleryview id=photos align=center>

    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 310, Column 27: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <DIV class=galleryview id=photos align=center>
  • Error Line 310, Column 40: there is no attribute "align"
    <DIV class=galleryview id=photos align=center>

    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 310, Column 40: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <DIV class=galleryview id=photos align=center>
  • Error Line 310, Column 46: element "DIV" undefined
    <DIV class=galleryview id=photos align=center>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 311, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <DIV class=panel><IMG src="/img/barra/one-piece.jpg" alt="one piece" width="5…
  • Error Line 311, Column 19: element "DIV" undefined
      <DIV class=panel><IMG src="/img/barra/one-piece.jpg" alt="one piece" width="5…

    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 311, Column 29: there is no attribute "src"
      <DIV class=panel><IMG src="/img/barra/one-piece.jpg" alt="one piece" width="5…

    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 311, Column 60: there is no attribute "alt"
    …l><IMG src="/img/barra/one-piece.jpg" alt="one piece" width="520" height="200">

    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 311, Column 78: there is no attribute "width"
    …l><IMG src="/img/barra/one-piece.jpg" alt="one piece" width="520" height="200">

    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 311, Column 91: there is no attribute "height"
    …l><IMG src="/img/barra/one-piece.jpg" alt="one piece" width="520" height="200">

    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 311, Column 96: element "IMG" undefined
    …l><IMG src="/img/barra/one-piece.jpg" alt="one piece" width="520" height="200">

    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 312, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <DIV class=panel-overlay>
  • Error Line 312, Column 29: element "DIV" undefined
        <DIV class=panel-overlay>

    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 313, Column 17: there is no attribute "align"
          <H2 align=center class="Estilo4">One Piece Cap. 585</H2>

    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 313, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <H2 align=center class="Estilo4">One Piece Cap. 585</H2>
  • Error Line 313, Column 30: there is no attribute "class"
          <H2 align=center class="Estilo4">One Piece Cap. 585</H2>

    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 313, Column 39: element "H2" undefined
          <H2 align=center class="Estilo4">One Piece Cap. 585</H2>

    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 315, Column 8: end tag for "IMG" omitted, but OMITTAG NO was specified
      </DIV>

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

  • Info Line 311, Column 20: start tag was here
      <DIV class=panel><IMG src="/img/barra/one-piece.jpg" alt="one piece" width="5…
  • Error Line 316, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <DIV class=panel><img src="https://lh4.googleusercontent.com/-5d2FfO2YrEM/Twl…
  • Error Line 316, Column 19: element "DIV" undefined
      <DIV class=panel><img src="https://lh4.googleusercontent.com/-5d2FfO2YrEM/Twl…

    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 316, Column 180: end tag for "img" omitted, but OMITTAG NO was specified
    …69rv5_sEt9c/s645/shippuden.jpg" alt="naruto shipuden" width="520" height="200">

    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 316, Column 20: start tag was here
      <DIV class=panel><img src="https://lh4.googleusercontent.com/-5d2FfO2YrEM/Twl…
  • Error Line 317, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <DIV class=panel-overlay>
  • Error Line 317, Column 29: element "DIV" undefined
        <DIV class=panel-overlay>

    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 318, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <H2 align=center class="Estilo4">Naruto Shippuden Cap. 301</H2>
  • Error Line 318, Column 39: element "H2" undefined
          <H2 align=center class="Estilo4">Naruto Shippuden Cap. 301</H2>

    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 321, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <DIV class=panel><img src="/img/barra/fairy-tail.jpg" alt="fairy tail" width=…
  • Error Line 321, Column 19: element "DIV" undefined
      <DIV class=panel><img src="/img/barra/fairy-tail.jpg" alt="fairy tail" width=…

    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 321, Column 99: end tag for "img" omitted, but OMITTAG NO was specified
    …<img src="/img/barra/fairy-tail.jpg" alt="fairy tail" width="520" height="200">

    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 321, Column 20: start tag was here
      <DIV class=panel><img src="/img/barra/fairy-tail.jpg" alt="fairy tail" width=…
  • Error Line 322, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <DIV class=panel-overlay>
  • Error Line 322, Column 29: element "DIV" undefined
        <DIV class=panel-overlay>

    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 323, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <H2 align=center class="Estilo4">Fairy Tail Cap 170</H2>
  • Error Line 323, Column 39: element "H2" undefined
          <H2 align=center class="Estilo4">Fairy Tail Cap 170</H2>

    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 326, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <DIV class=panel><img src="/img/barra/saint-seiya-omega.jpg" alt="Saint Seiya…
  • Error Line 326, Column 19: element "DIV" undefined
      <DIV class=panel><img src="/img/barra/saint-seiya-omega.jpg" alt="Saint Seiya…

    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 326, Column 113: end tag for "img" omitted, but OMITTAG NO was specified
    …/barra/saint-seiya-omega.jpg" alt="Saint Seiya Omega" width="520" height="200">

    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 326, Column 20: start tag was here
      <DIV class=panel><img src="/img/barra/saint-seiya-omega.jpg" alt="Saint Seiya…
  • Error Line 327, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <DIV class=panel-overlay>
  • Error Line 327, Column 29: element "DIV" undefined
        <DIV class=panel-overlay>

    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 328, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <H2 align=center class="Estilo4">Saint Seiya Omega Cap 46</H2>
  • Error Line 328, Column 39: element "H2" undefined
          <H2 align=center class="Estilo4">Saint Seiya Omega Cap 46</H2>

    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 331, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <DIV class=panel><img src="https://lh3.googleusercontent.com/-D0KKgCcDZSI/TMI…
  • Error Line 331, Column 19: element "DIV" undefined
      <DIV class=panel><img src="https://lh3.googleusercontent.com/-D0KKgCcDZSI/TMI…

    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 331, Column 173: end tag for "img" omitted, but OMITTAG NO was specified
    …AAADEw/hdAWQBG9TOs/s645/bakuman2.jpg" alt="Bakuman 3" width="520" height="200">

    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 331, Column 20: start tag was here
      <DIV class=panel><img src="https://lh3.googleusercontent.com/-D0KKgCcDZSI/TMI…
  • Error Line 332, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <DIV class=panel-overlay>
  • Error Line 332, Column 29: element "DIV" undefined
        <DIV class=panel-overlay>

    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 333, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <H2 align=center class="Estilo4">Bakuman 3 Cap 21</H2>
  • Error Line 333, Column 39: element "H2" undefined
          <H2 align=center class="Estilo4">Bakuman 3 Cap 21</H2>

    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 336, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <DIV class=panel><img src="https://lh3.googleusercontent.com/-F3-2JPdZLNA/Tu5…
  • Error Line 336, Column 19: element "DIV" undefined
      <DIV class=panel><img src="https://lh3.googleusercontent.com/-F3-2JPdZLNA/Tu5…

    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 336, Column 186: end tag for "img" omitted, but OMITTAG NO was specified
    …jfojU/s655/hunter-x-hunter.jpg" alt="hunter x hunter" width="520" height="200">

    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 336, Column 20: start tag was here
      <DIV class=panel><img src="https://lh3.googleusercontent.com/-F3-2JPdZLNA/Tu5…
  • Error Line 337, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <DIV class=panel-overlay>
  • Error Line 337, Column 29: element "DIV" undefined
        <DIV class=panel-overlay>

    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 338, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <H2 align=center class="Estilo4">Hunter x Hunter 2011 Cap 68</H2>
  • Error Line 338, Column 39: element "H2" undefined
          <H2 align=center class="Estilo4">Hunter x Hunter 2011 Cap 68</H2>

    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 341, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <DIV class=panel><img src="https://lh3.googleusercontent.com/_PdhnD2S3AdE/Ta4…
  • Error Line 341, Column 19: element "DIV" undefined
      <DIV class=panel><img src="https://lh3.googleusercontent.com/_PdhnD2S3AdE/Ta4…

    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 341, Column 168: end tag for "img" omitted, but OMITTAG NO was specified
    …AAAAAAAADUo/U7uvEr9g5wI/12toriko.jpg" alt="Beelzebub" width="520" height="200">

    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 341, Column 20: start tag was here
      <DIV class=panel><img src="https://lh3.googleusercontent.com/_PdhnD2S3AdE/Ta4…
  • Error Line 342, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <DIV class=panel-overlay>
  • Error Line 342, Column 29: element "DIV" undefined
        <DIV class=panel-overlay>

    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 343, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <H2 align=center class="Estilo4">Toriko Cap 94</H2>
  • Error Line 343, Column 39: element "H2" undefined
          <H2 align=center class="Estilo4">Toriko Cap 94</H2>

    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 346, Column 13: there is no attribute "class"
      <UL class=filmstrip>

    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 346, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <UL class=filmstrip>
  • Error Line 346, Column 22: element "UL" undefined
      <UL class=filmstrip>

    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 347, Column 8: element "LI" undefined
        <LI><a href="/anime/one-piece.html" target="_parent"><img src="https://lh3.…

    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 347, Column 272: end tag for "img" omitted, but OMITTAG NO was specified
    … One Piece en HD" width="55" height="30" border="0" title="One Piece"></a></LI>

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

  • Info Line 347, Column 58: start tag was here
    …nime/one-piece.html" target="_parent"><img src="https://lh3.googleusercontent.…
  • Error Line 348, Column 8: element "LI" undefined
        <LI><a href="/anime/naruto-shippuden.html" target="_parent"><img src="http:…

    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 348, Column 253: end tag for "img" omitted, but OMITTAG NO was specified
    …den en HD" width="55" height="30" border="0" title="Naruto Shippuden"></a></LI>

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

  • Info Line 348, Column 65: start tag was here
    …ruto-shippuden.html" target="_parent"><img src="http://lh5.ggpht.com/_PdhnD2S3…
  • Error Line 349, Column 8: element "LI" undefined
        <LI><a href="/anime/fairy-tail.html" target="_parent"><img src="http://lh4.…

    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 349, Column 240: end tag for "img" omitted, but OMITTAG NO was specified
    …airy Tail en HD" width="55" height="30" border="0" title="Fairy Tail"></a></LI>

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

  • Info Line 349, Column 59: start tag was here
    …ime/fairy-tail.html" target="_parent"><img src="http://lh4.ggpht.com/_PdhnD2S3…
  • Error Line 350, Column 8: element "LI" undefined
        <LI><a href="/anime/saint-seiya-omega.html" target="_parent"><img src="/img…

    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 350, Column 212: end tag for "img" omitted, but OMITTAG NO was specified
    …ga en HD" width="55" height="30" border="0" title="Saint Seiya Omega"></a></LI>

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

  • Info Line 350, Column 66: start tag was here
    …nt-seiya-omega.html" target="_parent"><img src="/img/barra/saint-seiya-omega-l…
  • Error Line 351, Column 8: element "LI" undefined
        <LI><a href="/anime/bakuman-3.html" target="_parent"><img src="https://lh3.…

    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 351, Column 245: end tag for "img" omitted, but OMITTAG NO was specified
    …"VER Bakuman en HD" width="55" height="30" border="0" title="Bakuman"></a></LI>

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

  • Info Line 351, Column 58: start tag was here
    …nime/bakuman-3.html" target="_parent"><img src="https://lh3.googleusercontent.…
  • Error Line 352, Column 8: element "LI" undefined
        <LI><a href="/anime/hunter-x-hunter-2011.html" target="_parent"><img src="h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 352, Column 301: end tag for "img" omitted, but OMITTAG NO was specified
    …en HD" width="55" height="30" border="0" title="Hunter x Hunter 2011"></a></LI>

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

  • Info Line 352, Column 69: start tag was here
    …-x-hunter-2011.html" target="_parent"><img src="https://lh3.googleusercontent.…
  • Error Line 353, Column 8: element "LI" undefined
        <LI><a href="/anime/toriko.html" target="_parent"><img src="https://lh3.goo…

    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 353, Column 259: end tag for "img" omitted, but OMITTAG NO was specified
    …t="VER Toriko en HD" width="55" height="30" border="0" title="Toriko"></a></LI>

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

  • Info Line 353, Column 55: start tag was here
    …"/anime/toriko.html" target="_parent"><img src="https://lh3.googleusercontent.…
  • Error Line 523, Column 39: end tag for "a" omitted, but OMITTAG NO was specified
                Final Fantasy Vll Adve</h1>

    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 522, Column 32: start tag was here
              <div class="tt2"><h1><a href="http://www.mundonlinetv.com/ver/final-f…
  • Error Line 524, Column 16: end tag for element "a" which is not open
                </a></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 528, Column 39: end tag for "a" omitted, but OMITTAG NO was specified
                Final Fantasy Vll Last</h1>

    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 527, Column 32: start tag was here
              <div class="tt2"><h1><a href="http://www.mundonlinetv.com/ver/final-f…
  • Error Line 529, Column 16: end tag for element "a" which is not open
                </a></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 533, Column 34: end tag for "a" omitted, but OMITTAG NO was specified
                Inukami! Película</h1>

    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 532, Column 32: start tag was here
              <div class="tt2"><h1><a href="http://www.mundonlinetv.com/ver/inukami…
  • Error Line 534, Column 16: end tag for element "a" which is not open
                </a></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.

  • Warning Line 1647, Column 242: character "<" is the first character of a delimiter but occurred as data
    …e))});var h=Math.ceil(g.length/d);if(h<2)return this;var j=p('<div class="swCo…

    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 1647, Column 289: document type does not allow element "div" here
    … this;var j=p('<div class="swControls">');for(var i=0;i<h;i++){g.slice(i*d,(i+…

    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 1647, Column 308: character ";" not allowed in attribute specification list
    … class="swControls">');for(var i=0;i<h;i++){g.slice(i*d,(i+1)*d).wrapAll('<div…
  • Error Line 1647, Column 308: element "h" undefined
    … class="swControls">');for(var i=0;i<h;i++){g.slice(i*d,(i+1)*d).wrapAll('<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 1647, Column 1296: end tag for "h" omitted, but OMITTAG NO was specified
    …);a.appendTo('#mamain');jQuery('.swShowPage').tipsy({gravity: 's'})});</script>

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

  • Info Line 1647, Column 306: start tag was here
    …iv class="swControls">');for(var i=0;i<h;i++){g.slice(i*d,(i+1)*d).wrapAll('<d…
  • Error Line 1647, Column 1296: end tag for "div" omitted, but OMITTAG NO was specified
    …);a.appendTo('#mamain');jQuery('.swShowPage').tipsy({gravity: 's'})});</script>

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

  • Info Line 1647, Column 266: start tag was here
    …length/d);if(h<2)return this;var j=p('<div class="swControls">');for(var i=0;i…
  • Error Line 1661, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

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

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

  • Warning Line 1665, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=179574048740927";

    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 1665, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=179574048740927";

    This is usually a cascading error caused by 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 1665, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=179574048740927";

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

  • Error Line 1665, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=179574048740927";

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

  • Info Line 1665, Column 56: entity was defined here
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=179574048740927";
  • Warning Line 1669, Column 76: cannot generate system identifier for general entity "banned_pop_types"
    …ttp://ad.adnetwork.net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=…

    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 1669, Column 76: general entity "banned_pop_types" not defined and no default entity
    …ttp://ad.adnetwork.net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=…

    This is usually a cascading error caused by 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 1669, Column 92: reference not terminated by REFC delimiter
    …rk.net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=2564424&pop_time…

    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 1669, Column 92: reference to external entity in attribute value
    …rk.net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=2564424&pop_time…

    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 1669, Column 92: reference to entity "banned_pop_types" for which no system identifier could be generated
    …rk.net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=2564424&pop_time…

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

  • Info Line 1669, Column 75: entity was defined here
    …http://ad.adnetwork.net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section…
  • Warning Line 1669, Column 96: cannot generate system identifier for general entity "ad_size"
    …et/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=2564424&pop_times=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 1669, Column 96: general entity "ad_size" not defined and no default entity
    …et/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=2564424&pop_times=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 1669, Column 103: reference not terminated by REFC delimiter
    …d_type=pop&banned_pop_types=30&ad_size=0x0&section=2564424&pop_times=1&pop_fre…

    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 1669, Column 103: reference to external entity in attribute value
    …d_type=pop&banned_pop_types=30&ad_size=0x0&section=2564424&pop_times=1&pop_fre…

    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 1669, Column 103: reference to entity "ad_size" for which no system identifier could be generated
    …d_type=pop&banned_pop_types=30&ad_size=0x0&section=2564424&pop_times=1&pop_fre…

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

  • Info Line 1669, Column 95: entity was defined here
    …net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=2564424&pop_times=1…
  • Warning Line 1669, Column 108: cannot generate system identifier for general entity "section"
    …e=pop&banned_pop_types=30&ad_size=0x0&section=2564424&pop_times=1&pop_frequenc…

    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 1669, Column 108: general entity "section" not defined and no default entity
    …e=pop&banned_pop_types=30&ad_size=0x0&section=2564424&pop_times=1&pop_frequenc…

    This is usually a cascading error caused by 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 1669, Column 115: reference not terminated by REFC delimiter
    …anned_pop_types=30&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600"…

    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 1669, Column 115: reference to external entity in attribute value
    …anned_pop_types=30&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600"…

    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 1669, Column 115: reference to entity "section" for which no system identifier could be generated
    …anned_pop_types=30&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600"…

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

  • Info Line 1669, Column 107: entity was defined here
    …pe=pop&banned_pop_types=30&ad_size=0x0&section=2564424&pop_times=1&pop_frequen…
  • Warning Line 1669, Column 124: cannot generate system identifier for general entity "pop_times"
    …_types=30&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600" ></scrip…

    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 1669, Column 124: general entity "pop_times" not defined and no default entity
    …_types=30&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600" ></scrip…

    This is usually a cascading error caused by 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 1669, Column 133: reference not terminated by REFC delimiter
    …0&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600" ></script></body>

    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 1669, Column 133: reference to external entity in attribute value
    …0&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600" ></script></body>

    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 1669, Column 133: reference to entity "pop_times" for which no system identifier could be generated
    …0&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600" ></script></body>

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

  • Info Line 1669, Column 123: entity was defined here
    …p_types=30&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600" ></scri…
  • Warning Line 1669, Column 136: cannot generate system identifier for general entity "pop_frequency"
    …0&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600" ></script></body>

    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 1669, Column 136: general entity "pop_frequency" not defined and no default entity
    …0&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600" ></script></body>

    This is usually a cascading error caused by 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 1669, Column 149: reference not terminated by REFC delimiter
    …0&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600" ></script></body>

    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 1669, Column 149: reference to external entity in attribute value
    …0&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600" ></script></body>

    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 1669, Column 149: reference to entity "pop_frequency" for which no system identifier could be generated
    …0&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600" ></script></body>

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

  • Info Line 1669, Column 135: entity was defined here
    …0&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600" ></script></body>
  • Error Line 1669, Column 172: end tag for "div" omitted, but OMITTAG NO was specified
    …0&ad_size=0x0&section=2564424&pop_times=1&pop_frequency=3600" ></script></body>

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

  • Info Line 176, Column 1: start tag was here
    <div id="header">

Visitor Analysis

Daily Visitor
  • 338 visits
Daily Visitor