En tusnovelas.net podras ver telenovelas actuales, telenovelas online gratis, telenovelas completas, ver novelas 2014 completas ...

tusnovelas.net
  • Domain Name
    tusnovelas.net
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #42321
  • Page Size
    38.5 KB
  • Ip Address
    37.58.81.245
  • Heading
    H1: 0, H2: 0, H3: 1, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 60 JPG, 2 PNG

Website Meta Analysis

  • Title
    telenovelas online, novelas online gratis, telenovelas completas
  • Meta Keyword
    telenovelas completas gratis, telenovelas online gratis, ver novelas actuales gratis.
  • Meta Description
    En tusnovelas.net podras ver telenovelas actuales, telenovelas online gratis, telenovelas completas, ver novelas 2014 completas

Technical Analysis

  • Webserver
    Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • Ip Address
    37.58.81.245
  • Domain Age
    2 Years, 9 Months, 16 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 06 Oct 2013 04:01:11 GMT
  • server: Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • x-powered-by: PHP/5.2.17
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for tusnovelas.net

DNS Analysis


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


DNS Records

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

Authority records

Additional records

IP 37.58.81.245 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 280 Errors
  • 65 Warnings
Ratio Text/Html
  • 0.8091442207610875
Message Error
  • Warning Line 7, 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 7, 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 7, 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 7, 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 7, 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 7, Column 265: entity was defined here
    …ing={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.performan…
  • Error Line 7, 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 7, 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 7, 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 7, 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 7, 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 7, 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 7, 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 7, 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 7, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, Column 162: entity was defined here
    …tE),j[d]("tbnd_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT()…
  • Warning Line 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, Column 212: entity was defined here
    …al&&(m=a.gtbExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&…
  • Warning Line 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 8, 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 9, 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 8, 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 9, 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 8, 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 9, 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 7, 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 35, Column 123: cannot generate system identifier for general entity "zx"
    ….css?targetBlogID=2582738190149103955&zx=5bf13b13-2d45-4b72-943a-26c22f09a4c7"…

    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 35, Column 123: general entity "zx" not defined and no default entity
    ….css?targetBlogID=2582738190149103955&zx=5bf13b13-2d45-4b72-943a-26c22f09a4c7"…

    This is usually a cascading error caused by 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 35, Column 125: reference not terminated by REFC delimiter
    …css?targetBlogID=2582738190149103955&zx=5bf13b13-2d45-4b72-943a-26c22f09a4c7"/>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another 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=2582738190149103955&zx=5bf13b13-2d45-4b72-943a-26c22f09a4c7"/>

    This is generally the sign of an ampersand that was not 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=2582738190149103955&zx=5bf13b13-2d45-4b72-943a-26c22f09a4c7"/>

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

  • Info Line 35, Column 122: entity was defined here
    …n.css?targetBlogID=2582738190149103955&zx=5bf13b13-2d45-4b72-943a-26c22f09a4c7…
  • Warning Line 37, Column 8: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 37, Column 12: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 37, Column 16: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 37, Column 20: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 37, Column 24: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 37, Column 28: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 37, Column 32: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 37, Column 36: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 37, Column 40: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 37, Column 44: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 37, Column 48: multiple comments in comment declaration
    /* -----------------------------------------------
  • Error Line 37, Column 50: 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 46, Column 16: there is no attribute "name"
    <Variable name="bgcolor" description="Page Background Color"

    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 46, Column 38: there is no attribute "description"
    <Variable name="bgcolor" description="Page Background Color"

    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 47, Column 6: there is no attribute "type"
    type="color" default="#fff">

    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 47, Column 22: there is no attribute "default"
    type="color" default="#fff">

    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 47, Column 28: element "Variable" undefined
    type="color" default="#fff">

    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 49, Column 28: element "Variable" undefined
    type="color" default="#222">

    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 51, Column 28: element "Variable" undefined
    type="color" default="#58a">

    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 53, Column 28: element "Variable" undefined
    type="color" default="#666">

    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 55, Column 28: element "Variable" undefined
    type="color" default="#999">

    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 57, Column 28: element "Variable" undefined
    type="color" default="#ddd">

    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 59, Column 28: element "Variable" undefined
    type="color" default="#ccc">

    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 61, Column 28: element "Variable" undefined
    type="color" default="#999">

    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 63, Column 28: element "Variable" undefined
    type="color" default="#666">

    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 65, Column 28: element "Variable" undefined
    type="color" default="#999">

    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 67, Column 56: element "Variable" undefined
    type="font" default="normal normal 100% Georgia, Serif">

    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 70, Column 78: element "Variable" undefined
    default="normal normal 78% 'Trebuchet MS',Trebuchet,Arial,Verdana,Sans-serif">

    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 73, Column 44: element "Variable" undefined
    default="normal normal 200% Georgia, Serif">

    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 76, Column 82: element "Variable" undefined
    …ault="normal normal 78% 'Trebuchet MS', Trebuchet, Arial, Verdana, Sans-serif">

    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 79, Column 82: element "Variable" undefined
    …ault="normal normal 78% 'Trebuchet MS', Trebuchet, Arial, Verdana, Sans-serif">

    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 81, Column 32: element "Variable" undefined
    type="automatic" default="left">

    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 83, Column 33: element "Variable" undefined
    type="automatic" default="right">

    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 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 82, Column 1: start tag was here
    <Variable name="endSide" description="Side where text ends in blog language"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 80, Column 1: start tag was here
    <Variable name="startSide" description="Side where text starts in blog language"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 77, Column 1: start tag was here
    <Variable name="postfooterfont" description="Post Footer Font"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 74, Column 1: start tag was here
    <Variable name="descriptionfont" description="Blog Description Font"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 71, Column 1: start tag was here
    <Variable name="pagetitlefont" description="Blog Title Font"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 68, Column 1: start tag was here
    <Variable name="headerfont" description="Sidebar Title Font"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 66, Column 1: start tag was here
    <Variable name="bodyfont" description="Text Font"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 64, Column 1: start tag was here
    <Variable name="visitedlinkcolor" description="Visited Link Color"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 62, Column 1: start tag was here
    <Variable name="sidebartextcolor" description="Sidebar Text Color"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 60, Column 1: start tag was here
    <Variable name="sidebarcolor" description="Sidebar Title Color"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 58, Column 1: start tag was here
    <Variable name="bordercolor" description="Border Color"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 56, Column 1: start tag was here
    <Variable name="titlecolor" description="Post Title Color"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 54, Column 1: start tag was here
    <Variable name="descriptioncolor" description="Blog Description Color"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 52, Column 1: start tag was here
    <Variable name="pagetitlecolor" description="Blog Title Color"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 50, Column 1: start tag was here
    <Variable name="linkcolor" description="Link Color"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 48, Column 1: start tag was here
    <Variable name="textcolor" description="Text Color"
  • Error Line 463, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 46, Column 1: start tag was here
    <Variable name="bgcolor" description="Page Background Color"
  • Error Line 464, Column 7: required attribute "type" not specified
    <style>

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

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

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

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

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

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

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

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

    If you meant to include an entity that starts with "&", then you should terminate it 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 511, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/es_LA/all.js#xfbml=1&appId=234304923326283";

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

  • Info Line 511, Column 56: entity was defined here
      js.src = "//connect.facebook.net/es_LA/all.js#xfbml=1&appId=234304923326283";
  • Error Line 528, Column 44: there is no attribute "name"
    …id="infolinks" class="infolinks" name="infolinks"><input type="hidden" name="I…

    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 558, Column 10: ID "infolinks" already defined
    <div id="infolinks" class="infolinks" name="infolinks"><input type="hidden" nam…

    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 528, Column 10: ID "infolinks" first defined here
    <div id="infolinks" class="infolinks" name="infolinks"><input type="hidden" nam…
  • Error Line 561, Column 8: element "center" undefined
    <center>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 562, Column 109: there is no attribute "target"
    …elevision-canal-4-en-vivo.html' target='_blank' title='Ver America television'>

    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 563, Column 42: there is no attribute "border"
    …g alt='Ver America Television' border='0px' height='100px' src='http://novelas…

    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 589, Column 10: ID "infolinks" already defined
    <div id="infolinks" class="infolinks" name="infolinks"><input type="hidden" nam…

    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 528, Column 10: ID "infolinks" first defined here
    <div id="infolinks" class="infolinks" name="infolinks"><input type="hidden" nam…
  • Error Line 596, 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>").

  • Error Line 618, Column 18: there is no attribute "language"
    <script language="JavaScript">

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

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

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

  • Error Line 618, Column 30: required attribute "type" not specified
    <script language="JavaScript">

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

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

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

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

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

  • Warning Line 631, Column 83: cannot generate system identifier for general entity "widgetType"
    …/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=e…

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

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

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

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

  • Error Line 631, Column 83: general entity "widgetType" not defined and no default entity
    …/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=e…

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

  • Warning Line 631, Column 93: reference not terminated by REFC delimiter
    …?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&…

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

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

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

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

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

  • Info Line 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 631, Column 99: cannot generate system identifier for general entity "widgetId"
    …D=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectio…

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

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

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

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

  • Error Line 631, Column 99: general entity "widgetId" not defined and no default entity
    …D=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectio…

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

  • Warning Line 631, Column 107: reference not terminated by REFC delimiter
    …8190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main…

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

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

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

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

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

  • Info Line 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 631, Column 115: cannot generate system identifier for general entity "action"
    …03955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclic…

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

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

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

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

  • Error Line 631, Column 115: general entity "action" not defined and no default entity
    …03955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclic…

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

  • Warning Line 631, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='ret…

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

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

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

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

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

  • Info Line 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 631, Column 133: cannot generate system identifier for general entity "sectionId"
    …TML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _WidgetM…

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

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

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

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

  • Error Line 631, Column 133: general entity "sectionId" not defined and no default entity
    …TML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _WidgetM…

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

  • Warning Line 631, Column 142: reference not terminated by REFC delimiter
    …tId=HTML20&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

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

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

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

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

  • Info Line 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Error Line 640, Column 39: value of attribute "id" invalid: "1" cannot start a name
    <!--Start 152 Media Slider--><div id='152MediaSliderAdContainer1350483362086' p…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 640, Column 88: there is no attribute "position"
    …derAdContainer1350483362086' position='absolute' z-index='99999'><script 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 640, Column 107: there is no attribute "z-index"
    …83362086' position='absolute' z-index='99999'><script src='http://code.jquery.…

    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 640, Column 735: value of attribute "id" invalid: "1" cannot start a name
    …62086').hide()});});</script><div id='152MediaSliderAdContents1350483362086' s…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 640, Column 1076: there is no attribute "align"
    …th=100%; visibility: visible; ' align='right'><div id='152MediaCloseButton1350…

    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 640, Column 1093: value of attribute "id" invalid: "1" cannot start a name
    …ty: visible; ' align='right'><div id='152MediaCloseButton1350483362086' style=…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 641, Column 21: there is no attribute "frameborder"
    <iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=160 heigh…

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

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

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

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

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

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

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

  • Error Line 641, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=160 heigh…
  • Error Line 641, Column 50: there is no attribute "marginheight"
    …meborder=0 marginwidth=0 marginheight=0 scrolling=no width=160 height=600 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 641, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginwidth=0 marginheight=0 scrolling=no width=160 height=600 src=…
  • Error Line 641, Column 62: there is no attribute "scrolling"
    …arginwidth=0 marginheight=0 scrolling=no width=160 height=600 src="http://ad.x…

    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 641, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arginwidth=0 marginheight=0 scrolling=no width=160 height=600 src="http://ad.x…
  • Error Line 641, Column 71: there is no attribute "width"
    …h=0 marginheight=0 scrolling=no width=160 height=600 src="http://ad.xtendmedia…

    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 641, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 marginheight=0 scrolling=no width=160 height=600 src="http://ad.xtendmedia…
  • Error Line 641, Column 82: there is no attribute "height"
    …eight=0 scrolling=no width=160 height=600 src="http://ad.xtendmedia.com/st?ad_…

    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 641, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eight=0 scrolling=no width=160 height=600 src="http://ad.xtendmedia.com/st?ad_…
  • Error Line 641, Column 90: there is no attribute "src"
    …scrolling=no width=160 height=600 src="http://ad.xtendmedia.com/st?ad_type=ifr…

    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 641, Column 134: cannot generate system identifier for general entity "ad_size"
    …//ad.xtendmedia.com/st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=…

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

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

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

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

  • Error Line 641, Column 134: general entity "ad_size" not defined and no default entity
    …//ad.xtendmedia.com/st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=…

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

  • Warning Line 641, Column 141: reference not terminated by REFC delimiter
    …endmedia.com/st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_U…

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

  • Warning Line 641, Column 141: reference to external entity in attribute value
    …endmedia.com/st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_U…

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

  • Error Line 641, Column 141: reference to entity "ad_size" for which no system identifier could be generated
    …endmedia.com/st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_U…

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

  • Info Line 641, Column 133: entity was defined here
    …://ad.xtendmedia.com/st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url…
  • Warning Line 641, Column 150: cannot generate system identifier for general entity "section"
    …com/st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></if…

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

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

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

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

  • Error Line 641, Column 150: general entity "section" not defined and no default entity
    …com/st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></if…

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

  • Warning Line 641, Column 157: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></iframe>

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

  • Warning Line 641, Column 157: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></iframe>

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

  • Error Line 641, Column 157: reference to entity "section" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></iframe>

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

  • Info Line 641, Column 149: entity was defined here
    ….com/st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></i…
  • Warning Line 641, Column 166: cannot generate system identifier for general entity "pub_url"
    …st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></iframe>

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

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

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

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

  • Error Line 641, Column 166: general entity "pub_url" not defined and no default entity
    …st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></iframe>

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

  • Warning Line 641, Column 173: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></iframe>

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

  • Warning Line 641, Column 173: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></iframe>

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

  • Error Line 641, Column 173: reference to entity "pub_url" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></iframe>

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

  • Info Line 641, Column 165: entity was defined here
    …st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></iframe>
  • Error Line 641, Column 185: element "iframe" undefined
    …st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></iframe>

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

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

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

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

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

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

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

  • Info Line 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 649, Column 107: reference not terminated by REFC delimiter
    …8190149103955&widgetType=HTML&widgetId=HTML19&action=editWidget&sectionId=main…

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

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

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

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

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

  • Info Line 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 649, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML19&action=editWidget&sectionId=main' onclick='ret…

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

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

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

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

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

  • Info Line 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 649, Column 142: reference not terminated by REFC delimiter
    …tId=HTML19&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

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

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

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

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

  • Info Line 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Error Line 658, Column 30: required attribute "type" not specified
    <script language="JavaScript">

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

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

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

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

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

  • Warning Line 667, Column 93: reference not terminated by REFC delimiter
    …?blogID=2582738190149103955&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 667, Column 93: reference to external entity in attribute value
    …?blogID=2582738190149103955&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 667, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2582738190149103955&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 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 667, Column 107: reference not terminated by REFC delimiter
    …8190149103955&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=main'…

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

  • Warning Line 667, Column 107: reference to external entity in attribute value
    …8190149103955&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=main'…

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

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

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

  • Info Line 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 667, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=main' onclick='ret…

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

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

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

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

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

  • Info Line 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 667, Column 141: reference not terminated by REFC delimiter
    …etId=HTML3&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Warning Line 667, Column 141: reference to external entity in attribute value
    …etId=HTML3&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Error Line 667, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML3&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Info Line 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Error Line 684, Column 55: there is no attribute "imageanchor"
    …tp://www.tusnovelas.net/" imageanchor="1" style="clear: left; float: left; mar…

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

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

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

  • Error Line 693, Column 32: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <h2 style="text-align: center;">

    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 808, Column 5: end tag for "ul" which is not finished
    </ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 817, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-el-reemplazante-capitulo-12-…

    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 818, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-el-reemplazante-capitulo-11-…

    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 819, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-el-reemplazante-capitulo-10-…

    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 820, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-el-reemplazante-capitulo-9-l…

    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 821, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-el-reemplazante-capitulo-8-l…

    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 822, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/telenovela-el-reemplazante-capit…

    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 823, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-el-reemplazante-capitulo-7-l…

    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 824, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-el-reemplazante-capitulo-6-l…

    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 825, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-el-reemplazante-capitulo-5-l…

    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 826, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-el-reemplazante-capitulo-4-l…

    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 827, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-el-reemplazante-capitulo-3-l…

    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 828, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-el-reemplazante-capitulo-2-l…

    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 829, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-el-reemplazante-capitulo-1-l…

    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 830, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/telenovela-el-reemplazante-capit…

    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 875, Column 5: end tag for "ul" which is not finished
    </ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 878, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-69-…

    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 879, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-68-…

    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 880, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-67-…

    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 881, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-66.…

    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 882, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-65-…

    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 883, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-64-…

    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 884, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/telenovela-mundos-opuestos-capit…

    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 885, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-63-…

    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 886, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-62-…

    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 887, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-61-…

    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 888, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-60.…

    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 889, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-59-…

    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 890, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-58-…

    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 891, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-57-…

    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 892, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-56-…

    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 893, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-55-…

    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 894, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-54.…

    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 895, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-53-…

    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 896, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-52-…

    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 897, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/12/ver-mundos-opuestos-capitulo-51-…

    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 898, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/telenovela-mundos-opuestos-capit…

    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 899, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-50-…

    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 900, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-49-…

    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 901, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-48.…

    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 902, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-47-…

    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 903, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-46-…

    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 904, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/telenovela-mundos-opuestos-capit…

    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 905, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-45-…

    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 906, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-44-…

    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 907, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-43-…

    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 908, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-42.…

    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 909, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-41-…

    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 910, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-40-…

    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 911, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-39-…

    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 912, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-38-…

    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 913, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-37-…

    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 914, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-36.…

    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 915, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-35-…

    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 916, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-34-…

    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 917, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-33-…

    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 918, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/telenovela-mundos-opuestos-capit…

    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 919, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-32-…

    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 920, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-31-…

    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 921, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-30.…

    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 922, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-29-…

    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 923, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-28-…

    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 924, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/11/ver-mundos-opuestos-capitulo-27-…

    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 925, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/telenovela-mundos-opuestos-capit…

    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 926, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-26-…

    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 927, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-25-…

    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 928, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-24.…

    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 929, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-23-…

    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 930, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-22-…

    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 931, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/telenovela-mundos-opuestos-capit…

    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 932, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-21-…

    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 933, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-20-…

    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 934, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-19-…

    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 935, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-18.…

    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 936, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-17-…

    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 937, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-16-…

    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 938, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-15-…

    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 939, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-14-…

    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 940, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-13-…

    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 941, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-12-…

    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 942, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-11-…

    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 943, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-10.…

    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 944, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-9-m…

    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 945, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-8-d…

    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 946, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-7-s…

    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 947, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-6-v…

    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 948, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-5-j…

    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 949, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-4.h…

    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 950, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-3-m…

    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 951, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-2-l…

    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 952, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/ver-mundos-opuestos-capitulo-1-d…

    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 953, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a href="http://www.tusnovelas.net/2012/10/telenovela-mundos-opuestos-capit…

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

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

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

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

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

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

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

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

  • Warning Line 1004, Column 107: reference to external entity in attribute value
    …8190149103955&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=slide…

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

  • Error Line 1004, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …8190149103955&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=slide…

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

  • Info Line 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 1004, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=slide' onclick='re…

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

  • Warning Line 1004, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=slide' onclick='re…

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

  • Error Line 1004, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=slide' onclick='re…

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

  • Info Line 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 1004, Column 141: reference not terminated by REFC delimiter
    …etId=HTML2&action=editWidget&sectionId=slide' 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 1004, Column 141: reference to external entity in attribute value
    …etId=HTML2&action=editWidget&sectionId=slide' 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 1004, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML2&action=editWidget&sectionId=slide' 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 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Error Line 1014, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1014, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1014, Column 314: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1015, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1015, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1015, Column 300: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1016, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1016, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1016, Column 310: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1017, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1017, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1017, Column 312: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1018, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1018, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1018, Column 308: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1019, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1019, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1019, Column 314: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1020, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1020, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1020, Column 331: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1021, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1021, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1021, Column 280: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1022, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href=" http://www.tusnovelas.net/2012…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1022, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href=" http://www.tusnovelas.net/2012…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1022, Column 342: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href=" http://www.tusnovelas.n…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1023, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1023, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1023, Column 306: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1024, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1024, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1024, Column 309: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1025, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1025, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1025, Column 296: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1026, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1026, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1026, Column 312: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1027, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1027, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1027, Column 338: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1028, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1028, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1028, Column 312: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1029, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1029, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1029, Column 310: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1030, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1030, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1030, Column 318: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1031, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1031, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1031, Column 304: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1032, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1032, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1032, Column 278: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1033, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1033, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1033, Column 306: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1034, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1034, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1034, Column 306: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1035, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1035, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1035, Column 296: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1036, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1036, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1036, Column 284: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1037, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1037, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1037, Column 304: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1038, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1038, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1038, Column 321: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1039, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1039, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1039, Column 304: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1040, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1040, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1040, Column 309: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href=" http://www.tusnovelas.n…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1041, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1041, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1041, Column 274: ID "title" already defined
    …"170" class="im" /></a></div><div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1042, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1042, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2013/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1042, Column 306: ID "title" already defined
    …"170" class="im" /></a></div><div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1043, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1043, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1043, Column 310: ID "title" already defined
    …"170" class="im" /></a></div><div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1044, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1044, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1044, Column 304: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1045, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1045, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1045, Column 324: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href=" http://www.tusnovelas.n…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1046, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1046, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1046, Column 302: ID "title" already defined
    …"170" class="im" /></a></div><div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1047, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1047, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1047, Column 302: ID "title" already defined
    …"170" class="im" /></a></div><div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1048, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1048, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1048, Column 312: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1049, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1049, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1049, Column 284: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1050, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1050, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1050, Column 280: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1051, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1051, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1051, Column 300: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1052, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1052, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1052, Column 300: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1053, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1053, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1053, Column 310: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1054, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1054, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1054, Column 288: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1055, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1055, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1055, Column 280: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1056, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1056, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1056, Column 296: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1057, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1057, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1057, Column 292: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1058, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1058, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1058, Column 300: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1059, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1059, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1059, Column 276: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1060, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1060, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1060, Column 308: ID "title" already defined
    …"170" class="im" /></a></div><div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1061, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1061, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1061, Column 284: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1062, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1062, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1062, Column 292: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1063, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1063, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1063, Column 325: ID "title" already defined
    …170" class="im" /></a></div> <div id="title"><a href="http://www.miltelenovela…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1064, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1064, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1064, Column 330: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1065, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1065, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1065, Column 326: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1066, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1066, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1066, Column 296: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1067, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1067, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1067, Column 305: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1068, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1068, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1068, Column 300: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1069, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1069, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1069, Column 280: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1070, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1070, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1070, Column 337: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1071, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1071, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1071, Column 321: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1072, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1072, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1072, Column 314: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1073, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1073, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1073, Column 288: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1074, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1074, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1074, Column 304: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1075, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1075, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1075, Column 304: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1076, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1076, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1076, Column 278: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1077, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1077, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1077, Column 314: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1078, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1078, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1078, Column 304: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1079, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1079, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1079, Column 274: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1080, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1080, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1080, Column 292: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1081, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.miltelenovelas.com/a…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1081, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.miltelenovelas.com/a…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1081, Column 355: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.miltelenovela…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1082, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1082, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1082, Column 284: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1083, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1083, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1083, Column 280: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1084, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1084, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1084, Column 306: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1085, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.miltelenovelas.com/a…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1085, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.miltelenovelas.com/a…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1085, Column 267: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.miltelenovela…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1086, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1086, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1086, Column 288: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Error Line 1087, Column 10: ID "novela-item" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 10: ID "novela-item" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1087, Column 32: ID "imagen" already defined
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…

    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 1013, Column 32: ID "imagen" first defined here
    <div id="novela-item"><div id="imagen"><a href="http://www.tusnovelas.net/2012/…
  • Error Line 1087, Column 334: ID "title" already defined
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…

    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 1013, Column 309: ID "title" first defined here
    …70" class="im" /></a></div>  <div id="title"><a href="http://www.tusnovelas.ne…
  • Warning Line 1092, Column 93: reference not terminated by REFC delimiter
    …?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML10&action=editWidget&…

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

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

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

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

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

  • Info Line 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 1092, Column 107: reference not terminated by REFC delimiter
    …8190149103955&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=slid…

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

  • Warning Line 1092, Column 107: reference to external entity in attribute value
    …8190149103955&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=slid…

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

  • Error Line 1092, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …8190149103955&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=slid…

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

  • Info Line 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 1092, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=slide' onclick='re…

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

  • Warning Line 1092, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=slide' onclick='re…

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

  • Error Line 1092, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=slide' onclick='re…

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

  • Info Line 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 1092, Column 142: reference not terminated by REFC delimiter
    …tId=HTML10&action=editWidget&sectionId=slide' 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 1092, Column 142: reference to external entity in attribute value
    …tId=HTML10&action=editWidget&sectionId=slide' 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 1092, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML10&action=editWidget&sectionId=slide' 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 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Error Line 1100, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 1101, Column 36: document type does not allow element "span" here
    document.write('<span class="index"><a href="/search/label/.">See all Movies</a…

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

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

  • Error Line 1102, Column 20: document type does not allow element "h1" here
    document.write('<h1><a href="/search/label/.?max-results=8">Movie Category 3</a…

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

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

  • Error Line 1103, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write("<script src=\"/feeds/posts/default/-/.?max-results="+numposts2+…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1103, Column 146: required attribute "type" not specified
    …&orderby=published&alt=json-in-script&callback=showrecentposts1\"><\/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 1103, Column 146: document type does not allow element "script" here
    …&orderby=published&alt=json-in-script&callback=showrecentposts1\"><\/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 1103, Column 147: character "<" is the first character of a delimiter but occurred as data
    …&orderby=published&alt=json-in-script&callback=showrecentposts1\"><\/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 1105, 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 1100, Column 1: start tag was here
    <script>
  • Error Line 1107, Column 10: ID "maskolis" already defined
    <div id='maskolis'>

    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 1099, Column 10: ID "maskolis" first defined here
    <div id='maskolis'>
  • Error Line 1108, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 1109, Column 36: document type does not allow element "span" here
    document.write('<span class="index"><a href="/search/label/

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

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

  • Error Line 1111, Column 20: document type does not allow element "h1" here
    document.write('<h1><a href="/search/label/

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

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

  • Error Line 1113, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write("<script src=\"/feeds/posts/default/-/

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1114, Column 1: character "?" not allowed in attribute specification list
    ?max-results="+numposts2+"&orderby=published&alt=json-in-script&callback=showre…
  • Error Line 1114, Column 1: document type does not allow element "script" here
    ?max-results="+numposts2+"&orderby=published&alt=json-in-script&callback=showre…

    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 1114, Column 28: cannot generate system identifier for general entity "orderby"
    ?max-results="+numposts2+"&orderby=published&alt=json-in-script&callback=showre…

    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 1114, Column 28: general entity "orderby" not defined and no default entity
    ?max-results="+numposts2+"&orderby=published&alt=json-in-script&callback=showre…

    This is usually a cascading error caused by 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 1114, Column 35: reference not terminated by REFC delimiter
    ?max-results="+numposts2+"&orderby=published&alt=json-in-script&callback=showre…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1114, Column 35: reference to entity "orderby" for which no system identifier could be generated
    ?max-results="+numposts2+"&orderby=published&alt=json-in-script&callback=showre…

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

  • Info Line 1114, Column 27: entity was defined here
    ?max-results="+numposts2+"&orderby=published&alt=json-in-script&callback=showre…
  • Warning Line 1114, Column 46: cannot generate system identifier for general entity "alt"
    …sults="+numposts2+"&orderby=published&alt=json-in-script&callback=showrecentpo…

    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 1114, Column 46: general entity "alt" not defined and no default entity
    …sults="+numposts2+"&orderby=published&alt=json-in-script&callback=showrecentpo…

    This is usually a cascading error caused by 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 1114, Column 49: reference not terminated by REFC delimiter
    …ts="+numposts2+"&orderby=published&alt=json-in-script&callback=showrecentposts…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1114, Column 49: reference to entity "alt" for which no system identifier could be generated
    …ts="+numposts2+"&orderby=published&alt=json-in-script&callback=showrecentposts…

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

  • Info Line 1114, Column 45: entity was defined here
    …esults="+numposts2+"&orderby=published&alt=json-in-script&callback=showrecentp…
  • Warning Line 1114, Column 65: cannot generate system identifier for general entity "callback"
    …&orderby=published&alt=json-in-script&callback=showrecentposts1\"><\/script>")…

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

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

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

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

  • Error Line 1114, Column 65: general entity "callback" not defined and no default entity
    …&orderby=published&alt=json-in-script&callback=showrecentposts1\"><\/script>")…

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

  • Warning Line 1114, Column 73: reference not terminated by REFC delimiter
    …&orderby=published&alt=json-in-script&callback=showrecentposts1\"><\/script>");

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

  • Error Line 1114, Column 73: reference to entity "callback" for which no system identifier could be generated
    …&orderby=published&alt=json-in-script&callback=showrecentposts1\"><\/script>");

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

  • Info Line 1114, Column 64: entity was defined here
    …"&orderby=published&alt=json-in-script&callback=showrecentposts1\"><\/script>"…
  • Warning Line 1114, Column 93: character "<" is the first character of a delimiter but occurred as data
    …&orderby=published&alt=json-in-script&callback=showrecentposts1\"><\/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 1116, 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 1108, Column 1: start tag was here
    <script>
  • Error Line 1118, Column 10: ID "maskolis" already defined
    <div id='maskolis'>

    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 1099, Column 10: ID "maskolis" first defined here
    <div id='maskolis'>
  • Error Line 1119, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 1120, Column 36: document type does not allow element "span" here
    document.write('<span class="index"><a href="/search/label/

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

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

  • Error Line 1122, Column 20: document type does not allow element "h1" here
    document.write('<h1><a href="/search/label/

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

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

  • Error Line 1124, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write("<script src=\"/feeds/posts/default/-/

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1125, Column 1: character "?" not allowed in attribute specification list
    ?max-results="+numposts2+"&orderby=published&alt=json-in-script&callback=showre…
  • Error Line 1125, Column 1: document type does not allow element "script" here
    ?max-results="+numposts2+"&orderby=published&alt=json-in-script&callback=showre…

    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 1125, Column 35: reference not terminated by REFC delimiter
    ?max-results="+numposts2+"&orderby=published&alt=json-in-script&callback=showre…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1125, Column 35: reference to entity "orderby" for which no system identifier could be generated
    ?max-results="+numposts2+"&orderby=published&alt=json-in-script&callback=showre…

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

  • Info Line 1114, Column 27: entity was defined here
    ?max-results="+numposts2+"&orderby=published&alt=json-in-script&callback=showre…
  • Warning Line 1125, Column 49: reference not terminated by REFC delimiter
    …ts="+numposts2+"&orderby=published&alt=json-in-script&callback=showrecentposts…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1125, Column 49: reference to entity "alt" for which no system identifier could be generated
    …ts="+numposts2+"&orderby=published&alt=json-in-script&callback=showrecentposts…

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

  • Info Line 1114, Column 45: entity was defined here
    …esults="+numposts2+"&orderby=published&alt=json-in-script&callback=showrecentp…
  • Warning Line 1125, Column 73: reference not terminated by REFC delimiter
    …&orderby=published&alt=json-in-script&callback=showrecentposts1\"><\/script>");

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

  • Error Line 1125, Column 73: reference to entity "callback" for which no system identifier could be generated
    …&orderby=published&alt=json-in-script&callback=showrecentposts1\"><\/script>");

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

  • Info Line 1114, Column 64: entity was defined here
    …"&orderby=published&alt=json-in-script&callback=showrecentposts1\"><\/script>"…
  • Warning Line 1125, Column 93: character "<" is the first character of a delimiter but occurred as data
    …&orderby=published&alt=json-in-script&callback=showrecentposts1\"><\/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 1127, 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 1119, Column 1: start tag was here
    <script>
  • Warning Line 1135, Column 93: reference not terminated by REFC delimiter
    …?blogID=2582738190149103955&widgetType=Attribution&widgetId=Attribution1&actio…

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

  • Warning Line 1135, Column 93: reference to external entity in attribute value
    …?blogID=2582738190149103955&widgetType=Attribution&widgetId=Attribution1&actio…

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

  • Error Line 1135, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2582738190149103955&widgetType=Attribution&widgetId=Attribution1&actio…

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

  • Info Line 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 1135, Column 114: reference not terminated by REFC delimiter
    …103955&widgetType=Attribution&widgetId=Attribution1&action=editWidget&sectionI…

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

  • Warning Line 1135, Column 114: reference to external entity in attribute value
    …103955&widgetType=Attribution&widgetId=Attribution1&action=editWidget&sectionI…

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

  • Error Line 1135, Column 114: reference to entity "widgetId" for which no system identifier could be generated
    …103955&widgetType=Attribution&widgetId=Attribution1&action=editWidget&sectionI…

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

  • Info Line 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 1135, Column 134: reference not terminated by REFC delimiter
    …tribution&widgetId=Attribution1&action=editWidget&sectionId=slide' onclick='re…

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

  • Warning Line 1135, Column 134: reference to external entity in attribute value
    …tribution&widgetId=Attribution1&action=editWidget&sectionId=slide' onclick='re…

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

  • Error Line 1135, Column 134: reference to entity "action" for which no system identifier could be generated
    …tribution&widgetId=Attribution1&action=editWidget&sectionId=slide' onclick='re…

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

  • Info Line 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 1135, Column 155: reference not terminated by REFC delimiter
    …tribution1&action=editWidget&sectionId=slide' 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 1135, Column 155: reference to external entity in attribute value
    …tribution1&action=editWidget&sectionId=slide' 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 1135, Column 155: reference to entity "sectionId" for which no system identifier could be generated
    …tribution1&action=editWidget&sectionId=slide' 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 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Warning Line 1178, 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 1178, 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 1206, Column 23: there is no attribute "annotation"
    <g:plusone annotation='bubble' href='http://www.tusnovelas.net/' size='tall' so…

    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 1206, Column 37: there is no attribute "href"
    <g:plusone annotation='bubble' href='http://www.tusnovelas.net/' size='tall' so…

    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 1206, Column 71: there is no attribute "size"
    …ref='http://www.tusnovelas.net/' size='tall' source='blogger:blog:plusone' wid…

    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 1206, Column 85: there is no attribute "source"
    …w.tusnovelas.net/' size='tall' source='blogger:blog:plusone' width='250'></g:p…

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

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

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

  • Error Line 1206, Column 114: there is no attribute "width"
    …ovelas.net/' size='tall' source='blogger:blog:plusone' width='250'></g:plusone>

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

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

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

  • Error Line 1206, Column 119: element "g:plusone" undefined
    …ovelas.net/' size='tall' source='blogger:blog:plusone' width='250'></g:plusone>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1222, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=300 heigh…
  • Error Line 1222, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=300 heigh…
  • Error Line 1222, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginwidth=0 marginheight=0 scrolling=no width=300 height=250 src=…
  • Error Line 1222, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arginwidth=0 marginheight=0 scrolling=no width=300 height=250 src="http://ad.m…
  • Error Line 1222, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 marginheight=0 scrolling=no width=300 height=250 src="http://ad.media-serv…
  • Error Line 1222, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eight=0 scrolling=no width=300 height=250 src="http://ad.media-servers.net/st?…
  • Warning Line 1222, Column 144: reference not terminated by REFC delimiter
    …-servers.net/st?ad_type=iframe&ad_size=300x250&section=4036644&pub_url=${PUB_U…

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

  • Warning Line 1222, Column 144: reference to external entity in attribute value
    …-servers.net/st?ad_type=iframe&ad_size=300x250&section=4036644&pub_url=${PUB_U…

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

  • Error Line 1222, Column 144: reference to entity "ad_size" for which no system identifier could be generated
    …-servers.net/st?ad_type=iframe&ad_size=300x250&section=4036644&pub_url=${PUB_U…

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

  • Info Line 641, Column 133: entity was defined here
    …://ad.xtendmedia.com/st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url…
  • Warning Line 1222, Column 160: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=4036644&pub_url=${PUB_URL}"></iframe>

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

  • Warning Line 1222, Column 160: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=4036644&pub_url=${PUB_URL}"></iframe>

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

  • Error Line 1222, Column 160: reference to entity "section" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=4036644&pub_url=${PUB_URL}"></iframe>

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

  • Info Line 641, Column 149: entity was defined here
    ….com/st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></i…
  • Warning Line 1222, Column 176: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=4036644&pub_url=${PUB_URL}"></iframe>

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

  • Warning Line 1222, Column 176: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=4036644&pub_url=${PUB_URL}"></iframe>

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

  • Error Line 1222, Column 176: reference to entity "pub_url" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=4036644&pub_url=${PUB_URL}"></iframe>

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

  • Info Line 641, Column 165: entity was defined here
    …st?ad_type=iframe&ad_size=160x600&section=2382903&pub_url=${PUB_URL}"></iframe>
  • Error Line 1222, Column 188: element "iframe" undefined
    …st?ad_type=iframe&ad_size=300x250&section=4036644&pub_url=${PUB_URL}"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1228, Column 93: reference not terminated by REFC delimiter
    …?blogID=2582738190149103955&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 1228, Column 93: reference to external entity in attribute value
    …?blogID=2582738190149103955&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 1228, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2582738190149103955&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 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 1228, Column 107: reference not terminated by REFC delimiter
    …8190149103955&widgetType=HTML&widgetId=HTML1&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 1228, Column 107: reference to external entity in attribute value
    …8190149103955&widgetType=HTML&widgetId=HTML1&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 1228, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …8190149103955&widgetType=HTML&widgetId=HTML1&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 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 1228, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 1228, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' onclick='…

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

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

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

  • Info Line 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 1228, Column 141: reference not terminated by REFC delimiter
    …etId=HTML1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 1228, Column 141: reference to external entity in attribute value
    …etId=HTML1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Error Line 1228, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Info Line 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Error Line 1237, Column 8: element "center" undefined
    <center><div class='menusearch'>

    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 1239, Column 65: there is no attribute "target"
    <form action='http://www.google.com/search' method='get' target='_blank'>

    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 1240, Column 82: 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 name='sitesearch' style='display:none;' value='http://www.tusnovelas.net'/>

    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 1241, Column 439: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …ype='text' value='busca tu novela...'/><input align='top' id='search-btn' src=…

    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 1241, Column 453: there is no attribute "align"
    …ue='busca tu novela...'/><input align='top' id='search-btn' src='http://2.bp.b…

    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 1241, Column 604: 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
    …L3I/AAAAAAAAHqc/H9V2g9h_x94/s1600/search_btn.png' type='image' value='Search'/>

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

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

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

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

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

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

  • Info Line 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 1249, Column 107: reference not terminated by REFC delimiter
    …8190149103955&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sideb…

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

  • Warning Line 1249, Column 107: reference to external entity in attribute value
    …8190149103955&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sideb…

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

  • Error Line 1249, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …8190149103955&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sideb…

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

  • Info Line 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 1249, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 1249, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sidebar' onclick='…

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

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

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

  • Info Line 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 1249, Column 141: reference not terminated by REFC delimiter
    …etId=HTML4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 1249, Column 141: reference to external entity in attribute value
    …etId=HTML4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Error Line 1249, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Info Line 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Error Line 1258, Column 8: element "center" undefined
    <center><script id="sid0010000003007363859">(function() {function async_load(){…

    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 1258, Column 44: required attribute "type" not specified
    …er><script id="sid0010000003007363859">(function() {function async_load(){s.id…

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

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

  • Warning Line 1258, Column 475: character "<" is the first character of a delimiter but occurred as data
    …script');for (var i=0, l=ss.length; i < l; i++){if (ss[i].id=='sid001000000300…

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

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

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

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

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

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

  • Info Line 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 1263, Column 107: reference not terminated by REFC delimiter
    …8190149103955&widgetType=HTML&widgetId=HTML8&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 1263, Column 107: reference to external entity in attribute value
    …8190149103955&widgetType=HTML&widgetId=HTML8&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 1263, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …8190149103955&widgetType=HTML&widgetId=HTML8&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 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 1263, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 1263, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=sidebar' onclick='…

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

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

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

  • Info Line 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 1263, Column 141: reference not terminated by REFC delimiter
    …etId=HTML8&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 1263, Column 141: reference to external entity in attribute value
    …etId=HTML8&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Error Line 1263, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML8&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Info Line 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Error Line 1272, Column 196: there is no attribute "style"
    … scrolling="no" frameborder="0" 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 1272, Column 273: there is no attribute "allowtransparency"
    …overflow:hidden; width:300px; height:250px;" allowtransparency="true"></iframe>

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

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

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

  • Error Line 1272, Column 279: element "iframe" undefined
    …overflow:hidden; width:300px; height:250px;" allowtransparency="true"></iframe>

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

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

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

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

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

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

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

  • Info Line 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 1277, Column 107: reference not terminated by REFC delimiter
    …8190149103955&widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=side…

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

  • Warning Line 1277, Column 107: reference to external entity in attribute value
    …8190149103955&widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=side…

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

  • Error Line 1277, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …8190149103955&widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=side…

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

  • Info Line 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 1277, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 1277, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=sidebar' onclick='…

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

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

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

  • Info Line 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 1277, Column 142: reference not terminated by REFC delimiter
    …tId=HTML14&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 1277, Column 142: reference to external entity in attribute value
    …tId=HTML14&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Error Line 1277, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML14&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Info Line 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Warning Line 1579, Column 93: reference not terminated by REFC delimiter
    …?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML9&action=editWidget&s…

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

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

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

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

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

  • Info Line 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 1579, Column 107: reference not terminated by REFC delimiter
    …8190149103955&widgetType=HTML&widgetId=HTML9&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 1579, Column 107: reference to external entity in attribute value
    …8190149103955&widgetType=HTML&widgetId=HTML9&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 1579, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …8190149103955&widgetType=HTML&widgetId=HTML9&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 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 1579, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 1579, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=sidebar' onclick='…

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

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

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

  • Info Line 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 1579, Column 141: reference not terminated by REFC delimiter
    …etId=HTML9&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 1579, Column 141: reference to external entity in attribute value
    …etId=HTML9&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Error Line 1579, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML9&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Info Line 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Warning Line 1663, Column 93: reference not terminated by REFC delimiter
    …?blogID=2582738190149103955&widgetType=PopularPosts&widgetId=PopularPosts1&act…

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

  • Warning Line 1663, Column 93: reference to external entity in attribute value
    …?blogID=2582738190149103955&widgetType=PopularPosts&widgetId=PopularPosts1&act…

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

  • Error Line 1663, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=2582738190149103955&widgetType=PopularPosts&widgetId=PopularPosts1&act…

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

  • Info Line 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 1663, Column 115: reference not terminated by REFC delimiter
    …03955&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

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

  • Warning Line 1663, Column 115: reference to external entity in attribute value
    …03955&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

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

  • Error Line 1663, Column 115: reference to entity "widgetId" for which no system identifier could be generated
    …03955&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

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

  • Info Line 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 1663, Column 136: reference not terminated by REFC delimiter
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 1663, Column 136: reference to external entity in attribute value
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=sidebar' onclick='…

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

  • Error Line 1663, Column 136: reference to entity "action" for which no system identifier could be generated
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=sidebar' onclick='…

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

  • Info Line 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 1663, Column 157: reference not terminated by REFC delimiter
    …ularPosts1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 1663, Column 157: reference to external entity in attribute value
    …ularPosts1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Error Line 1663, Column 157: reference to entity "sectionId" for which no system identifier could be generated
    …ularPosts1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Info Line 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Error Line 1673, Column 212: there is no attribute "alt"
    …w.darkiller.com/" target="_blank" alt="Telenovelas y Series" title="Telenovela…

    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 1675, Column 378: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …y blog, website, or RSS feed for Free">ping fast  my blog, website, or RSS fee…

    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 1675, Column 497: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …www.mypagerankcheck.com//" alt="google pagerank">google pagerank</a></noscript>

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

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

  • Warning Line 1684, Column 93: reference not terminated by REFC delimiter
    …?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML13&action=editWidget&…

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

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

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

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

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

  • Info Line 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 1684, Column 107: reference not terminated by REFC delimiter
    …8190149103955&widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=side…

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

  • Warning Line 1684, Column 107: reference to external entity in attribute value
    …8190149103955&widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=side…

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

  • Error Line 1684, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …8190149103955&widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=side…

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

  • Info Line 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 1684, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 1684, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=sidebar' onclick='…

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

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

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

  • Info Line 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 1684, Column 142: reference not terminated by REFC delimiter
    …tId=HTML13&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 1684, Column 142: reference to external entity in attribute value
    …tId=HTML13&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Error Line 1684, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML13&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Info Line 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Warning Line 1711, Column 93: reference not terminated by REFC delimiter
    …?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML5&action=editWidget&s…

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

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

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

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

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

  • Info Line 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 1711, Column 107: reference not terminated by REFC delimiter
    …8190149103955&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=foote…

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

  • Warning Line 1711, Column 107: reference to external entity in attribute value
    …8190149103955&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=foote…

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

  • Error Line 1711, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …8190149103955&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=foote…

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

  • Info Line 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 1711, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=footer1' 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 1711, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=footer1' 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 1711, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=footer1' 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 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 1711, Column 141: reference not terminated by REFC delimiter
    …etId=HTML5&action=editWidget&sectionId=footer1' 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 1711, Column 141: reference to external entity in attribute value
    …etId=HTML5&action=editWidget&sectionId=footer1' 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 1711, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML5&action=editWidget&sectionId=footer1' 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 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Warning Line 1728, Column 93: reference not terminated by REFC delimiter
    …?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML6&action=editWidget&s…

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

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

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

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

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

  • Info Line 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 1728, Column 107: reference not terminated by REFC delimiter
    …8190149103955&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=foote…

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

  • Warning Line 1728, Column 107: reference to external entity in attribute value
    …8190149103955&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=foote…

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

  • Error Line 1728, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …8190149103955&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=foote…

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

  • Info Line 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 1728, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=footer2' 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 1728, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=footer2' 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 1728, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=footer2' 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 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 1728, Column 141: reference not terminated by REFC delimiter
    …etId=HTML6&action=editWidget&sectionId=footer2' 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 1728, Column 141: reference to external entity in attribute value
    …etId=HTML6&action=editWidget&sectionId=footer2' 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 1728, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML6&action=editWidget&sectionId=footer2' 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 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Warning Line 1745, Column 93: reference not terminated by REFC delimiter
    …?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML7&action=editWidget&s…

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

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

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

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

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

  • Info Line 631, Column 82: entity was defined here
    …m/rearrange?blogID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=…
  • Warning Line 1745, Column 107: reference not terminated by REFC delimiter
    …8190149103955&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=foote…

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

  • Warning Line 1745, Column 107: reference to external entity in attribute value
    …8190149103955&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=foote…

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

  • Error Line 1745, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …8190149103955&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=foote…

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

  • Info Line 631, Column 98: entity was defined here
    …ID=2582738190149103955&widgetType=HTML&widgetId=HTML20&action=editWidget&secti…
  • Warning Line 1745, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=footer3' 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 1745, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=footer3' 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 1745, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=footer3' 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 631, Column 114: entity was defined here
    …103955&widgetType=HTML&widgetId=HTML20&action=editWidget&sectionId=main' oncli…
  • Warning Line 1745, Column 141: reference not terminated by REFC delimiter
    …etId=HTML7&action=editWidget&sectionId=footer3' 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 1745, Column 141: reference to external entity in attribute value
    …etId=HTML7&action=editWidget&sectionId=footer3' 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 1745, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML7&action=editWidget&sectionId=footer3' 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 631, Column 132: entity was defined here
    …HTML&widgetId=HTML20&action=editWidget&sectionId=main' onclick='return _Widget…
  • Warning Line 1779, 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 1779, 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.750 visits