peliculasonlineflv.net

peliculas divx online, ver peliculas gratis, cine gratis, estrenos online, descargar peliculas, series online, ver peliculas dvd online, ver videos divx ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    peliculasonlineflv.net
  • Favicon
  • Alexa Rank
    #9647
  • Google Page Rank
    PR 2
  • Ip Address
    173.194.67.121
  • Page Size
    130.5 KB
  • Images
    1 GIF, 28 JPG, 28 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 8 29 0 0 0

Website Meta Analysis



  • Title
    VER PELICULAS ONLINE FLV GRATIS WATCH MOVIES ONLINE FLV FREE
  • Meta Description
    peliculas divx online, ver peliculas gratis, cine gratis, estrenos online, descargar peliculas, series online, ver peliculas dvd online, ver videos divx

Technical Analysis



  • Webserver
    GSE
  • Ip Address
    173.194.67.121
  • Domain Age
    2 Years, 2 Months, 15 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from peliculasonlineflv.net.

HTML Analysis

  • content-type: text/html; charset=UTF-8
  • expires: Sun, 13 Jan 2013 22:17:12 GMT
  • date: Sun, 13 Jan 2013 22:17:12 GMT
  • cache-control: private, max-age=0
  • last-modified: Sun, 13 Jan 2013 21:44:32 GMT
  • etag: "731675ae-0ce2-4630-9f8a-238e772b2952"
  • content-encoding: gzip
  • x-content-type-options: nosniff
  • x-xss-protection: 1; mode=block
  • content-length: 25927
  • server: GSE
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for peliculasonlineflv.net

DNS Analysis


DNS servers
ns3.google.com [216.239.36.10]
ns2.google.com [216.239.34.10]
ns1.google.com [216.239.32.10]
ns4.google.com [216.239.38.10]


DNS Records

Answer records
ghs.l.google.com A 173.194.64.121 300s
ghs.l.google.com 28 [16 bytes] 300s

Authority records

Additional records

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 312 Errors
  • 269 Warnings
Ratio Text/Html
  • 0.5469811716107402
Message Error
  • Warning Line 27, Column 123: cannot generate system identifier for general entity "zx"
    ….css?targetBlogID=8268280334159796434&zx=731675ae-0ce2-4630-9f8a-238e772b2952"…

    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 "&" (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 æ 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 27, Column 123: general entity "zx" not defined and no default entity
    ….css?targetBlogID=8268280334159796434&zx=731675ae-0ce2-4630-9f8a-238e772b2952"…

    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 27, Column 125: reference not terminated by REFC delimiter
    …css?targetBlogID=8268280334159796434&zx=731675ae-0ce2-4630-9f8a-238e772b2952"/>

    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 27, Column 125: reference to external entity in attribute value
    …css?targetBlogID=8268280334159796434&zx=731675ae-0ce2-4630-9f8a-238e772b2952"/>

    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 '&'.

  • Error Line 27, Column 125: reference to entity "zx" for which no system identifier could be generated
    …css?targetBlogID=8268280334159796434&zx=731675ae-0ce2-4630-9f8a-238e772b2952"/>

    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 27, Column 122: entity was defined here
    …n.css?targetBlogID=8268280334159796434&zx=731675ae-0ce2-4630-9f8a-238e772b2952…
  • Warning Line 381, Column 5: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 381, Column 9: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 381, Column 13: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 381, Column 17: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 381, Column 21: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 381, Column 25: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 381, Column 29: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 381, Column 33: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 381, Column 37: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 381, Column 41: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 381, Column 45: multiple comments in comment declaration
    ----------------------------------------------- */
  • Error Line 381, Column 47: invalid comment declaration: found name character outside comment but inside comment declaration
    ----------------------------------------------- */
  • Info Line 28, Column 41: comment declaration started here
    <style id='page-skin-1' type='text/css'><!--
  • Error Line 540, Column 31: document type does not allow element "script" here
    <script type='text/javascript'>

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

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

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

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

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

  • Error Line 835, Column 8: required attribute "type" not specified
    <script>$(document).ready(function() {

    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 996, Column 78: cannot generate system identifier for general entity "m"
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function…

    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 996, Column 78: general entity "m" not defined and no default entity
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function…

    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 996, Column 79: reference not terminated by REFC delimiter
    …igator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function …

    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 996, Column 79: reference to entity "m" for which no system identifier could be generated
    …igator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function …

    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 996, Column 77: entity was defined here
    …avigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";functio…
  • Warning Line 996, Column 89: character "&" is the first character of a delimiter but occurred as data
    …userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function j(){var d=…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 996, Column 213: character "<" is the first character of a delimiter but occurred as data
    …gth){case 1:return d+i;case 2:return 0<=e[1].search(g)?null:d+f;default:return…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 996, Column 284: character "&" is the first character of a delimiter but occurred as data
    …:return null}}if(-1!=a[b][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iP…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 996, Column 285: character "&" is the first character of a delimiter but occurred as data
    …return null}}if(-1!=a[b][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iPa…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 996, Column 307: character "&" is the first character of a delimiter but occurred as data
    …b][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iPad")||-1!=a[b][c]("Oper…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 996, Column 308: character "&" is the first character of a delimiter but occurred as data
    …][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iPad")||-1!=a[b][c]("Opera…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 996, Column 393: character "&" is the first character of a delimiter but occurred as data
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 996, Column 395: cannot generate system identifier for general entity "window.location.replace"
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

    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 996, Column 395: general entity "window.location.replace" not defined and no default entity
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

    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 996, Column 418: reference not terminated by REFC delimiter
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

    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 996, Column 418: reference to entity "window.location.replace" for which no system identifier could be generated
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

    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 996, Column 394: entity was defined here
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};
  • Error Line 1002, Column 63: required attribute "type" not specified
    <script src='http://connect.facebook.net/es_ES/all.js#xfbml=1'></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 1006, Column 41: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <a href='/'><span class='menu-items'><h3>Página Principal</h3>Inicio</span></a>

    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 1007, Column 68: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …w.codificadotv.org/'><span class='menu-items'><h3>TV Adultos</h3>xxx</span></a>

    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 1008, Column 71: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …lasxxxflv.com/'><span class='menu-items'><h3>PELICULAS (+18)</h3>xxx</span></a>

    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 1009, Column 68: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …-flv.com'><span class='menu-items'><h3>Peliculas Eroticas</h3>Peliculas Erotic…

    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 1010, Column 78: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …spot.com'><span class='menu-items'><h3>Peliculas HD 720p</h3>Peliculas en HD</…

    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 1019, Column 8: element "center" undefined
    <center><!-- BEGIN STANDARD TAG - 350 x 250 - CN_peliculasonlineflv.net: Run-of…

    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 1020, Column 21: there is no attribute "frameborder"
    <iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=350 heigh…

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

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

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

  • Error Line 1020, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=350 heigh…
  • Error Line 1020, Column 35: there is no attribute "marginwidth"
    <iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=350 heigh…

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

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

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

  • Error Line 1020, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=350 heigh…
  • Error Line 1020, Column 50: there is no attribute "marginheight"
    …meborder=0 marginwidth=0 marginheight=0 scrolling=no width=350 height=250 src=…

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

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

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

  • Error Line 1020, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginwidth=0 marginheight=0 scrolling=no width=350 height=250 src=…
  • Error Line 1020, Column 62: there is no attribute "scrolling"
    …arginwidth=0 marginheight=0 scrolling=no width=350 height=250 src="http://peli…

    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 1020, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arginwidth=0 marginheight=0 scrolling=no width=350 height=250 src="http://peli…
  • Error Line 1020, Column 71: there is no attribute "width"
    …h=0 marginheight=0 scrolling=no width=350 height=250 src="http://peliculasonli…

    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 1020, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 marginheight=0 scrolling=no width=350 height=250 src="http://peliculasonli…
  • Error Line 1020, Column 82: there is no attribute "height"
    …eight=0 scrolling=no width=350 height=250 src="http://peliculasonline-hd.net/p…

    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 1020, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eight=0 scrolling=no width=350 height=250 src="http://peliculasonline-hd.net/p…
  • Error Line 1020, Column 90: there is no attribute "src"
    …scrolling=no width=350 height=250 src="http://peliculasonline-hd.net/publ/350x…

    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 1020, Column 139: element "iframe" undefined
    …=350 height=250 src="http://peliculasonline-hd.net/publ/350x250.html"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1026, Column 83: cannot generate system identifier for general entity "widgetType"
    …/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=ed…

    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 1026, Column 83: general entity "widgetType" not defined and no default entity
    …/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=ed…

    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 1026, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&s…

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

  • Warning Line 1026, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&s…

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

  • Error Line 1026, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&s…

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

  • Info Line 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 1026, Column 99: cannot generate system identifier for general entity "widgetId"
    …D=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&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 1026, Column 99: general entity "widgetId" not defined and no default entity
    …D=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&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 1026, Column 107: reference not terminated by REFC delimiter
    …0334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadge…

    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 1026, Column 107: reference to external entity in attribute value
    …0334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadge…

    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 1026, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadge…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 1026, Column 114: cannot generate system identifier for general entity "action"
    …796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' on…

    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 1026, Column 114: general entity "action" not defined and no default entity
    …796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' on…

    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 1026, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick=…

    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 1026, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick=…

    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 1026, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 1026, Column 132: cannot generate system identifier for general entity "sectionId"
    …HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wid…

    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 1026, Column 132: general entity "sectionId" not defined and no default entity
    …HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wid…

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

  • Warning Line 1026, Column 141: reference not terminated by REFC delimiter
    …etId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _WidgetManage…

    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 1026, Column 141: reference to external entity in attribute value
    …etId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _WidgetManage…

    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 1026, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Error Line 1026, Column 239: there is no attribute "target"
    …Config(document.getElementById("HTML5"));' target='configHTML5' title='Editar'>

    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 1046, Column 30: character "&" is the first character of a delimiter but occurred as data
              if (window.iframes && iframes.open) {

    This message may appear in several cases:

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

    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 1072, Column 27: there is no attribute "allowtransparency"
    <iframe allowtransparency='true' frameborder='0' scrolling='no' src='http://www…

    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 1072, Column 280: there is no attribute "style"
    …amp;header=true&amp;height=289' style='margin-top: -1px; margin-right: -1px; m…

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

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

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

  • Error Line 1072, Column 704: element "iframe" undefined
    …erflow-x: hidden; overflow-y: hidden; width: 385px; height: 249px; '/></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1072, Column 713: end tag for element "iframe" which is not open
    …erflow-x: hidden; overflow-y: hidden; width: 385px; height: 249px; '/></iframe>

    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 1077, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML9&action=editWidget&s…

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

  • Warning Line 1077, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML9&action=editWidget&s…

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

  • Error Line 1077, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML9&action=editWidget&s…

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

  • Info Line 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 1077, Column 107: reference not terminated by REFC delimiter
    …0334159796434&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=gadge…

    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 1077, Column 107: reference to external entity in attribute value
    …0334159796434&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=gadge…

    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 1077, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0334159796434&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=gadge…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 1077, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=gadget-2' onclick=…

    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 1077, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=gadget-2' onclick=…

    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 1077, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=gadget-2' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 1077, Column 141: reference not terminated by REFC delimiter
    …etId=HTML9&action=editWidget&sectionId=gadget-2' onclick='return _WidgetManage…

    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 1077, Column 141: reference to external entity in attribute value
    …etId=HTML9&action=editWidget&sectionId=gadget-2' onclick='return _WidgetManage…

    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 1077, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML9&action=editWidget&sectionId=gadget-2' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Error Line 1088, Column 8: element "center" undefined
    <center><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=7…

    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 1088, Column 29: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <center><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=7…
  • Error Line 1088, Column 43: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ter><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=728 …
  • Error Line 1088, Column 58: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginwidth=0 marginheight=0 scrolling=no width=728 height=90 src="…
  • Error Line 1088, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arginwidth=0 marginheight=0 scrolling=no width=728 height=90 src="http://pelic…
  • Error Line 1088, Column 79: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 marginheight=0 scrolling=no width=728 height=90 src="http://peliculasonlin…
  • Error Line 1088, Column 90: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eight=0 scrolling=no width=728 height=90 src="http://peliculasonline-hd.net/pu…
  • Error Line 1088, Column 147: element "iframe" undefined
    …ht=90 src="http://peliculasonline-hd.net/publ/mi728x90.html"></iframe></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).
  • Warning Line 1093, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML11&action=editWidget&…

    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 1093, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML11&action=editWidget&…

    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 1093, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML11&action=editWidget&…

    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 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 1093, Column 107: reference not terminated by REFC delimiter
    …0334159796434&widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=main…

    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 1093, Column 107: reference to external entity in attribute value
    …0334159796434&widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=main…

    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 1093, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0334159796434&widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=main…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 1093, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=main' onclick='ret…

    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 1093, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=main' onclick='ret…

    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 1093, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=main' onclick='ret…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 1093, Column 142: reference not terminated by REFC delimiter
    …tId=HTML11&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

    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 1093, Column 142: reference to external entity in attribute value
    …tId=HTML11&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

    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 1093, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML11&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Info Line 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Error Line 1105, Column 373: end tag for "img" omitted, but OMITTAG NO was specified
    …/s1600/aviso-legal.jpg" alt="Aviso legal" height="0" width="0"></a></div></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 1105, Column 205: start tag was here
    …viso-legal.html" title="Aviso legal"> <img class="redondeado" src="http://2.bp…
  • Error Line 1117, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1120, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1121, Column 426: end tag for "img" omitted, but OMITTAG NO was specified
    …t="Ver Una Chica En Apuros (2006) - Latino" height="0" width="0"></a></div><br>

    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 1121, Column 260: start tag was here
    …Una Chica En Apuros (2006) - Latino"> <img src="http://4.bp.blogspot.com/_R1XT…
  • Error Line 1121, Column 437: end tag for "br" omitted, but OMITTAG NO was specified
    …t="Ver Una Chica En Apuros (2006) - Latino" height="0" width="0"></a></div><br>

    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 1121, Column 433: start tag was here
    …t="Ver Una Chica En Apuros (2006) - Latino" height="0" width="0"></a></div><br>
  • Error Line 1134, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1137, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1138, Column 445: end tag for "img" omitted, but OMITTAG NO was specified
    …t="Ver Los Miserables (2012) - Subtitulada" height="0" width="0"></a></div><br>

    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 1138, Column 260: start tag was here
    …Los Miserables (2012) - Subtitulada"> <img src="http://4.bp.blogspot.com/-2_-d…
  • Error Line 1138, Column 456: end tag for "br" omitted, but OMITTAG NO was specified
    …t="Ver Los Miserables (2012) - Subtitulada" height="0" width="0"></a></div><br>

    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 1138, Column 452: start tag was here
    …t="Ver Los Miserables (2012) - Subtitulada" height="0" width="0"></a></div><br>
  • Error Line 1151, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1154, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1155, Column 453: end tag for "img" omitted, but OMITTAG NO was specified
    …Ver Parental Guidance (2012) - Subtitulada" height="0" width="0"></a></div><br>

    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 1155, Column 259: start tag was here
    …ental Guidance (2012) - Subtitulada"> <img src="https://lh6.googleusercontent.…
  • Error Line 1155, Column 464: end tag for "br" omitted, but OMITTAG NO was specified
    …Ver Parental Guidance (2012) - Subtitulada" height="0" width="0"></a></div><br>

    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 1155, Column 460: start tag was here
    …Ver Parental Guidance (2012) - Subtitulada" height="0" width="0"></a></div><br>
  • Error Line 1168, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1171, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1172, Column 585: end tag for "img" omitted, but OMITTAG NO was specified
    …ith the Dragon Tattoo (2013) - Subtitulada" height="0" width="0"></a></div><br>

    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 1172, Column 331: start tag was here
    … Dragon Tattoo (2013) - Subtitulada"> <img src="https://lh3.googleusercontent.…
  • Error Line 1172, Column 596: end tag for "br" omitted, but OMITTAG NO was specified
    …ith the Dragon Tattoo (2013) - Subtitulada" height="0" width="0"></a></div><br>

    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 1172, Column 592: start tag was here
    …ith the Dragon Tattoo (2013) - Subtitulada" height="0" width="0"></a></div><br>
  • Error Line 1185, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1188, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1189, Column 439: end tag for "img" omitted, but OMITTAG NO was specified
    …t="Ver Texas Chainsaw (2013) - Subtitulada" height="0" width="0"></a></div><br>

    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 1189, Column 256: start tag was here
    …Texas Chainsaw (2013) - Subtitulada"> <img src="https://lh5.googleusercontent.…
  • Error Line 1189, Column 450: end tag for "br" omitted, but OMITTAG NO was specified
    …t="Ver Texas Chainsaw (2013) - Subtitulada" height="0" width="0"></a></div><br>

    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 1189, Column 446: start tag was here
    …t="Ver Texas Chainsaw (2013) - Subtitulada" height="0" width="0"></a></div><br>
  • Error Line 1202, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1205, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1206, Column 462: end tag for "img" omitted, but OMITTAG NO was specified
    … La Carrera de la Muerte 3 (2013) - Latino" height="0" width="0"></a></div><br>

    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 1206, Column 265: start tag was here
    …rera de la Muerte 3 (2013) - Latino"> <img src="http://2.bp.blogspot.com/-7Yie…
  • Error Line 1206, Column 473: end tag for "br" omitted, but OMITTAG NO was specified
    … La Carrera de la Muerte 3 (2013) - Latino" height="0" width="0"></a></div><br>

    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 1206, Column 469: start tag was here
    … La Carrera de la Muerte 3 (2013) - Latino" height="0" width="0"></a></div><br>
  • Error Line 1219, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1222, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1223, Column 455: end tag for "img" omitted, but OMITTAG NO was specified
    …i quiero silbar, silbo (2010) - Castellano" height="0" width="0"></a></div><br>

    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 1223, Column 267: start tag was here
    …o silbar, silbo (2010) - Castellano"> <img src="https://lh3.googleusercontent.…
  • Error Line 1223, Column 466: end tag for "br" omitted, but OMITTAG NO was specified
    …i quiero silbar, silbo (2010) - Castellano" height="0" width="0"></a></div><br>

    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 1223, Column 462: start tag was here
    …i quiero silbar, silbo (2010) - Castellano" height="0" width="0"></a></div><br>
  • Error Line 1236, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1239, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1240, Column 448: end tag for "img" omitted, but OMITTAG NO was specified
    …The Imposter (El impostor) (2012) - Latino" height="0" width="0"></a></div><br>

    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 1240, Column 258: start tag was here
    …oster (El impostor) (2012) - Latino"> <img src="https://lh4.googleusercontent.…
  • Error Line 1240, Column 459: end tag for "br" omitted, but OMITTAG NO was specified
    …The Imposter (El impostor) (2012) - Latino" height="0" width="0"></a></div><br>

    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 1240, Column 455: start tag was here
    …The Imposter (El impostor) (2012) - Latino" height="0" width="0"></a></div><br>
  • Error Line 1253, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1256, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1257, Column 432: end tag for "img" omitted, but OMITTAG NO was specified
    … alt="Ver New Police Story (2004) - Latino" height="0" width="0"></a></div><br>

    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 1257, Column 254: start tag was here
    …er New Police Story (2004) - Latino"> <img src="http://2.bp.blogspot.com/-w61X…
  • Error Line 1257, Column 443: end tag for "br" omitted, but OMITTAG NO was specified
    … alt="Ver New Police Story (2004) - Latino" height="0" width="0"></a></div><br>

    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 1257, Column 439: start tag was here
    … alt="Ver New Police Story (2004) - Latino" height="0" width="0"></a></div><br>
  • Error Line 1270, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1273, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1274, Column 459: end tag for "img" omitted, but OMITTAG NO was specified
    …Death Race 3: Inferno (2013) - Subtitulada" height="0" width="0"></a></div><br>

    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 1274, Column 266: start tag was here
    …ace 3: Inferno (2013) - Subtitulada"> <img src="https://lh3.googleusercontent.…
  • Error Line 1274, Column 470: end tag for "br" omitted, but OMITTAG NO was specified
    …Death Race 3: Inferno (2013) - Subtitulada" height="0" width="0"></a></div><br>

    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 1274, Column 466: start tag was here
    …Death Race 3: Inferno (2013) - Subtitulada" height="0" width="0"></a></div><br>
  • Error Line 1287, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1290, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1291, Column 427: end tag for "img" omitted, but OMITTAG NO was specified
    …" alt="Ver Crawlspace (2012) - Subtitulada" height="0" width="0"></a></div><br>

    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 1291, Column 252: start tag was here
    …Ver Crawlspace (2012) - Subtitulada"> <img src="https://lh5.googleusercontent.…
  • Error Line 1291, Column 438: end tag for "br" omitted, but OMITTAG NO was specified
    …" alt="Ver Crawlspace (2012) - Subtitulada" height="0" width="0"></a></div><br>

    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 1291, Column 434: start tag was here
    …" alt="Ver Crawlspace (2012) - Subtitulada" height="0" width="0"></a></div><br>
  • Error Line 1304, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1307, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1308, Column 436: end tag for "img" omitted, but OMITTAG NO was specified
    …lt="Ver Anna Karenina (2012) - Subtitulada" height="0" width="0"></a></div><br>

    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 1308, Column 258: start tag was here
    … Anna Karenina (2012) - Subtitulada"> <img src="https://lh5.googleusercontent.…
  • Error Line 1308, Column 447: end tag for "br" omitted, but OMITTAG NO was specified
    …lt="Ver Anna Karenina (2012) - Subtitulada" height="0" width="0"></a></div><br>

    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 1308, Column 443: start tag was here
    …lt="Ver Anna Karenina (2012) - Subtitulada" height="0" width="0"></a></div><br>
  • Error Line 1321, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1324, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1325, Column 453: end tag for "img" omitted, but OMITTAG NO was specified
    …Won&#8217;t back down (2012) - Subtitulada" height="0" width="0"></a></div><br>

    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 1325, Column 267: start tag was here
    …17;t back down (2012) - Subtitulada"> <img src="https://lh3.googleusercontent.…
  • Error Line 1325, Column 464: end tag for "br" omitted, but OMITTAG NO was specified
    …Won&#8217;t back down (2012) - Subtitulada" height="0" width="0"></a></div><br>

    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 1325, Column 460: start tag was here
    …Won&#8217;t back down (2012) - Subtitulada" height="0" width="0"></a></div><br>
  • Error Line 1338, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1341, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1342, Column 486: end tag for "img" omitted, but OMITTAG NO was specified
    …s (Seven Psychopaths) (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1342, Column 283: start tag was here
    …n Psychopaths) (2012) Audio  Latino"> <img src="https://lh5.googleusercontent.…
  • Error Line 1342, Column 497: end tag for "br" omitted, but OMITTAG NO was specified
    …s (Seven Psychopaths) (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1342, Column 493: start tag was here
    …s (Seven Psychopaths) (2012) Audio  Latino" height="0" width="0"></a></div><br>
  • Error Line 1355, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1358, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1359, Column 447: end tag for "img" omitted, but OMITTAG NO was specified
    …r Hyde Park on Hudson (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1359, Column 261: start tag was here
    …Park on Hudson (2012) Audio  Latino"> <img src="https://lh3.googleusercontent.…
  • Error Line 1359, Column 458: end tag for "br" omitted, but OMITTAG NO was specified
    …r Hyde Park on Hudson (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1359, Column 454: start tag was here
    …r Hyde Park on Hudson (2012) Audio  Latino" height="0" width="0"></a></div><br>
  • Error Line 1372, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1375, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1376, Column 433: end tag for "img" omitted, but OMITTAG NO was specified
    …alt="Ver Little birds (2011) Audio  Latino" height="0" width="0"></a></div><br>

    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 1376, Column 254: start tag was here
    …r Little birds (2011) Audio  Latino"> <img src="https://lh4.googleusercontent.…
  • Error Line 1376, Column 444: end tag for "br" omitted, but OMITTAG NO was specified
    …alt="Ver Little birds (2011) Audio  Latino" height="0" width="0"></a></div><br>

    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 1376, Column 440: start tag was here
    …alt="Ver Little birds (2011) Audio  Latino" height="0" width="0"></a></div><br>
  • Error Line 1389, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1392, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1393, Column 429: end tag for "img" omitted, but OMITTAG NO was specified
    …" alt="Ver Doors Open (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1393, Column 252: start tag was here
    …Ver Doors Open (2012) Audio  Latino"> <img src="https://lh3.googleusercontent.…
  • Error Line 1393, Column 440: end tag for "br" omitted, but OMITTAG NO was specified
    …" alt="Ver Doors Open (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1393, Column 436: start tag was here
    …" alt="Ver Doors Open (2012) Audio  Latino" height="0" width="0"></a></div><br>
  • Error Line 1406, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1409, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1410, Column 464: end tag for "img" omitted, but OMITTAG NO was specified
    …kosmos (Unfair World) (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1410, Column 267: start tag was here
    …(Unfair World) (2012) Audio  Latino"> <img src="https://lh6.googleusercontent.…
  • Error Line 1410, Column 475: end tag for "br" omitted, but OMITTAG NO was specified
    …kosmos (Unfair World) (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1410, Column 471: start tag was here
    …kosmos (Unfair World) (2012) Audio  Latino" height="0" width="0"></a></div><br>
  • Error Line 1423, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1426, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1427, Column 462: end tag for "img" omitted, but OMITTAG NO was specified
    …l lenguaje del tiempo (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1427, Column 268: start tag was here
    …aje del tiempo (2012) Audio  Latino"> <img src="https://lh4.googleusercontent.…
  • Error Line 1427, Column 473: end tag for "br" omitted, but OMITTAG NO was specified
    …l lenguaje del tiempo (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1427, Column 469: start tag was here
    …l lenguaje del tiempo (2012) Audio  Latino" height="0" width="0"></a></div><br>
  • Error Line 1440, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1443, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1444, Column 461: end tag for "img" omitted, but OMITTAG NO was specified
    …erately seeking Santa (2011) Audio  Latino" height="0" width="0"></a></div><br>

    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 1444, Column 270: start tag was here
    … seeking Santa (2011) Audio  Latino"> <img src="https://lh3.googleusercontent.…
  • Error Line 1444, Column 472: end tag for "br" omitted, but OMITTAG NO was specified
    …erately seeking Santa (2011) Audio  Latino" height="0" width="0"></a></div><br>

    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 1444, Column 468: start tag was here
    …erately seeking Santa (2011) Audio  Latino" height="0" width="0"></a></div><br>
  • Error Line 1457, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1460, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1461, Column 443: end tag for "img" omitted, but OMITTAG NO was specified
    …="Ver Paris Manhattan (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1461, Column 262: start tag was here
    …aris Manhattan (2012) Audio  Latino"> <img src="https://lh4.googleusercontent.…
  • Error Line 1461, Column 454: end tag for "br" omitted, but OMITTAG NO was specified
    …="Ver Paris Manhattan (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1461, Column 450: start tag was here
    …="Ver Paris Manhattan (2012) Audio  Latino" height="0" width="0"></a></div><br>
  • Error Line 1474, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1477, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1478, Column 459: end tag for "img" omitted, but OMITTAG NO was specified
    …Todos tenemos un plan (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1478, Column 269: start tag was here
    …enemos un plan (2012) Audio  Latino"> <img src="https://lh6.googleusercontent.…
  • Error Line 1478, Column 470: end tag for "br" omitted, but OMITTAG NO was specified
    …Todos tenemos un plan (2012) Audio  Latino" height="0" width="0"></a></div><br>

    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 1478, Column 466: start tag was here
    …Todos tenemos un plan (2012) Audio  Latino" height="0" width="0"></a></div><br>
  • Error Line 1491, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1494, Column 10: ID "tamanho" already defined
    <div id='tamanho'>

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

  • Info Line 1104, Column 10: ID "tamanho" first defined here
    <div id='tamanho'>
  • Error Line 1495, Column 460: end tag for "img" omitted, but OMITTAG NO was specified
    …g" alt="Ver Hitchcock (2013) Audio  Latino" height="0" width="0"></a></div><br>

    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 1495, Column 250: start tag was here
    …"Ver Hitchcock (2013) Audio  Latino"> <img src="https://lh6.googleusercontent.…
  • Error Line 1495, Column 471: end tag for "br" omitted, but OMITTAG NO was specified
    …g" alt="Ver Hitchcock (2013) Audio  Latino" height="0" width="0"></a></div><br>

    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 1495, Column 467: start tag was here
    …g" alt="Ver Hitchcock (2013) Audio  Latino" height="0" width="0"></a></div><br>
  • Error Line 1508, Column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><p><strong></strong></p></p>

    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 1525, Column 8: element "center" undefined
    <center><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=7…

    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 1525, Column 29: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <center><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=7…
  • Error Line 1525, Column 43: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ter><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=728 …
  • Error Line 1525, Column 58: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginwidth=0 marginheight=0 scrolling=no width=728 height=90 src="…
  • Error Line 1525, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arginwidth=0 marginheight=0 scrolling=no width=728 height=90 src="http://pelic…
  • Error Line 1525, Column 79: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 marginheight=0 scrolling=no width=728 height=90 src="http://peliculasonlin…
  • Error Line 1525, Column 90: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eight=0 scrolling=no width=728 height=90 src="http://peliculasonline-hd.net/pu…
  • Error Line 1525, Column 147: element "iframe" undefined
    …ht=90 src="http://peliculasonline-hd.net/publ/mi728x90.html"></iframe></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).
  • Warning Line 1530, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML6&action=editWidget&s…

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

  • Warning Line 1530, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML6&action=editWidget&s…

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

  • Error Line 1530, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML6&action=editWidget&s…

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

  • Info Line 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 1530, Column 107: reference not terminated by REFC delimiter
    …0334159796434&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=main'…

    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 1530, Column 107: reference to external entity in attribute value
    …0334159796434&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=main'…

    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 1530, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0334159796434&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=main'…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 1530, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=main' onclick='ret…

    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 1530, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=main' onclick='ret…

    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 1530, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=main' onclick='ret…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 1530, Column 141: reference not terminated by REFC delimiter
    …etId=HTML6&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

    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 1530, Column 141: reference to external entity in attribute value
    …etId=HTML6&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

    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 1530, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML6&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Info Line 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Error Line 1546, 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).

  • Warning Line 1606, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=CustomSearch&widgetId=CustomSearch1&act…

    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 1606, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=CustomSearch&widgetId=CustomSearch1&act…

    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 1606, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=CustomSearch&widgetId=CustomSearch1&act…

    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 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 1606, Column 115: reference not terminated by REFC delimiter
    …96434&widgetType=CustomSearch&widgetId=CustomSearch1&action=editWidget&section…

    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 1606, Column 115: reference to external entity in attribute value
    …96434&widgetType=CustomSearch&widgetId=CustomSearch1&action=editWidget&section…

    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 1606, Column 115: reference to entity "widgetId" for which no system identifier could be generated
    …96434&widgetType=CustomSearch&widgetId=CustomSearch1&action=editWidget&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.

  • Info Line 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 1606, Column 136: reference not terminated by REFC delimiter
    …omSearch&widgetId=CustomSearch1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1606, Column 136: reference to external entity in attribute value
    …omSearch&widgetId=CustomSearch1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1606, Column 136: reference to entity "action" for which no system identifier could be generated
    …omSearch&widgetId=CustomSearch1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 1606, Column 157: reference not terminated by REFC delimiter
    …tomSearch1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1606, Column 157: reference to external entity in attribute value
    …tomSearch1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1606, Column 157: reference to entity "sectionId" for which no system identifier could be generated
    …tomSearch1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Error Line 1615, Column 68: there is no attribute "name"
    …ue' frameborder='0' height='300' name='poll-widget-6109787802804521623' src='h…

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

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

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

  • Warning Line 1615, Column 208: cannot generate system identifier for general entity "purl"
    …3/blogger_template/run_app?hideq=true&purl=http://www.peliculasonlineflv.net/'…

    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 1615, Column 208: general entity "purl" not defined and no default entity
    …3/blogger_template/run_app?hideq=true&purl=http://www.peliculasonlineflv.net/'…

    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 1615, Column 212: reference not terminated by REFC delimiter
    …ogger_template/run_app?hideq=true&purl=http://www.peliculasonlineflv.net/' sty…

    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 1615, Column 212: reference to external entity in attribute value
    …ogger_template/run_app?hideq=true&purl=http://www.peliculasonlineflv.net/' sty…

    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 1615, Column 212: reference to entity "purl" for which no system identifier could be generated
    …ogger_template/run_app?hideq=true&purl=http://www.peliculasonlineflv.net/' sty…

    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 1615, Column 207: entity was defined here
    …23/blogger_template/run_app?hideq=true&purl=http://www.peliculasonlineflv.net/…
  • Error Line 1615, Column 281: element "iframe" undefined
    …=http://www.peliculasonlineflv.net/' style='border:none; width:100%;'></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1619, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=Poll&widgetId=Poll1&action=editWidget&s…

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

  • Warning Line 1619, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=Poll&widgetId=Poll1&action=editWidget&s…

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

  • Error Line 1619, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=Poll&widgetId=Poll1&action=editWidget&s…

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

  • Info Line 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 1619, Column 107: reference not terminated by REFC delimiter
    …0334159796434&widgetType=Poll&widgetId=Poll1&action=editWidget&sectionId=cahay…

    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 1619, Column 107: reference to external entity in attribute value
    …0334159796434&widgetType=Poll&widgetId=Poll1&action=editWidget&sectionId=cahay…

    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 1619, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0334159796434&widgetType=Poll&widgetId=Poll1&action=editWidget&sectionId=cahay…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 1619, Column 120: reference not terminated by REFC delimiter
    …&widgetType=Poll&widgetId=Poll1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1619, Column 120: reference to external entity in attribute value
    …&widgetType=Poll&widgetId=Poll1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1619, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=Poll&widgetId=Poll1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 1619, Column 141: reference not terminated by REFC delimiter
    …etId=Poll1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1619, Column 141: reference to external entity in attribute value
    …etId=Poll1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1619, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=Poll1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Error Line 1628, Column 580: there is no attribute "border"
    …g" alt="Cerrar" title="Cerrar" border="0" />  </div>  <div style="float:right;…

    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 1630, Column 152: element "iframe" undefined
    …0" src="http://peliculasonline-hd.net/publ/350x250.html" ></iframe></div></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).
  • Warning Line 1635, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML4&action=editWidget&s…

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

  • Warning Line 1635, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML4&action=editWidget&s…

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

  • Error Line 1635, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML4&action=editWidget&s…

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

  • Info Line 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 1635, Column 107: reference not terminated by REFC delimiter
    …0334159796434&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=cahay…

    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 1635, Column 107: reference to external entity in attribute value
    …0334159796434&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=cahay…

    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 1635, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0334159796434&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=cahay…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 1635, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=cahaya13' onclick=…

    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 1635, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=cahaya13' onclick=…

    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 1635, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=cahaya13' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 1635, Column 141: reference not terminated by REFC delimiter
    …etId=HTML4&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1635, Column 141: reference to external entity in attribute value
    …etId=HTML4&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1635, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML4&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Error Line 1643, Column 23: there is no attribute "annotation"
    <g:plusone annotation='inline' href='http://www.peliculasonlineflv.net/' size='…

    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 1643, Column 37: there is no attribute "href"
    <g:plusone annotation='inline' href='http://www.peliculasonlineflv.net/' size='…

    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 1643, Column 79: there is no attribute "size"
    …p://www.peliculasonlineflv.net/' size='standard' source='blogger:blog:plusone'…

    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 1643, Column 97: there is no attribute "source"
    …nlineflv.net/' size='standard' source='blogger:blog:plusone' width='250'></g:p…

    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 1643, Column 126: there is no attribute "width"
    …lv.net/' size='standard' source='blogger:blog:plusone' width='250'></g:plusone>

    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 1643, Column 131: element "g:plusone" undefined
    …lv.net/' size='standard' source='blogger:blog:plusone' width='250'></g:plusone>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1657, 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 1657, 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 1657, Column 92: reference not terminated by REFC delimiter
    …rk.net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=3524243&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 1657, Column 92: reference to external entity in attribute value
    …rk.net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=3524243&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 1657, 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=3524243&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 1657, Column 75: entity was defined here
    …http://ad.adnetwork.net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section…
  • Warning Line 1657, Column 96: cannot generate system identifier for general entity "ad_size"
    …et/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=3524243&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 1657, 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=3524243&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 1657, Column 103: reference not terminated by REFC delimiter
    …d_type=pop&banned_pop_types=30&ad_size=0x0&section=3524243&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 1657, Column 103: reference to external entity in attribute value
    …d_type=pop&banned_pop_types=30&ad_size=0x0&section=3524243&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 1657, 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=3524243&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 1657, Column 95: entity was defined here
    …net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=3524243&pop_times=1…
  • Warning Line 1657, Column 108: cannot generate system identifier for general entity "section"
    …e=pop&banned_pop_types=30&ad_size=0x0&section=3524243&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 1657, Column 108: general entity "section" not defined and no default entity
    …e=pop&banned_pop_types=30&ad_size=0x0&section=3524243&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 1657, Column 115: reference not terminated by REFC delimiter
    …anned_pop_types=30&ad_size=0x0&section=3524243&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 1657, Column 115: reference to external entity in attribute value
    …anned_pop_types=30&ad_size=0x0&section=3524243&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 1657, Column 115: reference to entity "section" for which no system identifier could be generated
    …anned_pop_types=30&ad_size=0x0&section=3524243&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 1657, Column 107: entity was defined here
    …pe=pop&banned_pop_types=30&ad_size=0x0&section=3524243&pop_times=1&pop_frequen…
  • Warning Line 1657, Column 124: cannot generate system identifier for general entity "pop_times"
    …_types=30&ad_size=0x0&section=3524243&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 1657, Column 124: general entity "pop_times" not defined and no default entity
    …_types=30&ad_size=0x0&section=3524243&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 1657, Column 133: reference not terminated by REFC delimiter
    …types=30&ad_size=0x0&section=3524243&pop_times=1&pop_frequency=3600" ></script>

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

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

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

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

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

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

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

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

  • Error Line 1657, Column 136: general entity "pop_frequency" not defined and no default entity
    …types=30&ad_size=0x0&section=3524243&pop_times=1&pop_frequency=3600" ></script>

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

  • Warning Line 1657, Column 149: reference not terminated by REFC delimiter
    …types=30&ad_size=0x0&section=3524243&pop_times=1&pop_frequency=3600" ></script>

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

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

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

  • Info Line 1657, Column 135: entity was defined here
    …types=30&ad_size=0x0&section=3524243&pop_times=1&pop_frequency=3600" ></script>
  • Warning Line 1662, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML12&action=editWidget&…

    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 1662, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML12&action=editWidget&…

    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 1662, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML12&action=editWidget&…

    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 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 1662, Column 107: reference not terminated by REFC delimiter
    …0334159796434&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=caha…

    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 1662, Column 107: reference to external entity in attribute value
    …0334159796434&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=caha…

    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 1662, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0334159796434&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=caha…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 1662, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=cahaya13' onclick=…

    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 1662, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=cahaya13' onclick=…

    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 1662, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=cahaya13' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 1662, Column 142: reference not terminated by REFC delimiter
    …tId=HTML12&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1662, Column 142: reference to external entity in attribute value
    …tId=HTML12&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1662, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML12&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Error Line 1672, Column 211: required attribute "alt" not specified
    …pxY/UEPa4ieIPqI/AAAAAAAAJmg/rqveg7xRt6s/s1600/tuentisharebutton22es.png" /></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 1675, Column 382: element "iframe" undefined
    …verflow:hidden; width:100px; height:60px;" allowtransparency="true"> </iframe> 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1678, Column 71: element "g:plusone" undefined
    …"display:inline; margin-right:5px;"> <g:plusone size="tall"></g:plusone></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 1680, Column 74: there is no attribute "data-url"
    …class="twitter-share-button" data-url="http://www.peliculasonlineflv.net" data…

    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 1680, Column 120: there is no attribute "data-text"
    …www.peliculasonlineflv.net" data-text="Si quieres ver peliculas o series grati…

    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 1680, Column 224: there is no attribute "data-count"
    …o dudes en visitar esta pagina" data-count="vertical" data-lang="es">Tweet</a> 

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

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

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

  • Error Line 1680, Column 245: there is no attribute "data-lang"
    …o dudes en visitar esta pagina" data-count="vertical" data-lang="es">Tweet</a> 

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

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

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

  • Warning Line 1689, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML7&action=editWidget&s…

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

  • Warning Line 1689, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML7&action=editWidget&s…

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

  • Error Line 1689, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML7&action=editWidget&s…

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

  • Info Line 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 1689, Column 107: reference not terminated by REFC delimiter
    …0334159796434&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=cahay…

    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 1689, Column 107: reference to external entity in attribute value
    …0334159796434&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=cahay…

    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 1689, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0334159796434&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=cahay…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 1689, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=cahaya13' onclick=…

    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 1689, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=cahaya13' onclick=…

    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 1689, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=cahaya13' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 1689, Column 141: reference not terminated by REFC delimiter
    …etId=HTML7&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1689, Column 141: reference to external entity in attribute value
    …etId=HTML7&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1689, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML7&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Warning Line 1705, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML3&action=editWidget&s…

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

  • Warning Line 1705, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML3&action=editWidget&s…

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

  • Error Line 1705, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML3&action=editWidget&s…

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

  • Info Line 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 1705, Column 107: reference not terminated by REFC delimiter
    …0334159796434&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=cahay…

    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 1705, Column 107: reference to external entity in attribute value
    …0334159796434&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=cahay…

    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 1705, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0334159796434&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=cahay…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 1705, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=cahaya13' onclick=…

    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 1705, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=cahaya13' onclick=…

    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 1705, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=cahaya13' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 1705, Column 141: reference not terminated by REFC delimiter
    …etId=HTML3&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1705, Column 141: reference to external entity in attribute value
    …etId=HTML3&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1705, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML3&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Error Line 1718, Column 57: an attribute specification must start with a name or name token
              document.write('<script type="text/javascript"' +

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

  • Error Line 1718, Column 57: document type does not allow element "script" here
              document.write('<script type="text/javascript"' +

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

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

  • Error Line 1720, Column 21: delimiter "'" invalid: only S separators and TAGC allowed here
                  '</scr' + 'ipt>');
  • Error Line 1720, Column 21: end tag for element "scr" which is not open
                  '</scr' + 'ipt>');

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

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

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

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

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

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

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

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

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

  • Error Line 1781, Column 49: document type does not allow element "div" here
    <div id="div-pcy4wlxvh5ol" style="width: 100%; "></div>

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

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

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

  • Error Line 1812, Column 6: end tag for "script" 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 1716, Column 1: start tag was here
    <script type="text/javascript">
  • Warning Line 1817, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=Followers&widgetId=Followers1&action=ed…

    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 1817, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=Followers&widgetId=Followers1&action=ed…

    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 1817, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=Followers&widgetId=Followers1&action=ed…

    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 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 1817, Column 112: reference not terminated by REFC delimiter
    …59796434&widgetType=Followers&widgetId=Followers1&action=editWidget&sectionId=…

    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 1817, Column 112: reference to external entity in attribute value
    …59796434&widgetType=Followers&widgetId=Followers1&action=editWidget&sectionId=…

    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 1817, Column 112: reference to entity "widgetId" for which no system identifier could be generated
    …59796434&widgetType=Followers&widgetId=Followers1&action=editWidget&sectionId=…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 1817, Column 130: reference not terminated by REFC delimiter
    …e=Followers&widgetId=Followers1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1817, Column 130: reference to external entity in attribute value
    …e=Followers&widgetId=Followers1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1817, Column 130: reference to entity "action" for which no system identifier could be generated
    …e=Followers&widgetId=Followers1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 1817, Column 151: reference not terminated by REFC delimiter
    …Followers1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1817, Column 151: reference to external entity in attribute value
    …Followers1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1817, Column 151: reference to entity "sectionId" for which no system identifier could be generated
    …Followers1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Warning Line 1840, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML13&action=editWidget&…

    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 1840, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML13&action=editWidget&…

    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 1840, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML13&action=editWidget&…

    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 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 1840, Column 107: reference not terminated by REFC delimiter
    …0334159796434&widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=caha…

    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 1840, Column 107: reference to external entity in attribute value
    …0334159796434&widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=caha…

    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 1840, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0334159796434&widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=caha…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 1840, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=cahaya13' onclick=…

    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 1840, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=cahaya13' onclick=…

    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 1840, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=cahaya13' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 1840, Column 142: reference not terminated by REFC delimiter
    …tId=HTML13&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1840, Column 142: reference to external entity in attribute value
    …tId=HTML13&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1840, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML13&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Warning Line 1851, Column 71: cannot generate system identifier for general entity "max-results"
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>

    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 1851, Column 71: general entity "max-results" not defined and no default entity
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>

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

  • Warning Line 1851, Column 82: reference not terminated by REFC delimiter
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>

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

  • Warning Line 1851, Column 82: reference to external entity in attribute value
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>

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

  • Error Line 1851, Column 82: reference to entity "max-results" for which no system identifier could be generated
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1854, Column 86: reference not terminated by REFC delimiter
    …ttp://www.peliculasonlineflv.net/search/label/Accion?&max-results=5'>Accion</a>

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

  • Warning Line 1854, Column 86: reference to external entity in attribute value
    …ttp://www.peliculasonlineflv.net/search/label/Accion?&max-results=5'>Accion</a>

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

  • Error Line 1854, Column 86: reference to entity "max-results" for which no system identifier could be generated
    …ttp://www.peliculasonlineflv.net/search/label/Accion?&max-results=5'>Accion</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1857, Column 92: reference not terminated by REFC delimiter
    …liculasonlineflv.net/search/label/Adolescentes?&max-results=5'>Adolescentes</a>

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

  • Warning Line 1857, Column 92: reference to external entity in attribute value
    …liculasonlineflv.net/search/label/Adolescentes?&max-results=5'>Adolescentes</a>

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

  • Error Line 1857, Column 92: reference to entity "max-results" for which no system identifier could be generated
    …liculasonlineflv.net/search/label/Adolescentes?&max-results=5'>Adolescentes</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1860, Column 90: reference not terminated by REFC delimiter
    …w.peliculasonlineflv.net/search/label/Animacion.?&max-results=5'>Animacion.</a>

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

  • Warning Line 1860, Column 90: reference to external entity in attribute value
    …w.peliculasonlineflv.net/search/label/Animacion.?&max-results=5'>Animacion.</a>

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

  • Error Line 1860, Column 90: reference to entity "max-results" for which no system identifier could be generated
    …w.peliculasonlineflv.net/search/label/Animacion.?&max-results=5'>Animacion.</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1863, Column 97: reference not terminated by REFC delimiter
    …nlineflv.net/search/label/Artes%20marciales?&max-results=5'>Artes marciales</a>

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

  • Warning Line 1863, Column 97: reference to external entity in attribute value
    …nlineflv.net/search/label/Artes%20marciales?&max-results=5'>Artes marciales</a>

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

  • Error Line 1863, Column 97: reference to entity "max-results" for which no system identifier could be generated
    …nlineflv.net/search/label/Artes%20marciales?&max-results=5'>Artes marciales</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1866, Column 88: reference not terminated by REFC delimiter
    …//www.peliculasonlineflv.net/search/label/Aventura?&max-results=5'>Aventura</a>

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

  • Warning Line 1866, Column 88: reference to external entity in attribute value
    …//www.peliculasonlineflv.net/search/label/Aventura?&max-results=5'>Aventura</a>

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

  • Error Line 1866, Column 88: reference to entity "max-results" for which no system identifier could be generated
    …//www.peliculasonlineflv.net/search/label/Aventura?&max-results=5'>Aventura</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1869, Column 109: reference not terminated by REFC delimiter
    …label/Basado%20en%20hechos%20reales?&max-results=5'>Basado en hechos reales</a>

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

  • Warning Line 1869, Column 109: reference to external entity in attribute value
    …label/Basado%20en%20hechos%20reales?&max-results=5'>Basado en hechos reales</a>

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

  • Error Line 1869, Column 109: reference to entity "max-results" for which no system identifier could be generated
    …label/Basado%20en%20hechos%20reales?&max-results=5'>Basado en hechos reales</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1872, Column 86: reference not terminated by REFC delimiter
    …ttp://www.peliculasonlineflv.net/search/label/Belico?&max-results=5'>Belico</a>

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

  • Warning Line 1872, Column 86: reference to external entity in attribute value
    …ttp://www.peliculasonlineflv.net/search/label/Belico?&max-results=5'>Belico</a>

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

  • Error Line 1872, Column 86: reference to entity "max-results" for which no system identifier could be generated
    …ttp://www.peliculasonlineflv.net/search/label/Belico?&max-results=5'>Belico</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1875, Column 97: reference not terminated by REFC delimiter
    …nlineflv.net/search/label/Ciencia%20Ficcion?&max-results=5'>Ciencia Ficcion</a>

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

  • Warning Line 1875, Column 97: reference to external entity in attribute value
    …nlineflv.net/search/label/Ciencia%20Ficcion?&max-results=5'>Ciencia Ficcion</a>

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

  • Error Line 1875, Column 97: reference to entity "max-results" for which no system identifier could be generated
    …nlineflv.net/search/label/Ciencia%20Ficcion?&max-results=5'>Ciencia Ficcion</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1878, Column 87: reference not terminated by REFC delimiter
    …p://www.peliculasonlineflv.net/search/label/Comedia?&max-results=5'>Comedia</a>

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

  • Warning Line 1878, Column 87: reference to external entity in attribute value
    …p://www.peliculasonlineflv.net/search/label/Comedia?&max-results=5'>Comedia</a>

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

  • Error Line 1878, Column 87: reference to entity "max-results" for which no system identifier could be generated
    …p://www.peliculasonlineflv.net/search/label/Comedia?&max-results=5'>Comedia</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1881, Column 86: reference not terminated by REFC delimiter
    …ttp://www.peliculasonlineflv.net/search/label/Crimen?&max-results=5'>Crimen</a>

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

  • Warning Line 1881, Column 86: reference to external entity in attribute value
    …ttp://www.peliculasonlineflv.net/search/label/Crimen?&max-results=5'>Crimen</a>

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

  • Error Line 1881, Column 86: reference to entity "max-results" for which no system identifier could be generated
    …ttp://www.peliculasonlineflv.net/search/label/Crimen?&max-results=5'>Crimen</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1884, Column 88: reference not terminated by REFC delimiter
    …//www.peliculasonlineflv.net/search/label/Deportes?&max-results=5'>Deportes</a>

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

  • Warning Line 1884, Column 88: reference to external entity in attribute value
    …//www.peliculasonlineflv.net/search/label/Deportes?&max-results=5'>Deportes</a>

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

  • Error Line 1884, Column 88: reference to entity "max-results" for which no system identifier could be generated
    …//www.peliculasonlineflv.net/search/label/Deportes?&max-results=5'>Deportes</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1887, Column 90: reference not terminated by REFC delimiter
    …w.peliculasonlineflv.net/search/label/Documental?&max-results=5'>Documental</a>

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

  • Warning Line 1887, Column 90: reference to external entity in attribute value
    …w.peliculasonlineflv.net/search/label/Documental?&max-results=5'>Documental</a>

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

  • Error Line 1887, Column 90: reference to entity "max-results" for which no system identifier could be generated
    …w.peliculasonlineflv.net/search/label/Documental?&max-results=5'>Documental</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1890, Column 85: reference not terminated by REFC delimiter
    …'http://www.peliculasonlineflv.net/search/label/Drama?&max-results=5'>Drama</a>

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

  • Warning Line 1890, Column 85: reference to external entity in attribute value
    …'http://www.peliculasonlineflv.net/search/label/Drama?&max-results=5'>Drama</a>

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

  • Error Line 1890, Column 85: reference to entity "max-results" for which no system identifier could be generated
    …'http://www.peliculasonlineflv.net/search/label/Drama?&max-results=5'>Drama</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1893, Column 87: reference not terminated by REFC delimiter
    …p://www.peliculasonlineflv.net/search/label/Erotica?&max-results=5'>Erotica</a>

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

  • Warning Line 1893, Column 87: reference to external entity in attribute value
    …p://www.peliculasonlineflv.net/search/label/Erotica?&max-results=5'>Erotica</a>

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

  • Error Line 1893, Column 87: reference to entity "max-results" for which no system identifier could be generated
    …p://www.peliculasonlineflv.net/search/label/Erotica?&max-results=5'>Erotica</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1896, Column 88: reference not terminated by REFC delimiter
    …//www.peliculasonlineflv.net/search/label/Familiar?&max-results=5'>Familiar</a>

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

  • Warning Line 1896, Column 88: reference to external entity in attribute value
    …//www.peliculasonlineflv.net/search/label/Familiar?&max-results=5'>Familiar</a>

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

  • Error Line 1896, Column 88: reference to entity "max-results" for which no system identifier could be generated
    …//www.peliculasonlineflv.net/search/label/Familiar?&max-results=5'>Familiar</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1899, Column 88: reference not terminated by REFC delimiter
    …//www.peliculasonlineflv.net/search/label/Fantasia?&max-results=5'>Fantasia</a>

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

  • Warning Line 1899, Column 88: reference to external entity in attribute value
    …//www.peliculasonlineflv.net/search/label/Fantasia?&max-results=5'>Fantasia</a>

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

  • Error Line 1899, Column 88: reference to entity "max-results" for which no system identifier could be generated
    …//www.peliculasonlineflv.net/search/label/Fantasia?&max-results=5'>Fantasia</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1902, Column 95: reference not terminated by REFC delimiter
    …iculasonlineflv.net/search/label/Fant%C3%A1stico?&max-results=5'>Fantástico</a>

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

  • Warning Line 1902, Column 95: reference to external entity in attribute value
    …iculasonlineflv.net/search/label/Fant%C3%A1stico?&max-results=5'>Fantástico</a>

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

  • Error Line 1902, Column 95: reference to entity "max-results" for which no system identifier could be generated
    …iculasonlineflv.net/search/label/Fant%C3%A1stico?&max-results=5'>Fantástico</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1905, Column 82: reference not terminated by REFC delimiter
    … href='http://www.peliculasonlineflv.net/search/label/HD?&max-results=5'>HD</a>

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

  • Warning Line 1905, Column 82: reference to external entity in attribute value
    … href='http://www.peliculasonlineflv.net/search/label/HD?&max-results=5'>HD</a>

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

  • Error Line 1905, Column 82: reference to entity "max-results" for which no system identifier could be generated
    … href='http://www.peliculasonlineflv.net/search/label/HD?&max-results=5'>HD</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1908, Column 88: reference not terminated by REFC delimiter
    …//www.peliculasonlineflv.net/search/label/Infantil?&max-results=5'>Infantil</a>

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

  • Warning Line 1908, Column 88: reference to external entity in attribute value
    …//www.peliculasonlineflv.net/search/label/Infantil?&max-results=5'>Infantil</a>

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

  • Error Line 1908, Column 88: reference to entity "max-results" for which no system identifier could be generated
    …//www.peliculasonlineflv.net/search/label/Infantil?&max-results=5'>Infantil</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1911, Column 87: reference not terminated by REFC delimiter
    …p://www.peliculasonlineflv.net/search/label/Intriga?&max-results=5'>Intriga</a>

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

  • Warning Line 1911, Column 87: reference to external entity in attribute value
    …p://www.peliculasonlineflv.net/search/label/Intriga?&max-results=5'>Intriga</a>

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

  • Error Line 1911, Column 87: reference to entity "max-results" for which no system identifier could be generated
    …p://www.peliculasonlineflv.net/search/label/Intriga?&max-results=5'>Intriga</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1914, Column 88: reference not terminated by REFC delimiter
    …//www.peliculasonlineflv.net/search/label/Misterio?&max-results=5'>Misterio</a>

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

  • Warning Line 1914, Column 88: reference to external entity in attribute value
    …//www.peliculasonlineflv.net/search/label/Misterio?&max-results=5'>Misterio</a>

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

  • Error Line 1914, Column 88: reference to entity "max-results" for which no system identifier could be generated
    …//www.peliculasonlineflv.net/search/label/Misterio?&max-results=5'>Misterio</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1917, Column 87: reference not terminated by REFC delimiter
    …p://www.peliculasonlineflv.net/search/label/musical?&max-results=5'>musical</a>

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

  • Warning Line 1917, Column 87: reference to external entity in attribute value
    …p://www.peliculasonlineflv.net/search/label/musical?&max-results=5'>musical</a>

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

  • Error Line 1917, Column 87: reference to entity "max-results" for which no system identifier could be generated
    …p://www.peliculasonlineflv.net/search/label/musical?&max-results=5'>musical</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1920, Column 87: reference not terminated by REFC delimiter
    …p://www.peliculasonlineflv.net/search/label/Romance?&max-results=5'>Romance</a>

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

  • Warning Line 1920, Column 87: reference to external entity in attribute value
    …p://www.peliculasonlineflv.net/search/label/Romance?&max-results=5'>Romance</a>

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

  • Error Line 1920, Column 87: reference to entity "max-results" for which no system identifier could be generated
    …p://www.peliculasonlineflv.net/search/label/Romance?&max-results=5'>Romance</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1923, Column 89: reference not terminated by REFC delimiter
    …www.peliculasonlineflv.net/search/label/Romantica?&max-results=5'>Romantica</a>

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

  • Warning Line 1923, Column 89: reference to external entity in attribute value
    …www.peliculasonlineflv.net/search/label/Romantica?&max-results=5'>Romantica</a>

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

  • Error Line 1923, Column 89: reference to entity "max-results" for which no system identifier could be generated
    …www.peliculasonlineflv.net/search/label/Romantica?&max-results=5'>Romantica</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1926, Column 88: reference not terminated by REFC delimiter
    …//www.peliculasonlineflv.net/search/label/Suspense?&max-results=5'>Suspense</a>

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

  • Warning Line 1926, Column 88: reference to external entity in attribute value
    …//www.peliculasonlineflv.net/search/label/Suspense?&max-results=5'>Suspense</a>

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

  • Error Line 1926, Column 88: reference to entity "max-results" for which no system identifier could be generated
    …//www.peliculasonlineflv.net/search/label/Suspense?&max-results=5'>Suspense</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1929, Column 86: reference not terminated by REFC delimiter
    …ttp://www.peliculasonlineflv.net/search/label/Terror?&max-results=5'>Terror</a>

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

  • Warning Line 1929, Column 86: reference to external entity in attribute value
    …ttp://www.peliculasonlineflv.net/search/label/Terror?&max-results=5'>Terror</a>

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

  • Error Line 1929, Column 86: reference to entity "max-results" for which no system identifier could be generated
    …ttp://www.peliculasonlineflv.net/search/label/Terror?&max-results=5'>Terror</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1932, Column 88: reference not terminated by REFC delimiter
    …//www.peliculasonlineflv.net/search/label/Thriller?&max-results=5'>Thriller</a>

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

  • Warning Line 1932, Column 88: reference to external entity in attribute value
    …//www.peliculasonlineflv.net/search/label/Thriller?&max-results=5'>Thriller</a>

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

  • Error Line 1932, Column 88: reference to entity "max-results" for which no system identifier could be generated
    …//www.peliculasonlineflv.net/search/label/Thriller?&max-results=5'>Thriller</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1935, Column 87: reference not terminated by REFC delimiter
    …p://www.peliculasonlineflv.net/search/label/western?&max-results=5'>western</a>

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

  • Warning Line 1935, Column 87: reference to external entity in attribute value
    …p://www.peliculasonlineflv.net/search/label/western?&max-results=5'>western</a>

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

  • Error Line 1935, Column 87: reference to entity "max-results" for which no system identifier could be generated
    …p://www.peliculasonlineflv.net/search/label/western?&max-results=5'>western</a>

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

  • Info Line 1851, Column 70: entity was defined here
    … href='http://www.peliculasonlineflv.net/search/label/3D?&max-results=5'>3D</a>
  • Warning Line 1941, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=Label&widgetId=Label1&action=editWidget…

    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 1941, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=Label&widgetId=Label1&action=editWidget…

    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 1941, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=Label&widgetId=Label1&action=editWidget…

    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 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 1941, Column 108: reference not terminated by REFC delimiter
    …334159796434&widgetType=Label&widgetId=Label1&action=editWidget&sectionId=caha…

    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 1941, Column 108: reference to external entity in attribute value
    …334159796434&widgetType=Label&widgetId=Label1&action=editWidget&sectionId=caha…

    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 1941, Column 108: reference to entity "widgetId" for which no system identifier could be generated
    …334159796434&widgetType=Label&widgetId=Label1&action=editWidget&sectionId=caha…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 1941, Column 122: reference not terminated by REFC delimiter
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1941, Column 122: reference to external entity in attribute value
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1941, Column 122: reference to entity "action" for which no system identifier could be generated
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 1941, Column 143: reference not terminated by REFC delimiter
    …tId=Label1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1941, Column 143: reference to external entity in attribute value
    …tId=Label1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1941, Column 143: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Label1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Warning Line 2161, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=Label&widgetId=Label2&action=editWidget…

    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 2161, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=Label&widgetId=Label2&action=editWidget…

    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 2161, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=Label&widgetId=Label2&action=editWidget…

    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 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 2161, Column 108: reference not terminated by REFC delimiter
    …334159796434&widgetType=Label&widgetId=Label2&action=editWidget&sectionId=caha…

    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 2161, Column 108: reference to external entity in attribute value
    …334159796434&widgetType=Label&widgetId=Label2&action=editWidget&sectionId=caha…

    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 2161, Column 108: reference to entity "widgetId" for which no system identifier could be generated
    …334159796434&widgetType=Label&widgetId=Label2&action=editWidget&sectionId=caha…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 2161, Column 122: reference not terminated by REFC delimiter
    …idgetType=Label&widgetId=Label2&action=editWidget&sectionId=cahaya13' onclick=…

    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 2161, Column 122: reference to external entity in attribute value
    …idgetType=Label&widgetId=Label2&action=editWidget&sectionId=cahaya13' onclick=…

    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 2161, Column 122: reference to entity "action" for which no system identifier could be generated
    …idgetType=Label&widgetId=Label2&action=editWidget&sectionId=cahaya13' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 2161, Column 143: reference not terminated by REFC delimiter
    …tId=Label2&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 2161, Column 143: reference to external entity in attribute value
    …tId=Label2&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 2161, Column 143: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Label2&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Warning Line 2231, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=PopularPosts&widgetId=PopularPosts1&act…

    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 2231, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=PopularPosts&widgetId=PopularPosts1&act…

    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 2231, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=PopularPosts&widgetId=PopularPosts1&act…

    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 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 2231, Column 115: reference not terminated by REFC delimiter
    …96434&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

    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 2231, Column 115: reference to external entity in attribute value
    …96434&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

    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 2231, Column 115: reference to entity "widgetId" for which no system identifier could be generated
    …96434&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&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.

  • Info Line 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 2231, Column 136: reference not terminated by REFC delimiter
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=cahaya13' onclick=…

    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 2231, Column 136: reference to external entity in attribute value
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=cahaya13' onclick=…

    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 2231, Column 136: reference to entity "action" for which no system identifier could be generated
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 2231, Column 157: reference not terminated by REFC delimiter
    …ularPosts1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 2231, Column 157: reference to external entity in attribute value
    …ularPosts1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 2231, Column 157: reference to entity "sectionId" for which no system identifier could be generated
    …ularPosts1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Warning Line 2241, Column 97: cannot generate system identifier for general entity "tag"
    …vL3d3dy5wZWxpY3VsYXNvbmxpbmVmbHYubmV0&tag=3" alt="PageRank Checking Icon" styl…

    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 2241, Column 97: general entity "tag" not defined and no default entity
    …vL3d3dy5wZWxpY3VsYXNvbmxpbmVmbHYubmV0&tag=3" alt="PageRank Checking Icon" styl…

    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 2241, Column 100: reference not terminated by REFC delimiter
    …d3dy5wZWxpY3VsYXNvbmxpbmVmbHYubmV0&tag=3" alt="PageRank Checking Icon" style="…

    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 2241, Column 100: reference to external entity in attribute value
    …d3dy5wZWxpY3VsYXNvbmxpbmVmbHYubmV0&tag=3" alt="PageRank Checking Icon" style="…

    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 2241, Column 100: reference to entity "tag" for which no system identifier could be generated
    …d3dy5wZWxpY3VsYXNvbmxpbmVmbHYubmV0&tag=3" alt="PageRank Checking Icon" style="…

    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 2241, Column 96: entity was defined here
    …ovL3d3dy5wZWxpY3VsYXNvbmxpbmVmbHYubmV0&tag=3" alt="PageRank Checking Icon" sty…
  • Warning Line 2256, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML1&action=editWidget&s…

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

  • Warning Line 2256, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML1&action=editWidget&s…

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

  • Error Line 2256, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML1&action=editWidget&s…

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

  • Info Line 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 2256, Column 107: reference not terminated by REFC delimiter
    …0334159796434&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=cahay…

    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 2256, Column 107: reference to external entity in attribute value
    …0334159796434&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=cahay…

    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 2256, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0334159796434&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=cahay…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 2256, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=cahaya13' onclick=…

    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 2256, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=cahaya13' onclick=…

    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 2256, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=cahaya13' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 2256, Column 141: reference not terminated by REFC delimiter
    …etId=HTML1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 2256, Column 141: reference to external entity in attribute value
    …etId=HTML1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 2256, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML1&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Warning Line 2264, Column 92: reference not terminated by REFC delimiter
    …rk.net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=3569780&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 2264, Column 92: reference to external entity in attribute value
    …rk.net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=3569780&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 2264, 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=3569780&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 1657, Column 75: entity was defined here
    …http://ad.adnetwork.net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section…
  • Warning Line 2264, Column 103: reference not terminated by REFC delimiter
    …d_type=pop&banned_pop_types=30&ad_size=0x0&section=3569780&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 2264, Column 103: reference to external entity in attribute value
    …d_type=pop&banned_pop_types=30&ad_size=0x0&section=3569780&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 2264, 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=3569780&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 1657, Column 95: entity was defined here
    …net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=3524243&pop_times=1…
  • Warning Line 2264, Column 115: reference not terminated by REFC delimiter
    …anned_pop_types=30&ad_size=0x0&section=3569780&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 2264, Column 115: reference to external entity in attribute value
    …anned_pop_types=30&ad_size=0x0&section=3569780&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 2264, Column 115: reference to entity "section" for which no system identifier could be generated
    …anned_pop_types=30&ad_size=0x0&section=3569780&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 1657, Column 107: entity was defined here
    …pe=pop&banned_pop_types=30&ad_size=0x0&section=3524243&pop_times=1&pop_frequen…
  • Warning Line 2264, Column 133: reference not terminated by REFC delimiter
    …types=30&ad_size=0x0&section=3569780&pop_times=1&pop_frequency=3600" ></script>

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

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

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

  • Info Line 1657, Column 123: entity was defined here
    …p_types=30&ad_size=0x0&section=3524243&pop_times=1&pop_frequency=3600" ></scri…
  • Warning Line 2264, Column 149: reference not terminated by REFC delimiter
    …types=30&ad_size=0x0&section=3569780&pop_times=1&pop_frequency=3600" ></script>

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

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

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

  • Info Line 1657, Column 135: entity was defined here
    …types=30&ad_size=0x0&section=3524243&pop_times=1&pop_frequency=3600" ></script>
  • Warning Line 2266, Column 92: reference not terminated by REFC delimiter
    …rk.net/st?ad_type=pop&banned_pop_types=29&ad_size=0x0&section=3569780&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 2266, Column 92: reference to external entity in attribute value
    …rk.net/st?ad_type=pop&banned_pop_types=29&ad_size=0x0&section=3569780&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 2266, 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=29&ad_size=0x0&section=3569780&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 1657, Column 75: entity was defined here
    …http://ad.adnetwork.net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section…
  • Warning Line 2266, Column 103: reference not terminated by REFC delimiter
    …d_type=pop&banned_pop_types=29&ad_size=0x0&section=3569780&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 2266, Column 103: reference to external entity in attribute value
    …d_type=pop&banned_pop_types=29&ad_size=0x0&section=3569780&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 2266, Column 103: reference to entity "ad_size" for which no system identifier could be generated
    …d_type=pop&banned_pop_types=29&ad_size=0x0&section=3569780&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 1657, Column 95: entity was defined here
    …net/st?ad_type=pop&banned_pop_types=30&ad_size=0x0&section=3524243&pop_times=1…
  • Warning Line 2266, Column 115: reference not terminated by REFC delimiter
    …anned_pop_types=29&ad_size=0x0&section=3569780&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 2266, Column 115: reference to external entity in attribute value
    …anned_pop_types=29&ad_size=0x0&section=3569780&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 2266, Column 115: reference to entity "section" for which no system identifier could be generated
    …anned_pop_types=29&ad_size=0x0&section=3569780&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 1657, Column 107: entity was defined here
    …pe=pop&banned_pop_types=30&ad_size=0x0&section=3524243&pop_times=1&pop_frequen…
  • Warning Line 2266, Column 133: reference not terminated by REFC delimiter
    …types=29&ad_size=0x0&section=3569780&pop_times=1&pop_frequency=3600" ></script>

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

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

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

  • Info Line 1657, Column 123: entity was defined here
    …p_types=30&ad_size=0x0&section=3524243&pop_times=1&pop_frequency=3600" ></scri…
  • Warning Line 2266, Column 149: reference not terminated by REFC delimiter
    …types=29&ad_size=0x0&section=3569780&pop_times=1&pop_frequency=3600" ></script>

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

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

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

  • Info Line 1657, Column 135: entity was defined here
    …types=30&ad_size=0x0&section=3524243&pop_times=1&pop_frequency=3600" ></script>
  • Warning Line 2271, Column 93: reference not terminated by REFC delimiter
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML14&action=editWidget&…

    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 2271, Column 93: reference to external entity in attribute value
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML14&action=editWidget&…

    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 2271, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML14&action=editWidget&…

    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 1026, Column 82: entity was defined here
    …m/rearrange?blogID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=e…
  • Warning Line 2271, Column 107: reference not terminated by REFC delimiter
    …0334159796434&widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=caha…

    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 2271, Column 107: reference to external entity in attribute value
    …0334159796434&widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=caha…

    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 2271, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0334159796434&widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=caha…

    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 1026, Column 98: entity was defined here
    …ID=8268280334159796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectio…
  • Warning Line 2271, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=cahaya13' onclick=…

    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 2271, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=cahaya13' onclick=…

    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 2271, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=cahaya13' onclick=…

    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 1026, Column 113: entity was defined here
    …9796434&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' o…
  • Warning Line 2271, Column 142: reference not terminated by REFC delimiter
    …tId=HTML14&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 2271, Column 142: reference to external entity in attribute value
    …tId=HTML14&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 2271, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML14&action=editWidget&sectionId=cahaya13' onclick='return _WidgetManage…

    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 1026, Column 131: entity was defined here
    …=HTML&widgetId=HTML5&action=editWidget&sectionId=gadget-1' onclick='return _Wi…
  • Error Line 2291, Column 302: there is no attribute "align"
    …emplates Blogger </a></div><div align='right'><a href='http://www.blogger.com'…

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

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

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

  • Error Line 2292, Column 8: element "center" undefined
    <center><p></p>

    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 2293, Column 3: element "u" undefined
    <u> Tags:</u> ESTRENOS 2013,Peliculas en Estreno, Divx Online, Peliculas Gratis…

    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 2296, Column 8: element "center" undefined
    <center><a href='http://www.dmca.com/Protection/Status.aspx?ID=a0750f34-c522-46…

    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 2317, Column 7: required attribute "type" not specified
    <style>#fblikepop{background-color:#fff;display:none;position:fixed;top:200px;_…

    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 2317, Column 7: document type does not allow element "style" here
    <style>#fblikepop{background-color:#fff;display:none;position:fixed;top:200px;_…

    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 2320, Column 18: there is no attribute "language"
    <script language='javascript'> //<![CDATA[ $(document).ready(function(){ $().KN…

    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 2320, Column 30: required attribute "type" not specified
    <script language='javascript'> //<![CDATA[ $(document).ready(function(){ $().KN…

    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 2322, Column 21: there is no attribute "oncontextmenu"
    <body oncontextmenu='return false' ondragstart='return false' onselectstart='re…

    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 2322, Column 48: there is no attribute "ondragstart"
    …ontextmenu='return false' ondragstart='return false' onselectstart='return fal…

    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 2322, Column 77: there is no attribute "onselectstart"
    …='return false' ondragstart='return false' onselectstart='return false'></body>

    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 2322, Column 91: document type does not allow element "body" here
    …='return false' ondragstart='return false' onselectstart='return false'></body>

    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 2328, Column 49: character "&" is the first character of a delimiter but occurred as data
    …(BLOG_attachCsiOnload) != 'undefined' && BLOG_attachCsiOnload != null) { windo…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 2328, Column 50: character "&" is the first character of a delimiter but occurred as data
    …BLOG_attachCsiOnload) != 'undefined' && BLOG_attachCsiOnload != null) { window…

    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.

Visitor Analysis

Daily Visitor
  • 16.333 visits
Daily Visitor

In Page Analysis