PeliculasChingonas, Peliculas Online, Ver peliculas gratis sin cortes, cine gratis, estrenos online, descargar peliculas, series online, ver peliculas online, ver videos divx ...

peliculaschingonas.com
  • Domain Name
    peliculaschingonas.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #16613
  • Page Size
    176.5 KB
  • Ip Address
    216.239.36.21
  • Heading
    H1: 0, H2: 6, H3: 24, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 25 JPG, 18 PNG

Website Meta Analysis

  • Title
    Pelicula Online Gratis
  • Meta Keyword
    PeliculasChingonas, cine online,peliculas online,estrenos online,peliculas gratis, ver online
  • Meta Description
    PeliculasChingonas, Peliculas Online, Ver peliculas gratis sin cortes, cine gratis, estrenos online, descargar peliculas, series online, ver peliculas online, ver videos divx

Technical Analysis

  • Webserver
    GSE
  • Ip Address
    216.239.36.21
  • Domain Age
    1 Years, 9 Months, 7 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-type: text/html; charset=UTF-8
  • expires: Fri, 28 Jun 2013 12:14:23 GMT
  • date: Fri, 28 Jun 2013 12:14:23 GMT
  • cache-control: private, max-age=0
  • last-modified: Thu, 27 Jun 2013 23:11:05 GMT
  • etag: "bb86a213-951e-4ef7-816c-340260a41bc4"
  • content-encoding: gzip
  • x-content-type-options: nosniff
  • x-xss-protection: 1; mode=block
  • content-length: 28712
  • server: GSE
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for peliculaschingonas.com

DNS Analysis


DNS servers
dns1.name-services.com [98.124.192.1]
dns2.name-services.com [98.124.197.1]
dns3.name-services.com [98.124.193.1]
dns4.name-services.com [98.124.194.1]
dns5.name-services.com [98.124.196.1]


DNS Records

Answer records
peliculaschingonas.com MX
preference: 30
exchange: aspmx2.googlemail.com
1800s
peliculaschingonas.com A 216.239.32.21 1800s
peliculaschingonas.com NS  dns3.name-services.com 3600s
peliculaschingonas.com NS  dns1.name-services.com 3600s
peliculaschingonas.com SOA
server: dns1.name-services.com
email: info@name-services.com
serial: 2002050701
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
1800s
peliculaschingonas.com MX
preference: 30
exchange: aspmx3.googlemail.com
1800s
peliculaschingonas.com A 216.239.36.21 1800s
peliculaschingonas.com MX
preference: 20
exchange: alt1.aspmx.l.google.com
1800s
peliculaschingonas.com A 216.239.34.21 1800s
peliculaschingonas.com A 216.239.38.21 1800s
peliculaschingonas.com MX
preference: 20
exchange: alt2.aspmx.l.google.com
1800s
peliculaschingonas.com NS  dns4.name-services.com 3600s
peliculaschingonas.com MX
preference: 10
exchange: aspmx.l.google.com
1800s
peliculaschingonas.com NS  dns2.name-services.com 3600s
peliculaschingonas.com NS  dns5.name-services.com 3600s

Authority records

Additional records

IP 216.239.36.21 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • Checking IP address is 216.239.36.21

    IP Information

    Country Code: US
    Country Code3: USA
    Country Name: us United States
    City: San Francisco
    Area Code: 415
    Dma Code: 807
    Metro Code: 807
    Continent Code: NA
    Latitude: 37°76'45" North
    Longitude: 122°42'94" West

    IP Location Map

    Loading Map...

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 276 Errors
  • 207 Warnings
Ratio Text/Html
  • 0.37815251620187174
Message Error
  • Error Line 4, Column 15: there is no attribute "CONTENT"
    <META CONTENT='Peliculas Online gratis sin restricciones' NAME='Title'></META>

    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 4, Column 64: there is no attribute "NAME"
    <META CONTENT='Peliculas Online gratis sin restricciones' NAME='Title'></META>

    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 4, Column 71: element "META" undefined
    <META CONTENT='Peliculas Online gratis sin restricciones' NAME='Title'></META>

    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 5, Column 44: element "META" undefined
    <META CONTENT='Administrador' NAME='Author'></META>

    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 6, Column 55: element "META" undefined
    <META CONTENT='Peliculas Online Gratis' NAME='Subject'></META>

    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 7, Column 210: element "META" undefined
    …eries online, ver peliculas online, ver videos divx' NAME='Description'></META>

    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 8, Column 126: element "META" undefined
    …as online,estrenos online,peliculas gratis, ver online' NAME='Keywords'></META>

    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 9, Column 41: element "META" undefined
    <META CONTENT='Blogger' NAME='Generator'></META>

    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 10, Column 40: element "META" undefined
    <META CONTENT='Spanish' NAME='Language'></META>

    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 11, Column 37: element "META" undefined
    <META CONTENT='1 day' NAME='Revisit'></META>

    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 12, Column 43: element "META" undefined
    <META CONTENT='Global' NAME='Distribution'></META>

    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 13, Column 34: element "META" undefined
    <META CONTENT='All' NAME='Robots'></META>

    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 15, Column 275: character "&" is the first character of a delimiter but occurred as data
    …ming={Timer:d,load:a};if(b.performance&&b.performance.timing){var a=b.performa…

    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 15, Column 277: cannot generate system identifier for general entity "b.performance.timing"
    …ng={Timer:d,load:a};if(b.performance&&b.performance.timing){var a=b.performanc…

    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 15, Column 277: general entity "b.performance.timing" not defined and no default entity
    …ng={Timer:d,load:a};if(b.performance&&b.performance.timing){var a=b.performanc…

    This is usually a cascading error caused by 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 15, Column 297: reference not terminated by REFC delimiter
    …if(b.performance&&b.performance.timing){var a=b.performance.timing,c=b[e].load…

    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 15, Column 297: reference to entity "b.performance.timing" for which no system identifier could be generated
    …if(b.performance&&b.performance.timing){var a=b.performance.timing,c=b[e].load…

    This is usually a cascading error caused by 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 15, Column 276: entity was defined here
    …ing={Timer:d,load:a};if(b.performance&&b.performance.timing){var a=b.performan…
  • Error Line 15, Column 379: character "&" not allowed in attribute specification list
    ….navigationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("w…
  • Error Line 15, Column 379: element "f" undefined
    ….navigationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("w…

    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 15, Column 381: cannot generate system identifier for general entity "a"
    …avigationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("wts…

    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 15, Column 381: general entity "a" not defined and no default entity
    …avigationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("wts…

    This is usually a cascading error caused by 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 15, Column 382: reference not terminated by REFC delimiter
    …vigationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("wtsr…

    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 15, Column 382: reference to entity "a" for which no system identifier could be generated
    …vigationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("wtsr…

    This is usually a cascading error caused by 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 15, Column 380: entity was defined here
    …navigationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("wt…
  • Warning Line 15, Column 385: character "&" is the first character of a delimiter but occurred as data
    …ationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("wtsrt_"…

    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 15, Column 386: character "&" is the first character of a delimiter but occurred as data
    …tionStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("wtsrt_",…

    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 15, Column 481: character "&" is the first character of a delimiter but occurred as data
    …"tbsd_","wtsrt_"))}try{a=null,b.chrome&&b.chrome.csi&&(a=Math.floor(b.chrome.c…

    This message may appear in several cases:

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

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

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

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

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

  • Error Line 15, Column 483: general entity "b.chrome.csi" not defined and no default entity
    …bsd_","wtsrt_"))}try{a=null,b.chrome&&b.chrome.csi&&(a=Math.floor(b.chrome.csi…

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

  • Warning Line 15, Column 495: reference not terminated by REFC delimiter
    …_"))}try{a=null,b.chrome&&b.chrome.csi&&(a=Math.floor(b.chrome.csi().pageT),c&…

    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 15, Column 495: reference to entity "b.chrome.csi" for which no system identifier could be generated
    …_"))}try{a=null,b.chrome&&b.chrome.csi&&(a=Math.floor(b.chrome.csi().pageT),c&…

    This is usually a cascading error caused by 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 15, Column 482: entity was defined here
    …tbsd_","wtsrt_"))}try{a=null,b.chrome&&b.chrome.csi&&(a=Math.floor(b.chrome.cs…
  • Warning Line 15, Column 495: character "&" is the first character of a delimiter but occurred as data
    …_"))}try{a=null,b.chrome&&b.chrome.csi&&(a=Math.floor(b.chrome.csi().pageT),c&…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    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 15, Column 535: character "&" is the first character of a delimiter but occurred as data
    …(a=Math.floor(b.chrome.csi().pageT),c&&0<f&&(c[g]("_tbnd",void 0,b.chrome.csi(…

    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 15, Column 539: character "&" not allowed in attribute specification list
    …ath.floor(b.chrome.csi().pageT),c&&0<f&&(c[g]("_tbnd",void 0,b.chrome.csi().st…
  • Error Line 15, Column 539: element "f" undefined
    …ath.floor(b.chrome.csi().pageT),c&&0<f&&(c[g]("_tbnd",void 0,b.chrome.csi().st…

    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 15, Column 540: character "&" is the first character of a delimiter but occurred as data
    …th.floor(b.chrome.csi().pageT),c&&0<f&&(c[g]("_tbnd",void 0,b.chrome.csi().sta…

    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 16, Column 34: character "&" is the first character of a delimiter but occurred as data
    c[g]("tbnd_","_tbnd",f))),null==a&&b.gtbExternal&&(a=b.gtbExternal.pageT()),nul…

    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 16, Column 36: cannot generate system identifier for general entity "b.gtbExternal"
    c[g]("tbnd_","_tbnd",f))),null==a&&b.gtbExternal&&(a=b.gtbExternal.pageT()),nul…

    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 16, Column 36: general entity "b.gtbExternal" not defined and no default entity
    c[g]("tbnd_","_tbnd",f))),null==a&&b.gtbExternal&&(a=b.gtbExternal.pageT()),nul…

    This is usually a cascading error caused by 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 16, Column 49: reference not terminated by REFC delimiter
    …_","_tbnd",f))),null==a&&b.gtbExternal&&(a=b.gtbExternal.pageT()),null==a&&b.e…

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

  • Error Line 16, Column 49: reference to entity "b.gtbExternal" for which no system identifier could be generated
    …_","_tbnd",f))),null==a&&b.gtbExternal&&(a=b.gtbExternal.pageT()),null==a&&b.e…

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

  • Info Line 16, Column 35: entity was defined here
    c[g]("tbnd_","_tbnd",f))),null==a&&b.gtbExternal&&(a=b.gtbExternal.pageT()),nul…
  • Warning Line 16, Column 49: character "&" is the first character of a delimiter but occurred as data
    …_","_tbnd",f))),null==a&&b.gtbExternal&&(a=b.gtbExternal.pageT()),null==a&&b.e…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    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 16, Column 86: cannot generate system identifier for general entity "b.external"
    …l&&(a=b.gtbExternal.pageT()),null==a&&b.external&&(a=b.external.pageT,c&&0<f&&…

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

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

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

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

  • Error Line 16, Column 86: general entity "b.external" not defined and no default entity
    …l&&(a=b.gtbExternal.pageT()),null==a&&b.external&&(a=b.external.pageT,c&&0<f&&…

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

  • Warning Line 16, Column 96: reference not terminated by REFC delimiter
    …bExternal.pageT()),null==a&&b.external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tb…

    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 16, Column 96: reference to entity "b.external" for which no system identifier could be generated
    …bExternal.pageT()),null==a&&b.external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tb…

    This is usually a cascading error caused by 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 16, Column 85: entity was defined here
    …al&&(a=b.gtbExternal.pageT()),null==a&&b.external&&(a=b.external.pageT,c&&0<f&…
  • Warning Line 16, Column 96: character "&" is the first character of a delimiter but occurred as data
    …bExternal.pageT()),null==a&&b.external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tb…

    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 16, Column 97: character "&" is the first character of a delimiter but occurred as data
    …External.pageT()),null==a&&b.external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tbn…

    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 16, Column 119: character "&" is the first character of a delimiter but occurred as data
    …==a&&b.external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tbnd",void 0,b.external.s…

    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 16, Column 120: character "&" is the first character of a delimiter but occurred as data
    …=a&&b.external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tbnd",void 0,b.external.st…

    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 16, Column 124: character "&" not allowed in attribute specification list
    …b.external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tbnd",void 0,b.external.startE…
  • Error Line 16, Column 124: element "f" undefined
    …b.external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tbnd",void 0,b.external.startE…

    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 16, Column 125: character "&" is the first character of a delimiter but occurred as data
    ….external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tbnd",void 0,b.external.startE)…

    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 16, Column 193: character "&" is the first character of a delimiter but occurred as data
    …al.startE),c[g]("tbnd_","_tbnd",f))),a&&(b[e].pt=a)}catch(l){}})();b.tickAbove…

    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 16, Column 194: character "&" is the first character of a delimiter but occurred as data
    …l.startE),c[g]("tbnd_","_tbnd",f))),a&&(b[e].pt=a)}catch(l){}})();b.tickAboveF…

    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 16, Column 329: character "&" is the first character of a delimiter but occurred as data
    …Top;while(d=d.offsetParent)}d=a;750>=d&&b[e].load[g]("aft")};var h=!1;function…

    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 16, Column 331: cannot generate system identifier for general entity "b"
    …p;while(d=d.offsetParent)}d=a;750>=d&&b[e].load[g]("aft")};var h=!1;function 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 16, Column 331: general entity "b" not defined and no default entity
    …p;while(d=d.offsetParent)}d=a;750>=d&&b[e].load[g]("aft")};var h=!1;function 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 16, Column 332: reference not terminated by REFC delimiter
    …;while(d=d.offsetParent)}d=a;750>=d&&b[e].load[g]("aft")};var h=!1;function 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 16, Column 332: reference to entity "b" for which no system identifier could be generated
    …;while(d=d.offsetParent)}d=a;750>=d&&b[e].load[g]("aft")};var h=!1;function 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 16, Column 330: entity was defined here
    …op;while(d=d.offsetParent)}d=a;750>=d&&b[e].load[g]("aft")};var h=!1;function …
  • Error Line 17, Column 15: end tag for "f" omitted, but OMITTAG NO was specified
     })();</script>

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

  • Info Line 16, Column 122: start tag was here
    …&&b.external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tbnd",void 0,b.external.star…
  • Error Line 17, Column 15: end tag for "f" omitted, but OMITTAG NO was specified
     })();</script>

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

  • Info Line 15, Column 537: start tag was here
    …=Math.floor(b.chrome.csi().pageT),c&&0<f&&(c[g]("_tbnd",void 0,b.chrome.csi().…
  • Error Line 17, Column 15: end tag for "f" omitted, but OMITTAG NO was specified
     })();</script>

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

  • Info Line 15, Column 377: start tag was here
    …=a.navigationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g](…
  • Warning Line 34, Column 123: cannot generate system identifier for general entity "zx"
    ….css?targetBlogID=2205884632271679200&zx=fae88a1f-cfe2-471f-8236-871eae9a3097"…

    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 34, Column 123: general entity "zx" not defined and no default entity
    ….css?targetBlogID=2205884632271679200&zx=fae88a1f-cfe2-471f-8236-871eae9a3097"…

    This is usually a cascading error caused by 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 34, Column 125: reference not terminated by REFC delimiter
    …css?targetBlogID=2205884632271679200&zx=fae88a1f-cfe2-471f-8236-871eae9a3097"/>

    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 34, Column 125: reference to external entity in attribute value
    …css?targetBlogID=2205884632271679200&zx=fae88a1f-cfe2-471f-8236-871eae9a3097"/>

    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 34, Column 125: reference to entity "zx" for which no system identifier could be generated
    …css?targetBlogID=2205884632271679200&zx=fae88a1f-cfe2-471f-8236-871eae9a3097"/>

    This is usually a cascading error caused by 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 34, Column 122: entity was defined here
    …n.css?targetBlogID=2205884632271679200&zx=fae88a1f-cfe2-471f-8236-871eae9a3097…
  • Warning Line 36, Column 7: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 11: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 15: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 19: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 23: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 27: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 31: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 35: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 39: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 43: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 47: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 51: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 55: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 59: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 63: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 36, Column 67: multiple comments in comment declaration
    /*--------------------------------------------------------------------
  • Warning Line 40, Column 1: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 5: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 9: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 13: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 17: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 21: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 25: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 29: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 33: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 37: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 41: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 45: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 49: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 53: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 57: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 61: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 65: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 69: multiple comments in comment declaration
    ---------------------------------------------------------------------- */
  • Warning Line 40, Column 71: S separator in comment declaration
    ---------------------------------------------------------------------- */

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

  • Error Line 40, Column 72: invalid comment declaration: found character "*" outside comment but inside comment declaration
    ---------------------------------------------------------------------- */

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 35, Column 41: comment declaration started here
    <style id='page-skin-1' type='text/css'><!--
  • Error Line 1133, Column 10: document type does not allow element "noscript" here; assuming missing "object" start-tag
    <noscript></noscript><!-- --><script src='https://paginacion-script.googlecode.…
  • Error Line 1189, Column 7: required attribute "type" not specified
    <style>

    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 1189, Column 7: document type does not allow element "style" here
    <style>

    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 1239, Column 37: there is no attribute "property"
    <meta content='1188732491' property='fb:admins'/>

    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 1239, Column 49: document type does not allow element "meta" here
    <meta content='1188732491' property='fb:admins'/>

    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 1240, Column 54: document type does not allow element "meta" here
    <meta content='155725037799922' property='fb:app_id'/>

    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 1253, Column 78: cannot generate system identifier for general entity "m"
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",k="?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 1253, Column 78: general entity "m" not defined and no default entity
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",k="?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 1253, Column 79: reference not terminated by REFC delimiter
    …igator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",k="?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 1253, 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="?",k="?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 1253, Column 77: entity was defined here
    …avigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",k="?m=1";functio…
  • Warning Line 1253, Column 89: character "&" is the first character of a delimiter but occurred as data
    …userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",k="?m=1";function l(){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 1253, Column 213: character "<" is the first character of a delimiter but occurred as data
    …gth){case 1:return d+k;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 1253, 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 1253, 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 1253, 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 1253, 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 1253, Column 393: character "&" is the first character of a delimiter but occurred as data
    …pera Mini")||-1!=a[b][c]("IEMobile")){var m=l();m&&window.location.replace(m)};

    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 1253, Column 395: cannot generate system identifier for general entity "window.location.replace"
    …pera Mini")||-1!=a[b][c]("IEMobile")){var m=l();m&&window.location.replace(m)};

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

    This is usually a cascading error caused by 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 1253, Column 418: reference not terminated by REFC delimiter
    …pera Mini")||-1!=a[b][c]("IEMobile")){var m=l();m&&window.location.replace(m)};

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

    This is usually a cascading error caused by 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 1253, Column 394: entity was defined here
    …pera Mini")||-1!=a[b][c]("IEMobile")){var m=l();m&&window.location.replace(m)};
  • Error Line 1256, Column 16: end tag for "object" omitted, but OMITTAG NO was specified
    </script></head>

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

  • Info Line 1133, Column 1: start tag was here
    <noscript></noscript><!-- --><script src='https://paginacion-script.googlecode.…
  • Warning Line 1272, 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 1272, 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 1309, Column 102: there is no attribute "target"
    …nas.com/search/label/Estrenos' target='_blank' title='Peliculas Estrenos Onlin…

    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 1324, Column 35: ID "crosscol-bottom" already defined
    <div class='crosscol section' id='crosscol-bottom'><div class='widget HTML' id=…

    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 1323, Column 10: ID "crosscol-bottom" first defined here
    <div id='crosscol-bottom' style='text-align: center; padding: 10px; text-transf…
  • Error Line 1327, Column 42: there is no attribute "scrolling"
    …v class="slideshow"><iframe scrolling="No" width="920" frameborder="0" src="ht…

    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 1327, Column 53: there is no attribute "width"
    …ideshow"><iframe scrolling="No" width="920" frameborder="0" src="http://cinein…

    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 1327, Column 71: there is no attribute "frameborder"
    …crolling="No" width="920" frameborder="0" src="http://cineinternet.ucoz.com/es…

    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 1327, Column 79: there is no attribute "src"
    …="No" width="920" frameborder="0" src="http://cineinternet.ucoz.com/estrenopel…

    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 1327, Column 149: there is no attribute "height"
    …internet.ucoz.com/estrenopeliculasschingonas.html" height="125"></iframe></div>

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

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

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

  • Error Line 1327, Column 154: element "iframe" undefined
    …internet.ucoz.com/estrenopeliculasschingonas.html" height="125"></iframe></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 1333, Column 83: cannot generate system identifier for general entity "widgetType"
    …/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&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 1333, Column 83: general entity "widgetType" not defined and no default entity
    …/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&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 1333, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&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 1333, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&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 1333, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 1333, Column 99: cannot generate system identifier for general entity "widgetId"
    …D=2205884632271679200&widgetType=HTML&widgetId=HTML4&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 1333, Column 99: general entity "widgetId" not defined and no default entity
    …D=2205884632271679200&widgetType=HTML&widgetId=HTML4&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 1333, Column 107: reference not terminated by REFC delimiter
    …4632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=cross…

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

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

    This is usually a cascading error caused by 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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 1333, Column 114: cannot generate system identifier for general entity "action"
    …679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bot…

    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 1333, Column 114: general entity "action" not defined and no default entity
    …679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bot…

    This is usually a cascading error caused by 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 1333, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' o…

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

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

    This is usually a cascading error caused by 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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 1333, Column 132: cannot generate system identifier for general entity "sectionId"
    …HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='retu…

    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 1333, Column 132: general entity "sectionId" not defined and no default entity
    …HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='retu…

    This is usually a cascading error caused by 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 1333, Column 141: reference not terminated by REFC delimiter
    …etId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='return _Widge…

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

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

    This is usually a cascading error caused by 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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Error Line 1341, Column 8: element "center" undefined
    <center><a target="_blank" href="http://serieschingonas.com"><span style="font-…

    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 1341, Column 200: element "center" undefined
    …ucho mas...</span></a></center><center><table border="0" summary="Series Onlin…

    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 1342, Column 256: there is no attribute "border"
    …ries%2Bchingonas%2Bonline.png" border="0" alt="Series chingonas Online Gratis"…

    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 1347, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&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 1347, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&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 1347, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 1347, Column 107: reference not terminated by REFC delimiter
    …4632271679200&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=cross…

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

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

    This is usually a cascading error caused by 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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 1347, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=crosscol-bottom' o…

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

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

    This is usually a cascading error caused by 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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 1347, Column 141: reference not terminated by REFC delimiter
    …etId=HTML7&action=editWidget&sectionId=crosscol-bottom' onclick='return _Widge…

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

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

    This is usually a cascading error caused by 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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Error Line 1357, Column 8: element "center" undefined
    <center><table width="300" border="0"> 

    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 1360, Column 88: there is no attribute "marginwidth"
    …spot.com" frameborder="0" marginwidth="0" marginheight="0" scrolling="NO" widt…

    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 1360, Column 105: there is no attribute "marginheight"
    …rder="0" marginwidth="0" marginheight="0" scrolling="NO" width="300" height="2…

    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 1360, Column 148: element "iframe" undefined
    …" marginheight="0" scrolling="NO" width="300" height="250"></iframe></td><br />

    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 1360, Column 168: document type does not allow element "br" here; missing one of "th", "td" start-tag
    …" marginheight="0" scrolling="NO" width="300" height="250"></iframe></td><br />

    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 1361, Column 152: element "iframe" undefined
    …" marginheight="0" scrolling="NO" width="300" height="250"></iframe></td><br />

    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 1361, Column 172: document type does not allow element "br" here; missing one of "th", "td" start-tag
    …" marginheight="0" scrolling="NO" width="300" height="250"></iframe></td><br />

    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 1362, Column 152: element "iframe" undefined
    …dth="0" marginheight="0" scrolling="NO" width="300" height="250"></iframe></td>

    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 1369, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML2&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 1369, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML2&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 1369, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML2&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 1369, Column 107: reference not terminated by REFC delimiter
    …4632271679200&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=cross…

    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 1369, Column 107: reference to external entity in attribute value
    …4632271679200&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=cross…

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

    This is usually a cascading error caused by 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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 1369, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=crosscol-bottom' o…

    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 1369, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=crosscol-bottom' o…

    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 1369, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=crosscol-bottom' o…

    This is usually a cascading error caused by 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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 1369, Column 141: reference not terminated by REFC delimiter
    …etId=HTML2&action=editWidget&sectionId=crosscol-bottom' onclick='return _Widge…

    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 1369, Column 141: reference to external entity in attribute value
    …etId=HTML2&action=editWidget&sectionId=crosscol-bottom' onclick='return _Widge…

    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 1369, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML2&action=editWidget&sectionId=crosscol-bottom' onclick='return _Widge…

    This is usually a cascading error caused by 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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Error Line 1379, Column 42: there is no attribute "align"
    <div style='padding-top:0px;'><div align='center'><div id='cc0'>

    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 1399, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary7360325540413790653'><div style="text-align: justify;"><span st…

    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 1399, Column 1287: there is no attribute "imageanchor"
    …-n-love-2011-online.html" imageanchor="1" style="clear:left; float:left;margin…

    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 1399, Column 1578: required attribute "alt" not specified
    …99%2BLove%2529%2B%25282011%2529.jpg" /></a></div><div style="text-align: justi…

    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 1401, Column 989: end tag for "input" omitted, but OMITTAG NO was specified
    …mundo.</span></div><input name="IL_RELATED_TAGS" value="1" type="hidden"><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 1401, Column 935: start tag was here
    …a mejor música del mundo.</span></div><input name="IL_RELATED_TAGS" value="1" …
  • Error Line 1402, Column 8: element "center" undefined
    <center><span style="color: #0000f0; font-size:130%;"><strong>Idioma Subtitulad…

    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 1404, Column 190: element "iframe" undefined
    …e.html" frameborder="0" height="480" scrolling="no" width="600"></iframe><br />

    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 1408, Column 183: element "iframe" undefined
    …rameborder="0" height="480" scrolling="no" width="600"></iframe></center></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 1409, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1430, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary4448763141595209715'><div style="text-align: justify;"><span st…

    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 1430, Column 1063: required attribute "alt" not specified
    …cH2ZoWehds/s1600/Invasor+(2012).jpg" /></a></div><div style="text-align: justi…

    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 1433, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1433, Column 173: element "iframe" undefined
    ….org/2013/03/ver-invasor-2012-online.html" width="600"></iframe></center></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 1434, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1455, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary7922699586048018670'><div style="text-align: justify;"><span st…

    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 1455, Column 1175: required attribute "alt" not specified
    …hMo/s1600/Dans+La+Maison+(2012).jpg" /></a></div><div style="text-align: justi…

    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 1458, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1458, Column 180: element "iframe" undefined
    …13/03/ver-dans-la-maison-2012-online.html" width="600"></iframe></center></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 1459, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1480, Column 36: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary909359111168724808'><div style="text-align: justify;"><span sty…

    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 1480, Column 1030: required attribute "alt" not specified
    …/vThmfjsO1m8/s1600/Flukt+(2012).jpg" /></a></div><div style="text-align: justi…

    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 1483, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1483, Column 171: element "iframe" undefined
    …do.org/2013/03/ver-flukt-2012-online.html" width="600"></iframe></center></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 1484, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1505, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary6759437705347817541'><div style="text-align: justify;"><span st…

    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 1505, Column 1359: required attribute "alt" not specified
    …e+Fall+Of+The+Essex+Boys+(2012).jpg" /></a></div><div style="text-align: justi…

    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 1508, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1508, Column 184: element "iframe" undefined
    …3/ver-fall-of-essex-boys-2012-online.html" width="600"></iframe></center></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 1509, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1530, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary5123575772318625842'><div style="text-align: justify;"><span st…

    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 1535, Column 479: end tag for "input" omitted, but OMITTAG NO was specified
    …nción.</span></div><input name="IL_RELATED_TAGS" value="1" type="hidden"><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 1535, Column 425: start tag was here
    …e su centro de detención.</span></div><input name="IL_RELATED_TAGS" value="1" …
  • Error Line 1536, Column 8: element "center" undefined
    <center><span style="color: #0000f0; font-size:130%;"><strong>Idioma Latino:</s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1538, Column 190: element "iframe" undefined
    …2.html" frameborder="0" height="480" scrolling="no" width="600"></iframe><br />

    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 1542, Column 183: element "iframe" undefined
    …rameborder="0" height="480" scrolling="no" width="600"></iframe></center></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 1543, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1564, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary8941453444799743806'><div style="text-align: justify;"><span st…

    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 1564, Column 1645: required attribute "alt" not specified
    …e+in+the+Chamber)+(2012)+online.jpg" /></a></div><div style="text-align: justi…

    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 1567, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1567, Column 184: element "iframe" undefined
    …2/ver-una-bala-en-la-recamara-one-in.html" width="600"></iframe></center></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 1568, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1589, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary8532931044602523610'><div style="text-align: justify;"><span st…

    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 1589, Column 1320: required attribute "alt" not specified
    …ng+of+the+Streets+(2012)+online.jpg" /></a></div><div style="text-align: justi…

    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 1592, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1592, Column 181: element "iframe" undefined
    …3/02/ver-king-of-streets-2012-online.html" width="600"></iframe></center></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 1593, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1614, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary4701022641330544114'><div style="text-align: justify;"><span st…

    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 1614, Column 1326: required attribute "alt" not specified
    …garia+del+vidente+(2011)+online.jpg" /></a></div><div style="text-align: justi…

    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 1617, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1617, Column 189: element "iframe" undefined
    …-la-plegaria-del-vidente-2011-online.html" width="600"></iframe></center></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 1618, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1639, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary1819710245070863771'><div style="text-align: justify;"><span st…

    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 1639, Column 1340: required attribute "alt" not specified
    …re+(Desaparecida)+(2009)+online.jpg" /></a></div><div style="text-align: justi…

    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 1642, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1642, Column 188: element "iframe" undefined
    …r-elsewhere-desaparecida-2009-online.html" width="600"></iframe></center></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 1643, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1664, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary5137815572587434198'><div style="text-align: justify;"><span st…

    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 1664, Column 1338: required attribute "alt" not specified
    …ofeta+(Un+proph%C3%A8te)+(2009).jpg" /></a></div><div style="text-align: justi…

    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 1667, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1667, Column 188: element "iframe" undefined
    …r-un-profeta-un-prophete-2009-online.html" width="600"></iframe></center></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 1668, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1689, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary4100371937391450389'><div style="text-align: justify;"><span st…

    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 1689, Column 1335: required attribute "alt" not specified
    …Abrir+Puertas+Y+Ventanas+(2011).jpg" /></a></div><div style="text-align: justi…

    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 1692, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1692, Column 190: element "iframe" undefined
    …abrir-puertas-y-ventanas-2011-online.html" width="600"></iframe></center></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 1693, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1714, Column 35: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary94921015372131522'><div style="text-align: justify;"><span styl…

    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 1714, Column 1045: required attribute "alt" not specified
    …vyDyKyGPEqA/s1600/Empusa+(2010).jpg" /></a></div><div style="text-align: justi…

    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 1717, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1717, Column 172: element "iframe" undefined
    …o.org/2013/02/ver-empusa-2010-online.html" width="600"></iframe></center></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 1718, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1739, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary1707256980529305257'><div style="text-align: justify;"><span st…

    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 1739, Column 1417: required attribute "alt" not specified
    …e%2Binesperado%2B%25282012%2529.jpg" /></a></div><div style="text-align: justi…

    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 1741, Column 1001: end tag for "input" omitted, but OMITTAG NO was specified
    …ceros.</span></div><input name="IL_RELATED_TAGS" value="1" type="hidden"><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 1741, Column 947: start tag was here
    …mbia pieles y hechiceros.</span></div><input name="IL_RELATED_TAGS" value="1" …
  • Error Line 1742, Column 8: element "center" undefined
    <center><span style="color: #0000f0; font-size:130%;"><strong>Idioma Subtitulad…

    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 1744, Column 194: element "iframe" undefined
    …0.html" frameborder="0" height="480" scrolling="no" width="600"></iframe><br />

    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 1748, Column 189: element "iframe" undefined
    …2.html" frameborder="0" height="480" scrolling="no" width="600"></iframe><br />

    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 1752, Column 189: element "iframe" undefined
    …2.html" frameborder="0" height="480" scrolling="no" width="600"></iframe><br />

    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 1756, Column 191: element "iframe" undefined
    …3.html" frameborder="0" height="480" scrolling="no" width="600"></iframe><br />

    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 1758, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1779, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary4598355565366738401'><div style="text-align: justify;"><span st…

    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 1779, Column 1633: required attribute "alt" not specified
    …he%2BHead%2529%2B%25282013%2529.jpg" /></a></div><div style="text-align: justi…

    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 1782, Column 8: element "center" undefined
    <center><span style="color: #0000f0; font-size:130%;"><strong>Idioma Latino:</s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1784, Column 180: element "iframe" undefined
    …7.html" frameborder="0" height="480" scrolling="no" width="600"></iframe><br />

    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 1788, Column 177: element "iframe" undefined
    …rameborder="0" height="480" scrolling="no" width="600"></iframe></center></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 1789, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1810, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary3604339885191497684'><div style="text-align: justify;"><span st…

    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 1810, Column 1749: required attribute "alt" not specified
    …uardianes%2529%2B%25282012%2529.jpg" /></a></div><div style="text-align: justi…

    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 1812, Column 531: end tag for "input" omitted, but OMITTAG NO was specified
    …nemigo</span></div><input name="IL_RELATED_TAGS" value="1" type="hidden"><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 1812, Column 477: start tag was here
    …ndo de su pérfido enemigo</span></div><input name="IL_RELATED_TAGS" value="1" …
  • Error Line 1813, Column 8: element "center" undefined
    <center><span style="color: #0000f0; font-size:130%;"><strong>Idioma Subtitulad…

    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 1815, Column 189: element "iframe" undefined
    …s.html" frameborder="0" height="480" scrolling="no" width="600"></iframe><br />

    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 1819, Column 189: element "iframe" undefined
    …s.html" frameborder="0" height="480" scrolling="no" width="600"></iframe><br />

    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 1823, Column 189: element "iframe" undefined
    …rameborder="0" height="480" scrolling="no" width="600"></iframe></center></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 1824, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1845, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary1366786462122984880'><div style="text-align: justify;"><span st…

    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 1851, Column 55: end tag for "input" omitted, but OMITTAG NO was specified
    <input name="IL_RELATED_TAGS" value="1" type="hidden"><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 1851, Column 1: start tag was here
    <input name="IL_RELATED_TAGS" value="1" type="hidden"><br />
  • Error Line 1852, Column 8: element "center" undefined
    <center><span style="color: #0000f0; font-size:130%;"><strong>Idioma Latino:</s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1854, Column 190: element "iframe" undefined
    …e.html" frameborder="0" height="480" scrolling="no" width="600"></iframe><br />

    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 1858, Column 183: element "iframe" undefined
    …rameborder="0" height="480" scrolling="no" width="600"></iframe></center></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 1859, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1880, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary6200244582300375029'><div style="text-align: justify;"><span st…

    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 1880, Column 1166: required attribute "alt" not specified
    …600/Gun+Hill+Road+(2011)+online.jpg" /></a></div><div style="text-align: justi…

    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 1883, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1883, Column 179: element "iframe" undefined
    …013/02/ver-gun-hill-road-2011-online.html" width="600"></iframe></center></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 1884, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1905, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary1892106543877915020'><div style="text-align: justify;"><span st…

    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 1905, Column 1031: required attribute "alt" not specified
    …/1PtJK0Wqt-M/s1600/Masks+(2012).jpg" /></a></div><div style="text-align: justi…

    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 1908, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1908, Column 171: element "iframe" undefined
    …do.org/2013/02/ver-masks-2012-online.html" width="600"></iframe></center></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 1909, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1930, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary2396858245433829643'><div style="text-align: justify;"><span st…

    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 1930, Column 1358: required attribute "alt" not specified
    …ason+Becker+Not+Dead+Yet+(2012).jpg" /></a></div><div style="text-align: justi…

    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 1933, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1933, Column 184: element "iframe" undefined
    …2/ver-jason-becker-not-dead-yet-2012.html" width="600"></iframe></center></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 1934, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1955, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary4995034120320944145'><div style="text-align: justify;"><span st…

    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 1955, Column 1143: required attribute "alt" not specified
    …GpKc0/s1600/Side+By+Side+(2012).jpg" /></a></div><div style="text-align: justi…

    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 1958, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1958, Column 178: element "iframe" undefined
    …2013/02/ver-side-by-side-2012-online.html" width="600"></iframe></center></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 1959, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 1980, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary9193888185290188617'><div style="text-align: justify;"><span st…

    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 1980, Column 1313: required attribute "alt" not specified
    …0/The+Marine+3+Homefront+(2013).jpg" /></a></div><div style="text-align: justi…

    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 1983, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1983, Column 184: element "iframe" undefined
    …2/ver-marine-3-homefront-2013-online.html" width="600"></iframe></center></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 1984, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 2005, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary7529441446478692889'><div style="text-align: justify;"><span st…

    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 2005, Column 1079: required attribute "alt" not specified
    …WebQ_GOaM/s1600/Cold+War+(2012).jpg" /></a></div><div style="text-align: justi…

    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 2008, Column 8: element "center" undefined
    <center><iframe frameborder="0" height="480" marginheight="0" marginwidth="0" s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2008, Column 174: element "iframe" undefined
    …org/2013/02/ver-cold-war-2012-online.html" width="600"></iframe></center></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 2009, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 2030, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary4647131650478946172'><div style="text-align: justify;"><span st…

    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 2030, Column 1573: required attribute "alt" not specified
    …s+criaturas)+(2013).jpg" width="180" /></a></div><div style="text-align: justi…

    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 2035, Column 8: element "center" undefined
    <center><span style="color: #0000f0; font-size:130%;"><strong>Idioma Latino:</s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2037, Column 174: element "iframe" undefined
    …s.html" frameborder="0" height="480" scrolling="no" width="600"></iframe><br />

    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 2041, Column 177: element "iframe" undefined
    …rameborder="0" height="480" scrolling="no" width="600"></iframe></center></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 2042, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript></noscript>

    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 2083, Column 24: 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 2218, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&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 2218, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&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 2218, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 2218, Column 107: reference not terminated by REFC delimiter
    …4632271679200&widgetType=HTML&widgetId=HTML1&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 2218, Column 107: reference to external entity in attribute value
    …4632271679200&widgetType=HTML&widgetId=HTML1&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 2218, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …4632271679200&widgetType=HTML&widgetId=HTML1&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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 2218, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML1&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 2218, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML1&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 2218, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML1&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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 2218, Column 141: reference not terminated by REFC delimiter
    …etId=HTML1&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 2218, Column 141: reference to external entity in attribute value
    …etId=HTML1&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 2218, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML1&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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Error Line 2226, Column 126: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    … 50px;"><span><div class='likeboxwrap'><iframe src="http://www.facebook.com/pl…

    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 2226, Column 408: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:228…

    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 2226, Column 485: there is no attribute "allowtransparency"
    …8px; height:320px;" allowtransparency="true"></iframe></div></span></div></div…

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

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

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

  • Error Line 2226, Column 491: element "iframe" undefined
    …8px; height:320px;" allowtransparency="true"></iframe></div></span></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 2231, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML8&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 2231, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML8&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 2231, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML8&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 2231, Column 107: reference not terminated by REFC delimiter
    …4632271679200&widgetType=HTML&widgetId=HTML8&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 2231, Column 107: reference to external entity in attribute value
    …4632271679200&widgetType=HTML&widgetId=HTML8&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 2231, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …4632271679200&widgetType=HTML&widgetId=HTML8&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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 2231, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML8&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 2231, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML8&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 2231, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML8&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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 2231, Column 141: reference not terminated by REFC delimiter
    …etId=HTML8&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 2231, Column 141: reference to external entity in attribute value
    …etId=HTML8&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 2231, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML8&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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Error Line 2239, Column 8: element "center" undefined
    <center><!-- BEGIN STANDARD TAG - 300 x 250 - ROS: Run-of-site - DO NOT MODIFY …

    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 2240, 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=300 heigh…
  • Error Line 2240, 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=300 heigh…
  • Error Line 2240, 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=300 height=250 src=…
  • Error Line 2240, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arginwidth=0 marginheight=0 scrolling=no width=300 height=250 src="http://ad.y…
  • Error Line 2240, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 marginheight=0 scrolling=no width=300 height=250 src="http://ad.yieldmanag…
  • Error Line 2240, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eight=0 scrolling=no width=300 height=250 src="http://ad.yieldmanager.com/st?a…
  • Warning Line 2240, Column 136: cannot generate system identifier for general entity "ad_size"
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=…

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

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

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

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

  • Error Line 2240, Column 136: general entity "ad_size" not defined and no default entity
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=…

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

  • Warning Line 2240, Column 143: reference not terminated by REFC delimiter
    …dmanager.com/st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_U…

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

  • Warning Line 2240, Column 143: reference to external entity in attribute value
    …dmanager.com/st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_U…

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

  • Error Line 2240, Column 143: reference to entity "ad_size" for which no system identifier could be generated
    …dmanager.com/st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_U…

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

  • Info Line 2240, Column 135: entity was defined here
    …/ad.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url…
  • Warning Line 2240, Column 152: cannot generate system identifier for general entity "section"
    …com/st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_URL}"></if…

    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 2240, Column 152: general entity "section" not defined and no default entity
    …com/st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_URL}"></if…

    This is usually a cascading error caused by 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 2240, Column 159: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_URL}"></iframe>

    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 2240, Column 159: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_URL}"></iframe>

    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 2240, Column 159: reference to entity "section" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_URL}"></iframe>

    This is usually a cascading error caused by 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 2240, Column 151: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_URL}"></i…
  • Warning Line 2240, Column 168: cannot generate system identifier for general entity "pub_url"
    …st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_URL}"></iframe>

    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 2240, Column 168: general entity "pub_url" not defined and no default entity
    …st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_URL}"></iframe>

    This is usually a cascading error caused by 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 2240, Column 175: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_URL}"></iframe>

    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 2240, Column 175: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_URL}"></iframe>

    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 2240, Column 175: reference to entity "pub_url" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_URL}"></iframe>

    This is usually a cascading error caused by 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 2240, Column 167: entity was defined here
    …st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_URL}"></iframe>
  • Error Line 2240, Column 187: element "iframe" undefined
    …st?ad_type=iframe&ad_size=300x250&section=2738353&pub_url=${PUB_URL}"></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 2246, Column 18: there is no attribute "language"
    <script language="JavaScript">

    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 2246, Column 30: required attribute "type" not specified
    <script language="JavaScript">

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

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

  • Error Line 2249, Column 68: required attribute "type" not specified
    <script language="JavaScript" src="http://c4.zedo.com/jsc/c4/fo.js"></script>

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

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

  • Warning Line 2255, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&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 2255, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&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 2255, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 2255, Column 107: reference not terminated by REFC delimiter
    …4632271679200&widgetType=HTML&widgetId=HTML9&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 2255, Column 107: reference to external entity in attribute value
    …4632271679200&widgetType=HTML&widgetId=HTML9&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 2255, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …4632271679200&widgetType=HTML&widgetId=HTML9&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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 2255, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML9&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 2255, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML9&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 2255, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML9&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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 2255, Column 141: reference not terminated by REFC delimiter
    …etId=HTML9&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 2255, Column 141: reference to external entity in attribute value
    …etId=HTML9&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 2255, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML9&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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Error Line 2273, Column 8: element "center" undefined
    <center>Encuentra tu pelicula:

    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 2274, Column 180: required attribute "alt" not specified
    …R41yWXhc7Q/USpmdttE-2I/AAAAAAAANWM/jSUb8EsW6lE/s320/Buscar.png" /></a></center>

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

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

  • Warning Line 2279, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML10&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 2279, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML10&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 2279, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML10&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 2279, Column 107: reference not terminated by REFC delimiter
    …4632271679200&widgetType=HTML&widgetId=HTML10&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 2279, Column 107: reference to external entity in attribute value
    …4632271679200&widgetType=HTML&widgetId=HTML10&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 2279, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …4632271679200&widgetType=HTML&widgetId=HTML10&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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 2279, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=cahaya63' 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 2279, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=cahaya63' 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 2279, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=cahaya63' 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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 2279, Column 142: reference not terminated by REFC delimiter
    …tId=HTML10&action=editWidget&sectionId=cahaya63' 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 2279, Column 142: reference to external entity in attribute value
    …tId=HTML10&action=editWidget&sectionId=cahaya63' 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 2279, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML10&action=editWidget&sectionId=cahaya63' 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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Error Line 2288, Column 8: element "center" undefined
    <center><a target="_blank" href="http://www.peliculaschingonas.com/2012/11/ver-…

    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 2293, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&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 2293, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&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 2293, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 2293, Column 107: reference not terminated by REFC delimiter
    …4632271679200&widgetType=HTML&widgetId=HTML6&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 2293, Column 107: reference to external entity in attribute value
    …4632271679200&widgetType=HTML&widgetId=HTML6&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 2293, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …4632271679200&widgetType=HTML&widgetId=HTML6&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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 2293, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=cahaya63' 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 2293, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=cahaya63' 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 2293, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=cahaya63' 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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 2293, Column 141: reference not terminated by REFC delimiter
    …etId=HTML6&action=editWidget&sectionId=cahaya63' 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 2293, Column 141: reference to external entity in attribute value
    …etId=HTML6&action=editWidget&sectionId=cahaya63' 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 2293, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML6&action=editWidget&sectionId=cahaya63' 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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Error Line 2303, Column 248: there is no attribute "target"
    …ow", "scrollbars=yes,width=550,height=520"); return true' target='popupwindow'>

    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 2307, Column 65: there is no attribute "placeholder"
    …low-by-email-address' name='email' placeholder='Email address...' type='text'/>

    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 2309, Column 11: there is no attribute "width"
    <td width='64px'>

    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 2314, Column 65: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input name='uri' type='hidden' value='peliculaschingonas/hibN'/>

    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 2315, Column 47: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input name='loc' type='hidden' value='en_ES'/>

    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 2320, Column 19: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class='clear'></div>

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

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

  • Warning Line 2323, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&widgetType=FollowByEmail&widgetId=FollowByEmail1&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 2323, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&widgetType=FollowByEmail&widgetId=FollowByEmail1&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 2323, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&widgetType=FollowByEmail&widgetId=FollowByEmail1&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 2323, Column 116: reference not terminated by REFC delimiter
    …9200&widgetType=FollowByEmail&widgetId=FollowByEmail1&action=editWidget&sectio…

    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 2323, Column 116: reference to external entity in attribute value
    …9200&widgetType=FollowByEmail&widgetId=FollowByEmail1&action=editWidget&sectio…

    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 2323, Column 116: reference to entity "widgetId" for which no system identifier could be generated
    …9200&widgetType=FollowByEmail&widgetId=FollowByEmail1&action=editWidget&sectio…

    This is usually a cascading error caused by 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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 2323, Column 138: reference not terminated by REFC delimiter
    …ByEmail&widgetId=FollowByEmail1&action=editWidget&sectionId=cahaya63' 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 2323, Column 138: reference to external entity in attribute value
    …ByEmail&widgetId=FollowByEmail1&action=editWidget&sectionId=cahaya63' 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 2323, Column 138: reference to entity "action" for which no system identifier could be generated
    …ByEmail&widgetId=FollowByEmail1&action=editWidget&sectionId=cahaya63' 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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 2323, Column 159: reference not terminated by REFC delimiter
    …owByEmail1&action=editWidget&sectionId=cahaya63' 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 2323, Column 159: reference to external entity in attribute value
    …owByEmail1&action=editWidget&sectionId=cahaya63' 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 2323, Column 159: reference to entity "sectionId" for which no system identifier could be generated
    …owByEmail1&action=editWidget&sectionId=cahaya63' 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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Error Line 2328, Column 19: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class='clear'></div>

    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 2332, Column 8: element "center" undefined
    <center><iframe src="http://viaje-fin-de-semana.blogspot.com" frameborder="0" m…

    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 2332, Column 151: element "iframe" undefined
    …"0" marginheight="0" scrolling="NO" width="160" height="600"></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 2337, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&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 2337, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&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 2337, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 2337, Column 107: reference not terminated by REFC delimiter
    …4632271679200&widgetType=HTML&widgetId=HTML5&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 2337, Column 107: reference to external entity in attribute value
    …4632271679200&widgetType=HTML&widgetId=HTML5&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 2337, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …4632271679200&widgetType=HTML&widgetId=HTML5&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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 2337, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=cahaya63' 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 2337, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=cahaya63' 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 2337, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=cahaya63' 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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 2337, Column 141: reference not terminated by REFC delimiter
    …etId=HTML5&action=editWidget&sectionId=cahaya63' 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 2337, Column 141: reference to external entity in attribute value
    …etId=HTML5&action=editWidget&sectionId=cahaya63' 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 2337, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML5&action=editWidget&sectionId=cahaya63' 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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Warning Line 2477, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&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 2477, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&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 2477, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 2477, Column 108: reference not terminated by REFC delimiter
    …632271679200&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 2477, Column 108: reference to external entity in attribute value
    …632271679200&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 2477, Column 108: reference to entity "widgetId" for which no system identifier could be generated
    …632271679200&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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 2477, Column 122: reference not terminated by REFC delimiter
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=cahaya63' 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 2477, Column 122: reference to external entity in attribute value
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=cahaya63' 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 2477, Column 122: reference to entity "action" for which no system identifier could be generated
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=cahaya63' 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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 2477, Column 143: reference not terminated by REFC delimiter
    …tId=Label1&action=editWidget&sectionId=cahaya63' 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 2477, Column 143: reference to external entity in attribute value
    …tId=Label1&action=editWidget&sectionId=cahaya63' 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 2477, Column 143: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Label1&action=editWidget&sectionId=cahaya63' 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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Warning Line 2501, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&widgetType=Label&widgetId=Label3&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 2501, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&widgetType=Label&widgetId=Label3&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 2501, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&widgetType=Label&widgetId=Label3&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 2501, Column 108: reference not terminated by REFC delimiter
    …632271679200&widgetType=Label&widgetId=Label3&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 2501, Column 108: reference to external entity in attribute value
    …632271679200&widgetType=Label&widgetId=Label3&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 2501, Column 108: reference to entity "widgetId" for which no system identifier could be generated
    …632271679200&widgetType=Label&widgetId=Label3&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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 2501, Column 122: reference not terminated by REFC delimiter
    …idgetType=Label&widgetId=Label3&action=editWidget&sectionId=cahaya63' 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 2501, Column 122: reference to external entity in attribute value
    …idgetType=Label&widgetId=Label3&action=editWidget&sectionId=cahaya63' 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 2501, Column 122: reference to entity "action" for which no system identifier could be generated
    …idgetType=Label&widgetId=Label3&action=editWidget&sectionId=cahaya63' 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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 2501, Column 143: reference not terminated by REFC delimiter
    …tId=Label3&action=editWidget&sectionId=cahaya63' 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 2501, Column 143: reference to external entity in attribute value
    …tId=Label3&action=editWidget&sectionId=cahaya63' 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 2501, Column 143: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Label3&action=editWidget&sectionId=cahaya63' 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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Warning Line 2528, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&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 2528, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&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 2528, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 2528, Column 108: reference not terminated by REFC delimiter
    …632271679200&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 2528, Column 108: reference to external entity in attribute value
    …632271679200&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 2528, Column 108: reference to entity "widgetId" for which no system identifier could be generated
    …632271679200&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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 2528, Column 122: reference not terminated by REFC delimiter
    …idgetType=Label&widgetId=Label2&action=editWidget&sectionId=cahaya63' 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 2528, Column 122: reference to external entity in attribute value
    …idgetType=Label&widgetId=Label2&action=editWidget&sectionId=cahaya63' 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 2528, Column 122: reference to entity "action" for which no system identifier could be generated
    …idgetType=Label&widgetId=Label2&action=editWidget&sectionId=cahaya63' 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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 2528, Column 143: reference not terminated by REFC delimiter
    …tId=Label2&action=editWidget&sectionId=cahaya63' 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 2528, Column 143: reference to external entity in attribute value
    …tId=Label2&action=editWidget&sectionId=cahaya63' 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 2528, Column 143: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Label2&action=editWidget&sectionId=cahaya63' 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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Error Line 2537, Column 8: element "center" undefined
    <center><a href="http://peliculaschingonas.com"><img border="0" width="1" src="…

    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 2537, Column 186: required attribute "alt" not specified
    …png" height="1" title="Click to see how many people are online" /></a></center>

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

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

  • Warning Line 2542, Column 93: reference not terminated by REFC delimiter
    …?blogID=2205884632271679200&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 2542, Column 93: reference to external entity in attribute value
    …?blogID=2205884632271679200&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 2542, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2205884632271679200&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 1333, Column 82: entity was defined here
    …m/rearrange?blogID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=e…
  • Warning Line 2542, Column 107: reference not terminated by REFC delimiter
    …4632271679200&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 2542, Column 107: reference to external entity in attribute value
    …4632271679200&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 2542, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …4632271679200&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 1333, Column 98: entity was defined here
    …ID=2205884632271679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectio…
  • Warning Line 2542, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=cahaya63' 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 2542, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=cahaya63' 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 2542, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=cahaya63' 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 1333, Column 113: entity was defined here
    …1679200&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bo…
  • Warning Line 2542, Column 141: reference not terminated by REFC delimiter
    …etId=HTML3&action=editWidget&sectionId=cahaya63' 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 2542, Column 141: reference to external entity in attribute value
    …etId=HTML3&action=editWidget&sectionId=cahaya63' 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 2542, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML3&action=editWidget&sectionId=cahaya63' 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 1333, Column 131: entity was defined here
    …=HTML&widgetId=HTML4&action=editWidget&sectionId=crosscol-bottom' onclick='ret…
  • Error Line 2576, Column 146: document type does not allow element "link" here
    …AAAAQU/aOj5zHg5URA/s1600/favicon.ico' rel='shortcut icon' type='image/x-icon'/>

    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 2584, Column 71: cannot generate system identifier for general entity "ides"
    …twords.com.br/multiplos.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43…

    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 2584, Column 71: general entity "ides" not defined and no default entity
    …twords.com.br/multiplos.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43…

    This is usually a cascading error caused by 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 2584, Column 75: reference not terminated by REFC delimiter
    …ds.com.br/multiplos.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&…

    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 2584, Column 75: reference to external entity in attribute value
    …ds.com.br/multiplos.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&…

    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 2584, Column 75: reference to entity "ides" for which no system identifier could be generated
    …ds.com.br/multiplos.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&…

    This is usually a cascading error caused by 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 2584, Column 70: entity was defined here
    …otwords.com.br/multiplos.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=4…
  • Warning Line 2584, Column 82: cannot generate system identifier for general entity "idmx"
    …br/multiplos.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43…

    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 2584, Column 82: general entity "idmx" not defined and no default entity
    …br/multiplos.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43…

    This is usually a cascading error caused by 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 2584, Column 86: reference not terminated by REFC delimiter
    …ultiplos.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&…

    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 2584, Column 86: reference to external entity in attribute value
    …ultiplos.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&…

    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 2584, Column 86: reference to entity "idmx" for which no system identifier could be generated
    …ultiplos.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&…

    This is usually a cascading error caused by 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 2584, Column 81: entity was defined here
    ….br/multiplos.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=4…
  • Warning Line 2584, Column 93: cannot generate system identifier for general entity "idar"
    …s.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43…

    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 2584, Column 93: general entity "idar" not defined and no default entity
    …s.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43…

    This is usually a cascading error caused by 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 2584, Column 97: reference not terminated by REFC delimiter
    …p?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&…

    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 2584, Column 97: reference to external entity in attribute value
    …p?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&…

    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 2584, Column 97: reference to entity "idar" for which no system identifier could be generated
    …p?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&…

    This is usually a cascading error caused by 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 2584, Column 92: entity was defined here
    …os.jsp?padrao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=4…
  • Warning Line 2584, Column 104: cannot generate system identifier for general entity "idco"
    …o=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0…

    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 2584, Column 104: general entity "idco" not defined and no default entity
    …o=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0…

    This is usually a cascading error caused by 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 2584, Column 108: reference not terminated by REFC delimiter
    …&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&…

    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 2584, Column 108: reference to external entity in attribute value
    …&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&…

    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 2584, Column 108: reference to entity "idco" for which no system identifier could be generated
    …&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&…

    This is usually a cascading error caused by 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 2584, Column 103: entity was defined here
    …ao=mx&ides=43973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF…
  • Warning Line 2584, Column 115: cannot generate system identifier for general entity "idcl"
    …3973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div…

    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 2584, Column 115: general entity "idcl" not defined and no default entity
    …3973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div…

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

  • Warning Line 2584, Column 119: reference not terminated by REFC delimiter
    …&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr…

    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 2584, Column 119: reference to external entity in attribute value
    …&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr…

    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 2584, Column 119: reference to entity "idcl" for which no system identifier could be generated
    …&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr…

    This is usually a cascading error caused by 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 2584, Column 114: entity was defined here
    …43973&idmx=43048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=di…
  • Warning Line 2584, Column 126: cannot generate system identifier for general entity "idus"
    …3048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&…

    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 2584, Column 126: general entity "idus" not defined and no default entity
    …3048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&…

    This is usually a cascading error caused by 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 2584, Column 130: reference not terminated by REFC delimiter
    …&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr…

    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 2584, Column 130: reference to external entity in attribute value
    …&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr…

    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 2584, Column 130: reference to entity "idus" for which no system identifier could be generated
    …&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr…

    This is usually a cascading error caused by 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 2584, Column 125: entity was defined here
    …43048&idar=43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class…
  • Warning Line 2584, Column 137: cannot generate system identifier for general entity "cor"
    …3972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"…

    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 2584, Column 137: general entity "cor" not defined and no default entity
    …3972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"…

    This is usually a cascading error caused by 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 2584, Column 140: reference not terminated by REFC delimiter
    …2&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></…

    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 2584, Column 140: reference to external entity in attribute value
    …2&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></…

    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 2584, Column 140: reference to entity "cor" for which no system identifier could be generated
    …2&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></…

    This is usually a cascading error caused by 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 2584, Column 136: entity was defined here
    …43972&idco=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry…
  • Warning Line 2584, Column 148: cannot generate system identifier for general entity "tag"
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 148: general entity "tag" not defined and no default entity
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 151: reference not terminated by REFC delimiter
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 151: reference to external entity in attribute value
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 151: reference to entity "tag" for which no system identifier could be generated
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 147: entity was defined here
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></script>
  • Warning Line 2584, Column 156: cannot generate system identifier for general entity "atr"
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 156: general entity "atr" not defined and no default entity
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 159: reference not terminated by REFC delimiter
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 159: reference to external entity in attribute value
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 159: reference to entity "atr" for which no system identifier could be generated
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 155: entity was defined here
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></script>
  • Warning Line 2584, Column 166: cannot generate system identifier for general entity "vatr"
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 166: general entity "vatr" not defined and no default entity
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 170: reference not terminated by REFC delimiter
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 170: reference to external entity in attribute value
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 170: reference to entity "vatr" for which no system identifier could be generated
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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 2584, Column 165: entity was defined here
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></script>
  • Error Line 2584, Column 177: required attribute "type" not specified
    …=43974&idcl=43975&idus=43976&cor=FF0000&tag=div&atr=class&vatr=entry"></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>.

  • Warning Line 2605, 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 2605, 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
  • 13.067 visits
Daily Visitor