Películas Español latino dvdrip 1 link ...

tuspelislatino.com
  • Domain Name
    tuspelislatino.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #20195
  • Page Size
    152.5 KB
  • Ip Address
    184.168.221.17
  • Heading
    H1: 0, H2: 36, H3: 40, H4: 0, H5: 0, H6: 0
  • Images
    4 GIF, 54 JPG, 21 PNG

Website Meta Analysis

  • Title
    TusPelisLatino.com - Peliculas Online en Español latino Gratis
  • Meta Keyword
    peliculas, latino, online, dvdrip, ver online, estreno, español, en latino, en linea, movies, pelis, online gratis, peliculas online, ver en linea, cine gratis
  • Meta Description
    Películas Español latino dvdrip 1 link

Technical Analysis

  • Webserver
    GSE
  • Ip Address
    184.168.221.17
  • Domain Age
    1 Years, 0 Months, 18 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-type: text/html; charset=UTF-8
  • expires: Sat, 02 Mar 2013 10:05:12 GMT
  • date: Sat, 02 Mar 2013 10:05:12 GMT
  • cache-control: private, max-age=0
  • last-modified: Sat, 02 Mar 2013 01:42:30 GMT
  • etag: "fee2f514-6536-4997-9de9-1a9fd6829970"
  • content-encoding: gzip
  • x-content-type-options: nosniff
  • x-xss-protection: 1; mode=block
  • content-length: 28127
  • server: GSE
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
TusPelisLatino
Av. del ejercito # 1148
Trujillo, La Libertad Tru
Peru

Domain Name: TUSPELISLATINO.COM
Created on: 18-Feb-12
Expires on: 18-Feb-13
Last Updated on: 18-Feb-12

Administrative Contact:
Tafur Vera, Daniel email
TusPelisLatino
Av. del ejercito # 1148
Trujillo, La Libertad Tru
Peru
51965631487

Technical Contact:
Tafur Vera, Daniel email
TusPelisLatino
Av. del ejercito # 1148
Trujillo, La Libertad Tru
Peru
51965631487

Domain servers in listed order:
NS29.DOMAINCONTROL.COM
NS30.DOMAINCONTROL.COM

DNS Analysis


DNS servers
ns29.domaincontrol.com [216.69.185.15]
ns30.domaincontrol.com [208.109.255.15]


DNS Records

Answer records
tuspelislatino.com A 216.239.32.21 3600s
tuspelislatino.com A 216.239.34.21 3600s
tuspelislatino.com A 216.239.36.21 3600s
tuspelislatino.com A 64.202.189.170 3600s
tuspelislatino.com MX
preference: 0
exchange: smtp.secureserver.net
3600s
tuspelislatino.com MX
preference: 10
exchange: mailstore1.secureserver.net
3600s
tuspelislatino.com NS  ns29.domaincontrol.com 3600s
tuspelislatino.com NS  ns30.domaincontrol.com 3600s
tuspelislatino.com SOA
server: ns29.domaincontrol.com
email: dns@jomax.net
serial: 2012103100
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records

IP 184.168.221.17 Analysis

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

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

    NetRange: 184.168.0.0 - 184.168.255.255
    CIDR: 184.168.0.0/16
    OriginAS: AS26496
    NetName: GO-DADDY-COM-LLC
    NetHandle: NET-184-168-0-0-1
    Parent: NET-184-0-0-0-0
    NetType: Direct Allocation
    Comment: Please send abuse complaints to abuse@godaddy.com
    RegDate: 2010-09-21
    Updated: 2012-02-24
    Ref: http://whois.arin.net/rest/net/NET-184-168-0-0-1

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

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

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

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

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 426 Errors
  • 422 Warnings
Ratio Text/Html
  • 0.6077323648661632
Message Error
  • Error Line 12, Column 42: there is no attribute "property"
    <meta content='100000369061701' 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.

  • Warning Line 27, 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 27, 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 27, 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 27, 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 27, 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 27, Column 276: entity was defined here
    …ing={Timer:d,load:a};if(b.performance&&b.performance.timing){var a=b.performan…
  • Error Line 27, 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 27, 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 27, 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 27, 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 27, 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 27, 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 27, 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 27, 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 27, 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 27, 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 27, 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 27, 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 27, 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 27, 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 27, Column 482: entity was defined here
    …tbsd_","wtsrt_"))}try{a=null,b.chrome&&b.chrome.csi&&(a=Math.floor(b.chrome.cs…
  • Warning Line 27, 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 27, 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 27, 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 27, 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 27, 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 27, 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 27, 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 28, 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 28, 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 28, 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 28, 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 28, 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 28, Column 35: entity was defined here
    c[g]("tbnd_","_tbnd",f))),null==a&&b.gtbExternal&&(a=b.gtbExternal.pageT()),nul…
  • Warning Line 28, 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 28, 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 28, 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 28, 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 28, 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 28, 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 28, 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 28, Column 85: entity was defined here
    …al&&(a=b.gtbExternal.pageT()),null==a&&b.external&&(a=b.external.pageT,c&&0<f&…
  • Warning Line 28, 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 28, 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 28, 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 28, 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 28, 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 28, 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 28, 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 28, 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 28, 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 28, 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 28, 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 28, 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 28, 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 28, 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 28, 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 29, 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 28, 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 29, 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 27, 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 29, 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 27, 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 45, Column 123: cannot generate system identifier for general entity "zx"
    ….css?targetBlogID=6786839474821523869&zx=fee2f514-6536-4997-9de9-1a9fd6829970"…

    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 45, Column 123: general entity "zx" not defined and no default entity
    ….css?targetBlogID=6786839474821523869&zx=fee2f514-6536-4997-9de9-1a9fd6829970"…

    This is usually a cascading error caused by 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 45, Column 125: reference not terminated by REFC delimiter
    …css?targetBlogID=6786839474821523869&zx=fee2f514-6536-4997-9de9-1a9fd6829970"/>

    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 45, Column 125: reference to external entity in attribute value
    …css?targetBlogID=6786839474821523869&zx=fee2f514-6536-4997-9de9-1a9fd6829970"/>

    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 45, Column 125: reference to entity "zx" for which no system identifier could be generated
    …css?targetBlogID=6786839474821523869&zx=fee2f514-6536-4997-9de9-1a9fd6829970"/>

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

  • Info Line 45, Column 122: entity was defined here
    …n.css?targetBlogID=6786839474821523869&zx=fee2f514-6536-4997-9de9-1a9fd6829970…
  • Warning Line 48, Column 5: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 48, Column 9: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 48, Column 13: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 48, Column 17: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 48, Column 21: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 48, Column 25: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 48, Column 29: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 48, Column 33: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 48, Column 37: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 48, Column 41: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 48, Column 45: multiple comments in comment declaration
    -----------------------------------------------
  • Error Line 48, Column 47: invalid comment declaration: found name character outside comment but inside comment declaration
    -----------------------------------------------
  • Info Line 46, Column 41: comment declaration started here
    <style id='page-skin-1' type='text/css'><!--
  • Error Line 819, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Warning Line 1001, 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 1001, 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 1001, 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 1001, 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 1001, Column 77: entity was defined here
    …avigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",k="?m=1";functio…
  • Warning Line 1001, 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 1001, 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 1001, 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 1001, 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 1001, 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 1001, 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 1001, 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 1001, 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 1001, 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 1001, 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 1001, 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 1001, Column 394: entity was defined here
    …pera Mini")||-1!=a[b][c]("IEMobile")){var m=l();m&&window.location.replace(m)};
  • Warning Line 1020, 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 1020, 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 1044, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

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

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

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

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

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

    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 1048, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/es_LA/all.js#xfbml=1&appId=224272791031908";

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

  • Info Line 1048, Column 56: entity was defined here
      js.src = "//connect.facebook.net/es_LA/all.js#xfbml=1&appId=224272791031908";
  • Error Line 1053, Column 36: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <a id='top' onclick='scrollTo(0,0)'><div id='message'></div></a>

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

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

  • Error Line 1053, Column 54: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <a id='top' onclick='scrollTo(0,0)'><div id='message'></div></a>

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

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

  • Error Line 1069, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 1079, Column 16: element "gcse:searchbox" undefined
    <gcse:searchbox></gcse:searchbox>

    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 1084, Column 83: cannot generate system identifier for general entity "widgetType"
    …/rearrange?blogID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=e…

    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 1084, Column 83: general entity "widgetType" not defined and no default entity
    …/rearrange?blogID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=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.

  • Warning Line 1084, Column 93: reference not terminated by REFC delimiter
    …?blogID=6786839474821523869&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 1084, Column 93: reference to external entity in attribute value
    …?blogID=6786839474821523869&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 1084, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=6786839474821523869&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 1084, Column 82: entity was defined here
    …m/rearrange?blogID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=…
  • Warning Line 1084, Column 99: cannot generate system identifier for general entity "widgetId"
    …D=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectio…

    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 1084, Column 99: general entity "widgetId" not defined and no default entity
    …D=6786839474821523869&widgetType=HTML&widgetId=HTML10&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.

  • Warning Line 1084, Column 107: reference not terminated by REFC delimiter
    …9474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9…

    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 1084, Column 107: reference to external entity in attribute value
    …9474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9…

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

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

  • Info Line 1084, Column 98: entity was defined here
    …ID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&secti…
  • Warning Line 1084, Column 115: cannot generate system identifier for general entity "action"
    …23869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclic…

    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 1084, Column 115: general entity "action" not defined and no default entity
    …23869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclic…

    This is usually a cascading error caused by 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 1084, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' 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 1084, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' 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 1084, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' 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 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1084, Column 133: cannot generate system identifier for general entity "sectionId"
    …TML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _WidgetM…

    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 1084, Column 133: general entity "sectionId" not defined and no default entity
    …TML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _WidgetM…

    This is usually a cascading error caused by 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 1084, Column 142: reference not terminated by REFC delimiter
    …tId=HTML10&action=editWidget&sectionId=col9' 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 1084, Column 142: reference to external entity in attribute value
    …tId=HTML10&action=editWidget&sectionId=col9' 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 1084, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML10&action=editWidget&sectionId=col9' 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 1084, Column 132: entity was defined here
    …HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _Widget…
  • Error Line 1084, Column 237: there is no attribute "target"
    …nfig(document.getElementById("HTML10"));' target='configHTML10' title='Editar'>

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

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

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

  • Error Line 1230, Column 20: element "gcse:searchresults" undefined
    <gcse:searchresults></gcse:searchresults>

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

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

  • Warning Line 1235, Column 93: reference to external entity in attribute value
    …?blogID=6786839474821523869&widgetType=HTML&widgetId=HTML11&action=editWidget&…

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

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

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

  • Info Line 1084, Column 82: entity was defined here
    …m/rearrange?blogID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=…
  • Warning Line 1235, Column 107: reference not terminated by REFC delimiter
    …9474821523869&widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=main…

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

  • Warning Line 1235, Column 107: reference to external entity in attribute value
    …9474821523869&widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=main…

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

  • Error Line 1235, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …9474821523869&widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=main…

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

  • Info Line 1084, Column 98: entity was defined here
    …ID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&secti…
  • Warning Line 1235, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=main' onclick='ret…

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

  • Warning Line 1235, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=main' onclick='ret…

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

  • Error Line 1235, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=main' onclick='ret…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1235, Column 142: reference not terminated by REFC delimiter
    …tId=HTML11&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Warning Line 1235, Column 142: reference to external entity in attribute value
    …tId=HTML11&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Error Line 1235, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML11&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Info Line 1084, Column 132: entity was defined here
    …HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _Widget…
  • Error Line 1251, Column 52: there is no attribute "oncontextmenu"
    …ost-body entry-content' oncontextmenu='return false' ondragstart='return false…

    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 1251, Column 79: there is no attribute "ondragstart"
    …ontextmenu='return false' ondragstart='return false' onmousedown='return false…

    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 1251, Column 135: there is no attribute "onselectstart"
    …agstart='return false' onmousedown='return false' onselectstart='return false'>

    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 1256, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1256, Column 1: start tag was here
    <br>
  • Error Line 1258, Column 58: there is no attribute "border"
    … Quiere Ser Millonario Online" border="0" height="320" src="http://3.bp.blogsp…

    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 1258, Column 263: end tag for "img" omitted, but OMITTAG NO was specified
    …o_Online.jpg" title="ver Quien Quiere Ser Millonario Online" width="225"></div>

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

  • Info Line 1258, Column 1: start tag was here
    <img alt="ver Quien Quiere Ser Millonario Online" border="0" height="320" src="…
  • Error Line 1259, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1259, Column 1: start tag was here
    <br>
  • Error Line 1274, Column 27: there is no attribute "allowTransparency"
    <iframe allowTransparency='true' frameborder='0' scrolling='no' src='http://www…

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

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

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

  • Error Line 1274, Column 46: there is no attribute "frameborder"
    … allowTransparency='true' frameborder='0' scrolling='no' src='http://www.faceb…

    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 1274, Column 60: there is no attribute "scrolling"
    …ency='true' frameborder='0' scrolling='no' src='http://www.facebook.com/plugin…

    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 1274, Column 69: there is no attribute "src"
    …e' frameborder='0' scrolling='no' src='http://www.facebook.com/plugins/like.ph…

    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 1274, Column 199: cannot generate system identifier for general entity "layout"
    …uiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wid…

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

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

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

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

  • Error Line 1274, Column 199: general entity "layout" not defined and no default entity
    …uiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wid…

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

  • Warning Line 1274, Column 205: reference not terminated by REFC delimiter
    …ser-millonario-2008-online.html&layout=button_count&show_faces=false&width=100…

    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 1274, Column 205: reference to external entity in attribute value
    …ser-millonario-2008-online.html&layout=button_count&show_faces=false&width=100…

    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 1274, Column 205: reference to entity "layout" for which no system identifier could be generated
    …ser-millonario-2008-online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1274, Column 219: cannot generate system identifier for general entity "show_faces"
    …-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&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 1274, Column 219: general entity "show_faces" not defined and no default entity
    …-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&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 1274, Column 229: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1274, Column 229: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1274, Column 229: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1274, Column 236: cannot generate system identifier for general entity "width"
    …&layout=button_count&show_faces=false&width=100&action=like&font=arial&colorsc…

    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 1274, Column 236: general entity "width" not defined and no default entity
    …&layout=button_count&show_faces=false&width=100&action=like&font=arial&colorsc…

    This is usually a cascading error caused by 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 1274, Column 241: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1274, Column 241: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1274, Column 241: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1274, Column 252: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1274, Column 252: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1274, Column 252: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1274, Column 258: cannot generate system identifier for general entity "font"
    …how_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bor…

    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 1274, Column 258: general entity "font" not defined and no default entity
    …how_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bor…

    This is usually a cascading error caused by 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 1274, Column 262: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1274, Column 262: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1274, Column 262: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1274, Column 269: cannot generate system identifier for general entity "colorscheme"
    …alse&width=100&action=like&font=arial&colorscheme=light' style='border:none; o…

    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 1274, Column 269: general entity "colorscheme" not defined and no default entity
    …alse&width=100&action=like&font=arial&colorscheme=light' style='border:none; 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.

  • Warning Line 1274, Column 280: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1274, Column 280: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1274, Column 280: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1274, Column 294: there is no attribute "style"
    …e&font=arial&colorscheme=light' style='border:none; overflow:hidden; width:96p…

    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 1274, Column 349: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1274, Column 393: there is no attribute "href"
    …ame><div class='plus'><g:plusone href='http://www.tuspelislatino.com/2013/03/q…

    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 1274, Column 483: there is no attribute "size"
    …n-quiere-ser-millonario-2008-online.html' size='small'></g:plusone></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 1274, Column 490: element "g:plusone" undefined
    …n-quiere-ser-millonario-2008-online.html' size='small'></g:plusone></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).
  • Error Line 1289, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1300, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1300, Column 1: start tag was here
    <br>
  • Error Line 1302, Column 254: end tag for "img" omitted, but OMITTAG NO was specified
    …anes-online.jpg" title="ver Origen de los guardianes online" width="224"></div>

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

  • Info Line 1302, Column 1: start tag was here
    <img alt="ver Origen de los guardianes online" border="0" height="320" src="htt…
  • Error Line 1303, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1303, Column 1: start tag was here
    <br>
  • Warning Line 1318, Column 204: reference not terminated by REFC delimiter
    …s-guardianes-online-latino.html&layout=button_count&show_faces=false&width=100…

    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 1318, Column 204: reference to external entity in attribute value
    …s-guardianes-online-latino.html&layout=button_count&show_faces=false&width=100…

    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 1318, Column 204: reference to entity "layout" for which no system identifier could be generated
    …s-guardianes-online-latino.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1318, Column 228: reference not terminated by REFC delimiter
    …no.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1318, Column 228: reference to external entity in attribute value
    …no.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1318, Column 228: reference to entity "show_faces" for which no system identifier could be generated
    …no.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1318, Column 240: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1318, Column 240: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1318, Column 240: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1318, Column 251: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1318, Column 251: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1318, Column 251: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1318, Column 261: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1318, Column 261: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1318, Column 261: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1318, Column 279: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1318, Column 279: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1318, Column 279: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1318, Column 348: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1318, Column 488: element "g:plusone" undefined
    …gen-de-los-guardianes-online-latino.html' size='small'></g:plusone></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).
  • Error Line 1336, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1347, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1347, Column 1: start tag was here
    <br>
  • Error Line 1349, Column 213: end tag for "img" omitted, but OMITTAG NO was specified
    …/s320/ver_Siniestro_Online.jpg" title="ver Siniestro Online" width="216"></div>

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

  • Info Line 1349, Column 1: start tag was here
    <img alt="ver Siniestro Online" border="0" height="320" src="http://1.bp.blogsp…
  • Error Line 1350, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1350, Column 1: start tag was here
    <br>
  • Warning Line 1365, Column 187: reference not terminated by REFC delimiter
    …3/03/siniestro-2012-online.html&layout=button_count&show_faces=false&width=100…

    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 1365, Column 187: reference to external entity in attribute value
    …3/03/siniestro-2012-online.html&layout=button_count&show_faces=false&width=100…

    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 1365, Column 187: reference to entity "layout" for which no system identifier could be generated
    …3/03/siniestro-2012-online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1365, Column 211: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1365, Column 211: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1365, Column 211: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1365, Column 223: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1365, Column 223: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1365, Column 223: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1365, Column 234: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1365, Column 234: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1365, Column 234: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1365, Column 244: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1365, Column 244: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1365, Column 244: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1365, Column 262: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1365, Column 262: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1365, Column 262: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1365, Column 331: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1365, Column 454: element "g:plusone" undefined
    …o.com/2013/03/siniestro-2012-online.html' size='small'></g:plusone></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).
  • Error Line 1378, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1389, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1389, Column 1: start tag was here
    <br>
  • Error Line 1390, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1390, Column 1: start tag was here
    <br>
  • Error Line 1392, Column 195: end tag for "img" omitted, but OMITTAG NO was specified
    …ABTw/lCMZcX9UXKQ/s320/amor.jpg" title=" Amour Online gratis" width="226"></div>

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

  • Info Line 1392, Column 1: start tag was here
    <img alt=" Amour Online Gratis" height="320" src="https://lh6.googleusercontent…
  • Warning Line 1407, Column 177: reference not terminated by REFC delimiter
    …no.com/2013/01/amor-online.html&layout=button_count&show_faces=false&width=100…

    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 1407, Column 177: reference to external entity in attribute value
    …no.com/2013/01/amor-online.html&layout=button_count&show_faces=false&width=100…

    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 1407, Column 177: reference to entity "layout" for which no system identifier could be generated
    …no.com/2013/01/amor-online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1407, Column 201: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1407, Column 201: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1407, Column 201: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1407, Column 213: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1407, Column 213: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1407, Column 213: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1407, Column 224: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1407, Column 224: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1407, Column 224: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1407, Column 234: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1407, Column 234: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1407, Column 234: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1407, Column 252: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1407, Column 252: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1407, Column 252: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1407, Column 321: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1407, Column 434: element "g:plusone" undefined
    …pelislatino.com/2013/01/amor-online.html' size='small'></g:plusone></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).
  • Error Line 1420, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1431, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1431, Column 1: start tag was here
    <br>
  • Error Line 1433, Column 251: end tag for "img" omitted, but OMITTAG NO was specified
    …ill_2_Online.jpg" title="ver Terror en Silent Hill 2 Online" width="232"></div>

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

  • Info Line 1433, Column 1: start tag was here
    <img alt="ver Terror en Silent Hill 2 Online" border="0" height="320" src="http…
  • Error Line 1434, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1434, Column 1: start tag was here
    <br>
  • Warning Line 1449, Column 201: reference not terminated by REFC delimiter
    …-Silent-Hill-2-2012-Online.html&layout=button_count&show_faces=false&width=100…

    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 1449, Column 201: reference to external entity in attribute value
    …-Silent-Hill-2-2012-Online.html&layout=button_count&show_faces=false&width=100…

    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 1449, Column 201: reference to entity "layout" for which no system identifier could be generated
    …-Silent-Hill-2-2012-Online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1449, Column 225: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1449, Column 225: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1449, Column 225: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1449, Column 237: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1449, Column 237: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1449, Column 237: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1449, Column 248: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1449, Column 248: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1449, Column 248: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1449, Column 258: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1449, Column 258: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1449, Column 258: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1449, Column 276: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1449, Column 276: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1449, Column 276: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1449, Column 345: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1449, Column 482: element "g:plusone" undefined
    …terror-en-Silent-Hill-2-2012-Online.html' size='small'></g:plusone></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).
  • Error Line 1465, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1477, Column 155: there is no attribute "imageanchor"
    …y.tuspelislatino.com.png" imageanchor="1" style="clear: left; float: left; mar…

    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 1477, Column 469: end tag for "img" omitted, but OMITTAG NO was specified
    ….by.tuspelislatino.com.png" title="desconocido latino online Gratis"></a></div>

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

  • Info Line 1477, Column 232: start tag was here
    …rgin-bottom: 1em; margin-right: 1em;"><img alt="desconocido latino online Grat…
  • Warning Line 1492, Column 191: reference not terminated by REFC delimiter
    …/desconocido-latino-online.html&layout=button_count&show_faces=false&width=100…

    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 1492, Column 191: reference to external entity in attribute value
    …/desconocido-latino-online.html&layout=button_count&show_faces=false&width=100…

    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 1492, Column 191: reference to entity "layout" for which no system identifier could be generated
    …/desconocido-latino-online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1492, Column 215: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1492, Column 215: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1492, Column 215: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1492, Column 227: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1492, Column 227: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1492, Column 227: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1492, Column 238: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1492, Column 238: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1492, Column 238: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1492, Column 248: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1492, Column 248: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1492, Column 248: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1492, Column 266: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1492, Column 266: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1492, Column 266: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1492, Column 335: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1492, Column 462: element "g:plusone" undefined
    …m/2012/08/desconocido-latino-online.html' size='small'></g:plusone></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).
  • Error Line 1505, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1517, Column 463: end tag for "img" omitted, but OMITTAG NO was specified
    …reets_Online.jpg" title="The King of the Streets Online" width="246"></a></div>

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

  • Info Line 1517, Column 219: start tag was here
    …rgin-bottom: 1em; margin-right: 1em;"><img alt="The King of the Streets Online…
  • Warning Line 1532, Column 197: reference not terminated by REFC delimiter
    …ing-of-streets-2012-online.html&layout=button_count&show_faces=false&width=100…

    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 1532, Column 197: reference to external entity in attribute value
    …ing-of-streets-2012-online.html&layout=button_count&show_faces=false&width=100…

    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 1532, Column 197: reference to entity "layout" for which no system identifier could be generated
    …ing-of-streets-2012-online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1532, Column 221: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1532, Column 221: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1532, Column 221: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1532, Column 233: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1532, Column 233: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1532, Column 233: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1532, Column 244: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1532, Column 244: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1532, Column 244: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1532, Column 254: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1532, Column 254: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1532, Column 254: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1532, Column 272: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1532, Column 272: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1532, Column 272: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1532, Column 341: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1532, Column 474: element "g:plusone" undefined
    …/02/the-king-of-streets-2012-online.html' size='small'></g:plusone></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).
  • Error Line 1544, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1556, Column 407: end tag for "img" omitted, but OMITTAG NO was specified
    …/s320/ver_9_meses_Online.jpg" title="ver 9 meses Online" width="216"></a></div>

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

  • Info Line 1556, Column 203: start tag was here
    …rgin-bottom: 1em; margin-right: 1em;"><img alt="ver 9 meses Online" border="0"…
  • Warning Line 1571, Column 185: reference not terminated by REFC delimiter
    …013/02/9-meses-2010-online.html&layout=button_count&show_faces=false&width=100…

    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 1571, Column 185: reference to external entity in attribute value
    …013/02/9-meses-2010-online.html&layout=button_count&show_faces=false&width=100…

    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 1571, Column 185: reference to entity "layout" for which no system identifier could be generated
    …013/02/9-meses-2010-online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1571, Column 209: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1571, Column 209: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1571, Column 209: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1571, Column 221: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1571, Column 221: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1571, Column 221: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1571, Column 232: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1571, Column 232: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1571, Column 232: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1571, Column 242: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1571, Column 242: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1571, Column 242: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1571, Column 260: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1571, Column 260: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1571, Column 260: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1571, Column 329: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1571, Column 450: element "g:plusone" undefined
    …ino.com/2013/02/9-meses-2010-online.html' size='small'></g:plusone></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).
  • Error Line 1583, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1594, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1594, Column 1: start tag was here
    <br>
  • Error Line 1596, Column 234: end tag for "img" omitted, but OMITTAG NO was specified
    …2520posesion.jpg" title="La Posesión Satánica Online Latino" width="207"></div>

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

  • Info Line 1596, Column 1: start tag was here
    <img alt="La Posesión Satánica Online Latino" height="320" src="https://lh5.goo…
  • Error Line 1597, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1597, Column 1: start tag was here
    <br>
  • Warning Line 1612, Column 191: reference not terminated by REFC delimiter
    …/ver-the-possession-online.html&layout=button_count&show_faces=false&width=100…

    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 1612, Column 191: reference to external entity in attribute value
    …/ver-the-possession-online.html&layout=button_count&show_faces=false&width=100…

    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 1612, Column 191: reference to entity "layout" for which no system identifier could be generated
    …/ver-the-possession-online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1612, Column 215: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1612, Column 215: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1612, Column 215: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1612, Column 227: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1612, Column 227: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1612, Column 227: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1612, Column 238: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1612, Column 238: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1612, Column 238: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1612, Column 248: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1612, Column 248: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1612, Column 248: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1612, Column 266: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1612, Column 266: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1612, Column 266: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1612, Column 335: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1612, Column 462: element "g:plusone" undefined
    …m/2012/09/ver-the-possession-online.html' size='small'></g:plusone></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).
  • Error Line 1630, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1641, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1641, Column 1: start tag was here
    <br>
  • Error Line 1643, Column 207: end tag for "img" omitted, but OMITTAG NO was specified
    …ofiA/s320/ver_Invasor_Online.jpg" title="ver Invasor Online" width="210"></div>

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

  • Info Line 1643, Column 1: start tag was here
    <img alt="ver Invasor Online" border="0" height="320" src="http://4.bp.blogspot…
  • Error Line 1644, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1644, Column 1: start tag was here
    <br>
  • Warning Line 1659, Column 185: reference not terminated by REFC delimiter
    …013/02/invasor-2012-online.html&layout=button_count&show_faces=false&width=100…

    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 1659, Column 185: reference to external entity in attribute value
    …013/02/invasor-2012-online.html&layout=button_count&show_faces=false&width=100…

    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 1659, Column 185: reference to entity "layout" for which no system identifier could be generated
    …013/02/invasor-2012-online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1659, Column 209: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1659, Column 209: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1659, Column 209: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1659, Column 221: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1659, Column 221: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1659, Column 221: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1659, Column 232: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1659, Column 232: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1659, Column 232: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1659, Column 242: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1659, Column 242: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1659, Column 242: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1659, Column 260: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1659, Column 260: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1659, Column 260: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1659, Column 329: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1659, Column 450: element "g:plusone" undefined
    …ino.com/2013/02/invasor-2012-online.html' size='small'></g:plusone></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).
  • Error Line 1671, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1683, Column 485: end tag for "img" omitted, but OMITTAG NO was specified
    …C3%B1ol.jpg" title="Generation Um... Online Sub Español" width="213"></a></div>

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

  • Info Line 1683, Column 225: start tag was here
    …rgin-bottom: 1em; margin-right: 1em;"><img alt="Generation Um... Online Sub Es…
  • Warning Line 1698, Column 186: reference not terminated by REFC delimiter
    …12/08/generation-um-online.html&layout=button_count&show_faces=false&width=100…

    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 1698, Column 186: reference to external entity in attribute value
    …12/08/generation-um-online.html&layout=button_count&show_faces=false&width=100…

    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 1698, Column 186: reference to entity "layout" for which no system identifier could be generated
    …12/08/generation-um-online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1698, Column 210: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1698, Column 210: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1698, Column 210: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1698, Column 222: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1698, Column 222: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1698, Column 222: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1698, Column 233: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1698, Column 233: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1698, Column 233: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1698, Column 243: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1698, Column 243: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1698, Column 243: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1698, Column 261: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1698, Column 261: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1698, Column 261: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1698, Column 330: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1698, Column 452: element "g:plusone" undefined
    …no.com/2012/08/generation-um-online.html' size='small'></g:plusone></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).
  • Error Line 1713, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1725, Column 425: end tag for "img" omitted, but OMITTAG NO was specified
    …+_Peso_Pesado_Online.jpg" title="ver Peso Pesado Online" width="225"></a></div>

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

  • Info Line 1725, Column 208: start tag was here
    …rgin-bottom: 1em; margin-right: 1em;"><img alt="ver Peso Pesado Online" border…
  • Warning Line 1740, Column 189: reference not terminated by REFC delimiter
    …01/peso-pesado-2012-online.html&layout=button_count&show_faces=false&width=100…

    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 1740, Column 189: reference to external entity in attribute value
    …01/peso-pesado-2012-online.html&layout=button_count&show_faces=false&width=100…

    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 1740, Column 189: reference to entity "layout" for which no system identifier could be generated
    …01/peso-pesado-2012-online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1740, Column 213: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1740, Column 213: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1740, Column 213: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1740, Column 225: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1740, Column 225: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1740, Column 225: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1740, Column 236: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1740, Column 236: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1740, Column 236: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1740, Column 246: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1740, Column 246: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1740, Column 246: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1740, Column 264: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1740, Column 264: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1740, Column 264: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1740, Column 333: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1740, Column 458: element "g:plusone" undefined
    …com/2013/01/peso-pesado-2012-online.html' size='small'></g:plusone></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).
  • Error Line 1757, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1768, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1768, Column 1: start tag was here
    <br>
  • Error Line 1769, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1769, Column 1: start tag was here
    <br>
  • Error Line 1771, Column 218: end tag for "img" omitted, but OMITTAG NO was specified
    …s320/rompe%2520ralph.jpg" title="Ralph: El Demoledor Online" width="216"></div>

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

  • Info Line 1771, Column 1: start tag was here
    <img alt="Ralph: El Demoledor Online" height="320" src="https://lh5.googleuserc…
  • Warning Line 1786, Column 198: reference not terminated by REFC delimiter
    …el-demoledor-online-latino.html&layout=button_count&show_faces=false&width=100…

    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 1786, Column 198: reference to external entity in attribute value
    …el-demoledor-online-latino.html&layout=button_count&show_faces=false&width=100…

    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 1786, Column 198: reference to entity "layout" for which no system identifier could be generated
    …el-demoledor-online-latino.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1786, Column 222: reference not terminated by REFC delimiter
    …no.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1786, Column 222: reference to external entity in attribute value
    …no.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1786, Column 222: reference to entity "show_faces" for which no system identifier could be generated
    …no.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1786, Column 234: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1786, Column 234: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1786, Column 234: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1786, Column 245: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1786, Column 245: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1786, Column 245: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1786, Column 255: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1786, Column 255: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1786, Column 255: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1786, Column 273: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1786, Column 273: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1786, Column 273: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1786, Column 342: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1786, Column 476: element "g:plusone" undefined
    …12/ralph-el-demoledor-online-latino.html' size='small'></g:plusone></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).
  • Error Line 1804, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1815, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1815, Column 1: start tag was here
    <br>
  • Error Line 1817, Column 205: end tag for "img" omitted, but OMITTAG NO was specified
    …yD0/s320/ver+Argo+Online+Latino.jpg" title="ver Argo Online" width="208"></div>

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

  • Info Line 1817, Column 1: start tag was here
    <img alt="ver Argo Online" border="0" height="320" src="http://1.bp.blogspot.co…
  • Error Line 1818, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1818, Column 1: start tag was here
    <br>
  • Warning Line 1833, Column 181: reference not terminated by REFC delimiter
    …om/2012/10/ver-Argo-Online.html&layout=button_count&show_faces=false&width=100…

    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 1833, Column 181: reference to external entity in attribute value
    …om/2012/10/ver-Argo-Online.html&layout=button_count&show_faces=false&width=100…

    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 1833, Column 181: reference to entity "layout" for which no system identifier could be generated
    …om/2012/10/ver-Argo-Online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1833, Column 205: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1833, Column 205: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1833, Column 205: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1833, Column 217: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1833, Column 217: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1833, Column 217: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1833, Column 228: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1833, Column 228: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1833, Column 228: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1833, Column 238: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1833, Column 238: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1833, Column 238: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1833, Column 256: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1833, Column 256: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1833, Column 256: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1833, Column 325: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1833, Column 442: element "g:plusone" undefined
    …slatino.com/2012/10/ver-Argo-Online.html' size='small'></g:plusone></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).
  • Error Line 1850, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1861, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1861, Column 1: start tag was here
    <br>
  • Error Line 1863, Column 237: end tag for "img" omitted, but OMITTAG NO was specified
    …nline+Latino+en+HD.jpg" title="Valiente Online Latino en HD" width="226"></div>

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

  • Info Line 1863, Column 1: start tag was here
    <img alt="Valiente Online Latino en HD" border="0" height="320" src="http://1.b…
  • Error Line 1864, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1864, Column 1: start tag was here
    <br>
  • Warning Line 1879, Column 191: reference not terminated by REFC delimiter
    …/valiente-online-latino-hd.html&layout=button_count&show_faces=false&width=100…

    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 1879, Column 191: reference to external entity in attribute value
    …/valiente-online-latino-hd.html&layout=button_count&show_faces=false&width=100…

    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 1879, Column 191: reference to entity "layout" for which no system identifier could be generated
    …/valiente-online-latino-hd.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1879, Column 215: reference not terminated by REFC delimiter
    …hd.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1879, Column 215: reference to external entity in attribute value
    …hd.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1879, Column 215: reference to entity "show_faces" for which no system identifier could be generated
    …hd.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1879, Column 227: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1879, Column 227: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1879, Column 227: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1879, Column 238: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1879, Column 238: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1879, Column 238: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1879, Column 248: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1879, Column 248: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1879, Column 248: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1879, Column 266: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1879, Column 266: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1879, Column 266: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1879, Column 335: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1879, Column 462: element "g:plusone" undefined
    …m/2012/11/valiente-online-latino-hd.html' size='small'></g:plusone></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).
  • Error Line 1897, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1908, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1908, Column 1: start tag was here
    <br>
  • Error Line 1910, Column 240: end tag for "img" omitted, but OMITTAG NO was specified
    …suavemente_Online.jpg" title="ver Matalos suavemente Online" width="224"></div>

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

  • Info Line 1910, Column 1: start tag was here
    <img alt="ver Matalos suavemente Online" border="0" height="320" src="http://1.…
  • Error Line 1911, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1911, Column 1: start tag was here
    <br>
  • Warning Line 1926, Column 195: reference not terminated by REFC delimiter
    …alos-suavemente-2012Online.html&layout=button_count&show_faces=false&width=100…

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

  • Warning Line 1926, Column 195: reference to external entity in attribute value
    …alos-suavemente-2012Online.html&layout=button_count&show_faces=false&width=100…

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

  • Error Line 1926, Column 195: reference to entity "layout" for which no system identifier could be generated
    …alos-suavemente-2012Online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1926, Column 219: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Warning Line 1926, Column 219: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Error Line 1926, Column 219: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1926, Column 231: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Warning Line 1926, Column 231: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Error Line 1926, Column 231: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1926, Column 242: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Warning Line 1926, Column 242: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Error Line 1926, Column 242: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1926, Column 252: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Warning Line 1926, Column 252: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Error Line 1926, Column 252: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1926, Column 270: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Warning Line 1926, Column 270: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Error Line 1926, Column 270: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1926, Column 339: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1926, Column 470: element "g:plusone" undefined
    …13/02/Matalos-suavemente-2012Online.html' size='small'></g:plusone></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).
  • Error Line 1938, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 1949, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1949, Column 1: start tag was here
    <br>
  • Error Line 1950, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1950, Column 1: start tag was here
    <br>
  • Error Line 1952, Column 252: end tag for "img" omitted, but OMITTAG NO was specified
    …it.jpg" title="El Hobbit: Un viaje inesperado Online Gratis" width="208"></div>

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

  • Info Line 1952, Column 1: start tag was here
    <img alt="El Hobbit: Un viaje inesperado Online Gratis" height="320" src="https…
  • Warning Line 1967, Column 202: reference not terminated by REFC delimiter
    …un-viaje-inesperado-online.html&layout=button_count&show_faces=false&width=100…

    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 1967, Column 202: reference to external entity in attribute value
    …un-viaje-inesperado-online.html&layout=button_count&show_faces=false&width=100…

    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 1967, Column 202: reference to entity "layout" for which no system identifier could be generated
    …un-viaje-inesperado-online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 1967, Column 226: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1967, Column 226: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 1967, Column 226: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 1967, Column 238: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1967, Column 238: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 1967, Column 238: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 1967, Column 249: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1967, Column 249: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 1967, Column 249: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 1967, Column 259: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1967, Column 259: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 1967, Column 259: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 1967, Column 277: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1967, Column 277: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 1967, Column 277: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 1967, Column 346: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1967, Column 484: element "g:plusone" undefined
    …l-hobbit-un-viaje-inesperado-online.html' size='small'></g:plusone></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).
  • Error Line 1986, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 2002, Column 36: element "u" undefined
    En esta quita entrega de la saga <u>John McLane</u>, volverá a meterse en probl…

    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 2013, Column 12: there is no attribute "align"
    <div align="center">

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

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

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

  • Error Line 2029, Column 32: there is no attribute "height"
    <iframe frameborder="0" height="360" src="http://vk.com/video_ext.php?oid=17387…

    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 2029, Column 144: there is no attribute "width"
    …5850&amp;id=164703866&amp;hash=d1de47079f538f9b&amp;hd=1" width="650"></iframe>

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

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

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

  • Error Line 2029, Column 149: element "iframe" undefined
    …5850&amp;id=164703866&amp;hash=d1de47079f538f9b&amp;hd=1" width="650"></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 2036, Column 148: element "iframe" undefined
    …62247744a2190fa84af7577b444" style="z-index: 2147483647;" width="650"></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 2043, Column 149: element "iframe" undefined
    …5850&amp;id=164703884&amp;hash=00ec96a0f07cc6a7&amp;hd=1" width="650"></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 2050, Column 149: element "iframe" undefined
    …5850&amp;id=164703890&amp;hash=1428ce2b28269f87&amp;hd=1" width="650"></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 2054, Column 93: element "u" undefined
    … a good day to die hard online</b>, <u>ver un buen día para morir online</u>, …

    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 2054, Column 257: element "u" undefined
    …ea, duro de matar 5 español online, <u>duro de matar 2013</u> online, 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 2054, Column 350: element "u" undefined
    …o de matar cinco, duro de matar 5 - <u>un buen dia para morir online latino</u…

    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 2067, Column 211: reference not terminated by REFC delimiter
    …buen-dia-para-morir-online.html&layout=button_count&show_faces=false&width=100…

    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 2067, Column 211: reference to external entity in attribute value
    …buen-dia-para-morir-online.html&layout=button_count&show_faces=false&width=100…

    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 2067, Column 211: reference to entity "layout" for which no system identifier could be generated
    …buen-dia-para-morir-online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 2067, Column 235: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 2067, Column 235: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 2067, Column 235: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 2067, Column 247: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 2067, Column 247: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 2067, Column 247: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 2067, Column 258: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 2067, Column 258: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 2067, Column 258: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 2067, Column 268: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 2067, Column 268: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 2067, Column 268: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 2067, Column 286: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 2067, Column 286: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 2067, Column 286: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 2067, Column 355: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2067, Column 502: element "g:plusone" undefined
    …tar-5-un-buen-dia-para-morir-online.html' size='small'></g:plusone></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).
  • Error Line 2084, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 2095, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 2095, Column 1: start tag was here
    <br>
  • Error Line 2097, Column 233: end tag for "img" omitted, but OMITTAG NO was specified
    …scendientes_Online.jpg" title="ver Los descendientes Online" width="222"></div>

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

  • Info Line 2097, Column 1: start tag was here
    <img alt="ver Los descendientes Online" border="0" height="320" src="http://2.b…
  • Error Line 2098, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 2098, Column 1: start tag was here
    <br>
  • Warning Line 2113, Column 195: reference not terminated by REFC delimiter
    …-descendientes-2011-online.html&layout=button_count&show_faces=false&width=100…

    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 2113, Column 195: reference to external entity in attribute value
    …-descendientes-2011-online.html&layout=button_count&show_faces=false&width=100…

    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 2113, Column 195: reference to entity "layout" for which no system identifier could be generated
    …-descendientes-2011-online.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 2113, Column 219: reference not terminated by REFC delimiter
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 2113, Column 219: reference to external entity in attribute value
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 2113, Column 219: reference to entity "show_faces" for which no system identifier could be generated
    …ne.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 2113, Column 231: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 2113, Column 231: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 2113, Column 231: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 2113, Column 242: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 2113, Column 242: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 2113, Column 242: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 2113, Column 252: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 2113, Column 252: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 2113, Column 252: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 2113, Column 270: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 2113, Column 270: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 2113, Column 270: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 2113, Column 339: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2113, Column 470: element "g:plusone" undefined
    …13/02/los-descendientes-2011-online.html' size='small'></g:plusone></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).
  • Error Line 2127, Column 23: ID "post" already defined
    <div class='post' id='post'>

    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 1245, Column 23: ID "post" first defined here
    <div class='post' id='post'>
  • Error Line 2138, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 2138, Column 1: start tag was here
    <br>
  • Error Line 2140, Column 338: end tag for "img" omitted, but OMITTAG NO was specified
    …r El Señor de los anillos II - Las dos torres Online Latino" width="206"></div>

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

  • Info Line 2140, Column 1: start tag was here
    <img alt="ver El Señor de los anillos II - Las dos torres Online Latino" border…
  • Warning Line 2155, Column 222: reference not terminated by REFC delimiter
    …s-dos-torres-Online-Latino.html&layout=button_count&show_faces=false&width=100…

    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 2155, Column 222: reference to external entity in attribute value
    …s-dos-torres-Online-Latino.html&layout=button_count&show_faces=false&width=100…

    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 2155, Column 222: reference to entity "layout" for which no system identifier could be generated
    …s-dos-torres-Online-Latino.html&layout=button_count&show_faces=false&width=100…

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

  • Info Line 1274, Column 198: entity was defined here
    …quiere-ser-millonario-2008-online.html&layout=button_count&show_faces=false&wi…
  • Warning Line 2155, Column 246: reference not terminated by REFC delimiter
    …no.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 2155, Column 246: reference to external entity in attribute value
    …no.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

    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 2155, Column 246: reference to entity "show_faces" for which no system identifier could be generated
    …no.html&layout=button_count&show_faces=false&width=100&action=like&font=arial&…

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

  • Info Line 1274, Column 218: entity was defined here
    …o-2008-online.html&layout=button_count&show_faces=false&width=100&action=like&…
  • Warning Line 2155, Column 258: reference not terminated by REFC delimiter
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 2155, Column 258: reference to external entity in attribute value
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

    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 2155, Column 258: reference to entity "width" for which no system identifier could be generated
    …ut=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=…

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

  • Info Line 1274, Column 235: entity was defined here
    …l&layout=button_count&show_faces=false&width=100&action=like&font=arial&colors…
  • Warning Line 2155, Column 269: reference not terminated by REFC delimiter
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 2155, Column 269: reference to external entity in attribute value
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

    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 2155, Column 269: reference to entity "action" for which no system identifier could be generated
    …ount&show_faces=false&width=100&action=like&font=arial&colorscheme=light' styl…

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 2155, Column 279: reference not terminated by REFC delimiter
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 2155, Column 279: reference to external entity in attribute value
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

    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 2155, Column 279: reference to entity "font" for which no system identifier could be generated
    …faces=false&width=100&action=like&font=arial&colorscheme=light' style='border:…

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

  • Info Line 1274, Column 257: entity was defined here
    …show_faces=false&width=100&action=like&font=arial&colorscheme=light' style='bo…
  • Warning Line 2155, Column 297: reference not terminated by REFC delimiter
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 2155, Column 297: reference to external entity in attribute value
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

    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 2155, Column 297: reference to entity "colorscheme" for which no system identifier could be generated
    …100&action=like&font=arial&colorscheme=light' style='border:none; overflow:hid…

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

  • Info Line 1274, Column 268: entity was defined here
    …false&width=100&action=like&font=arial&colorscheme=light' style='border:none; …
  • Error Line 2155, Column 366: element "iframe" undefined
    …rflow:hidden; width:96px; height:20px'></iframe><div class='plus'><g:plusone h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2155, Column 524: element "g:plusone" undefined
    …nillos-Las-dos-torres-Online-Latino.html' size='small'></g:plusone></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).
  • Error Line 2226, Column 149: required attribute "alt" not specified
    …l.png' style='float:left;margin-top:-3px;'/> Recibe las últimas Películas </h2>

    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 2228, Column 160: there is no attribute "target"
    …fb/a/mailverify" method="post" target="popupwindow" onsubmit="window.open('htt…

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

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

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

  • Error Line 2229, Column 298: 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
    …en" value="TusPelisLatino" name="uri"/><input type="hidden" name="loc" value="…

    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 2229, Column 345: 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
    …ype="hidden" name="loc" value="es_ES"/><div><input type="submit" value="Enviar…

    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 2231, Column 92: there is no attribute "data-show-count"
    …witter-follow-button" data-show-count="false" data-lang="es">Seguir a @TusPeli…

    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 2231, Column 110: there is no attribute "data-lang"
    …low-button" data-show-count="false" data-lang="es">Seguir a @TusPelisLatino</a>

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

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

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

  • Error Line 2232, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

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

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

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

  • Warning Line 2296, Column 93: reference not terminated by REFC delimiter
    …?blogID=6786839474821523869&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 2296, Column 93: reference to external entity in attribute value
    …?blogID=6786839474821523869&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 2296, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=6786839474821523869&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 1084, Column 82: entity was defined here
    …m/rearrange?blogID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=…
  • Warning Line 2296, Column 107: reference not terminated by REFC delimiter
    …9474821523869&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=sideb…

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

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

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

  • Info Line 1084, Column 98: entity was defined here
    …ID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&secti…
  • Warning Line 2296, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=sidebar' 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 2296, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=sidebar' 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 2296, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=sidebar' 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 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 2296, Column 141: reference not terminated by REFC delimiter
    …etId=HTML5&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

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

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

  • Info Line 1084, Column 132: entity was defined here
    …HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _Widget…
  • Error Line 2303, Column 143: required attribute "alt" not specified
    …TKl5iuplw/s1600/folder.png' style='float:left;margin-top:-3px;'/> Géneros </h2>

    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 2374, Column 93: reference not terminated by REFC delimiter
    …?blogID=6786839474821523869&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 2374, Column 93: reference to external entity in attribute value
    …?blogID=6786839474821523869&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 2374, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=6786839474821523869&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 1084, Column 82: entity was defined here
    …m/rearrange?blogID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=…
  • Warning Line 2374, Column 108: reference not terminated by REFC delimiter
    …474821523869&widgetType=Label&widgetId=Label1&action=editWidget&sectionId=side…

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

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

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

  • Info Line 1084, Column 98: entity was defined here
    …ID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&secti…
  • Warning Line 2374, Column 122: reference not terminated by REFC delimiter
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=sidebar' 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 2374, Column 122: reference to external entity in attribute value
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=sidebar' 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 2374, Column 122: reference to entity "action" for which no system identifier could be generated
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=sidebar' 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 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 2374, Column 143: reference not terminated by REFC delimiter
    …tId=Label1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

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

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

  • Info Line 1084, Column 132: entity was defined here
    …HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _Widget…
  • Error Line 2385, Column 6: required attribute "action" not specified
    <form><select name="menu" onchange="window.open(this.options[this.selectedIndex…

    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 2385, Column 107: document type does not allow element "select" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …change="window.open(this.options[this.selectedIndex].value,'_blank')" size="1">

    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 2386, Column 11: character data is not allowed here
    <option />Buscar Películas por Año...

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2387, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2013" />2013 

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2388, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2012" />2012

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2389, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2011" />2011

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2390, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2010" />2010

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2391, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2009" />2009

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2392, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2008" />2008

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2393, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2007" />2007

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2394, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2006" />2006

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2395, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2005" />2005

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2396, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2004" />2004

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2397, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2003" />2003

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2398, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2002" />2002

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2399, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2001" />2001

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2400, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/2000" />2000

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2401, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1999" />1999

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2402, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1998" />1998

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2403, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1997" />1997

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2404, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1996" />1996

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2405, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1995" />1995

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2406, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1994" />1994

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2407, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1993" />1993

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2408, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1992" />1992

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2409, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1991" />1991

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2410, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1990" />1990

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2411, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1989" />1989

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2412, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1988" />1988

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2413, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1987" />1987

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2414, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1986" />1986

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2415, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1985" />1985

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2416, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1984" />1984

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2417, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1980" />1980

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2418, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1973" />1972

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2419, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1971" />1971

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2420, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1964" />1967

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2421, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1964" />1964

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2422, Column 67: character data is not allowed here
    <option value="http://www.tuspelislatino.com/search/label/1964" />1940

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 2429, Column 93: reference not terminated by REFC delimiter
    …?blogID=6786839474821523869&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 2429, Column 93: reference to external entity in attribute value
    …?blogID=6786839474821523869&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 2429, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=6786839474821523869&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 1084, Column 82: entity was defined here
    …m/rearrange?blogID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=…
  • Warning Line 2429, Column 107: reference not terminated by REFC delimiter
    …9474821523869&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sideb…

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

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

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

  • Info Line 1084, Column 98: entity was defined here
    …ID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&secti…
  • Warning Line 2429, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sidebar' 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 2429, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sidebar' 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 2429, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sidebar' 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 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 2429, Column 141: reference not terminated by REFC delimiter
    …etId=HTML3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

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

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

  • Info Line 1084, Column 132: entity was defined here
    …HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _Widget…
  • Error Line 2436, Column 139: required attribute "alt" not specified
    …0c/s1600/tv.png' style='float:left;margin-top:-3px;'/>Peliculas Más Vistas</h2>

    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 2515, Column 93: reference not terminated by REFC delimiter
    …?blogID=6786839474821523869&widgetType=PopularPosts&widgetId=PopularPosts1&act…

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

  • Warning Line 2515, Column 93: reference to external entity in attribute value
    …?blogID=6786839474821523869&widgetType=PopularPosts&widgetId=PopularPosts1&act…

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

  • Error Line 2515, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=6786839474821523869&widgetType=PopularPosts&widgetId=PopularPosts1&act…

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

  • Info Line 1084, Column 82: entity was defined here
    …m/rearrange?blogID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=…
  • Warning Line 2515, Column 115: reference not terminated by REFC delimiter
    …23869&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

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

  • Warning Line 2515, Column 115: reference to external entity in attribute value
    …23869&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

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

  • Error Line 2515, Column 115: reference to entity "widgetId" for which no system identifier could be generated
    …23869&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

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

  • Info Line 1084, Column 98: entity was defined here
    …ID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&secti…
  • Warning Line 2515, Column 136: reference not terminated by REFC delimiter
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=sidebar' 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 2515, Column 136: reference to external entity in attribute value
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=sidebar' 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 2515, Column 136: reference to entity "action" for which no system identifier could be generated
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=sidebar' 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 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 2515, Column 157: reference not terminated by REFC delimiter
    …ularPosts1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

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

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

  • Info Line 1084, Column 132: entity was defined here
    …HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _Widget…
  • Error Line 2524, Column 36: required attribute "type" not specified
    <script id="sid0010000021241785768">(function() {function async_load(){s.id="ci…

    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 2524, Column 348: character "<" is the first character of a delimiter but occurred as data
    …script');for (var i=0, l=ss.length; i < l; i++){if (ss[i].id=='sid001000002124…

    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 2529, Column 93: reference not terminated by REFC delimiter
    …?blogID=6786839474821523869&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 2529, Column 93: reference to external entity in attribute value
    …?blogID=6786839474821523869&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 2529, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=6786839474821523869&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 1084, Column 82: entity was defined here
    …m/rearrange?blogID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=…
  • Warning Line 2529, Column 107: reference not terminated by REFC delimiter
    …9474821523869&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=sideb…

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

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

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

  • Info Line 1084, Column 98: entity was defined here
    …ID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&secti…
  • Warning Line 2529, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=sidebar' 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 2529, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=sidebar' 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 2529, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=sidebar' 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 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 2529, Column 141: reference not terminated by REFC delimiter
    …etId=HTML6&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

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

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

  • Info Line 1084, Column 132: entity was defined here
    …HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _Widget…
  • Error Line 2546, Column 23: document type does not allow element "style" here
    <style type='text/css'>

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

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

  • Error Line 2566, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 2572, Column 446: there is no attribute "allowtransparency"
    …; background:#fff;" allowtransparency="true"></iframe><span><a href="http://ww…

    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 2572, Column 452: element "iframe" undefined
    …ground:#fff;" allowtransparency="true"></iframe><span><a href="http://www.tusp…

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

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

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

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

  • Info Line 1084, Column 98: entity was defined here
    …ID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&secti…
  • Warning Line 2578, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sidebar' 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 2578, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sidebar' 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 2578, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sidebar' 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 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 2578, Column 141: reference not terminated by REFC delimiter
    …etId=HTML4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

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

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

  • Info Line 1084, Column 132: entity was defined here
    …HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _Widget…
  • Error Line 2590, Column 15: there is no attribute "style"
    <script style='text/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 2590, Column 32: required attribute "type" not specified
    <script style='text/javascript'>

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

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

  • Error Line 2596, Column 104: required attribute "type" not specified
    …lislatino.com/script/blogger-page-navi-v2.js' style='text/javascript'></script>

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

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

  • Error Line 2599, Column 12: there is no attribute "CLASS"
    <div CLASS='cpy'>

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

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

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

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

  • Info Line 1084, Column 98: entity was defined here
    …ID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&secti…
  • Warning Line 2619, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=LinkList1' 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 2619, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=LinkList1' 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 2619, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=LinkList1' 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 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 2619, Column 141: reference not terminated by REFC delimiter
    …etId=HTML7&action=editWidget&sectionId=LinkList1' onclick='return _WidgetManag…

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

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

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

  • Info Line 1084, Column 132: entity was defined here
    …HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _Widget…
  • Error Line 2627, Column 21: required attribute "type" not specified
    <script id='_waus83'>var _wau = _wau || []; _wau.push(["small", "4zdofi1f57ub",…

    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 2627, Column 21: document type does not allow element "script" here; assuming missing "li" start-tag
    <script id='_waus83'>var _wau = _wau || []; _wau.push(["small", "4zdofi1f57ub",…
  • Error Line 2632, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    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 2627, Column 1: start tag was here
    <script id='_waus83'>var _wau = _wau || []; _wau.push(["small", "4zdofi1f57ub",…
  • Error Line 2637, Column 74: ID "Feed1" already defined
    <div class='widget Feed section' id='Feed1'><div class='widget Feed' id='Feed1'>

    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 2637, Column 38: ID "Feed1" first defined here
    <div class='widget Feed section' id='Feed1'><div class='widget Feed' id='Feed1'>
  • Warning Line 2647, Column 93: reference not terminated by REFC delimiter
    …?blogID=6786839474821523869&widgetType=Feed&widgetId=Feed1&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 2647, Column 93: reference to external entity in attribute value
    …?blogID=6786839474821523869&widgetType=Feed&widgetId=Feed1&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 2647, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=6786839474821523869&widgetType=Feed&widgetId=Feed1&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 1084, Column 82: entity was defined here
    …m/rearrange?blogID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=…
  • Warning Line 2647, Column 107: reference not terminated by REFC delimiter
    …9474821523869&widgetType=Feed&widgetId=Feed1&action=editWidget&sectionId=Feed1…

    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 2647, Column 107: reference to external entity in attribute value
    …9474821523869&widgetType=Feed&widgetId=Feed1&action=editWidget&sectionId=Feed1…

    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 2647, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …9474821523869&widgetType=Feed&widgetId=Feed1&action=editWidget&sectionId=Feed1…

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

  • Info Line 1084, Column 98: entity was defined here
    …ID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&secti…
  • Warning Line 2647, Column 120: reference not terminated by REFC delimiter
    …&widgetType=Feed&widgetId=Feed1&action=editWidget&sectionId=Feed1' onclick='re…

    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 2647, Column 120: reference to external entity in attribute value
    …&widgetType=Feed&widgetId=Feed1&action=editWidget&sectionId=Feed1' onclick='re…

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

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 2647, Column 141: reference not terminated by REFC delimiter
    …etId=Feed1&action=editWidget&sectionId=Feed1' onclick='return _WidgetManager._…

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

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

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

  • Info Line 1084, Column 132: entity was defined here
    …HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _Widget…
  • Warning Line 2679, Column 93: reference not terminated by REFC delimiter
    …?blogID=6786839474821523869&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 2679, Column 93: reference to external entity in attribute value
    …?blogID=6786839474821523869&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 2679, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=6786839474821523869&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 1084, Column 82: entity was defined here
    …m/rearrange?blogID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=…
  • Warning Line 2679, Column 107: reference not terminated by REFC delimiter
    …9474821523869&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=Feed2…

    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 2679, Column 107: reference to external entity in attribute value
    …9474821523869&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=Feed2…

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

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

  • Info Line 1084, Column 98: entity was defined here
    …ID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&secti…
  • Warning Line 2679, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=Feed2' onclick='re…

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

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

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

  • Info Line 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 2679, Column 141: reference not terminated by REFC delimiter
    …etId=HTML8&action=editWidget&sectionId=Feed2' onclick='return _WidgetManager._…

    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 2679, Column 141: reference to external entity in attribute value
    …etId=HTML8&action=editWidget&sectionId=Feed2' onclick='return _WidgetManager._…

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

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

  • Info Line 1084, Column 132: entity was defined here
    …HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _Widget…
  • Error Line 2686, Column 6: end tag for element "div" which is not open
    </div>

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

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

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

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

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

  • Error Line 2693, Column 23: document type does not allow element "style" here
    <style type='text/css'>

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

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

  • Warning Line 2733, Column 93: reference not terminated by REFC delimiter
    …?blogID=6786839474821523869&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 2733, Column 93: reference to external entity in attribute value
    …?blogID=6786839474821523869&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 2733, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=6786839474821523869&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 1084, Column 82: entity was defined here
    …m/rearrange?blogID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=…
  • Warning Line 2733, Column 107: reference not terminated by REFC delimiter
    …9474821523869&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=LinkL…

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

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

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

  • Info Line 1084, Column 98: entity was defined here
    …ID=6786839474821523869&widgetType=HTML&widgetId=HTML10&action=editWidget&secti…
  • Warning Line 2733, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=LinkList2' 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 2733, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=LinkList2' 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 2733, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=LinkList2' 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 1084, Column 114: entity was defined here
    …523869&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=col9' oncli…
  • Warning Line 2733, Column 141: reference not terminated by REFC delimiter
    …etId=HTML9&action=editWidget&sectionId=LinkList2' onclick='return _WidgetManag…

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

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

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

  • Info Line 1084, Column 132: entity was defined here
    …HTML&widgetId=HTML10&action=editWidget&sectionId=col9' onclick='return _Widget…
  • Error Line 2740, Column 6: end tag for element "div" which is not open
    </div>

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

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

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

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

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

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

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

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

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

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

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

  • Error Line 2753, Column 14: there is no attribute "TYPE"
    <SCRIPT TYPE="text/javascript" SRC="http://ad.xtendmedia.com/st?ad_type=ad&ad_s…

    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 2753, Column 36: there is no attribute "SRC"
    <SCRIPT TYPE="text/javascript" SRC="http://ad.xtendmedia.com/st?ad_type=ad&ad_s…

    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 2753, Column 76: cannot generate system identifier for general entity "ad_size"
    …ttp://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=3826902&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 2753, Column 76: general entity "ad_size" not defined and no default entity
    …ttp://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=3826902&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 2753, Column 83: reference not terminated by REFC delimiter
    …d.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=3826902&pub_url=${tuspel…

    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 2753, Column 83: reference to external entity in attribute value
    …d.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=3826902&pub_url=${tuspel…

    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 2753, Column 83: reference to entity "ad_size" for which no system identifier could be generated
    …d.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=3826902&pub_url=${tuspel…

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

  • Info Line 2753, Column 75: entity was defined here
    …http://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=3826902&pub_url=…
  • Warning Line 2753, Column 91: cannot generate system identifier for general entity "section"
    …edia.com/st?ad_type=ad&ad_size=728x90&section=3826902&pub_url=${tuspelislatino…

    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 2753, Column 91: general entity "section" not defined and no default entity
    …edia.com/st?ad_type=ad&ad_size=728x90&section=3826902&pub_url=${tuspelislatino…

    This is usually a cascading error caused by 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 2753, Column 98: reference not terminated by REFC delimiter
    …m/st?ad_type=ad&ad_size=728x90&section=3826902&pub_url=${tuspelislatino.com}">…

    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 2753, Column 98: reference to external entity in attribute value
    …m/st?ad_type=ad&ad_size=728x90&section=3826902&pub_url=${tuspelislatino.com}">…

    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 2753, Column 98: reference to entity "section" for which no system identifier could be generated
    …m/st?ad_type=ad&ad_size=728x90&section=3826902&pub_url=${tuspelislatino.com}">…

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

  • Info Line 2753, Column 90: entity was defined here
    …media.com/st?ad_type=ad&ad_size=728x90&section=3826902&pub_url=${tuspelislatin…
  • Warning Line 2753, Column 107: cannot generate system identifier for general entity "pub_url"
    …type=ad&ad_size=728x90&section=3826902&pub_url=${tuspelislatino.com}"></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 2753, Column 107: general entity "pub_url" not defined and no default entity
    …type=ad&ad_size=728x90&section=3826902&pub_url=${tuspelislatino.com}"></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 2753, Column 114: reference not terminated by REFC delimiter
    …type=ad&ad_size=728x90&section=3826902&pub_url=${tuspelislatino.com}"></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 2753, Column 114: reference to external entity in attribute value
    …type=ad&ad_size=728x90&section=3826902&pub_url=${tuspelislatino.com}"></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 2753, Column 114: reference to entity "pub_url" for which no system identifier could be generated
    …type=ad&ad_size=728x90&section=3826902&pub_url=${tuspelislatino.com}"></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 2753, Column 106: entity was defined here
    …type=ad&ad_size=728x90&section=3826902&pub_url=${tuspelislatino.com}"></SCRIPT…
  • Error Line 2753, Column 137: element "SCRIPT" undefined
    …type=ad&ad_size=728x90&section=3826902&pub_url=${tuspelislatino.com}"></SCRIPT>

    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 2756, Column 19: there is no attribute "onMouseOver"
    <span onMouseOver="jQuery(this).hide('fast');jQuery('#asd').show('slow')" class…

    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 2759, Column 15: there is no attribute "onClick"
    <span onClick="jQuery(this).parent().parent().remove();" class="jbtn">cerrar</s…

    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 2763, Column 91: cannot generate system identifier for general entity "rotateur"
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=83664"></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 2763, Column 91: general entity "rotateur" not defined and no default entity
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=83664"></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 2763, Column 99: reference not terminated by REFC delimiter
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=83664"></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 2763, Column 99: reference to external entity in attribute value
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=83664"></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 2763, Column 99: reference to entity "rotateur" for which no system identifier could be generated
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=83664"></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 2763, Column 90: entity was defined here
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=83664"></script>
  • Warning Line 2775, 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 2775, 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
  • 11.783 visits
Daily Visitor