malastv.net

malastv.net has Alexa Rank 102.597 and Google Page Rank is 0

Display Widget for this domain on your website. Click Here
This data was last updated from 15-09-2013 02:45:50  (update).

Overview Info

  • Domain Name
    malastv.net
  • Favicon
  • Alexa Rank
    #102597
  • Google Page Rank
    PR 0
  • Ip Address
    75.126.104.232
  • Page Size
    145.5 KB
  • Images
    0 GIF, 94 JPG, 13 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 6 20 0 0 0

Website Meta Analysis



  • Title
    MalasTV: Videos deFamosas Nuas

Technical Analysis



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

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

HTML Analysis

  • content-type: text/html; charset=UTF-8
  • expires: Sun, 15 Sep 2013 14:45:39 GMT
  • date: Sun, 15 Sep 2013 14:45:39 GMT
  • cache-control: private, max-age=0
  • last-modified: Fri, 06 Sep 2013 06:28:17 GMT
  • etag: "1029c489-e01e-4e75-bab1-8591a1ee5e0e"
  • content-encoding: gzip
  • x-content-type-options: nosniff
  • x-xss-protection: 1; mode=block
  • content-length: 30919
  • server: GSE
  • alternate-protocol: 80:quic,80:quic
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for malastv.net

DNS Analysis


DNS servers
ns1dhl.name.com [184.172.60.181]
ns2cvx.name.com [5.153.6.209]
ns3gnv.name.com [208.43.116.40]
ns4fmx.name.com [50.17.205.133]


DNS Records

Answer records
malastv.net MX
preference: 10
exchange: aspmx.l.google.com
1800s
malastv.net NS  ns1dhl.name.com 300s
malastv.net MX
preference: 30
exchange: aspmx3.googlemail.com
1800s
malastv.net MX
preference: 20
exchange: alt2.aspmx.l.google.com
1800s
malastv.net MX
preference: 30
exchange: aspmx5.googlemail.com
1800s
malastv.net SOA
server: ns1dhl.name.com
email: support@name.com
serial: 1
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
300s
malastv.net A 75.126.101.245 300s
malastv.net NS  ns2cvx.name.com 300s
malastv.net MX
preference: 30
exchange: aspmx2.googlemail.com
1800s
malastv.net NS  ns3gnv.name.com 300s
malastv.net MX
preference: 30
exchange: aspmx4.googlemail.com
1800s
malastv.net MX
preference: 20
exchange: alt1.aspmx.l.google.com
1800s
malastv.net NS  ns4fmx.name.com 300s

Authority records

Additional records
ns3gnv.name.com A 208.43.116.40 86400s
ns2cvx.name.com A 5.153.6.209 86400s
ns1dhl.name.com A 184.172.60.181 86400s
ns4fmx.name.com A 50.17.205.133 86400s

IP 75.126.104.232 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 276 Errors
  • 130 Warnings
Ratio Text/Html
  • 0.5056933385253717
Message Error
  • Warning Line 7, Column 275: character "&" is the first character of a delimiter but occurred as data
    …ming={Timer:d,load:a};if(b.performance&&b.performance.timing){var a=b.performa…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 7, Column 277: cannot generate system identifier for general entity "b.performance.timing"
    …ng={Timer:d,load:a};if(b.performance&&b.performance.timing){var a=b.performanc…

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

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

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

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

  • Error Line 7, Column 277: general entity "b.performance.timing" not defined and no default entity
    …ng={Timer:d,load:a};if(b.performance&&b.performance.timing){var a=b.performanc…

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

  • Warning Line 7, Column 297: reference not terminated by REFC delimiter
    …if(b.performance&&b.performance.timing){var a=b.performance.timing,c=b[e].load…

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

  • Error Line 7, Column 297: reference to entity "b.performance.timing" for which no system identifier could be generated
    …if(b.performance&&b.performance.timing){var a=b.performance.timing,c=b[e].load…

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

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

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 7, Column 381: cannot generate system identifier for general entity "a"
    …avigationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("wts…

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

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

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

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

  • Error Line 7, Column 381: general entity "a" not defined and no default entity
    …avigationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("wts…

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

  • Warning Line 7, Column 382: reference not terminated by REFC delimiter
    …vigationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("wtsr…

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

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

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

  • Info Line 7, Column 380: entity was defined here
    …navigationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("wt…
  • Warning Line 7, Column 385: character "&" is the first character of a delimiter but occurred as data
    …ationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g]("wtsrt_"…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

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

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

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

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

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

  • Error Line 7, Column 495: reference to entity "b.chrome.csi" for which no system identifier could be generated
    …_"))}try{a=null,b.chrome&&b.chrome.csi&&(a=Math.floor(b.chrome.csi().pageT),c&…

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

  • Info Line 7, Column 482: entity was defined here
    …tbsd_","wtsrt_"))}try{a=null,b.chrome&&b.chrome.csi&&(a=Math.floor(b.chrome.cs…
  • Warning Line 7, Column 495: character "&" is the first character of a delimiter but occurred as data
    …_"))}try{a=null,b.chrome&&b.chrome.csi&&(a=Math.floor(b.chrome.csi().pageT),c&…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 7, Column 539: character "&" not allowed in attribute specification list
    …ath.floor(b.chrome.csi().pageT),c&&0<f&&(c[g]("_tbnd",void 0,b.chrome.csi().st…
  • Error Line 7, Column 539: element "f" undefined
    …ath.floor(b.chrome.csi().pageT),c&&0<f&&(c[g]("_tbnd",void 0,b.chrome.csi().st…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 7, Column 540: character "&" is the first character of a delimiter but occurred as data
    …th.floor(b.chrome.csi().pageT),c&&0<f&&(c[g]("_tbnd",void 0,b.chrome.csi().sta…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

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

  • Error Line 8, Column 36: general entity "b.gtbExternal" not defined and no default entity
    c[g]("tbnd_","_tbnd",f))),null==a&&b.gtbExternal&&(a=b.gtbExternal.pageT()),nul…

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

  • Warning Line 8, Column 49: reference not terminated by REFC delimiter
    …_","_tbnd",f))),null==a&&b.gtbExternal&&(a=b.gtbExternal.pageT()),null==a&&b.e…

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

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 8, Column 86: cannot generate system identifier for general entity "b.external"
    …l&&(a=b.gtbExternal.pageT()),null==a&&b.external&&(a=b.external.pageT,c&&0<f&&…

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

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

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

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

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

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

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

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

  • Error Line 8, Column 96: reference to entity "b.external" for which no system identifier could be generated
    …bExternal.pageT()),null==a&&b.external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tb…

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

  • Info Line 8, Column 85: entity was defined here
    …al&&(a=b.gtbExternal.pageT()),null==a&&b.external&&(a=b.external.pageT,c&&0<f&…
  • Warning Line 8, Column 96: character "&" is the first character of a delimiter but occurred as data
    …bExternal.pageT()),null==a&&b.external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tb…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 8, Column 124: character "&" not allowed in attribute specification list
    …b.external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tbnd",void 0,b.external.startE…
  • Error Line 8, Column 124: element "f" undefined
    …b.external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tbnd",void 0,b.external.startE…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 8, Column 125: character "&" is the first character of a delimiter but occurred as data
    ….external&&(a=b.external.pageT,c&&0<f&&(c[g]("_tbnd",void 0,b.external.startE)…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 8, Column 193: character "&" is the first character of a delimiter but occurred as data
    …al.startE),c[g]("tbnd_","_tbnd",f))),a&&(b[e].pt=a)}catch(l){}})();b.tickAbove…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 8, Column 194: character "&" is the first character of a delimiter but occurred as data
    …l.startE),c[g]("tbnd_","_tbnd",f))),a&&(b[e].pt=a)}catch(l){}})();b.tickAboveF…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 8, Column 329: character "&" is the first character of a delimiter but occurred as data
    …Top;while(d=d.offsetParent)}d=a;750>=d&&b[e].load[g]("aft")};var h=!1;function…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 8, Column 331: cannot generate system identifier for general entity "b"
    …p;while(d=d.offsetParent)}d=a;750>=d&&b[e].load[g]("aft")};var h=!1;function k…

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

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

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

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

  • Error Line 8, Column 331: general entity "b" not defined and no default entity
    …p;while(d=d.offsetParent)}d=a;750>=d&&b[e].load[g]("aft")};var h=!1;function k…

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

  • Warning Line 8, Column 332: reference not terminated by REFC delimiter
    …;while(d=d.offsetParent)}d=a;750>=d&&b[e].load[g]("aft")};var h=!1;function k(…

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

  • Error Line 8, Column 332: reference to entity "b" for which no system identifier could be generated
    …;while(d=d.offsetParent)}d=a;750>=d&&b[e].load[g]("aft")};var h=!1;function k(…

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

  • Info Line 8, Column 330: entity was defined here
    …op;while(d=d.offsetParent)}d=a;750>=d&&b[e].load[g]("aft")};var h=!1;function …
  • Error Line 9, Column 15: end tag for "f" omitted, but OMITTAG NO was specified
     })();</script>

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

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

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

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

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

  • Info Line 7, Column 377: start tag was here
    …=a.navigationStart,a=a.responseStart;0<f&&a>=f&&(c[g]("_wtsrt",void 0,f),c[g](…
  • Warning Line 36, Column 123: cannot generate system identifier for general entity "zx"
    ….css?targetBlogID=8116885351228484106&zx=10154025-c9a2-4d89-8bd8-81ea753a4f2a"…

    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 36, Column 123: general entity "zx" not defined and no default entity
    ….css?targetBlogID=8116885351228484106&zx=10154025-c9a2-4d89-8bd8-81ea753a4f2a"…

    This is usually a cascading error caused by 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 36, Column 125: reference not terminated by REFC delimiter
    …css?targetBlogID=8116885351228484106&zx=10154025-c9a2-4d89-8bd8-81ea753a4f2a"/>

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

  • Warning Line 36, Column 125: reference to external entity in attribute value
    …css?targetBlogID=8116885351228484106&zx=10154025-c9a2-4d89-8bd8-81ea753a4f2a"/>

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

  • Error Line 36, Column 125: reference to entity "zx" for which no system identifier could be generated
    …css?targetBlogID=8116885351228484106&zx=10154025-c9a2-4d89-8bd8-81ea753a4f2a"/>

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

  • Info Line 36, Column 122: entity was defined here
    …n.css?targetBlogID=8116885351228484106&zx=10154025-c9a2-4d89-8bd8-81ea753a4f2a…
  • Warning Line 38, Column 8: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 38, Column 12: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 38, Column 16: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 38, Column 20: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 38, Column 24: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 38, Column 28: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 38, Column 32: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 38, Column 36: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 38, Column 40: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 38, Column 44: multiple comments in comment declaration
    /* -----------------------------------------------
  • Warning Line 38, Column 48: multiple comments in comment declaration
    /* -----------------------------------------------
  • Error Line 38, Column 50: invalid comment declaration: found name character outside comment but inside comment declaration
    /* -----------------------------------------------
  • Info Line 37, Column 41: comment declaration started here
    <style id='page-skin-1' type='text/css'><!--
  • Error Line 47, 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 47, 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 48, 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 48, 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 48, 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 50, Column 28: element "Variable" undefined
    type="color" default="#444">

    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 52, 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 54, 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 56, 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 58, Column 28: element "Variable" undefined
    type="color" default="#c60">

    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 60, 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 62, 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 64, 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 66, 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 68, 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 71, 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 74, 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 77, 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 80, 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 82, 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 84, 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 259, 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 83, Column 1: start tag was here
    <Variable name="endSide" description="Side where text ends in blog language"
  • Error Line 259, 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 81, Column 1: start tag was here
    <Variable name="startSide" description="Side where text starts in blog language"
  • Error Line 259, 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 78, Column 1: start tag was here
    <Variable name="postfooterfont" description="Post Footer Font"
  • Error Line 259, 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 75, Column 1: start tag was here
    <Variable name="descriptionfont" description="Blog Description Font"
  • Error Line 259, 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 72, Column 1: start tag was here
    <Variable name="pagetitlefont" description="Blog Title Font"
  • Error Line 259, 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 69, Column 1: start tag was here
    <Variable name="headerfont" description="Sidebar Title Font"
  • Error Line 259, 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 67, Column 1: start tag was here
    <Variable name="bodyfont" description="Text Font"
  • Error Line 259, 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 65, Column 1: start tag was here
    <Variable name="visitedlinkcolor" description="Visited Link Color"
  • Error Line 259, 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 63, Column 1: start tag was here
    <Variable name="sidebartextcolor" description="Sidebar Text Color"
  • Error Line 259, 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 61, Column 1: start tag was here
    <Variable name="sidebarcolor" description="Sidebar Title Color"
  • Error Line 259, 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 59, Column 1: start tag was here
    <Variable name="bordercolor" description="Border Color"
  • Error Line 259, 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 57, Column 1: start tag was here
    <Variable name="titlecolor" description="Post Title Color"
  • Error Line 259, 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 55, Column 1: start tag was here
    <Variable name="descriptioncolor" description="Blog Description Color"
  • Error Line 259, 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 53, Column 1: start tag was here
    <Variable name="pagetitlecolor" description="Blog Title Color"
  • Error Line 259, 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 51, Column 1: start tag was here
    <Variable name="linkcolor" description="Link Color"
  • Error Line 259, 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 49, Column 1: start tag was here
    <Variable name="textcolor" description="Text Color"
  • Error Line 259, 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 47, Column 1: start tag was here
    <Variable name="bgcolor" description="Page Background Color"
  • Error Line 260, 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 295, Column 78: cannot generate system identifier for general entity "m"
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",k="?m=1";function…

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

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

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

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

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

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

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

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

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

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

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

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

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

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

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

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

  • Info Line 295, Column 394: entity was defined here
    …pera Mini")||-1!=a[b][c]("IEMobile")){var m=l();m&&window.location.replace(m)};
  • Error Line 314, Column 16: there is no attribute "border"
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=736 height=98…

    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 314, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=736 height=98…
  • Error Line 314, Column 30: there is no attribute "frameborder"
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=736 height=98…

    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 314, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=736 height=98…
  • Error Line 314, Column 45: there is no attribute "marginheight"
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=736 height=98 scro…

    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 314, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=736 height=98 scro…
  • Error Line 314, Column 59: there is no attribute "marginwidth"
    …meborder=0 marginheight=0 marginwidth=0 width=736 height=98 scrolling=no allow…

    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 314, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=736 height=98 scrolling=no allow…
  • Error Line 314, Column 67: there is no attribute "width"
    …=0 marginheight=0 marginwidth=0 width=736 height=98 scrolling=no allowtranspar…

    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 314, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=736 height=98 scrolling=no allowtranspar…
  • Error Line 314, Column 78: there is no attribute "height"
    …ight=0 marginwidth=0 width=736 height=98 scrolling=no allowtransparency=true s…

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

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

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

  • Error Line 314, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=736 height=98 scrolling=no allowtransparency=true s…
  • Error Line 314, Column 91: there is no attribute "scrolling"
    …width=0 width=736 height=98 scrolling=no allowtransparency=true src=http://ads…

    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 314, Column 91: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …width=0 width=736 height=98 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 314, Column 112: there is no attribute "allowtransparency"
    …ght=98 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/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 314, Column 112: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ght=98 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 314, Column 121: there is no attribute "src"
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…

    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 314, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 314, Column 127: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 314, Column 127: element "iframe" undefined
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 314, Column 183: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=184201></iframe>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 320, Column 83: cannot generate system identifier for general entity "widgetType"
    …/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=ed…

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

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

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

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

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

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

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

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

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

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

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

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

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

  • Warning Line 320, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page'…

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

  • Warning Line 320, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page'…

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

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

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

  • Info Line 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 320, Column 114: cannot generate system identifier for general entity "action"
    …484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' 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 320, Column 114: general entity "action" not defined and no default entity
    …484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' 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 320, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' 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 320, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' 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 320, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' 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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 320, Column 132: cannot generate system identifier for general entity "sectionId"
    …HTML&widgetId=HTML1&action=editWidget&sectionId=page' 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 320, Column 132: general entity "sectionId" not defined and no default entity
    …HTML&widgetId=HTML1&action=editWidget&sectionId=page' 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 320, Column 141: reference not terminated by REFC delimiter
    …etId=HTML1&action=editWidget&sectionId=page' 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 320, Column 141: reference to external entity in attribute value
    …etId=HTML1&action=editWidget&sectionId=page' 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 320, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML1&action=editWidget&sectionId=page' 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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 320, Column 235: there is no attribute "target"
    …Config(document.getElementById("HTML1"));' target='configHTML1' title='Editar'>

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

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

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

  • Error Line 422, Column 193: required attribute "alt" not specified
    …aed5d93805933f718969b1c80/38b221aaed5d93805933f718969b1c80.29.jpg" width="0" />

    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 423, Column 120: element "iframe" undefined
    …" src="http://flashservice.xvideos.com/embedframe/589603" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 424, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 447, Column 193: required attribute "alt" not specified
    …57c3660c33dbf3500d5/d3a29c03c634c57c3660c33dbf3500d5.29.jpg" width="0" /><br />

    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 449, Column 121: element "iframe" undefined
    …os.com/embedframe/3805013" width="690"></iframe><span style="font-size: large;…

    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 471, Column 192: required attribute "alt" not specified
    …2168759a7b84f105ddeec9bd6/f594f0b2168759a7b84f105ddeec9bd6.26.jpg" width="0" />

    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 472, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s.com/embedframe/1285423" frameborder=0 width=690 height=500 scrolling=no></if…
  • Error Line 472, Column 86: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …m/embedframe/1285423" frameborder=0 width=690 height=500 scrolling=no></iframe>
  • Error Line 472, Column 97: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …m/embedframe/1285423" frameborder=0 width=690 height=500 scrolling=no></iframe>
  • Error Line 472, Column 111: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …m/embedframe/1285423" frameborder=0 width=690 height=500 scrolling=no></iframe>
  • Error Line 472, Column 113: element "iframe" undefined
    …m/embedframe/1285423" frameborder=0 width=690 height=500 scrolling=no></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 473, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 495, Column 193: required attribute "alt" not specified
    …3cb3e9feadede4c31036318e5/46021173cb3e9feadede4c31036318e5.18.jpg" width="0" />

    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 496, Column 121: element "iframe" undefined
    … src="http://flashservice.xvideos.com/embedframe/3587399" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 497, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 518, Column 193: required attribute "alt" not specified
    …32913144360cc228ec52ce05b/1e3d5d432913144360cc228ec52ce05b.21.jpg" width="0" />

    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 519, Column 120: element "iframe" undefined
    …" src="http://flashservice.xvideos.com/embedframe/241018" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 520, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 543, Column 193: required attribute "alt" not specified
    …1e69447d0bb05988fb1/cb74d41cc303d1e69447d0bb05988fb1.22.jpg" width="0" /><br />

    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 545, Column 120: element "iframe" undefined
    …" src="http://flashservice.xvideos.com/embedframe/155959" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 546, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 567, Column 276: required attribute "alt" not specified
    …3034d0f096509b0ac2.10.jpg" width="0" /></a><iframe frameborder="0" height="500…

    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 567, Column 401: element "iframe" undefined
    …os.com/embedframe/2310121" width="690"></iframe><br /><b><span style="font-siz…

    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 588, Column 193: required attribute "alt" not specified
    …27a96b1f44a6b474a20aca002/177f5b127a96b1f44a6b474a20aca002.15.jpg" width="0" />

    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 589, Column 121: element "iframe" undefined
    …http://flashservice.xvideos.com/embedframe/1133146" width="690"></iframe></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 610, Column 193: required attribute "alt" not specified
    …ef86e170320606150d42e1125/c0bf93fef86e170320606150d42e1125.11.jpg" width="0" />

    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 612, Column 120: element "iframe" undefined
    …"http://flashservice.xvideos.com/embedframe/490803" width="690"></iframe></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 634, Column 193: required attribute "alt" not specified
    …f1196ead273592e732a/f73b9e75b90fbf1196ead273592e732a.12.jpg" width="0" /><br />

    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 635, Column 120: element "iframe" undefined
    …" src="http://flashservice.xvideos.com/embedframe/803781" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 656, Column 193: required attribute "alt" not specified
    …eb6ceead71540f30fb658df09/8a71b2feb6ceead71540f30fb658df09.26.jpg" width="0" />

    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 658, Column 121: element "iframe" undefined
    …http://flashservice.xvideos.com/embedframe/3882601" width="690"></iframe></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 679, Column 193: required attribute "alt" not specified
    …dfb96667bc80c2517b9f5e506/1094a5bdfb96667bc80c2517b9f5e506.17.jpg" width="0" />

    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 680, Column 121: element "iframe" undefined
    …os.com/embedframe/3909245" width="690"></iframe><b><span style="font-size: lar…

    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 682, Column 216: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 705, Column 192: required attribute "alt" not specified
    …f02dff563600c545c9b6a57d3/c5caa1ff02dff563600c545c9b6a57d3.16.jpg" width="0" />

    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 706, Column 120: element "iframe" undefined
    …" src="http://flashservice.xvideos.com/embedframe/418561" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 707, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 728, Column 193: required attribute "alt" not specified
    …34e5117ab50a385d7a9/4ec5267e05c4834e5117ab50a385d7a9.20.jpg" width="0" /><br />

    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 729, Column 121: element "iframe" undefined
    …http://flashservice.xvideos.com/embedframe/2559479" width="690"></iframe></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 749, Column 192: required attribute "alt" not specified
    …dd15ead1c3ac120840dd01d64/4c7aee1dd15ead1c3ac120840dd01d64.26.jpg" width="0" />

    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 751, Column 121: element "iframe" undefined
    … src="http://flashservice.xvideos.com/embedframe/3787282" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 752, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 777, Column 191: required attribute "alt" not specified
    …e6ed29c809e6670f64238b29d3/227391e6ed29c809e6670f64238b29d3.9.jpg" width="0" />

    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 778, Column 121: element "iframe" undefined
    … src="http://flashservice.xvideos.com/embedframe/3142444" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 779, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 800, Column 193: required attribute "alt" not specified
    …ad79e2ee96be679b310f0e45d/3af2c43ad79e2ee96be679b310f0e45d.24.jpg" width="0" />

    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 802, Column 121: element "iframe" undefined
    …http://flashservice.xvideos.com/embedframe/2741803" width="690"></iframe></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 823, Column 193: required attribute "alt" not specified
    …a74d0c32190aeac0ddf05b37b/6fed7dea74d0c32190aeac0ddf05b37b.26.jpg" width="0" />

    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 824, Column 120: element "iframe" undefined
    …" src="http://flashservice.xvideos.com/embedframe/691158" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 825, Column 213: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 847, Column 193: required attribute "alt" not specified
    …08844a212e94241e5429fddad/553471a08844a212e94241e5429fddad.20.jpg" width="0" />

    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 848, Column 121: element "iframe" undefined
    … src="http://flashservice.xvideos.com/embedframe/2955853" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 849, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 871, Column 193: required attribute "alt" not specified
    …efbb57c078c48407868e4b805/6339789efbb57c078c48407868e4b805.14.jpg" width="0" />

    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 872, Column 120: element "iframe" undefined
    …" src="http://flashservice.xvideos.com/embedframe/668783" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 873, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 895, Column 193: required attribute "alt" not specified
    …5ed847d12b2acd60c825b43a5/31af5cd5ed847d12b2acd60c825b43a5.29.jpg" width="0" />

    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 896, Column 121: element "iframe" undefined
    … src="http://flashservice.xvideos.com/embedframe/3835756" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 897, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 919, Column 276: required attribute "alt" not specified
    …d21f6c4ea196c20c/fb81cbc0b510e88bd21f6c4ea196c20c.8.jpg" width="0" /></a><br />

    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 921, Column 119: element "iframe" undefined
    …="http://flashservice.xvideos.com/embedframe/26948" width="690"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 944, Column 273: required attribute "alt" not specified
    …9f21f14433dcd851/ec69952d82ba3a579f21f14433dcd851.8.jpg" width="0" /></a><br />

    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 950, Column 120: element "iframe" undefined
    …"http://flashservice.xvideos.com/embedframe/521008" width="690"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 975, Column 276: required attribute "alt" not specified
    …76810b111d996d1aa9.12.jpg" width="0" /></a><br />Escandalo aconteceu em Roraim…

    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 975, Column 588: element "iframe" undefined
    …os.com/embedframe/2245770" width="690"></iframe><br /><span class="Apple-style…

    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 975, Column 983: there is no attribute "face"
    …pan></b></span><br /><br /><font face="Arial" style="font-size: 9pt" color="#F…

    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 975, Column 997: there is no attribute "style"
    …><br /><br /><font face="Arial" style="font-size: 9pt" color="#F4F4F4"><embed …

    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 975, Column 1020: there is no attribute "color"
    …="Arial" style="font-size: 9pt" color="#F4F4F4"><embed src="http://www.pornati…

    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 975, Column 1029: element "font" undefined
    …style="font-size: 9pt" color="#F4F4F4"><embed src="http://www.pornative.com/fl…

    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 975, Column 1041: there is no attribute "src"
    …size: 9pt" color="#F4F4F4"><embed src="http://www.pornative.com/flash/player_n…

    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 975, Column 1099: there is no attribute "FlashVars"
    …e.com/flash/player_new.swf" FlashVars="file=rtmp://file1.pornative.com:443/por…

    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 975, Column 1146: cannot generate system identifier for general entity "id"
    …p://file1.pornative.com:443/pornative&id=mp4:pornative1/2/6/267112/267112.mp4&…

    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 975, Column 1146: general entity "id" not defined and no default entity
    …p://file1.pornative.com:443/pornative&id=mp4:pornative1/2/6/267112/267112.mp4&…

    This is usually a cascading error caused by 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 975, Column 1148: reference not terminated by REFC delimiter
    …//file1.pornative.com:443/pornative&id=mp4:pornative1/2/6/267112/267112.mp4&au…

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

  • Warning Line 975, Column 1148: reference to external entity in attribute value
    …//file1.pornative.com:443/pornative&id=mp4:pornative1/2/6/267112/267112.mp4&au…

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

  • Error Line 975, Column 1148: reference to entity "id" for which no system identifier could be generated
    …//file1.pornative.com:443/pornative&id=mp4:pornative1/2/6/267112/267112.mp4&au…

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

  • Info Line 975, Column 1145: entity was defined here
    …mp://file1.pornative.com:443/pornative&id=mp4:pornative1/2/6/267112/267112.mp4…
  • Warning Line 975, Column 1186: cannot generate system identifier for general entity "autostart"
    …=mp4:pornative1/2/6/267112/267112.mp4&autostart=true&type=rtmp&image=&xmlurl=h…

    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 975, Column 1186: general entity "autostart" not defined and no default entity
    …=mp4:pornative1/2/6/267112/267112.mp4&autostart=true&type=rtmp&image=&xmlurl=h…

    This is usually a cascading error caused by 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 975, Column 1195: reference not terminated by REFC delimiter
    …ative1/2/6/267112/267112.mp4&autostart=true&type=rtmp&image=&xmlurl=http://glo…

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

  • Warning Line 975, Column 1195: reference to external entity in attribute value
    …ative1/2/6/267112/267112.mp4&autostart=true&type=rtmp&image=&xmlurl=http://glo…

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

  • Error Line 975, Column 1195: reference to entity "autostart" for which no system identifier could be generated
    …ative1/2/6/267112/267112.mp4&autostart=true&type=rtmp&image=&xmlurl=http://glo…

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

  • Info Line 975, Column 1185: entity was defined here
    …d=mp4:pornative1/2/6/267112/267112.mp4&autostart=true&type=rtmp&image=&xmlurl=…
  • Warning Line 975, Column 1201: cannot generate system identifier for general entity "type"
    …/2/6/267112/267112.mp4&autostart=true&type=rtmp&image=&xmlurl=http://globosexy…

    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 975, Column 1201: general entity "type" not defined and no default entity
    …/2/6/267112/267112.mp4&autostart=true&type=rtmp&image=&xmlurl=http://globosexy…

    This is usually a cascading error caused by 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 975, Column 1205: reference not terminated by REFC delimiter
    …/267112/267112.mp4&autostart=true&type=rtmp&image=&xmlurl=http://globosexy.com…

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

  • Warning Line 975, Column 1205: reference to external entity in attribute value
    …/267112/267112.mp4&autostart=true&type=rtmp&image=&xmlurl=http://globosexy.com…

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

  • Error Line 975, Column 1205: reference to entity "type" for which no system identifier could be generated
    …/267112/267112.mp4&autostart=true&type=rtmp&image=&xmlurl=http://globosexy.com…

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

  • Info Line 975, Column 1200: entity was defined here
    …1/2/6/267112/267112.mp4&autostart=true&type=rtmp&image=&xmlurl=http://globosex…
  • Warning Line 975, Column 1216: reference not terminated by REFC delimiter
    …112.mp4&autostart=true&type=rtmp&image=&xmlurl=http://globosexy.com=2349%26max…

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

  • Warning Line 975, Column 1218: cannot generate system identifier for general entity "xmlurl"
    …2.mp4&autostart=true&type=rtmp&image=&xmlurl=http://globosexy.com=2349%26maxit…

    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 975, Column 1218: general entity "xmlurl" not defined and no default entity
    …2.mp4&autostart=true&type=rtmp&image=&xmlurl=http://globosexy.com=2349%26maxit…

    This is usually a cascading error caused by 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 975, Column 1224: reference not terminated by REFC delimiter
    …autostart=true&type=rtmp&image=&xmlurl=http://globosexy.com=2349%26maxitems=2%…

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

  • Warning Line 975, Column 1224: reference to external entity in attribute value
    …autostart=true&type=rtmp&image=&xmlurl=http://globosexy.com=2349%26maxitems=2%…

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

  • Error Line 975, Column 1224: reference to entity "xmlurl" for which no system identifier could be generated
    …autostart=true&type=rtmp&image=&xmlurl=http://globosexy.com=2349%26maxitems=2%…

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

  • Info Line 975, Column 1217: entity was defined here
    …12.mp4&autostart=true&type=rtmp&image=&xmlurl=http://globosexy.com=2349%26maxi…
  • Error Line 975, Column 1322: there is no attribute "quality"
    …w.pornative.com%2F65832.html" quality="high" bgcolor="#000000" height="500" wi…

    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 975, Column 1337: there is no attribute "bgcolor"
    …%2F65832.html" quality="high" bgcolor="#000000" height="500" width="690" allow…

    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 975, Column 1354: there is no attribute "height"
    …ality="high" bgcolor="#000000" height="500" width="690" allowScriptAccess="alw…

    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 975, Column 1366: there is no attribute "width"
    … bgcolor="#000000" height="500" width="690" allowScriptAccess="always"  type="…

    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 975, Column 1390: there is no attribute "allowScriptAccess"
    …t="500" width="690" allowScriptAccess="always"  type="application/x-shockwave-…

    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 975, Column 1405: there is no attribute "type"
    …690" allowScriptAccess="always"  type="application/x-shockwave-flash" pluginsp…

    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 975, Column 1449: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 975, Column 1494: element "embed" undefined
    …/www.macromedia.com/go/getflashplayer"></font> <!--JuicyAds v2.0--><iframe all…

    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 975, Column 1501: end tag for "embed" omitted, but OMITTAG NO was specified
    …cromedia.com/go/getflashplayer"></font> <!--JuicyAds v2.0--><iframe allowtrans…

    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 975, Column 1030: start tag was here
    …tyle="font-size: 9pt" color="#F4F4F4"><embed src="http://www.pornative.com/fla…
  • Error Line 975, Column 1714: element "iframe" undefined
    …ds.com/adshow.php?adzone=184265" width="476"></iframe><!--JuicyAds END--></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 998, Column 193: required attribute "alt" not specified
    …adc1bde0805117ed1ea/f574c8491216cadc1bde0805117ed1ea.23.jpg" width="0" /><br />

    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 77: end tag for "param" omitted, but OMITTAG NO was specified
    …m name="allowfullscreen" value="true"><param name="AllowScriptAccess" value="a…

    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 999, Column 34: start tag was here
    <object height="500" width="690"><param name="allowfullscreen" value="true"><pa…
  • Error Line 999, Column 124: end tag for "param" omitted, but OMITTAG NO was specified
    …me="AllowScriptAccess" value="always"><param name="movie" value="http://embed.…

    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 999, Column 77: start tag was here
    …m name="allowfullscreen" value="true"><param name="AllowScriptAccess" value="a…
  • Error Line 999, Column 185: end tag for "param" omitted, but OMITTAG NO was specified
    …ue="http://embed.redtube.com/player/"><param name="FlashVars" value="id=267655…

    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 999, Column 124: start tag was here
    …me="AllowScriptAccess" value="always"><param name="movie" value="http://embed.…
  • Warning Line 999, Column 226: cannot generate system identifier for general entity "style"
    …ram name="FlashVars" value="id=267655&style=redtube&autostart=false"><embed sr…

    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 999, Column 226: general entity "style" not defined and no default entity
    …ram name="FlashVars" value="id=267655&style=redtube&autostart=false"><embed sr…

    This is usually a cascading error caused by 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 999, Column 231: reference not terminated by REFC delimiter
    …ame="FlashVars" value="id=267655&style=redtube&autostart=false"><embed src="ht…

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

  • Warning Line 999, Column 231: reference to external entity in attribute value
    …ame="FlashVars" value="id=267655&style=redtube&autostart=false"><embed src="ht…

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

  • Error Line 999, Column 231: reference to entity "style" for which no system identifier could be generated
    …ame="FlashVars" value="id=267655&style=redtube&autostart=false"><embed src="ht…

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

  • Info Line 999, Column 225: entity was defined here
    …aram name="FlashVars" value="id=267655&style=redtube&autostart=false"><embed s…
  • Warning Line 999, Column 249: reference not terminated by REFC delimiter
    …lue="id=267655&style=redtube&autostart=false"><embed src="http://embed.redtube…

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

  • Warning Line 999, Column 249: reference to external entity in attribute value
    …lue="id=267655&style=redtube&autostart=false"><embed src="http://embed.redtube…

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

  • Error Line 999, Column 249: reference to entity "autostart" for which no system identifier could be generated
    …lue="id=267655&style=redtube&autostart=false"><embed src="http://embed.redtube…

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

  • Info Line 975, Column 1185: entity was defined here
    …d=mp4:pornative1/2/6/267112/267112.mp4&autostart=true&type=rtmp&image=&xmlurl=…
  • Error Line 999, Column 257: end tag for "param" omitted, but OMITTAG NO was specified
    …267655&style=redtube&autostart=false"><embed src="http://embed.redtube.com/pla…

    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 999, Column 185: start tag was here
    …ue="http://embed.redtube.com/player/"><param name="FlashVars" value="id=267655…
  • Warning Line 999, Column 317: reference not terminated by REFC delimiter
    …ed.redtube.com/player/?id=267655&style=redtube" allowfullscreen="true" AllowSc…

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

  • Warning Line 999, Column 317: reference to external entity in attribute value
    …ed.redtube.com/player/?id=267655&style=redtube" allowfullscreen="true" AllowSc…

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

  • Error Line 999, Column 317: reference to entity "style" for which no system identifier could be generated
    …ed.redtube.com/player/?id=267655&style=redtube" allowfullscreen="true" AllowSc…

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

  • Info Line 999, Column 225: entity was defined here
    …aram name="FlashVars" value="id=267655&style=redtube&autostart=false"><embed s…
  • Error Line 999, Column 343: there is no attribute "allowfullscreen"
    …267655&style=redtube" allowfullscreen="true" AllowScriptAccess="always" flashv…

    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 999, Column 368: there is no attribute "AllowScriptAccess"
    …owfullscreen="true" AllowScriptAccess="always" flashvars="autostart=false" plu…

    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 999, Column 387: there is no attribute "flashvars"
    … AllowScriptAccess="always" flashvars="autostart=false" pluginspage="http://ww…

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

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

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

  • Error Line 999, Column 566: element "embed" undefined
    …type="application/x-shockwave-flash" height="500" width="690" /></object></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1020, Column 192: required attribute "alt" not specified
    …84817159863288a17179/fdb3d7a5545384817159863288a17179.8.jpg" width="0" /><br />

    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 1022, Column 120: element "iframe" undefined
    …" src="http://flashservice.xvideos.com/embedframe/467488" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1023, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1046, Column 193: required attribute "alt" not specified
    …6126bc3e70979dfe1b2/71379e5a95ed16126bc3e70979dfe1b2.28.jpg" width="0" /><br />

    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 1050, Column 119: element "iframe" undefined
    …="http://flashservice.xvideos.com/embedframe/45287" width="690"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1052, Column 120: element "iframe" undefined
    …" src="http://flashservice.xvideos.com/embedframe/240745" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1077, Column 192: required attribute "alt" not specified
    …37dfe6c4b7cbcf018212d04001/6ddcca37dfe6c4b7cbcf018212d04001.2.jpg" width="0" />

    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 1078, Column 121: element "iframe" undefined
    … src="http://flashservice.xvideos.com/embedframe/2601859" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1079, Column 213: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1101, Column 193: required attribute "alt" not specified
    …67806f483ed5c97880c538f64/5d34aaf67806f483ed5c97880c538f64.29.jpg" width="0" />

    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 1102, Column 121: element "iframe" undefined
    … src="http://flashservice.xvideos.com/embedframe/3454450" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1103, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1125, Column 193: required attribute "alt" not specified
    …e2d5e54c49f5e1fef4e7b382a/4f57e24e2d5e54c49f5e1fef4e7b382a.13.jpg" width="0" />

    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 1126, Column 121: element "iframe" undefined
    … src="http://flashservice.xvideos.com/embedframe/1811823" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1127, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1149, Column 193: required attribute "alt" not specified
    …4342e888b7f8f6b1197b61208/61b53574342e888b7f8f6b1197b61208.23.jpg" width="0" />

    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 1150, Column 121: element "iframe" undefined
    … src="http://flashservice.xvideos.com/embedframe/1144530" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1151, Column 212: element "iframe" undefined
    …p://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1172, Column 191: required attribute "alt" not specified
    …007d434c8c3caed3aed250e29b/27d143007d434c8c3caed3aed250e29b.7.jpg" width="0" />

    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 1173, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …os.com/embedframe/581122" frameborder=0 width=690 height=500 scrolling=no></if…
  • Error Line 1173, Column 85: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …om/embedframe/581122" frameborder=0 width=690 height=500 scrolling=no></iframe>
  • Error Line 1173, Column 96: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …om/embedframe/581122" frameborder=0 width=690 height=500 scrolling=no></iframe>
  • Error Line 1173, Column 110: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …om/embedframe/581122" frameborder=0 width=690 height=500 scrolling=no></iframe>
  • Error Line 1173, Column 112: element "iframe" undefined
    …om/embedframe/581122" frameborder=0 width=690 height=500 scrolling=no></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1175, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68…
  • Error Line 1175, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68…
  • Error Line 1175, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68 scro…
  • Error Line 1175, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=476 height=68 scrolling=no allow…
  • Error Line 1175, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=476 height=68 scrolling=no allowtranspar…
  • Error Line 1175, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=476 height=68 scrolling=no allowtransparency=true s…
  • Error Line 1175, Column 91: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …width=0 width=476 height=68 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 1175, Column 112: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ght=68 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 1175, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 1175, Column 127: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 1175, Column 127: element "iframe" undefined
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 1175, Column 183: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=184265></iframe>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1198, Column 193: required attribute "alt" not specified
    …a6490d5db7f470cdd62252c54/fe319dfa6490d5db7f470cdd62252c54.14.jpg" width="0" />

    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 1199, Column 121: element "iframe" undefined
    … src="http://flashservice.xvideos.com/embedframe/2468339" width="690"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1201, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68…
  • Error Line 1201, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68…
  • Error Line 1201, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68 scro…
  • Error Line 1201, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=476 height=68 scrolling=no allow…
  • Error Line 1201, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=476 height=68 scrolling=no allowtranspar…
  • Error Line 1201, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=476 height=68 scrolling=no allowtransparency=true s…
  • Error Line 1201, Column 91: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …width=0 width=476 height=68 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 1201, Column 112: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ght=68 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 1201, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 1201, Column 127: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 1201, Column 127: element "iframe" undefined
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 1201, Column 183: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=184265></iframe>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1223, Column 116: required attribute "alt" not specified
    …tive.com/3/4/340422/5.jpg" width="0" />Ela quer ser famosa igual a prima, dize…

    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 1223, Column 319: there is no attribute "allowscriptaccess"
    …-size: 9pt;"><embed allowscriptaccess="always" bgcolor="#000000" flashvars="fi…

    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 1223, Column 832: element "embed" undefined
    …layer_new.swf" type="application/x-shockwave-flash" width="690"></embed></span>

    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 1225, Column 192: element "iframe" undefined
    …c="http://adserver.juicyads.com/adshow.php?adzone=184265" width="476"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1247, Column 159: required attribute "alt" not specified
    …8eORK7qjE/UR2ceuOOBzI/AAAAAAAAOaU/kzIcZxtfM_M/s200/nat1.jpg" width="0" /><br />

    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 1249, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s.com/embedframe/2590621" frameborder=0 width=690 height=500 scrolling=no></if…
  • Error Line 1249, Column 86: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …m/embedframe/2590621" frameborder=0 width=690 height=500 scrolling=no></iframe>
  • Error Line 1249, Column 97: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …m/embedframe/2590621" frameborder=0 width=690 height=500 scrolling=no></iframe>
  • Error Line 1249, Column 111: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …m/embedframe/2590621" frameborder=0 width=690 height=500 scrolling=no></iframe>
  • Error Line 1249, Column 113: element "iframe" undefined
    …m/embedframe/2590621" frameborder=0 width=690 height=500 scrolling=no></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1250, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s.com/embedframe/3717191" frameborder=0 width=690 height=500 scrolling=no></if…
  • Error Line 1250, Column 86: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …bedframe/3717191" frameborder=0 width=690 height=500 scrolling=no></iframe></d…
  • Error Line 1250, Column 97: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …dframe/3717191" frameborder=0 width=690 height=500 scrolling=no></iframe></div>
  • Error Line 1250, Column 111: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …dframe/3717191" frameborder=0 width=690 height=500 scrolling=no></iframe></div>
  • Error Line 1250, Column 113: element "iframe" undefined
    …dframe/3717191" frameborder=0 width=690 height=500 scrolling=no></iframe></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1272, Column 193: required attribute "alt" not specified
    …96bfd62dd1931edd555/53385612b2e5396bfd62dd1931edd555.22.jpg" width="0" /><br />

    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 1300, Column 192: required attribute "alt" not specified
    …d7fb88d3907196271f6.8.jpg" width="0" />&nbsp;Assistente do Pragama: Melhor do …

    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 1300, Column 412: element "iframe" undefined
    …os.com/embedframe/3437084" width="690"></iframe><!--JuicyAds v2.0--><iframe al…

    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 1300, Column 633: element "iframe" undefined
    …ds.com/adshow.php?adzone=184265" width="476"></iframe><!--JuicyAds END--></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1321, Column 193: required attribute "alt" not specified
    …92619bd1c3ce8ea584.20.jpg" width="0" /><div>Larissa Riquelme nua, a musa da Co…

    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 1321, Column 353: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s.com/embedframe/2186733" frameborder=0 width=690 height=500 scrolling=no></if…
  • Error Line 1321, Column 361: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …bedframe/2186733" frameborder=0 width=690 height=500 scrolling=no></iframe><!-…
  • Error Line 1321, Column 372: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …86733" frameborder=0 width=690 height=500 scrolling=no></iframe><!--JuicyAds v…
  • Error Line 1321, Column 386: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rder=0 width=690 height=500 scrolling=no></iframe><!--JuicyAds v2.0--><iframe …
  • Error Line 1321, Column 388: element "iframe" undefined
    …er=0 width=690 height=500 scrolling=no></iframe><!--JuicyAds v2.0--><iframe al…

    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 1321, Column 609: element "iframe" undefined
    …ds.com/adshow.php?adzone=184265" width="476"></iframe><!--JuicyAds END--></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1343, Column 193: required attribute "alt" not specified
    …a3470c3889937c1d0e.14.jpg" width="0" /><iframe src="http://flashservice.xvideo…

    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 1343, Column 271: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s.com/embedframe/3727020" frameborder=0 width=690 height=500 scrolling=no></if…
  • Error Line 1343, Column 279: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …bedframe/3727020" frameborder=0 width=690 height=500 scrolling=no></iframe><!-…
  • Error Line 1343, Column 290: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …27020" frameborder=0 width=690 height=500 scrolling=no></iframe><!--JuicyAds v…
  • Error Line 1343, Column 304: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rder=0 width=690 height=500 scrolling=no></iframe><!--JuicyAds v2.0--><iframe …
  • Error Line 1343, Column 306: element "iframe" undefined
    …er=0 width=690 height=500 scrolling=no></iframe><!--JuicyAds v2.0--><iframe al…

    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 1343, Column 527: element "iframe" undefined
    …ds.com/adshow.php?adzone=184265" width="476"></iframe><!--JuicyAds END--></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1365, Column 192: required attribute "alt" not specified
    …fe2657e1ab974641038.9.jpg" width="0" /><br />Angelina Jolie nua e fazendo sexo…

    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 1365, Column 384: element "iframe" undefined
    …eos.com/embedframe/534211" width="690"></iframe><span style="font-size: large;…

    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 1387, Column 269: required attribute "alt" not specified
    …08fa039ff0e1c04864.17.jpg" width="0" /></a><br />Filme Completo, de A Escrava …

    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 1387, Column 510: element "iframe" undefined
    …os.com/embedframe/1124928" width="690"></iframe><!--JuicyAds v2.0--><iframe al…

    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 1387, Column 731: element "iframe" undefined
    …ds.com/adshow.php?adzone=184265" width="476"></iframe><!--JuicyAds END--></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1408, Column 274: required attribute "alt" not specified
    …b0b224b93c848d4d2d.20.jpg" width="0" /></a><br />Mirela Santos nua no DVD da P…

    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 1408, Column 523: element "iframe" undefined
    …os.com/embedframe/1500426" width="690"></iframe><br /><br /><span class="Apple…

    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 1431, Column 191: required attribute "alt" not specified
    …8cedc12304e36409662.6.jpg" width="0" />&nbsp;<iframe frameborder="0" height="4…

    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 1431, Column 318: element "iframe" undefined
    …os.com/embedframe/1477847" width="690"></iframe><!--JuicyAds v2.0--><iframe al…

    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 1431, Column 539: element "iframe" undefined
    …ds.com/adshow.php?adzone=184265" width="476"></iframe><!--JuicyAds END--></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1454, Column 193: required attribute "alt" not specified
    …93b9add71e0387c2a5.17.jpg" width="0" /><iframe src="http://flashservice.xvideo…

    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 1454, Column 270: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …os.com/embedframe/481993" frameborder=0 width=690 height=500 scrolling=no></if…
  • Error Line 1454, Column 278: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …mbedframe/481993" frameborder=0 width=690 height=500 scrolling=no></iframe><!-…
  • Error Line 1454, Column 289: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …81993" frameborder=0 width=690 height=500 scrolling=no></iframe><!--JuicyAds v…
  • Error Line 1454, Column 303: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rder=0 width=690 height=500 scrolling=no></iframe><!--JuicyAds v2.0--><iframe …
  • Error Line 1454, Column 305: element "iframe" undefined
    …er=0 width=690 height=500 scrolling=no></iframe><!--JuicyAds v2.0--><iframe al…

    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 1454, Column 526: element "iframe" undefined
    …ds.com/adshow.php?adzone=184265" width="476"></iframe><!--JuicyAds END--></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1475, Column 193: required attribute "alt" not specified
    …3e036064c5d03fde7b.29.jpg" width="0" /><iframe frameborder="0" height="440" sc…

    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 1475, Column 314: element "iframe" undefined
    …os.com/embedframe/3097624" width="690"></iframe><!--JuicyAds v2.0--><iframe al…

    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 1475, Column 535: element "iframe" undefined
    …ds.com/adshow.php?adzone=184265" width="476"></iframe><!--JuicyAds END--></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1496, Column 193: required attribute "alt" not specified
    …78ed51fedd73fe794b.19.jpg" width="0" /><br />Mayara Shelson, uma das mais gost…

    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 1496, Column 426: element "iframe" undefined
    …deos.com/embedframe/48369" width="690"></iframe><!--JuicyAds v2.0--><iframe al…

    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 1496, Column 647: element "iframe" undefined
    …ds.com/adshow.php?adzone=184265" width="476"></iframe><!--JuicyAds END--></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1518, Column 193: required attribute "alt" not specified
    …d4c1df3acc2fea27ec.14.jpg" width="0" /><iframe width="690" height="500" src="h…

    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 1518, Column 308: element "iframe" undefined
    …108210" frameborder="0" scrolling="no"></iframe><!--JuicyAds v2.0--><iframe al…

    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 1518, Column 529: element "iframe" undefined
    …ds.com/adshow.php?adzone=184265" width="476"></iframe><!--JuicyAds END--></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1539, Column 193: required attribute "alt" not specified
    …94d579d608c3cc893e.21.jpg" width="0" /><br />Vivi Fernandez nua e fazendo sexo…

    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 1540, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s.com/embedframe/3831880" frameborder=0 width=690 height=500 scrolling=no></if…
  • Error Line 1540, Column 86: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …m/embedframe/3831880" frameborder=0 width=690 height=500 scrolling=no></iframe>
  • Error Line 1540, Column 97: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …m/embedframe/3831880" frameborder=0 width=690 height=500 scrolling=no></iframe>
  • Error Line 1540, Column 111: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …m/embedframe/3831880" frameborder=0 width=690 height=500 scrolling=no></iframe>
  • Error Line 1540, Column 113: element "iframe" undefined
    …m/embedframe/3831880" frameborder=0 width=690 height=500 scrolling=no></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1541, Column 212: element "iframe" undefined
    …ds.com/adshow.php?adzone=184265" width="476"></iframe><!--JuicyAds END--></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1580, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML25&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 1580, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML25&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 1580, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML25&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1580, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML25&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 1580, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML25&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 1580, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML25&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1580, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML25&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 1580, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML25&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 1580, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML25&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1580, Column 142: reference not terminated by REFC delimiter
    …tId=HTML25&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 1580, Column 142: reference to external entity in attribute value
    …tId=HTML25&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 1580, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML25&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1589, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=13…
  • Error Line 1589, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=13…
  • Error Line 1589, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=136 scr…
  • Error Line 1589, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=476 height=136 scrolling=no allo…
  • Error Line 1589, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=476 height=136 scrolling=no allowtranspa…
  • Error Line 1589, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=476 height=136 scrolling=no allowtransparency=true …
  • Error Line 1589, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=476 height=136 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 1589, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=136 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 1589, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 1589, Column 128: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 1589, Column 128: element "iframe" undefined
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 1589, Column 184: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=172783></iframe>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 1595, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML21&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 1595, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML21&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 1595, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML21&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1595, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML21&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 1595, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML21&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 1595, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML21&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1595, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML21&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 1595, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML21&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 1595, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML21&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1595, Column 142: reference not terminated by REFC delimiter
    …tId=HTML21&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 1595, Column 142: reference to external entity in attribute value
    …tId=HTML21&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 1595, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML21&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Warning Line 1612, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML41&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 1612, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML41&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 1612, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML41&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1612, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML41&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 1612, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML41&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 1612, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML41&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1612, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML41&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 1612, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML41&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 1612, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML41&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1612, Column 142: reference not terminated by REFC delimiter
    …tId=HTML41&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 1612, Column 142: reference to external entity in attribute value
    …tId=HTML41&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 1612, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML41&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1622, Column 235: required attribute "alt" not specified
    …amas/paniconatv/fotos/GAL_3718/grandes/IFOT_35879.jpg" width="700" /></a></div>

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

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

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

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

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

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

  • Info Line 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1627, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=main' onclick='ret…

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

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

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

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

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

  • Info Line 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1627, Column 141: reference not terminated by REFC delimiter
    …etId=HTML9&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

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

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

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

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

  • Info Line 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1637, Column 211: required attribute "alt" not specified
    …pjs/UJXsosFzWPI/AAAAAAAAAG0/qafRb0Nb7Ys/s320/mulh.PNG" width="700" /></a></div>

    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 1642, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML31&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 1642, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML31&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 1642, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML31&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1642, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML31&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 1642, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML31&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 1642, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML31&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1642, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML31&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 1642, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML31&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 1642, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML31&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1642, Column 142: reference not terminated by REFC delimiter
    …tId=HTML31&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 1642, Column 142: reference to external entity in attribute value
    …tId=HTML31&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 1642, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML31&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1652, Column 198: required attribute "alt" not specified
    …00nRg/T5IZBPLUhzI/AAAAAAAAIeo/7Nq0NUOrwvo/s640/mi.jpg" width="700" /></a></div>

    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 1657, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML27&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 1657, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML27&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 1657, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML27&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1657, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML27&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 1657, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML27&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 1657, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML27&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1657, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML27&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 1657, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML27&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 1657, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML27&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1657, Column 142: reference not terminated by REFC delimiter
    …tId=HTML27&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 1657, Column 142: reference to external entity in attribute value
    …tId=HTML27&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 1657, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML27&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1667, Column 243: required attribute "alt" not specified
    …ShUd5mOuI/s640/Bruna-Ferraz-e-Pamela-Butt-Private.jpg" width="700" /></a></div>

    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 1672, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML32&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 1672, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML32&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 1672, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML32&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1672, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML32&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 1672, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML32&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 1672, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML32&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1672, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML32&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 1672, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML32&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 1672, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML32&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1672, Column 142: reference not terminated by REFC delimiter
    …tId=HTML32&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 1672, Column 142: reference to external entity in attribute value
    …tId=HTML32&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 1672, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML32&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1682, Column 222: required attribute "alt" not specified
    …bUes/T4T2WxLH64I/AAAAAAAAU_w/dl-z0U4ARhA/s640/001.jpg" width="700" /></a></div>

    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 1687, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&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 1687, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&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 1687, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1687, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML2&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 1687, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML2&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 1687, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML2&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1687, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML2&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 1687, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML2&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 1687, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML2&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1687, Column 141: reference not terminated by REFC delimiter
    …etId=HTML2&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 1687, Column 141: reference to external entity in attribute value
    …etId=HTML2&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 1687, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML2&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1697, Column 197: required attribute "alt" not specified
    …um.com/images/2010/05/19/roberthaportelafaustao12.jpg" width="700" /></a></div>

    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 1702, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML34&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 1702, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML34&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 1702, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML34&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1702, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML34&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 1702, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML34&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 1702, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML34&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1702, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML34&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 1702, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML34&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 1702, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML34&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1702, Column 142: reference not terminated by REFC delimiter
    …tId=HTML34&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 1702, Column 142: reference to external entity in attribute value
    …tId=HTML34&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 1702, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML34&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Warning Line 1715, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&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 1715, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&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 1715, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1715, Column 107: reference not terminated by REFC delimiter
    …5351228484106&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 1715, Column 107: reference to external entity in attribute value
    …5351228484106&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 1715, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1715, 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 1715, 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 1715, 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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1715, 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 1715, 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 1715, 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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1725, Column 232: required attribute "alt" not specified
    …AAAAdM/lXlGlI2k-CQ/s400/malastv-globosexy.com-001.jpg" width="700" /></a></div>

    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 1730, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML48&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 1730, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML48&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 1730, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML48&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1730, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML48&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 1730, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML48&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 1730, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML48&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1730, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML48&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 1730, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML48&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 1730, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML48&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1730, Column 142: reference not terminated by REFC delimiter
    …tId=HTML48&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 1730, Column 142: reference to external entity in attribute value
    …tId=HTML48&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 1730, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML48&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1740, Column 256: required attribute "alt" not specified
    …/s400/72217_Renata.Schmidt.DDGirls_2400_123_208lo.jpg" width="700" /></a></div>

    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 1745, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&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 1745, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&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 1745, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1745, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML10&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 1745, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML10&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 1745, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML10&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1745, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML10&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 1745, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML10&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 1745, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML10&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1745, Column 142: reference not terminated by REFC delimiter
    …tId=HTML10&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 1745, Column 142: reference to external entity in attribute value
    …tId=HTML10&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 1745, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML10&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1754, Column 53: there is no attribute "border"
    …//www.super.malastv.net/"><img border="0" src="http://3.bp.blogspot.com/-tCRAS…

    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 1754, Column 157: required attribute "alt" not specified
    …CRASOHSqwA/USU37Nd3uOI/AAAAAAAAAXI/1K0cWZvmrrM/s1600/malassss.PNG" /></a></div>

    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 1760, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML28&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 1760, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML28&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 1760, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML28&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1760, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML28&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 1760, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML28&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 1760, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML28&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1760, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML28&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 1760, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML28&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 1760, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML28&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1760, Column 142: reference not terminated by REFC delimiter
    …tId=HTML28&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 1760, Column 142: reference to external entity in attribute value
    …tId=HTML28&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 1760, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML28&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1785, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=258 height=25…
  • Error Line 1785, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=258 height=25…
  • Error Line 1785, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=258 height=258 scr…
  • Error Line 1785, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=258 height=258 scrolling=no allo…
  • Error Line 1785, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=258 height=258 scrolling=no allowtranspa…
  • Error Line 1785, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=258 height=258 scrolling=no allowtransparency=true …
  • Error Line 1785, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=258 height=258 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 1785, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=258 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 1785, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 1785, Column 128: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 1785, Column 128: element "iframe" undefined
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 1785, Column 184: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=184261></iframe>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 1791, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML15&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 1791, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML15&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 1791, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML15&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1791, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML15&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 1791, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML15&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 1791, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML15&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1791, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML15&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 1791, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML15&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 1791, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML15&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1791, Column 142: reference not terminated by REFC delimiter
    …tId=HTML15&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 1791, Column 142: reference to external entity in attribute value
    …tId=HTML15&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 1791, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML15&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Warning Line 1807, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML12&action=editWidget&…

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

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

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

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

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

  • Info Line 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1807, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML12&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 1807, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML12&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 1807, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML12&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1807, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML12&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 1807, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML12&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 1807, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML12&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1807, Column 142: reference not terminated by REFC delimiter
    …tId=HTML12&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 1807, Column 142: reference to external entity in attribute value
    …tId=HTML12&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 1807, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML12&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Warning Line 1821, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&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 1821, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&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 1821, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1821, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML19&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 1821, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML19&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 1821, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML19&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1821, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML19&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 1821, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML19&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 1821, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML19&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1821, Column 142: reference not terminated by REFC delimiter
    …tId=HTML19&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 1821, Column 142: reference to external entity in attribute value
    …tId=HTML19&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 1821, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML19&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1832, Column 227: required attribute "alt" not specified
    …MJyI/AAAAAAAAC9I/YXWbNkNID0Q/s320/malastv.net-001.jpg" width="250" /></a></div>

    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 1837, Column 224: required attribute "alt" not specified
    …yNQI/AAAAAAAAC28/s4h1BR4KAIc/s640/malastv.net-001.jpg" width="250" /></a></div>

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

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

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

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

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

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

  • Info Line 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1843, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML11&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 1843, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML11&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 1843, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML11&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1843, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML11&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 1843, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML11&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 1843, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML11&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1843, Column 142: reference not terminated by REFC delimiter
    …tId=HTML11&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 1843, Column 142: reference to external entity in attribute value
    …tId=HTML11&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 1843, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML11&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1852, Column 216: required attribute "alt" not specified
    …Oz0Oq1SHk/UPbCY9jV84I/AAAAAAAAAIY/YK0Zk-7U_gw/s200/fer1.jpg" width="250" /></a>

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

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

  • Warning Line 1857, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML17&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 1857, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML17&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 1857, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML17&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1857, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML17&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 1857, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML17&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 1857, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML17&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1857, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML17&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 1857, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML17&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 1857, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML17&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1857, Column 142: reference not terminated by REFC delimiter
    …tId=HTML17&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 1857, Column 142: reference to external entity in attribute value
    …tId=HTML17&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 1857, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML17&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1867, Column 230: required attribute "alt" not specified
    …My8I/AAAAAAAACzA/ZlCwR9SKpSo/s640/malastv.net-001.jpg" width="250" /></a></div>

    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 1872, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML47&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 1872, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML47&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 1872, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML47&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1872, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML47&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 1872, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML47&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 1872, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML47&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1872, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML47&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 1872, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML47&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 1872, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML47&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1872, Column 142: reference not terminated by REFC delimiter
    …tId=HTML47&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 1872, Column 142: reference to external entity in attribute value
    …tId=HTML47&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 1872, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML47&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Warning Line 1885, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&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 1885, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&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 1885, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1885, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=sideb…

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

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

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

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

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

  • Info Line 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1885, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=sidebar' onclick='…

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

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

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

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

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

  • Info Line 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1885, Column 141: reference not terminated by REFC delimiter
    …etId=HTML5&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

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

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

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

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

  • Info Line 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1894, Column 234: required attribute "alt" not specified
    …y5K_I/AAAAAAAACq0/gv0OB4bxMDs/s320/carine-felizardo-sx1.jpg" width="250" /></a>

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

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

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

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

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

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

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

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

  • Info Line 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1899, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=sidebar' onclick='…

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

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

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

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

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

  • Info Line 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1899, Column 141: reference not terminated by REFC delimiter
    …etId=HTML6&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

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

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

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

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

  • Info Line 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1909, Column 201: required attribute "alt" not specified
    …om/wp-content/uploads/2009/09/helen-ganzerolli-21.jpg" width="250" /></a><br />

    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 1910, Column 221: required attribute "alt" not specified
    …rQ/UPceKyjK7FI/AAAAAAAACj8/3myQ5t8sdu4/s200/malastv.net.jpg" width="250" /></a>

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

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

  • Warning Line 1915, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&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 1915, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&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 1915, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1915, Column 107: reference not terminated by REFC delimiter
    …5351228484106&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 1915, Column 107: reference to external entity in attribute value
    …5351228484106&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 1915, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1915, 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 1915, 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 1915, 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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1915, 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 1915, 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 1915, 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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Warning Line 1929, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&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 1929, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&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 1929, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1929, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML7&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 1929, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML7&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 1929, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML7&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1929, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML7&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 1929, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML7&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 1929, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML7&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1929, Column 141: reference not terminated by REFC delimiter
    …etId=HTML7&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 1929, Column 141: reference to external entity in attribute value
    …etId=HTML7&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 1929, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML7&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1940, Column 217: required attribute "alt" not specified
    …T6SoqrSL4AI/AAAAAAAAA6Q/TjVJQWDXA0I/s400/14758094.jpg" width="250" /></a></div>

    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 1946, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML29&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 1946, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML29&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 1946, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML29&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1946, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML29&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 1946, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML29&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 1946, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML29&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1946, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML29&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 1946, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML29&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 1946, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML29&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1946, Column 142: reference not terminated by REFC delimiter
    …tId=HTML29&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 1946, Column 142: reference to external entity in attribute value
    …tId=HTML29&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 1946, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML29&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1955, Column 263: required attribute "alt" not specified
    …sa-urach-bikini-strip-topless-in-miami-beach-04-675x900.jpg" width="250" /></a>

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

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

  • Warning Line 1960, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML45&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 1960, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML45&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 1960, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML45&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1960, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML45&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 1960, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML45&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 1960, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML45&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1960, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML45&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 1960, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML45&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 1960, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML45&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1960, Column 142: reference not terminated by REFC delimiter
    …tId=HTML45&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 1960, Column 142: reference to external entity in attribute value
    …tId=HTML45&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 1960, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML45&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1969, Column 214: required attribute "alt" not specified
    …/-jcg3VhwCz-k/TysFng6dpgI/AAAAAAAAAeM/LZHTDJ-uBzM/s200/an19" width="250" /></a>

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

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

  • Warning Line 1974, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML38&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 1974, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML38&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 1974, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML38&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1974, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML38&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 1974, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML38&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 1974, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML38&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1974, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML38&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 1974, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML38&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 1974, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML38&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1974, Column 142: reference not terminated by REFC delimiter
    …tId=HTML38&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 1974, Column 142: reference to external entity in attribute value
    …tId=HTML38&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 1974, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML38&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1983, Column 211: required attribute "alt" not specified
    …994xE/T_YN6YLVMqI/AAAAAAAAI0w/X1KwwPnArAM/s200/Capturar.JPG" width="250" /></a>

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

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

  • Warning Line 1988, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML43&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 1988, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML43&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 1988, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML43&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1988, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML43&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 1988, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML43&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 1988, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML43&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1988, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML43&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 1988, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML43&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 1988, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML43&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 1988, Column 142: reference not terminated by REFC delimiter
    …tId=HTML43&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 1988, Column 142: reference to external entity in attribute value
    …tId=HTML43&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 1988, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML43&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 1997, Column 221: required attribute "alt" not specified
    …iL3w/T6YqrnMliVI/AAAAAAAAA8A/GmSWMa50k7w/s320/Renatinha.jpg" width="250" /></a>

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

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

  • Warning Line 2002, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML16&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 2002, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML16&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 2002, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML16&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 2002, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML16&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 2002, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML16&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 2002, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML16&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 2002, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML16&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 2002, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML16&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 2002, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML16&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 2002, Column 142: reference not terminated by REFC delimiter
    …tId=HTML16&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 2002, Column 142: reference to external entity in attribute value
    …tId=HTML16&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 2002, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML16&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 2011, Column 226: required attribute "alt" not specified
    …Oh0lyAZt2I/AAAAAAAACbU/tyr0MDZBi88/s320/malastv.net-001.jpg" width="250" /></a>

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

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

  • Warning Line 2016, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML37&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 2016, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML37&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 2016, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML37&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 2016, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML37&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 2016, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML37&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 2016, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML37&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 2016, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML37&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 2016, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML37&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 2016, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML37&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 2016, Column 142: reference not terminated by REFC delimiter
    …tId=HTML37&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 2016, Column 142: reference to external entity in attribute value
    …tId=HTML37&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 2016, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML37&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 2025, Column 231: required attribute "alt" not specified
    …gLMIII/AAAAAAAAej4/aGeXM_ThgPg/s320/nathalia-rodrigues2.jpg" width="250" /></a>

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

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

  • Warning Line 2030, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML35&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 2030, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML35&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 2030, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML35&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 2030, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML35&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 2030, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML35&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 2030, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML35&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 2030, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML35&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 2030, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML35&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 2030, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML35&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 2030, Column 142: reference not terminated by REFC delimiter
    …tId=HTML35&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 2030, Column 142: reference to external entity in attribute value
    …tId=HTML35&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 2030, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML35&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 2039, Column 219: required attribute "alt" not specified
    …FGDGwEtvXI/AAAAAAAABkc/Zev-dGCWNi8/s320/malastv.net-001.jpg" width="250" /></a>

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

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

  • Warning Line 2044, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML18&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 2044, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML18&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 2044, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML18&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 2044, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML18&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 2044, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML18&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 2044, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML18&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 2044, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML18&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 2044, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML18&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 2044, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML18&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 2044, Column 142: reference not terminated by REFC delimiter
    …tId=HTML18&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 2044, Column 142: reference to external entity in attribute value
    …tId=HTML18&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 2044, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML18&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 2053, Column 227: required attribute "alt" not specified
    …JRLUiXnNoI/AAAAAAAAB2k/hj4d0kxEbYQ/s320/malastv.net-001.jpg" width="250" /></a>

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

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

  • Warning Line 2058, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML40&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 2058, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML40&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 2058, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML40&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 2058, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML40&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 2058, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML40&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 2058, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML40&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 2058, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML40&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 2058, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML40&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 2058, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML40&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 2058, Column 142: reference not terminated by REFC delimiter
    …tId=HTML40&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 2058, Column 142: reference to external entity in attribute value
    …tId=HTML40&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 2058, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML40&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 2067, Column 170: required attribute "alt" not specified
    …q4/UMuOscvlv3I/AAAAAAAAAK0/k8CyEsgRTYY/s320/iaryane_rep.jpg" width="250" /></a>

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

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

  • Warning Line 2072, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML24&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 2072, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML24&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 2072, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML24&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 2072, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML24&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 2072, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML24&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 2072, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML24&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 2072, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML24&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 2072, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML24&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 2072, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML24&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 2072, Column 142: reference not terminated by REFC delimiter
    …tId=HTML24&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 2072, Column 142: reference to external entity in attribute value
    …tId=HTML24&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 2072, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML24&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Error Line 2081, Column 216: required attribute "alt" not specified
    …C-1pPAw/UFoj9j5qtAI/AAAAAAAAkLY/Qeg-cRA_VjA/s320/WSXC01.jpg" width="250" /></a>

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

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

  • Warning Line 2086, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML30&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 2086, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML30&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 2086, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML30&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 2086, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML30&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 2086, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML30&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 2086, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML30&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 2086, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML30&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 2086, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML30&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 2086, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML30&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 2086, Column 142: reference not terminated by REFC delimiter
    …tId=HTML30&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 2086, Column 142: reference to external entity in attribute value
    …tId=HTML30&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 2086, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML30&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Warning Line 2100, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML36&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 2100, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML36&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 2100, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML36&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 2100, Column 107: reference not terminated by REFC delimiter
    …5351228484106&widgetType=HTML&widgetId=HTML36&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 2100, Column 107: reference to external entity in attribute value
    …5351228484106&widgetType=HTML&widgetId=HTML36&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 2100, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&widgetType=HTML&widgetId=HTML36&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 2100, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML36&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 2100, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML36&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 2100, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML36&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 2100, Column 142: reference not terminated by REFC delimiter
    …tId=HTML36&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 2100, Column 142: reference to external entity in attribute value
    …tId=HTML36&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 2100, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML36&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Warning Line 2250, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=Label&widgetId=Label1&action=editWidget…

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

  • Warning Line 2250, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=Label&widgetId=Label1&action=editWidget…

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

  • Error Line 2250, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=Label&widgetId=Label1&action=editWidget…

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

  • Info Line 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 2250, Column 108: reference not terminated by REFC delimiter
    …351228484106&widgetType=Label&widgetId=Label1&action=editWidget&sectionId=side…

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

  • Warning Line 2250, Column 108: reference to external entity in attribute value
    …351228484106&widgetType=Label&widgetId=Label1&action=editWidget&sectionId=side…

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

  • Error Line 2250, Column 108: reference to entity "widgetId" for which no system identifier could be generated
    …351228484106&widgetType=Label&widgetId=Label1&action=editWidget&sectionId=side…

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

  • Info Line 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 2250, Column 122: reference not terminated by REFC delimiter
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 2250, Column 122: reference to external entity in attribute value
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=sidebar' onclick='…

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

  • Error Line 2250, Column 122: reference to entity "action" for which no system identifier could be generated
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=sidebar' onclick='…

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

  • Info Line 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 2250, Column 143: reference not terminated by REFC delimiter
    …tId=Label1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 2250, Column 143: reference to external entity in attribute value
    …tId=Label1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Error Line 2250, Column 143: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Label1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Info Line 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Warning Line 2264, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&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 2264, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&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 2264, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 2264, Column 107: reference not terminated by REFC delimiter
    …5351228484106&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 2264, Column 107: reference to external entity in attribute value
    …5351228484106&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 2264, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …5351228484106&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 2264, 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 2264, 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 2264, 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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 2264, 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 2264, 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 2264, 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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Warning Line 2367, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=PopularPosts&widgetId=PopularPosts4&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 2367, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=PopularPosts&widgetId=PopularPosts4&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 2367, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=PopularPosts&widgetId=PopularPosts4&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 2367, Column 115: reference not terminated by REFC delimiter
    …84106&widgetType=PopularPosts&widgetId=PopularPosts4&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 2367, Column 115: reference to external entity in attribute value
    …84106&widgetType=PopularPosts&widgetId=PopularPosts4&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 2367, Column 115: reference to entity "widgetId" for which no system identifier could be generated
    …84106&widgetType=PopularPosts&widgetId=PopularPosts4&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 2367, Column 136: reference not terminated by REFC delimiter
    …larPosts&widgetId=PopularPosts4&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 2367, Column 136: reference to external entity in attribute value
    …larPosts&widgetId=PopularPosts4&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 2367, Column 136: reference to entity "action" for which no system identifier could be generated
    …larPosts&widgetId=PopularPosts4&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 2367, Column 157: reference not terminated by REFC delimiter
    …ularPosts4&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 2367, Column 157: reference to external entity in attribute value
    …ularPosts4&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 2367, Column 157: reference to entity "sectionId" for which no system identifier could be generated
    …ularPosts4&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Warning Line 2464, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&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 2464, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&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 2464, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 2464, Column 115: reference not terminated by REFC delimiter
    …84106&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 2464, Column 115: reference to external entity in attribute value
    …84106&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 2464, Column 115: reference to entity "widgetId" for which no system identifier could be generated
    …84106&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 2464, Column 136: reference not terminated by REFC delimiter
    …larPosts&widgetId=PopularPosts1&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 2464, Column 136: reference to external entity in attribute value
    …larPosts&widgetId=PopularPosts1&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 2464, Column 136: reference to entity "action" for which no system identifier could be generated
    …larPosts&widgetId=PopularPosts1&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 2464, Column 157: reference not terminated by REFC delimiter
    …ularPosts1&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 2464, Column 157: reference to external entity in attribute value
    …ularPosts1&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 2464, Column 157: reference to entity "sectionId" for which no system identifier could be generated
    …ularPosts1&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Warning Line 2562, Column 93: reference not terminated by REFC delimiter
    …?blogID=8116885351228484106&widgetType=PopularPosts&widgetId=PopularPosts3&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 2562, Column 93: reference to external entity in attribute value
    …?blogID=8116885351228484106&widgetType=PopularPosts&widgetId=PopularPosts3&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 2562, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=8116885351228484106&widgetType=PopularPosts&widgetId=PopularPosts3&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 320, Column 82: entity was defined here
    …m/rearrange?blogID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 2562, Column 115: reference not terminated by REFC delimiter
    …84106&widgetType=PopularPosts&widgetId=PopularPosts3&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 2562, Column 115: reference to external entity in attribute value
    …84106&widgetType=PopularPosts&widgetId=PopularPosts3&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 2562, Column 115: reference to entity "widgetId" for which no system identifier could be generated
    …84106&widgetType=PopularPosts&widgetId=PopularPosts3&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 320, Column 98: entity was defined here
    …ID=8116885351228484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 2562, Column 136: reference not terminated by REFC delimiter
    …larPosts&widgetId=PopularPosts3&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 2562, Column 136: reference to external entity in attribute value
    …larPosts&widgetId=PopularPosts3&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 2562, Column 136: reference to entity "action" for which no system identifier could be generated
    …larPosts&widgetId=PopularPosts3&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 320, Column 113: entity was defined here
    …8484106&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=page' oncli…
  • Warning Line 2562, Column 157: reference not terminated by REFC delimiter
    …ularPosts3&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 2562, Column 157: reference to external entity in attribute value
    …ularPosts3&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 2562, Column 157: reference to entity "sectionId" for which no system identifier could be generated
    …ularPosts3&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 320, Column 131: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=page' onclick='return _Widget…
  • Warning Line 2610, 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 2610, Column 50: character "&" is the first character of a delimiter but occurred as data
    …BLOG_attachCsiOnload) != 'undefined' && BLOG_attachCsiOnload != null) { window…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.

Visitor Analysis

Daily Visitor
  • 1.983 visits

In Page Analysis