Primiciatv portal de Entretenimiento, ocio e información de tus telenovelas favoritas y lo mejor en Deportes Online ...

primiciatv.com
  • Domain Name
    primiciatv.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #43505
  • Page Size
    88.8 KB
  • Ip Address
    74.125.132.121
  • Heading
    H1: 1, H2: 10, H3: 7, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 7 JPG, 12 PNG

Website Meta Analysis

  • Title
    Primicia tv
  • Meta Keyword
    capitulos completo, telenovelas gratis, novelas de tv, series online, videos favoritos, promo, avances deportivos, deportes en vivo, liga nacional
  • Meta Description
    Primiciatv portal de Entretenimiento, ocio e información de tus telenovelas favoritas y lo mejor en Deportes Online

Technical Analysis

  • Webserver
    GSE
  • Ip Address
    74.125.132.121
  • Domain Age
    4 Years, 1 Months, 17 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-type: text/html; charset=UTF-8
  • expires: Mon, 22 Jul 2013 22:06:57 GMT
  • date: Mon, 22 Jul 2013 22:06:57 GMT
  • cache-control: private, max-age=0
  • last-modified: Mon, 22 Jul 2013 20:16:45 GMT
  • etag: "9634853c-abc1-476b-bedd-c2d9bef177c9"
  • content-encoding: gzip
  • x-content-type-options: nosniff
  • x-xss-protection: 1; mode=block
  • content-length: 19072
  • server: GSE
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registro de Dominios: INCUBA IDEAS SAC - www.host.pe
Contacto: +511.7269550 - email

Domain Name: PRIMICIATV.COM

Registrant:
Personal
pascual gerrero olivera ( email )
barrios altos la victoria
LIMA
LIMA,00000
PE
Tel. +51.1992405077

Creation Date: 27-May-2009
Expiration Date: 27-May-2014

Domain servers in listed order:
ns1.cdmon.net
ns2.cdmon.net
ns3.cdmon.net


Administrative Contact:
Personal
pascual gerrero olivera ( email )
barrios altos la victoria
LIMA
LIMA,00000
PE
Tel. +51.1992405077

Technical Contact:
Personal
pascual gerrero olivera ( email )
barrios altos la victoria
LIMA
LIMA,00000
PE
Tel. +51.1992405077

Billing Contact:
Personal
pascual gerrero olivera ( email )
barrios altos la victoria
LIMA
LIMA,00000
PE
Tel. +51.1992405077

Status:LOCKED

DNS Analysis


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


DNS Records

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

Authority records

Additional records

IP 74.125.132.121 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Mountain View
  • Continent Code
    94043
  • Latitude
    650
  • Longitude
    807
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 74.125.132.121"
    #
    # Use "?" to get help.
    #

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

    NetRange: 74.125.0.0 - 74.125.255.255
    CIDR: 74.125.0.0/16
    OriginAS:
    NetName: GOOGLE
    NetHandle: NET-74-125-0-0-1
    Parent: NET-74-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2007-03-13
    Updated: 2012-02-24
    Ref: http://whois.arin.net/rest/net/NET-74-125-0-0-1


    OrgName: Google Inc.
    OrgId: GOGL
    Address: 1600 Amphitheatre Parkway
    City: Mountain View
    StateProv: CA
    PostalCode: 94043
    Country: US
    RegDate: 2000-03-30
    Updated: 2011-09-24
    Ref: http://whois.arin.net/rest/org/GOGL

    OrgTechHandle: ZG39-ARIN
    OrgTechName: Google Inc
    OrgTechPhone: +1-650-253-0000
    OrgTechEmail: arin-contact@google.com
    OrgTechRef: http://whois.arin.net/rest/poc/ZG39-ARIN

    OrgAbuseHandle: ZG39-ARIN
    OrgAbuseName: Google Inc
    OrgAbusePhone: +1-650-253-0000
    OrgAbuseEmail: arin-contact@google.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/ZG39-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
  • 162 Errors
  • 157 Warnings
Ratio Text/Html
  • 0.476315673677726
Message Error
  • Warning Line 5, Column 264: character "&" is the first character of a delimiter but occurred as data
    …ming={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.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 5, Column 266: cannot generate system identifier for general entity "a.performance.timing"
    …ng={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.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 5, Column 266: general entity "a.performance.timing" not defined and no default entity
    …ng={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.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 5, Column 286: reference not terminated by REFC delimiter
    …if(a.performance&&a.performance.timing){var g=a.performance.timing,j=a[b].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 5, Column 286: reference to entity "a.performance.timing" for which no system identifier could be generated
    …if(a.performance&&a.performance.timing){var g=a.performance.timing,j=a[b].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 5, Column 265: entity was defined here
    …ing={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.performan…
  • Error Line 5, Column 368: character "&" not allowed in attribute specification list
    ….navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("w…
  • Error Line 5, Column 368: element "k" undefined
    ….navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("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 5, Column 370: cannot generate system identifier for general entity "l"
    …avigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("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 5, Column 370: general entity "l" not defined and no default entity
    …avigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("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 5, Column 371: reference not terminated by REFC delimiter
    …vigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("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 5, Column 371: reference to entity "l" for which no system identifier could be generated
    …vigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("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 5, Column 369: entity was defined here
    …navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wt…
  • Warning Line 5, Column 374: character "&" is the first character of a delimiter but occurred as data
    …ationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("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 5, Column 375: character "&" is the first character of a delimiter but occurred as data
    …tionStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("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 6, Column 24: character "&" is the first character of a delimiter but occurred as data
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

    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 6, Column 26: cannot generate system identifier for general entity "a.chrome.csi"
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

    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 6, Column 26: general entity "a.chrome.csi" not defined and no default entity
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

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

  • Warning Line 6, Column 38: reference not terminated by REFC delimiter
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

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

  • Error Line 6, Column 38: reference to entity "a.chrome.csi" for which no system identifier could be generated
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

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

  • Info Line 6, Column 25: entity was defined here
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…
  • Warning Line 6, Column 38: character "&" is the first character of a delimiter but occurred as data
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

    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 6, Column 39: character "&" is the first character of a delimiter but occurred as data
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

    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 6, Column 77: character "&" is the first character of a delimiter but occurred as data
    …&(m=Math.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.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 6, Column 78: character "&" is the first character of a delimiter but occurred as data
    …(m=Math.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.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 6, Column 82: character "&" not allowed in attribute specification list
    …ath.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.chrome.csi().st…
  • Error Line 6, Column 82: element "k" undefined
    …ath.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.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 6, Column 83: character "&" is the first character of a delimiter but occurred as data
    …th.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.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 6, Column 161: character "&" is the first character of a delimiter but occurred as data
    …rtE),j[d]("tbnd_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT(…

    This message may appear in several cases:

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

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

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

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

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

  • Error Line 6, Column 163: general entity "a.gtbExternal" not defined and no default entity
    …E),j[d]("tbnd_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT())…

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

  • Warning Line 6, Column 176: reference not terminated by REFC delimiter
    …_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT());null==m&&a.e…

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

  • Error Line 6, Column 176: reference to entity "a.gtbExternal" for which no system identifier could be generated
    …_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT());null==m&&a.e…

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

  • Info Line 6, Column 162: entity was defined here
    …tE),j[d]("tbnd_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT()…
  • Warning Line 6, Column 176: character "&" is the first character of a delimiter but occurred as data
    …_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT());null==m&&a.e…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 6, Column 213: cannot generate system identifier for general entity "a.external"
    …l&&(m=a.gtbExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<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 6, Column 213: general entity "a.external" not defined and no default entity
    …l&&(m=a.gtbExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<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 6, Column 223: reference not terminated by REFC delimiter
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_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 6, Column 223: reference to entity "a.external" for which no system identifier could be generated
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_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 6, Column 212: entity was defined here
    …al&&(m=a.gtbExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&…
  • Warning Line 6, Column 223: character "&" is the first character of a delimiter but occurred as data
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_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 6, Column 224: character "&" is the first character of a delimiter but occurred as data
    …External.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_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 6, Column 246: character "&" is the first character of a delimiter but occurred as data
    …==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.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 6, Column 247: character "&" is the first character of a delimiter but occurred as data
    …=m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.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 6, Column 251: character "&" not allowed in attribute specification list
    …a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.external.startE…
  • Error Line 6, Column 251: element "k" undefined
    …a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.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 6, Column 252: character "&" is the first character of a delimiter but occurred as data
    ….external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.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 6, Column 320: character "&" is the first character of a delimiter but occurred as data
    …al.startE),j[d]("tbnd_","_tbnd",k)));m&&(a[b].pt=m)}catch(n){};a.tickAboveFold…

    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 6, Column 321: character "&" is the first character of a delimiter but occurred as data
    …l.startE),j[d]("tbnd_","_tbnd",k)));m&&(a[b].pt=m)}catch(n){};a.tickAboveFold=…

    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 6, Column 452: character "&" is the first character of a delimiter but occurred as data
    …Top;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!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 6, Column 454: cannot generate system identifier for general entity "a"
    …p;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r…

    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 6, Column 454: general entity "a" not defined and no default entity
    …p;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r…

    This is usually a cascading error caused by 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 6, Column 455: reference not terminated by REFC delimiter
    …;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r(…

    If you meant to include an entity that starts with "&", then you should terminate it 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 6, Column 455: reference to entity "a" for which no system identifier could be generated
    …;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r(…

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

  • Info Line 6, Column 453: entity was defined here
    …op;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function …
  • Error Line 7, Column 15: end tag for "k" 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 6, Column 249: start tag was here
    …&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.external.star…
  • Error Line 7, Column 15: end tag for "k" 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 6, Column 80: start tag was here
    …=Math.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.chrome.csi().…
  • Error Line 7, Column 15: end tag for "k" 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 5, Column 366: start tag was here
    …=g.navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d](…
  • Warning Line 34, Column 123: cannot generate system identifier for general entity "zx"
    ….css?targetBlogID=8641709788013651094&zx=2b00b5ce-e704-476f-8d27-12ac6035c685"…

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

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

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

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

  • Error Line 34, Column 123: general entity "zx" not defined and no default entity
    ….css?targetBlogID=8641709788013651094&zx=2b00b5ce-e704-476f-8d27-12ac6035c685"…

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

  • Warning Line 34, Column 125: reference not terminated by REFC delimiter
    …css?targetBlogID=8641709788013651094&zx=2b00b5ce-e704-476f-8d27-12ac6035c685"/>

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

  • Warning Line 34, Column 125: reference to external entity in attribute value
    …css?targetBlogID=8641709788013651094&zx=2b00b5ce-e704-476f-8d27-12ac6035c685"/>

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

  • Error Line 34, Column 125: reference to entity "zx" for which no system identifier could be generated
    …css?targetBlogID=8641709788013651094&zx=2b00b5ce-e704-476f-8d27-12ac6035c685"/>

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

  • Info Line 34, Column 122: entity was defined here
    …n.css?targetBlogID=8641709788013651094&zx=2b00b5ce-e704-476f-8d27-12ac6035c685…
  • Warning Line 35, Column 125: reference not terminated by REFC delimiter
    …css?targetBlogID=8641709788013651094&zx=2b00b5ce-e704-476f-8d27-12ac6035c685"/>

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

  • Warning Line 35, Column 125: reference to external entity in attribute value
    …css?targetBlogID=8641709788013651094&zx=2b00b5ce-e704-476f-8d27-12ac6035c685"/>

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

  • Error Line 35, Column 125: reference to entity "zx" for which no system identifier could be generated
    …css?targetBlogID=8641709788013651094&zx=2b00b5ce-e704-476f-8d27-12ac6035c685"/>

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

  • Info Line 34, Column 122: entity was defined here
    …n.css?targetBlogID=8641709788013651094&zx=2b00b5ce-e704-476f-8d27-12ac6035c685…
  • Warning Line 38, Column 5: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 38, Column 9: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 38, Column 13: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 38, Column 17: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 38, Column 21: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 38, Column 25: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 38, Column 29: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 38, Column 33: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 38, Column 37: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 38, Column 41: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 38, Column 45: multiple comments in comment declaration
    -----------------------------------------------
  • Error Line 38, Column 47: invalid comment declaration: found name character outside comment but inside comment declaration
    -----------------------------------------------
  • Info Line 36, Column 41: comment declaration started here
    <style id='page-skin-1' type='text/css'><!--
  • Error Line 945, Column 14: there is no attribute "type"
    <SCRIPT type='text/javascript'> var thumbnail_mode = "no-float" ; summary_noimg…

    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 945, Column 31: element "SCRIPT" undefined
    <SCRIPT type='text/javascript'> var thumbnail_mode = "no-float" ; summary_noimg…

    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 946, Column 13: there is no attribute "src"
    <SCRIPT src='http://yohoudini.googlecode.com/files/readmore.js' type='text/java…

    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 946, Column 87: element "SCRIPT" undefined
    …://yohoudini.googlecode.com/files/readmore.js' type='text/javascript'></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).
  • Warning Line 956, Column 78: cannot generate system identifier for general entity "m"
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function…

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

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

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

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

  • Error Line 956, Column 78: general entity "m" not defined and no default entity
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function…

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

  • Warning Line 956, Column 79: reference not terminated by REFC delimiter
    …igator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function …

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

  • Error Line 956, Column 79: reference to entity "m" for which no system identifier could be generated
    …igator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function …

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

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

  • Error Line 956, Column 395: general entity "window.location.replace" not defined and no default entity
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

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

  • Warning Line 956, Column 418: reference not terminated by REFC delimiter
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

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

  • Error Line 956, Column 418: reference to entity "window.location.replace" for which no system identifier could be generated
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

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

  • Info Line 956, Column 394: entity was defined here
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};
  • Error Line 972, Column 43: required attribute "type" not specified
    document.write('<script src="' + cual + '"><\/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 972, Column 43: document type does not allow element "script" here
    document.write('<script src="' + cual + '"><\/script>');

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

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

  • Warning Line 972, Column 44: character "<" is the first character of a delimiter but occurred as data
    document.write('<script src="' + cual + '"><\/script>');

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

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

  • Info Line 963, Column 1: start tag was here
    <script type="text/javascript">
  • Warning Line 979, Column 83: cannot generate system identifier for general entity "widgetType"
    …/rearrange?blogID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=ed…

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

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

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

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

  • Error Line 979, Column 83: general entity "widgetType" not defined and no default entity
    …/rearrange?blogID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=ed…

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

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

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

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

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

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

  • Error Line 979, Column 99: general entity "widgetId" not defined and no default entity
    …D=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=editWidget&section…

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

  • Warning Line 979, Column 107: reference not terminated by REFC delimiter
    …9788013651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=conte…

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

  • Warning Line 979, Column 107: reference to external entity in attribute value
    …9788013651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=conte…

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

  • Error Line 979, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …9788013651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=conte…

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

  • Info Line 979, Column 98: entity was defined here
    …ID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectio…
  • Warning Line 979, Column 114: cannot generate system identifier for general entity "action"
    …651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorSc…

    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 979, Column 114: general entity "action" not defined and no default entity
    …651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorSc…

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

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

  • Warning Line 979, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorScripts'…

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

  • Error Line 979, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorScripts'…

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

  • Info Line 979, Column 113: entity was defined here
    …3651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorS…
  • Warning Line 979, Column 132: cannot generate system identifier for general entity "sectionId"
    …HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorScripts' onclick='re…

    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 979, Column 132: general entity "sectionId" not defined and no default entity
    …HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorScripts' 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.

  • Warning Line 979, Column 141: reference not terminated by REFC delimiter
    …etId=HTML3&action=editWidget&sectionId=contenedorScripts' onclick='return _Wid…

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

  • Warning Line 979, Column 141: reference to external entity in attribute value
    …etId=HTML3&action=editWidget&sectionId=contenedorScripts' onclick='return _Wid…

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

  • Error Line 979, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML3&action=editWidget&sectionId=contenedorScripts' onclick='return _Wid…

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

  • Info Line 979, Column 131: entity was defined here
    …=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorScripts' onclick='r…
  • Error Line 979, Column 248: there is no attribute "target"
    …Config(document.getElementById("HTML3"));' target='configHTML3' title='Editar'>

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

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

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

  • Warning Line 1000, 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 1000, 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 1023, Column 43: document type does not allow element "span" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <span id='skiplinks' style='display:none;'>

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

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

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

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

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

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

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

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

  • Info Line 979, Column 82: entity was defined here
    …m/rearrange?blogID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=e…
  • Warning Line 1055, Column 107: reference not terminated by REFC delimiter
    …9788013651094&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=hbann…

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

  • Warning Line 1055, Column 107: reference to external entity in attribute value
    …9788013651094&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=hbann…

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

  • Error Line 1055, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …9788013651094&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=hbann…

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

  • Info Line 979, Column 98: entity was defined here
    …ID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectio…
  • Warning Line 1055, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=hbanner' 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 1055, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=hbanner' 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 1055, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=hbanner' 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 979, Column 113: entity was defined here
    …3651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorS…
  • Warning Line 1055, Column 141: reference not terminated by REFC delimiter
    …etId=HTML1&action=editWidget&sectionId=hbanner' 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 1055, Column 141: reference to external entity in attribute value
    …etId=HTML1&action=editWidget&sectionId=hbanner' 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 1055, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML1&action=editWidget&sectionId=hbanner' 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 979, Column 131: entity was defined here
    …=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorScripts' onclick='r…
  • Error Line 1064, Column 10: ID "navbar" already defined
    <div id='navbar'>

    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 986, Column 33: ID "navbar" first defined here
    <div class='navbar section' id='navbar'><div class='widget Navbar' id='Navbar1'…
  • Error Line 1066, Column 67: there is no attribute "border"
    …iciatv.com/'><img alt='Inicio' border='0' src='http://1.bp.blogspot.com/-Yx-Nu…

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

    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 1084, Column 10: ID "miku" first defined here
    <div id='miku'>
  • Error Line 1107, Column 10: ID "miku" already defined
    <div id='miku'>

    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 1084, Column 10: ID "miku" first defined here
    <div id='miku'>
  • Error Line 1120, Column 10: ID "miku" already defined
    <div id='miku'>

    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 1084, Column 10: ID "miku" first defined here
    <div id='miku'>
  • Error Line 1133, Column 10: ID "miku" already defined
    <div id='miku' style='width:184px;'>

    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 1084, Column 10: ID "miku" first defined here
    <div id='miku'>
  • Error Line 1149, Column 10: ID "miku" already defined
    <div id='miku'>

    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 1084, Column 10: ID "miku" first defined here
    <div id='miku'>
  • Error Line 1153, Column 10: ID "miku" already defined
    <div id='miku'>

    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 1084, Column 10: ID "miku" first defined here
    <div id='miku'>
  • Error Line 1159, Column 10: ID "miku" already defined
    <div id='miku'>

    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 1084, Column 10: ID "miku" first defined here
    <div id='miku'>
  • Error Line 1164, Column 10: ID "miku" already defined
    <div id='miku'>

    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 1084, Column 10: ID "miku" first defined here
    <div id='miku'>
  • Error Line 1169, Column 10: ID "miku" already defined
    <div id='miku'>

    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 1084, Column 10: ID "miku" first defined here
    <div id='miku'>
  • Error Line 1228, Column 9: there is no attribute "id"
    <DIV id='summary8102678804715205295'><p><img border="0" alt="La Vida De Pi" src…

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

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

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

  • Error Line 1228, Column 37: element "DIV" undefined
    <DIV id='summary8102678804715205295'><p><img border="0" alt="La Vida De Pi" src…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1228, Column 224: end tag for "img" omitted, but OMITTAG NO was specified
    …sor:hand;width: 120px; height: 90px;"> <strong>Life of Pi (La Vida De Pi)</str…

    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 1228, Column 41: start tag was here
    …IV id='summary8102678804715205295'><p><img border="0" alt="La Vida De Pi" src=…
  • Error Line 1237, Column 8: element "center" undefined
    <center><iframe width="520" height="315" src="http://www.youtube.com/embed/veIP…

    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 1237, Column 23: there is no attribute "width"
    <center><iframe width="520" height="315" src="http://www.youtube.com/embed/veIP…

    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 1237, Column 36: there is no attribute "height"
    <center><iframe width="520" height="315" src="http://www.youtube.com/embed/veIP…

    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 1237, Column 46: there is no attribute "src"
    …><iframe width="520" height="315" src="http://www.youtube.com/embed/veIPItzgRI…

    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 1237, Column 113: there is no attribute "frameborder"
    …/veIPItzgRI8?theme=light" frameborder="0" allowfullscreen></iframe><br/><br/>O…

    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 1237, Column 132: "allowfullscreen" is not a member of a group specified for any attribute
    …light" frameborder="0" allowfullscreen></iframe><br/><br/>Once Nominaciones  <…
  • Error Line 1237, Column 132: element "iframe" undefined
    …light" frameborder="0" allowfullscreen></iframe><br/><br/>Once Nominaciones  <…

    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 1237, Column 304: "allowfullscreen" is not a member of a group specified for any attribute
    …light" frameborder="0" allowfullscreen></iframe><br/><br/>Life of Pi (La Vida …
  • Error Line 1237, Column 304: element "iframe" undefined
    …light" frameborder="0" allowfullscreen></iframe><br/><br/>Life of Pi (La Vida …

    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 1240, Column 31: element "SCRIPT" undefined
    <SCRIPT type='text/javascript'>createSummaryAndThumb("summary810267880471520529…

    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 1272, Column 37: element "DIV" undefined
    <DIV id='summary4585612233018875462'><p><img border="0" alt="Argo" src="http://…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1272, Column 215: end tag for "img" omitted, but OMITTAG NO was specified
    …sor:hand;width: 120px; height: 90px;"><strong>Argo Película</strong> nominada …

    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 1272, Column 41: start tag was here
    …IV id='summary4585612233018875462'><p><img border="0" alt="Argo" src="http://i…
  • Error Line 1279, Column 8: element "center" undefined
    <center><iframe width="520" height="315" src="http://www.youtube.com/embed/ieGA…

    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 1279, Column 132: "allowfullscreen" is not a member of a group specified for any attribute
    …light" frameborder="0" allowfullscreen></iframe><br/><br/>Argo Película (Opini…
  • Error Line 1279, Column 132: element "iframe" undefined
    …light" frameborder="0" allowfullscreen></iframe><br/><br/>Argo Película (Opini…

    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 1281, Column 31: element "SCRIPT" undefined
    <SCRIPT type='text/javascript'>createSummaryAndThumb("summary458561223301887546…

    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 1311, Column 37: element "DIV" undefined
    <DIV id='summary8040992678613010957'><p><img border="0" alt="Zero Dark Thirty" …

    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 1311, Column 227: end tag for "img" omitted, but OMITTAG NO was specified
    …sor:hand;width: 120px; height: 90px;"><strong>Zero Dark Thirty (La Noche Mas O…

    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 1311, Column 41: start tag was here
    …IV id='summary8040992678613010957'><p><img border="0" alt="Zero Dark Thirty" s…
  • Error Line 1315, Column 8: element "center" undefined
    <center><iframe width="520" height="315" src="http://www.youtube.com/embed/uP6b…

    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 1315, Column 132: "allowfullscreen" is not a member of a group specified for any attribute
    …light" frameborder="0" allowfullscreen></iframe><br/><br/>Zero Dark Thirty (La…
  • Error Line 1315, Column 132: element "iframe" undefined
    …light" frameborder="0" allowfullscreen></iframe><br/><br/>Zero Dark Thirty (La…

    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 1317, Column 31: element "SCRIPT" undefined
    <SCRIPT type='text/javascript'>createSummaryAndThumb("summary804099267861301095…

    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 1346, Column 36: element "DIV" undefined
    <DIV id='summary842072921915102609'><p><img  style="clear:left; float:left;marg…

    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 1346, Column 265: required attribute "alt" not specified
    …s200/pasion-prohibida-telemundo.jpg" /> Ver Pasión Prohibida Capitulo 22, una …

    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 1352, Column 8: element "center" undefined
    <center><object width="500" height="340" type="application/x-shockwave-flash" d…

    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 1352, Column 246: end tag for "param" omitted, but OMITTAG NO was specified
    …er_flv_multi-fcde75.swf" name="movie"><param value="true" name="allowFullScree…

    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 1352, Column 152: start tag was here
    …es/f/4/b/player_flv_multi-fcde75.swf"><param value="http://img44.xooimage.com/…
  • Error Line 1352, Column 289: end tag for "param" omitted, but OMITTAG NO was specified
    …m value="true" name="allowFullScreen"><param value="flv=http://store43.media43…

    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 1352, Column 246: start tag was here
    …er_flv_multi-fcde75.swf" name="movie"><param value="true" name="allowFullScree…
  • Error Line 1352, Column 1075: end tag for "param" omitted, but OMITTAG NO was specified
    …1=000000&amp;bgcolor2=000000&amp;playercolor=666666" name="FlashVars"></object>

    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 1352, Column 289: start tag was here
    …m value="true" name="allowFullScreen"><param value="flv=http://store43.media43…
  • Error Line 1355, Column 31: element "SCRIPT" undefined
    <SCRIPT type='text/javascript'>createSummaryAndThumb("summary842072921915102609…

    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 1385, Column 36: element "DIV" undefined
    <DIV id='summary367260655720224352'><p><img style="float:left; margin:0 10px 10…

    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 1390, Column 8: element "center" undefined
    <center><object width="500" height="340" type="application/x-shockwave-flash" d…

    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 1390, Column 246: end tag for "param" omitted, but OMITTAG NO was specified
    …er_flv_multi-fcde75.swf" name="movie"><param value="true" name="allowFullScree…

    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 152: start tag was here
    …es/f/4/b/player_flv_multi-fcde75.swf"><param value="http://img44.xooimage.com/…
  • Error Line 1390, Column 289: end tag for "param" omitted, but OMITTAG NO was specified
    …m value="true" name="allowFullScreen"><param value="flv=http://store33.media33…

    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 246: start tag was here
    …er_flv_multi-fcde75.swf" name="movie"><param value="true" name="allowFullScree…
  • Error Line 1390, Column 897: end tag for "param" omitted, but OMITTAG NO was specified
    …playercolor=666666" name="FlashVars"></object><br /><br /> Opción 2<br /><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 289: start tag was here
    …m value="true" name="allowFullScreen"><param value="flv=http://store33.media33…
  • Error Line 1391, Column 152: "allowfullscreen" is not a member of a group specified for any attribute
    …Vm3FC" frameborder="0" allowfullscreen></iframe><br/><br/>Ver Amores verdadero…
  • Error Line 1391, Column 152: element "iframe" undefined
    …Vm3FC" frameborder="0" allowfullscreen></iframe><br/><br/>Ver Amores verdadero…

    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 1393, Column 31: element "SCRIPT" undefined
    <SCRIPT type='text/javascript'>createSummaryAndThumb("summary367260655720224352…

    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 1422, Column 37: element "DIV" undefined
    <DIV id='summary8498565983584442622'><p><img style="clear:left; float:left;marg…

    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 1422, Column 53: literal is missing closing delimiter
    …ry8498565983584442622'><p><img style="clear:left; float:left;margin-right:1em;…

    Did you forget to close a (double) quote mark?

  • Error Line 1422, Column 103: end tag for "img" omitted, but OMITTAG NO was specified
    …float:left;margin-right:1em; border="0" height="89" width="180" src="http://1.…

    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 1422, Column 41: start tag was here
    …IV id='summary8498565983584442622'><p><img style="clear:left; float:left;margi…
  • Error Line 1428, Column 8: element "center" undefined
    <center><iframe frameborder="0" width="520" height="320" src="http://www.dailym…

    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 1428, Column 116: cannot generate system identifier for general entity "forcedQuality"
    …ttp://www.dailymotion.com/embed/video/xxnur2?logo=0&forcedQuality=sd"></iframe>

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

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

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

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

  • Error Line 1428, Column 116: general entity "forcedQuality" not defined and no default entity
    …ttp://www.dailymotion.com/embed/video/xxnur2?logo=0&forcedQuality=sd"></iframe>

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

  • Warning Line 1428, Column 129: reference not terminated by REFC delimiter
    …ttp://www.dailymotion.com/embed/video/xxnur2?logo=0&forcedQuality=sd"></iframe>

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

  • Warning Line 1428, Column 129: reference to external entity in attribute value
    …ttp://www.dailymotion.com/embed/video/xxnur2?logo=0&forcedQuality=sd"></iframe>

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

  • Error Line 1428, Column 129: reference to entity "forcedQuality" for which no system identifier could be generated
    …ttp://www.dailymotion.com/embed/video/xxnur2?logo=0&forcedQuality=sd"></iframe>

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

  • Info Line 1428, Column 115: entity was defined here
    …ttp://www.dailymotion.com/embed/video/xxnur2?logo=0&forcedQuality=sd"></iframe>
  • Error Line 1428, Column 133: element "iframe" undefined
    …ttp://www.dailymotion.com/embed/video/xxnur2?logo=0&forcedQuality=sd"></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 1429, Column 153: "allowfullscreen" is not a member of a group specified for any attribute
    …be.com/embed/KUIwto2MfFk?theme=light" frameborder="0" allowfullscreen></iframe>
  • Error Line 1429, Column 153: element "iframe" undefined
    …be.com/embed/KUIwto2MfFk?theme=light" frameborder="0" allowfullscreen></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 1433, Column 31: element "SCRIPT" undefined
    <SCRIPT type='text/javascript'>createSummaryAndThumb("summary849856598358444262…

    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 1460, Column 33: there is no attribute "data-height"
    <div class="g-plus" data-height="69" data-href="https://plus.google.com/1043813…

    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 1460, Column 48: there is no attribute "data-href"
    …s="g-plus" data-height="69" data-href="https://plus.google.com/104381302495341…

    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 1460, Column 105: there is no attribute "data-rel"
    …e.com/104381302495341208651" data-rel="publisher"></div><form onsubmit="window…

    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 1460, Column 288: there is no attribute "target"
    …=550,height=520');return true" target="popupwindow" method="post" action="http…

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

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

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

  • Error Line 1460, Column 575: 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
    …idden" name="uri" value="PrimiciaTv" /><input type="hidden" value="es_ES" name…

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

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

  • Error Line 1460, Column 623: 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
    …pe="hidden" value="es_ES" name="loc" /><input type="submit" value="Subscribir"…

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

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

  • Error Line 1460, Column 665: 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
    …put type="submit" value="Subscribir" /></form><br/><br/><center><iframe scroll…

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

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

  • Error Line 1460, Column 690: element "center" undefined
    …Subscribir" /></form><br/><br/><center><iframe scrolling="no" frameborder="0" …

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

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

    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 1460, Column 748: there is no attribute "allowtransparency"
    …no" frameborder="0" allowtransparency="true" style="border:none; overflow:hidd…

    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 1460, Column 761: there is no attribute "style"
    …er="0" allowtransparency="true" style="border:none; overflow:hidden; width:300…

    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 1460, Column 1065: element "iframe" undefined
    …false&amp;header=false&amp;height=252"></iframe></center><center><a href="http…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1460, Column 1091: element "center" undefined
    …;height=252"></iframe></center><center><a href="https://twitter.com/primiciatv…

    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 1460, Column 1180: there is no attribute "data-show-count"
    …witter-follow-button" data-show-count="false" data-lang="es" data-size="large"…

    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 1460, Column 1198: there is no attribute "data-lang"
    …on" data-show-count="false" data-lang="es" data-size="large">Seguir a @primici…

    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 1460, Column 1213: there is no attribute "data-size"
    …a-show-count="false" data-lang="es" data-size="large">Seguir a @primiciatv_</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 1461, 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>.

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

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

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

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

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

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

  • Info Line 979, Column 82: entity was defined here
    …m/rearrange?blogID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=e…
  • Warning Line 1466, Column 107: reference not terminated by REFC delimiter
    …9788013651094&widgetType=HTML&widgetId=HTML2&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 1466, Column 107: reference to external entity in attribute value
    …9788013651094&widgetType=HTML&widgetId=HTML2&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 1466, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …9788013651094&widgetType=HTML&widgetId=HTML2&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 979, Column 98: entity was defined here
    …ID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectio…
  • Warning Line 1466, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=sidebar-ads' oncli…

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

  • Warning Line 1466, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=sidebar-ads' oncli…

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

  • Error Line 1466, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=sidebar-ads' oncli…

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

  • Info Line 979, Column 113: entity was defined here
    …3651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorS…
  • Warning Line 1466, Column 141: reference not terminated by REFC delimiter
    …etId=HTML2&action=editWidget&sectionId=sidebar-ads' onclick='return _WidgetMan…

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

  • Warning Line 1466, Column 141: reference to external entity in attribute value
    …etId=HTML2&action=editWidget&sectionId=sidebar-ads' onclick='return _WidgetMan…

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

  • Error Line 1466, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML2&action=editWidget&sectionId=sidebar-ads' onclick='return _WidgetMan…

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

  • Info Line 979, Column 131: entity was defined here
    …=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorScripts' onclick='r…
  • Warning Line 1485, Column 93: reference not terminated by REFC delimiter
    …?blogID=8641709788013651094&widgetType=LinkList&widgetId=LinkList4&action=edit…

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

  • Warning Line 1485, Column 93: reference to external entity in attribute value
    …?blogID=8641709788013651094&widgetType=LinkList&widgetId=LinkList4&action=edit…

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

  • Error Line 1485, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8641709788013651094&widgetType=LinkList&widgetId=LinkList4&action=edit…

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

  • Info Line 979, Column 82: entity was defined here
    …m/rearrange?blogID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=e…
  • Warning Line 1485, Column 111: reference not terminated by REFC delimiter
    …013651094&widgetType=LinkList&widgetId=LinkList4&action=editWidget&sectionId=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 1485, Column 111: reference to external entity in attribute value
    …013651094&widgetType=LinkList&widgetId=LinkList4&action=editWidget&sectionId=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 1485, Column 111: reference to entity "widgetId" for which no system identifier could be generated
    …013651094&widgetType=LinkList&widgetId=LinkList4&action=editWidget&sectionId=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 979, Column 98: entity was defined here
    …ID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectio…
  • Warning Line 1485, Column 128: reference not terminated by REFC delimiter
    …ype=LinkList&widgetId=LinkList4&action=editWidget&sectionId=sidebar-ads' oncli…

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

  • Warning Line 1485, Column 128: reference to external entity in attribute value
    …ype=LinkList&widgetId=LinkList4&action=editWidget&sectionId=sidebar-ads' oncli…

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

  • Error Line 1485, Column 128: reference to entity "action" for which no system identifier could be generated
    …ype=LinkList&widgetId=LinkList4&action=editWidget&sectionId=sidebar-ads' oncli…

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

  • Info Line 979, Column 113: entity was defined here
    …3651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorS…
  • Warning Line 1485, Column 149: reference not terminated by REFC delimiter
    …=LinkList4&action=editWidget&sectionId=sidebar-ads' onclick='return _WidgetMan…

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

  • Warning Line 1485, Column 149: reference to external entity in attribute value
    …=LinkList4&action=editWidget&sectionId=sidebar-ads' onclick='return _WidgetMan…

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

  • Error Line 1485, Column 149: reference to entity "sectionId" for which no system identifier could be generated
    …=LinkList4&action=editWidget&sectionId=sidebar-ads' onclick='return _WidgetMan…

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

  • Info Line 979, Column 131: entity was defined here
    …=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorScripts' onclick='r…
  • Warning Line 1502, Column 93: reference not terminated by REFC delimiter
    …?blogID=8641709788013651094&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 1502, Column 93: reference to external entity in attribute value
    …?blogID=8641709788013651094&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 1502, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8641709788013651094&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 979, Column 82: entity was defined here
    …m/rearrange?blogID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=e…
  • Warning Line 1502, Column 107: reference not terminated by REFC delimiter
    …9788013651094&widgetType=Feed&widgetId=Feed1&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 1502, Column 107: reference to external entity in attribute value
    …9788013651094&widgetType=Feed&widgetId=Feed1&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 1502, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …9788013651094&widgetType=Feed&widgetId=Feed1&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 979, Column 98: entity was defined here
    …ID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectio…
  • Warning Line 1502, Column 120: reference not terminated by REFC delimiter
    …&widgetType=Feed&widgetId=Feed1&action=editWidget&sectionId=sidebar-ads' oncli…

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

  • Warning Line 1502, Column 120: reference to external entity in attribute value
    …&widgetType=Feed&widgetId=Feed1&action=editWidget&sectionId=sidebar-ads' oncli…

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

  • Error Line 1502, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=Feed&widgetId=Feed1&action=editWidget&sectionId=sidebar-ads' oncli…

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

  • Info Line 979, Column 113: entity was defined here
    …3651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorS…
  • Warning Line 1502, Column 141: reference not terminated by REFC delimiter
    …etId=Feed1&action=editWidget&sectionId=sidebar-ads' onclick='return _WidgetMan…

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

  • Warning Line 1502, Column 141: reference to external entity in attribute value
    …etId=Feed1&action=editWidget&sectionId=sidebar-ads' onclick='return _WidgetMan…

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

  • Error Line 1502, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=Feed1&action=editWidget&sectionId=sidebar-ads' onclick='return _WidgetMan…

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

  • Info Line 979, Column 131: entity was defined here
    …=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorScripts' onclick='r…
  • Warning Line 1535, Column 93: reference not terminated by REFC delimiter
    …?blogID=8641709788013651094&widgetType=LinkList&widgetId=LinkList1&action=edit…

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

  • Warning Line 1535, Column 93: reference to external entity in attribute value
    …?blogID=8641709788013651094&widgetType=LinkList&widgetId=LinkList1&action=edit…

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

  • Error Line 1535, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8641709788013651094&widgetType=LinkList&widgetId=LinkList1&action=edit…

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

  • Info Line 979, Column 82: entity was defined here
    …m/rearrange?blogID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=e…
  • Warning Line 1535, Column 111: reference not terminated by REFC delimiter
    …013651094&widgetType=LinkList&widgetId=LinkList1&action=editWidget&sectionId=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 1535, Column 111: reference to external entity in attribute value
    …013651094&widgetType=LinkList&widgetId=LinkList1&action=editWidget&sectionId=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 1535, Column 111: reference to entity "widgetId" for which no system identifier could be generated
    …013651094&widgetType=LinkList&widgetId=LinkList1&action=editWidget&sectionId=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 979, Column 98: entity was defined here
    …ID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectio…
  • Warning Line 1535, Column 128: reference not terminated by REFC delimiter
    …ype=LinkList&widgetId=LinkList1&action=editWidget&sectionId=sidebar-top' oncli…

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

  • Warning Line 1535, Column 128: reference to external entity in attribute value
    …ype=LinkList&widgetId=LinkList1&action=editWidget&sectionId=sidebar-top' oncli…

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

  • Error Line 1535, Column 128: reference to entity "action" for which no system identifier could be generated
    …ype=LinkList&widgetId=LinkList1&action=editWidget&sectionId=sidebar-top' oncli…

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

  • Info Line 979, Column 113: entity was defined here
    …3651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorS…
  • Warning Line 1535, Column 149: reference not terminated by REFC delimiter
    …=LinkList1&action=editWidget&sectionId=sidebar-top' onclick='return _WidgetMan…

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

  • Warning Line 1535, Column 149: reference to external entity in attribute value
    …=LinkList1&action=editWidget&sectionId=sidebar-top' onclick='return _WidgetMan…

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

  • Error Line 1535, Column 149: reference to entity "sectionId" for which no system identifier could be generated
    …=LinkList1&action=editWidget&sectionId=sidebar-top' onclick='return _WidgetMan…

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

  • Info Line 979, Column 131: entity was defined here
    …=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorScripts' onclick='r…
  • Warning Line 1562, Column 93: reference not terminated by REFC delimiter
    …?blogID=8641709788013651094&widgetType=LinkList&widgetId=LinkList2&action=edit…

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

  • Warning Line 1562, Column 93: reference to external entity in attribute value
    …?blogID=8641709788013651094&widgetType=LinkList&widgetId=LinkList2&action=edit…

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

  • Error Line 1562, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8641709788013651094&widgetType=LinkList&widgetId=LinkList2&action=edit…

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

  • Info Line 979, Column 82: entity was defined here
    …m/rearrange?blogID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=e…
  • Warning Line 1562, Column 111: reference not terminated by REFC delimiter
    …013651094&widgetType=LinkList&widgetId=LinkList2&action=editWidget&sectionId=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 1562, Column 111: reference to external entity in attribute value
    …013651094&widgetType=LinkList&widgetId=LinkList2&action=editWidget&sectionId=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 1562, Column 111: reference to entity "widgetId" for which no system identifier could be generated
    …013651094&widgetType=LinkList&widgetId=LinkList2&action=editWidget&sectionId=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 979, Column 98: entity was defined here
    …ID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectio…
  • Warning Line 1562, Column 128: reference not terminated by REFC delimiter
    …ype=LinkList&widgetId=LinkList2&action=editWidget&sectionId=sidebar-top' oncli…

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

  • Warning Line 1562, Column 128: reference to external entity in attribute value
    …ype=LinkList&widgetId=LinkList2&action=editWidget&sectionId=sidebar-top' oncli…

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

  • Error Line 1562, Column 128: reference to entity "action" for which no system identifier could be generated
    …ype=LinkList&widgetId=LinkList2&action=editWidget&sectionId=sidebar-top' oncli…

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

  • Info Line 979, Column 113: entity was defined here
    …3651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorS…
  • Warning Line 1562, Column 149: reference not terminated by REFC delimiter
    …=LinkList2&action=editWidget&sectionId=sidebar-top' onclick='return _WidgetMan…

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

  • Warning Line 1562, Column 149: reference to external entity in attribute value
    …=LinkList2&action=editWidget&sectionId=sidebar-top' onclick='return _WidgetMan…

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

  • Error Line 1562, Column 149: reference to entity "sectionId" for which no system identifier could be generated
    …=LinkList2&action=editWidget&sectionId=sidebar-top' onclick='return _WidgetMan…

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

  • Info Line 979, Column 131: entity was defined here
    …=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorScripts' onclick='r…
  • Warning Line 1604, Column 93: reference not terminated by REFC delimiter
    …?blogID=8641709788013651094&widgetType=LinkList&widgetId=LinkList3&action=edit…

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

  • Warning Line 1604, Column 93: reference to external entity in attribute value
    …?blogID=8641709788013651094&widgetType=LinkList&widgetId=LinkList3&action=edit…

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

  • Error Line 1604, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8641709788013651094&widgetType=LinkList&widgetId=LinkList3&action=edit…

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

  • Info Line 979, Column 82: entity was defined here
    …m/rearrange?blogID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=e…
  • Warning Line 1604, Column 111: reference not terminated by REFC delimiter
    …013651094&widgetType=LinkList&widgetId=LinkList3&action=editWidget&sectionId=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 1604, Column 111: reference to external entity in attribute value
    …013651094&widgetType=LinkList&widgetId=LinkList3&action=editWidget&sectionId=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 1604, Column 111: reference to entity "widgetId" for which no system identifier could be generated
    …013651094&widgetType=LinkList&widgetId=LinkList3&action=editWidget&sectionId=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 979, Column 98: entity was defined here
    …ID=8641709788013651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectio…
  • Warning Line 1604, Column 128: reference not terminated by REFC delimiter
    …ype=LinkList&widgetId=LinkList3&action=editWidget&sectionId=sidebar-bottom' on…

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

  • Warning Line 1604, Column 128: reference to external entity in attribute value
    …ype=LinkList&widgetId=LinkList3&action=editWidget&sectionId=sidebar-bottom' on…

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

  • Error Line 1604, Column 128: reference to entity "action" for which no system identifier could be generated
    …ype=LinkList&widgetId=LinkList3&action=editWidget&sectionId=sidebar-bottom' on…

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

  • Info Line 979, Column 113: entity was defined here
    …3651094&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorS…
  • Warning Line 1604, Column 149: reference not terminated by REFC delimiter
    …=LinkList3&action=editWidget&sectionId=sidebar-bottom' onclick='return _Widget…

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

  • Warning Line 1604, Column 149: reference to external entity in attribute value
    …=LinkList3&action=editWidget&sectionId=sidebar-bottom' onclick='return _Widget…

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

  • Error Line 1604, Column 149: reference to entity "sectionId" for which no system identifier could be generated
    …=LinkList3&action=editWidget&sectionId=sidebar-bottom' onclick='return _Widget…

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

  • Info Line 979, Column 131: entity was defined here
    …=HTML&widgetId=HTML3&action=editWidget&sectionId=contenedorScripts' onclick='r…
  • Warning Line 1647, 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 1647, 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
  • 1.983 visits