dytoshare.us

Free Download Software Full Version ...

Display Widget for this domain on your website. Click Here
This data was last updated from 20-08-2013 06:04:10  (update).

Overview Info

  • Domain Name
    dytoshare.us
  • Favicon
  • Alexa Rank
    #29395
  • Google Page Rank
    PR 1
  • Ip Address
    108.162.198.93
  • Page Size
    143.8 KB
  • Images
    8 GIF, 3 JPG, 32 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 12 3 0 0 0

Website Meta Analysis



  • Title
    DYTOSHARE™ : Free Download Software Full Version
  • Meta Keyword
    Computer, Internet, PTC, Software, Download, Tips, Trik, Video, MP3, Antivirus, Berbagi File Gratis, Free Download, Crack, Keygen, Serial, License, Avira, Editing, Free, Movie, Games, Patch, Gratis, Office, Terbaru, Full, Full Version, Mediafire, hack, adsense, retail, tegal, cpns, terbaru, hosting, domain, tegal, download, sharing, center, SEO, Blog, Webmaster, multimedia, Tips Komputer, Meningkatkan kecepatan komputer, meningkatkan kecepatan internet, hack facebook, download crack, download serial, download keygen, free software full version, software terbaru, mediafire link, Tips SEO, Edit Video
  • Meta Description
    Free Download Software Full Version

Technical Analysis



  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.198.93
  • Domain Age
    2 Years, 2 Months, 8 days.
  • Javascript Library
    yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from dytoshare.us.

HTML Analysis

  • server: cloudflare-nginx
  • date: Tue, 20 Aug 2013 18:04:05 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • expires: Tue, 20 Aug 2013 18:04:05 GMT
  • cache-control: private, max-age=0
  • last-modified: Tue, 20 Aug 2013 13:30:16 GMT
  • x-content-type-options: nosniff
  • x-xss-protection: 1; mode=block
  • alternate-protocol: 80:quic,80:quic
  • cf-ray: a110103684205af
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for dytoshare.us

DNS Analysis


DNS servers
luckyhost.mercury.orderbox-dns.com
luckyhost.venus.orderbox-dns.com
luckyhost.mars.orderbox-dns.com
luckyhost.earth.orderbox-dns.com


DNS Records

Answer records
dytoshare.us MX
preference: 10
exchange: aspmx4.googlemail.com
38400s
dytoshare.us A 216.239.36.21 38400s
dytoshare.us MX
preference: 5
exchange: alt2.aspmx.l.google.com
38400s
dytoshare.us NS  luckyhost.earth.orderbox-dns.com 38400s
dytoshare.us A 216.239.32.21 38400s
dytoshare.us A 216.239.38.21 38400s
dytoshare.us TXT v=spf1 redirect=_spf.mailhostbox.com 38400s
dytoshare.us MX
preference: 1
exchange: aspmx.l.google.com
38400s
dytoshare.us MX
preference: 10
exchange: aspmx2.googlemail.com
38400s
dytoshare.us NS  luckyhost.venus.orderbox-dns.com 38400s
dytoshare.us A 216.239.34.21 38400s
dytoshare.us MX
preference: 10
exchange: aspmx5.googlemail.com
38400s
dytoshare.us MX
preference: 10
exchange: aspmx3.googlemail.com
38400s
dytoshare.us NS  luckyhost.mercury.orderbox-dns.com 38400s
dytoshare.us SOA
server: luckyhost.mercury.orderbox-dns.com
email: sandy@dyto.gmail.com
serial: 2012060501
refresh: 7200
retry: 7200
expire: 172800
minimum ttl: 7200
14400s
dytoshare.us NS  luckyhost.mars.orderbox-dns.com 38400s

Authority records

Additional records

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 303 Errors
  • 316 Warnings
Ratio Text/Html
  • 0.4483262035716711
Message Error
  • Warning Line 5, Column 264: character "&" is the first character of a delimiter but occurred as data
    …ming={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.performa…

    This message may appear in several cases:

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

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

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

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

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

  • Error Line 5, Column 266: general entity "a.performance.timing" not defined and no default entity
    …ng={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.performanc…

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

  • Warning Line 5, Column 286: reference not terminated by REFC delimiter
    …if(a.performance&&a.performance.timing){var g=a.performance.timing,j=a[b].load…

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

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

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

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

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

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

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

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

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

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

  • Error Line 5, Column 370: general entity "l" not defined and no default entity
    …avigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wts…

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

  • Warning Line 5, Column 371: reference not terminated by REFC delimiter
    …vigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wtsr…

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

  • Error Line 5, Column 371: reference to entity "l" for which no system identifier could be generated
    …vigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wtsr…

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

  • Info Line 5, Column 369: entity was defined here
    …navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wt…
  • Warning Line 5, Column 374: character "&" is the first character of a delimiter but occurred as data
    …ationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wtsrt_"…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

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

  • Error Line 6, Column 26: general entity "a.chrome.csi" not defined and no default entity
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

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

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

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

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

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

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

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

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

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

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

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

  • Error Line 6, Column 213: general entity "a.external" not defined and no default entity
    …l&&(m=a.gtbExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&…

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

  • Warning Line 6, Column 223: reference not terminated by REFC delimiter
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tb…

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

  • Error Line 6, Column 223: reference to entity "a.external" for which no system identifier could be generated
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tb…

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

  • Info Line 6, Column 212: entity was defined here
    …al&&(m=a.gtbExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&…
  • Warning Line 6, Column 223: character "&" is the first character of a delimiter but occurred as data
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tb…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

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

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

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

  • Warning Line 6, Column 455: reference not terminated by REFC delimiter
    …;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r(…

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

  • Error Line 6, Column 455: reference to entity "a" for which no system identifier could be generated
    …;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r(…

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

  • Info Line 6, Column 453: entity was defined here
    …op;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function …
  • Error Line 7, Column 15: end tag for "k" omitted, but OMITTAG NO was specified
     })();</script>

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

  • Info Line 6, Column 249: start tag was here
    …&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.external.star…
  • Error Line 7, Column 15: end tag for "k" omitted, but OMITTAG NO was specified
     })();</script>

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

  • Info Line 6, Column 80: start tag was here
    …=Math.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.chrome.csi().…
  • Error Line 7, Column 15: end tag for "k" omitted, but OMITTAG NO was specified
     })();</script>

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

  • Info Line 5, Column 366: start tag was here
    …=g.navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d](…
  • Warning Line 23, Column 264: character "&" is the first character of a delimiter but occurred as data
    …ming={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.performa…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 23, Column 286: reference not terminated by REFC delimiter
    …if(a.performance&&a.performance.timing){var g=a.performance.timing,j=a[b].load…

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

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

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

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

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 23, Column 371: reference not terminated by REFC delimiter
    …vigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wtsr…

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

  • Error Line 23, Column 371: reference to entity "l" for which no system identifier could be generated
    …vigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wtsr…

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

  • Info Line 5, Column 369: entity was defined here
    …navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wt…
  • Warning Line 23, Column 374: character "&" is the first character of a delimiter but occurred as data
    …ationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wtsrt_"…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 24, Column 38: reference not terminated by REFC delimiter
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

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

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 24, Column 223: reference not terminated by REFC delimiter
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tb…

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

  • Error Line 24, Column 223: reference to entity "a.external" for which no system identifier could be generated
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tb…

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

  • Info Line 6, Column 212: entity was defined here
    …al&&(m=a.gtbExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&…
  • Warning Line 24, Column 223: character "&" is the first character of a delimiter but occurred as data
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tb…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 24, Column 455: reference not terminated by REFC delimiter
    …;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r(…

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

  • Error Line 24, Column 455: reference to entity "a" for which no system identifier could be generated
    …;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r(…

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

  • Info Line 6, Column 453: entity was defined here
    …op;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function …
  • Error Line 25, Column 15: end tag for "k" omitted, but OMITTAG NO was specified
     })();</script>

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

  • Info Line 24, Column 249: start tag was here
    …&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.external.star…
  • Error Line 25, Column 15: end tag for "k" omitted, but OMITTAG NO was specified
     })();</script>

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

  • Info Line 24, Column 80: start tag was here
    …=Math.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.chrome.csi().…
  • Error Line 25, Column 15: end tag for "k" omitted, but OMITTAG NO was specified
     })();</script>

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

  • Info Line 23, Column 366: start tag was here
    …=g.navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d](…
  • Error Line 38, Column 15: there is no attribute "content"
    <META content='fa366f3fa73c9590' name='y_key'></META>

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

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

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

  • Error Line 38, Column 39: there is no attribute "name"
    <META content='fa366f3fa73c9590' name='y_key'></META>

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

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

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

  • Error Line 38, Column 46: element "META" undefined
    <META content='fa366f3fa73c9590' name='y_key'></META>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 41, Column 46: element "META" undefined
    <META content='c3502d527cda5d8a' name='y_key'></META>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 42, Column 7: document type does not allow element "title" here
    <title>DYTOSHARE</title>

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

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

  • Warning Line 56, Column 264: character "&" is the first character of a delimiter but occurred as data
    …ming={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.performa…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 56, Column 286: reference not terminated by REFC delimiter
    …if(a.performance&&a.performance.timing){var g=a.performance.timing,j=a[b].load…

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

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

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

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

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 56, Column 371: reference not terminated by REFC delimiter
    …vigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wtsr…

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

  • Error Line 56, Column 371: reference to entity "l" for which no system identifier could be generated
    …vigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wtsr…

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

  • Info Line 5, Column 369: entity was defined here
    …navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wt…
  • Warning Line 56, Column 374: character "&" is the first character of a delimiter but occurred as data
    …ationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wtsrt_"…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 57, Column 38: reference not terminated by REFC delimiter
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

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

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 57, Column 223: reference not terminated by REFC delimiter
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tb…

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

  • Error Line 57, Column 223: reference to entity "a.external" for which no system identifier could be generated
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tb…

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

  • Info Line 6, Column 212: entity was defined here
    …al&&(m=a.gtbExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&…
  • Warning Line 57, Column 223: character "&" is the first character of a delimiter but occurred as data
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tb…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 57, Column 455: reference not terminated by REFC delimiter
    …;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r(…

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

  • Error Line 57, Column 455: reference to entity "a" for which no system identifier could be generated
    …;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r(…

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

  • Info Line 6, Column 453: entity was defined here
    …op;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function …
  • Error Line 58, Column 15: end tag for "k" omitted, but OMITTAG NO was specified
     })();</script>

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

  • Info Line 57, Column 249: start tag was here
    …&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.external.star…
  • Error Line 58, Column 15: end tag for "k" omitted, but OMITTAG NO was specified
     })();</script>

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

  • Info Line 57, Column 80: start tag was here
    …=Math.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.chrome.csi().…
  • Error Line 58, Column 15: end tag for "k" omitted, but OMITTAG NO was specified
     })();</script>

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

  • Info Line 56, Column 366: start tag was here
    …=g.navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d](…
  • Error Line 71, Column 7: document type does not allow element "title" here
    <title>DYTOSHARE&#8482; : Free Download Software Full VersionDYTOSHARE | Free D…

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

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

  • Error Line 75, Column 7: document type does not allow element "title" here
    <title>DYTOSHARE&#8482; : Free Download Software Full Version</title>

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

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

  • Warning Line 99, Column 123: cannot generate system identifier for general entity "zx"
    ….css?targetBlogID=7968484805077137352&zx=98f99b91-4afc-4dda-8f90-131ae59d231e"…

    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 99, Column 123: general entity "zx" not defined and no default entity
    ….css?targetBlogID=7968484805077137352&zx=98f99b91-4afc-4dda-8f90-131ae59d231e"…

    This is usually a cascading error caused by 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 99, Column 125: reference not terminated by REFC delimiter
    …css?targetBlogID=7968484805077137352&zx=98f99b91-4afc-4dda-8f90-131ae59d231e"/>

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

  • Warning Line 99, Column 125: reference to external entity in attribute value
    …css?targetBlogID=7968484805077137352&zx=98f99b91-4afc-4dda-8f90-131ae59d231e"/>

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

  • Error Line 99, Column 125: reference to entity "zx" for which no system identifier could be generated
    …css?targetBlogID=7968484805077137352&zx=98f99b91-4afc-4dda-8f90-131ae59d231e"/>

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

  • Info Line 99, Column 122: entity was defined here
    …n.css?targetBlogID=7968484805077137352&zx=98f99b91-4afc-4dda-8f90-131ae59d231e…
  • Warning Line 102, Column 5: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 102, Column 9: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 102, Column 13: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 102, Column 17: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 102, Column 21: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 102, Column 25: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 102, Column 29: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 102, Column 33: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 102, Column 37: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 102, Column 41: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 102, Column 45: multiple comments in comment declaration
    -----------------------------------------------
  • Error Line 102, Column 47: invalid comment declaration: found name character outside comment but inside comment declaration
    -----------------------------------------------
  • Info Line 100, Column 41: comment declaration started here
    <style id='page-skin-1' type='text/css'><!--
  • Error Line 113, 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 113, Column 37: 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 114, 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 114, Column 21: 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 114, Column 27: 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 116, Column 27: 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 118, Column 27: 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 120, Column 27: 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 122, Column 27: 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 124, Column 27: 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 126, Column 27: 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 128, Column 27: 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 130, Column 27: 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 132, Column 30: element "Variable" undefined
    type="color"default="#f2f2f2">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 134, Column 55: 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 137, 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 140, 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 143, 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 146, 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 148, Column 31: 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 150, Column 32: 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 156, 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 149, Column 1: start tag was here
    <Variable name="endSide"description="Side where text ends in blog language"
  • Error Line 156, 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 147, Column 1: start tag was here
    <Variable name="startSide"description="Side where text starts in blog language"
  • Error Line 156, 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 144, Column 1: start tag was here
    <Variable name="postfooterfont"description="Post Footer Font"
  • Error Line 156, 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 141, Column 1: start tag was here
    <Variable name="descriptionfont"description="Blog Description Font"
  • Error Line 156, 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 138, Column 1: start tag was here
    <Variable name="pagetitlefont"description="Blog Title Font"
  • Error Line 156, 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 135, Column 1: start tag was here
    <Variable name="headerfont"description="Sidebar Title Font"
  • Error Line 156, 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 133, Column 1: start tag was here
    <Variable name="bodyfont"description="Text Font"
  • Error Line 156, 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 131, Column 1: start tag was here
    <Variable name="visitedlinkcolor"description="Visited Link Color"
  • Error Line 156, 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 129, Column 1: start tag was here
    <Variable name="sidebartextcolor"description="Sidebar Text Color"
  • Error Line 156, 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 127, Column 1: start tag was here
    <Variable name="sidebarcolor"description="Sidebar Title Color"
  • Error Line 156, 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 125, Column 1: start tag was here
    <Variable name="bordercolor"description="Border Color"
  • Error Line 156, 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 123, Column 1: start tag was here
    <Variable name="titlecolor"description="Post Title Color"
  • Error Line 156, 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 121, Column 1: start tag was here
    <Variable name="descriptioncolor"description="Blog Description Color"
  • Error Line 156, 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 119, Column 1: start tag was here
    <Variable name="pagetitlecolor"description="Blog Title Color"
  • Error Line 156, 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 117, Column 1: start tag was here
    <Variable name="linkcolor"description="Link Color"
  • Error Line 156, 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 115, Column 1: start tag was here
    <Variable name="textcolor"description="Text Color"
  • Error Line 156, 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 113, Column 1: start tag was here
    <Variable name="bgcolor"description="Page Background Color"
  • Error Line 548, Column 75: there is no attribute "property"
    …ontent='DYTOSHARE™ : Free Download Software Full Version' property='og:title'/>

    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 557, Column 72: character data is not allowed here
    <meta content='https://facebook.com/1786734729' property='fb:admins'/> >

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 559, Column 80: cannot generate system identifier for general entity "m"
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function…

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

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

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

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

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

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

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

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

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

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

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

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

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

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

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

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

  • Info Line 559, Column 396: entity was defined here
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};
  • Error Line 563, Column 19: there is no attribute "ondragstart"
    <body ondragstart='return false' onselectstart='return false' style='-moz-user-…

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

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

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

  • Error Line 563, Column 48: there is no attribute "onselectstart"
    …ragstart='return false' onselectstart='return false' style='-moz-user-select: …

    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 565, Column 8: required attribute "type" not specified
    <script> 

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

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

  • Warning Line 595, Column 30: character "&" is the first character of a delimiter but occurred as data
              if (window.iframes && iframes.open) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 595, Column 31: character "&" is the first character of a delimiter but occurred as data
              if (window.iframes && iframes.open) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 646, Column 83: cannot generate system identifier for general entity "widgetType"
    …/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&a…

    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 646, Column 83: general entity "widgetType" not defined and no default entity
    …/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&a…

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

  • Warning Line 646, Column 93: reference not terminated by REFC delimiter
    …?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&action=edit…

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

  • Warning Line 646, Column 93: reference to external entity in attribute value
    …?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&action=edit…

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

  • Error Line 646, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&action=edit…

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

  • Info Line 646, Column 82: entity was defined here
    …m/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&…
  • Warning Line 646, Column 103: cannot generate system identifier for general entity "widgetId"
    …68484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&sec…

    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 646, Column 103: general entity "widgetId" not defined and no default entity
    …68484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&sec…

    This is usually a cascading error caused by 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 646, Column 111: reference not terminated by REFC delimiter
    …077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=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 646, Column 111: reference to external entity in attribute value
    …077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=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 646, Column 111: reference to entity "widgetId" for which no system identifier could be generated
    …077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=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 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 646, Column 122: cannot generate system identifier for general entity "action"
    …idgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmenu…

    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 646, Column 122: general entity "action" not defined and no default entity
    …idgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmenu…

    This is usually a cascading error caused by 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 646, Column 128: reference not terminated by REFC delimiter
    …ype=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog'…

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

  • Warning Line 646, Column 128: reference to external entity in attribute value
    …ype=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog'…

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

  • Error Line 646, Column 128: reference to entity "action" for which no system identifier could be generated
    …ype=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog'…

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

  • Info Line 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 646, Column 140: cannot generate system identifier for general entity "sectionId"
    …&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='re…

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

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

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

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

  • Error Line 646, Column 140: general entity "sectionId" not defined and no default entity
    …&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='re…

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

  • Warning Line 646, Column 149: reference not terminated by REFC delimiter
    …=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='return _Wid…

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

  • Warning Line 646, Column 149: reference to external entity in attribute value
    …=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='return _Wid…

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

  • Error Line 646, Column 149: reference to entity "sectionId" for which no system identifier could be generated
    …=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='return _Wid…

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

  • Info Line 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Error Line 646, Column 260: there is no attribute "target"
    …(document.getElementById("PageList1"));' target='configPageList1' title='Edit'>

    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 658, Column 179: required attribute "alt" not specified
    …zlUkbRpyI/AAAAAAAABTs/emARtiSaUI4/s000/rss.png' style='margin:0 2px 0 0;'/></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>.

  • Error Line 659, Column 233: required attribute "alt" not specified
    …0/facebook.png' style='margin:0 2px 0 0; ' title='Follow me on Facebook!'/></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>.

  • Error Line 660, Column 229: required attribute "alt" not specified
    …000/twitter.png' style='margin:0 2px 0 0; ' title='Follow me on Twitter!'/></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>.

  • Error Line 664, Column 21: required attribute "type" not specified
    <script id='_wauxdz'>var _wau = _wau || []; _wau.push(["small", "fqz7wx5se4nr",…

    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 688, Column 83: there is no attribute "border"
    …dytoshare.us/'><img alt='Home' border='0' id='BLOGGER_PHOTO_ID_564667790263029…

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

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

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

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

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

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

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

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

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

  • Info Line 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 868, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=crosscol' 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 868, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=crosscol' 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 868, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=crosscol' 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 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 868, Column 141: reference not terminated by REFC delimiter
    …etId=HTML5&action=editWidget&sectionId=crosscol' onclick='return _WidgetManage…

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

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

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

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

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

  • Info Line 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Error Line 880, Column 15: element "center" undefined
    <p></p><center><a href="http://www.riksdark.web.id/2012/12/os-windows-software.…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 880, Column 216: required attribute "alt" not specified
    …PFax1ndhLI/AAAAAAAABTM/cg4hB46xkc8/s1600/Banner+ads+A+Win8.gif" /></a></center>

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

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

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

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

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

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

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

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

  • Info Line 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 885, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=sidebarleft' oncli…

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

  • Warning Line 885, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=sidebarleft' oncli…

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

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

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

  • Info Line 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 885, Column 141: reference not terminated by REFC delimiter
    …etId=HTML9&action=editWidget&sectionId=sidebarleft' onclick='return _WidgetMan…

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

  • Warning Line 885, Column 141: reference to external entity in attribute value
    …etId=HTML9&action=editWidget&sectionId=sidebarleft' onclick='return _WidgetMan…

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

  • Error Line 885, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML9&action=editWidget&sectionId=sidebarleft' onclick='return _WidgetMan…

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

  • Info Line 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Warning Line 962, Column 93: reference not terminated by REFC delimiter
    …?blogID=7968484805077137352&widgetType=Label&widgetId=Label2&action=editWidget…

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

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

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

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

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

  • Info Line 646, Column 82: entity was defined here
    …m/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&…
  • Warning Line 962, Column 108: reference not terminated by REFC delimiter
    …805077137352&widgetType=Label&widgetId=Label2&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 962, Column 108: reference to external entity in attribute value
    …805077137352&widgetType=Label&widgetId=Label2&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 962, Column 108: reference to entity "widgetId" for which no system identifier could be generated
    …805077137352&widgetType=Label&widgetId=Label2&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 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 962, Column 122: reference not terminated by REFC delimiter
    …idgetType=Label&widgetId=Label2&action=editWidget&sectionId=sidebarleft' oncli…

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

  • Warning Line 962, Column 122: reference to external entity in attribute value
    …idgetType=Label&widgetId=Label2&action=editWidget&sectionId=sidebarleft' oncli…

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

  • Error Line 962, Column 122: reference to entity "action" for which no system identifier could be generated
    …idgetType=Label&widgetId=Label2&action=editWidget&sectionId=sidebarleft' oncli…

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

  • Info Line 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 962, Column 143: reference not terminated by REFC delimiter
    …tId=Label2&action=editWidget&sectionId=sidebarleft' onclick='return _WidgetMan…

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

  • Warning Line 962, Column 143: reference to external entity in attribute value
    …tId=Label2&action=editWidget&sectionId=sidebarleft' onclick='return _WidgetMan…

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

  • Error Line 962, Column 143: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Label2&action=editWidget&sectionId=sidebarleft' onclick='return _WidgetMan…

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

  • Info Line 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Error Line 972, Column 15: element "center" undefined
    <p></p><center><a href="http://dhanietronik.blogspot.com/" target="_blank"><img…

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

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

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

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

  • Warning Line 977, Column 93: reference not terminated by REFC delimiter
    …?blogID=7968484805077137352&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 977, Column 93: reference to external entity in attribute value
    …?blogID=7968484805077137352&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 977, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7968484805077137352&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 646, Column 82: entity was defined here
    …m/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&…
  • Warning Line 977, Column 107: reference not terminated by REFC delimiter
    …4805077137352&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 977, Column 107: reference to external entity in attribute value
    …4805077137352&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 977, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …4805077137352&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 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 977, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=sidebarleft' oncli…

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

  • Warning Line 977, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=sidebarleft' oncli…

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

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

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

  • Info Line 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 977, Column 142: reference not terminated by REFC delimiter
    …tId=HTML11&action=editWidget&sectionId=sidebarleft' onclick='return _WidgetMan…

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

  • Warning Line 977, Column 142: reference to external entity in attribute value
    …tId=HTML11&action=editWidget&sectionId=sidebarleft' onclick='return _WidgetMan…

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

  • Error Line 977, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML11&action=editWidget&sectionId=sidebarleft' onclick='return _WidgetMan…

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

  • Info Line 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Warning Line 993, Column 93: reference not terminated by REFC delimiter
    …?blogID=7968484805077137352&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 993, Column 93: reference to external entity in attribute value
    …?blogID=7968484805077137352&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 993, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7968484805077137352&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 646, Column 82: entity was defined here
    …m/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&…
  • Warning Line 993, Column 107: reference not terminated by REFC delimiter
    …4805077137352&widgetType=HTML&widgetId=HTML7&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 993, Column 107: reference to external entity in attribute value
    …4805077137352&widgetType=HTML&widgetId=HTML7&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 993, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …4805077137352&widgetType=HTML&widgetId=HTML7&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 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 993, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML7&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 993, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML7&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 993, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML7&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 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 993, Column 141: reference not terminated by REFC delimiter
    …etId=HTML7&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 993, Column 141: reference to external entity in attribute value
    …etId=HTML7&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 993, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML7&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 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Error Line 1010, Column 100: required attribute "alt" not specified
    ….blogspot.com/-2lLi4jQfNRQ/TgzlYzNFWfI/AAAAAAAABUQ/OvZZUInOpnI/s000/date.png'/>

    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 1012, Column 100: required attribute "alt" not specified
    ….blogspot.com/-8yo_CE56-IE/TgzlZPRUytI/AAAAAAAABUU/hgSO1cpJeM0/s000/user.png'/>

    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 1015, Column 112: required attribute "alt" not specified
    …m/-dpr10ZQkr_M/T-FiwiE7i4I/AAAAAAAAGpM/jG5bEr5pA58/s1600/commentfb-ds.us.png'/>

    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 1016, Column 110: there is no attribute "href"
    …html#fb-root'><fb:comments-count href='http://www.dytoshare.us/2013/02/aquariu…

    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 1016, Column 178: element "fb:comments-count" undefined
    …/2013/02/aquarium-deskop-3-3-pack-full.html'></fb:comments-count> Comments </a>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1021, Column 121: cannot generate system identifier for general entity "postID"
    …are-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email'…

    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 1021, Column 121: general entity "postID" not defined and no default entity
    …are-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email'…

    This is usually a cascading error caused by 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 1021, Column 127: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=email' targe…

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

  • Warning Line 1021, Column 127: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=email' targe…

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

  • Error Line 1021, Column 127: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=email' targe…

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

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1021, Column 148: cannot generate system identifier for general entity "target"
    …5077137352&postID=4558188668692067666&target=email' target='_blank' title='Kir…

    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 1021, Column 148: general entity "target" not defined and no default entity
    …5077137352&postID=4558188668692067666&target=email' target='_blank' title='Kir…

    This is usually a cascading error caused by 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 1021, Column 154: reference not terminated by REFC delimiter
    …7352&postID=4558188668692067666&target=email' target='_blank' title='Kirimkan …

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

  • Warning Line 1021, Column 154: reference to external entity in attribute value
    …7352&postID=4558188668692067666&target=email' target='_blank' title='Kirimkan …

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

  • Error Line 1021, Column 154: reference to entity "target" for which no system identifier could be generated
    …7352&postID=4558188668692067666&target=email' target='_blank' title='Kirimkan …

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Warning Line 1023, Column 126: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=blog' onclic…

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

  • Warning Line 1023, Column 126: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=blog' onclic…

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

  • Error Line 1023, Column 126: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=blog' 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.

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1023, Column 153: reference not terminated by REFC delimiter
    …7352&postID=4558188668692067666&target=blog' onclick='window.open(this.href, "…

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

  • Warning Line 1023, Column 153: reference to external entity in attribute value
    …7352&postID=4558188668692067666&target=blog' onclick='window.open(this.href, "…

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

  • Error Line 1023, Column 153: reference to entity "target" for which no system identifier could be generated
    …7352&postID=4558188668692067666&target=blog' onclick='window.open(this.href, "…

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Warning Line 1025, Column 129: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=twitter' tar…

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

  • Warning Line 1025, Column 129: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=twitter' tar…

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

  • Error Line 1025, Column 129: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=twitter' tar…

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

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1025, Column 156: reference not terminated by REFC delimiter
    …7352&postID=4558188668692067666&target=twitter' target='_blank' title='Berbagi…

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

  • Warning Line 1025, Column 156: reference to external entity in attribute value
    …7352&postID=4558188668692067666&target=twitter' target='_blank' title='Berbagi…

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

  • Error Line 1025, Column 156: reference to entity "target" for which no system identifier could be generated
    …7352&postID=4558188668692067666&target=twitter' target='_blank' title='Berbagi…

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Warning Line 1027, Column 130: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=facebook' on…

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

  • Warning Line 1027, Column 130: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=facebook' on…

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

  • Error Line 1027, Column 130: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=facebook' on…

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

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1027, Column 157: reference not terminated by REFC delimiter
    …7352&postID=4558188668692067666&target=facebook' onclick='window.open(this.hre…

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

  • Warning Line 1027, Column 157: reference to external entity in attribute value
    …7352&postID=4558188668692067666&target=facebook' onclick='window.open(this.hre…

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

  • Error Line 1027, Column 157: reference to entity "target" for which no system identifier could be generated
    …7352&postID=4558188668692067666&target=facebook' onclick='window.open(this.hre…

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Warning Line 1029, Column 126: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=buzz' onclic…

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

  • Warning Line 1029, Column 126: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=buzz' onclic…

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

  • Error Line 1029, Column 126: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=4558188668692067666&target=buzz' 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.

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1029, Column 153: reference not terminated by REFC delimiter
    …7352&postID=4558188668692067666&target=buzz' onclick='window.open(this.href, "…

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

  • Warning Line 1029, Column 153: reference to external entity in attribute value
    …7352&postID=4558188668692067666&target=buzz' onclick='window.open(this.href, "…

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

  • Error Line 1029, Column 153: reference to entity "target" for which no system identifier could be generated
    …7352&postID=4558188668692067666&target=buzz' onclick='window.open(this.href, "…

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Error Line 1032, Column 66: there is no attribute "source"
    …ck dummy-container'><g:plusone source='blogger:blog:plusone' href='http://www.…

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

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

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

  • Error Line 1032, Column 94: there is no attribute "href"
    …ne source='blogger:blog:plusone' href='http://www.dytoshare.us/2013/02/aquariu…

    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 1032, Column 168: there is no attribute "size"
    …arium-deskop-3-3-pack-full.html' size='medium' width='300' annotation='inline'…

    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 1032, Column 183: there is no attribute "width"
    …eskop-3-3-pack-full.html' size='medium' width='300' annotation='inline'/></div>

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

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

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

  • Error Line 1032, Column 200: there is no attribute "annotation"
    …eskop-3-3-pack-full.html' size='medium' width='300' annotation='inline'/></div>

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

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

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

  • Error Line 1032, Column 209: element "g:plusone" undefined
    …eskop-3-3-pack-full.html' size='medium' width='300' annotation='inline'/></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 1034, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary4558188668692067666'>

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

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

  • Error Line 1036, Column 133: there is no attribute "imageanchor"
    …uarium_View_1280x800.jpg" imageanchor="1" style="clear: left; float: left; mar…

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

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

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

  • Error Line 1036, Column 418: required attribute "alt" not specified
    …8/eOxiOmeHi2A/s200/ws_Aquarium_View_1280x800.jpg" width="125"></span></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 1036, Column 425: end tag for "img" omitted, but OMITTAG NO was specified
    …8/eOxiOmeHi2A/s200/ws_Aquarium_View_1280x800.jpg" width="125"></span></a></div>

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

  • Info Line 1036, Column 263: start tag was here
    …nt-family: Trebuchet MS, sans-serif;"><img border="0" height="125" src="http:/…
  • Error Line 1037, Column 402: end tag for "br" omitted, but OMITTAG NO was specified
    …an lain-lain. Dijamin aplikasi ini akan menambah segar desktop anda!</span><br>

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

  • Info Line 1037, Column 398: start tag was here
    …an lain-lain. Dijamin aplikasi ini akan menambah segar desktop anda!</span><br>
  • Error Line 1038, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 1038, Column 1: start tag was here
    <br>
  • Error Line 1041, Column 124: required attribute "alt" not specified
    …AAAAABUc/V0SjgyoVO-c/s000/folder.png'/> Posted in:  <a href='http://www.dytosh…

    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 1054, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7968484805077137352&postID=4558188668692067666&from=pencil' title=…

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

  • Warning Line 1054, Column 78: reference to external entity in attribute value
    …it.g?blogID=7968484805077137352&postID=4558188668692067666&from=pencil' title=…

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

  • Error Line 1054, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7968484805077137352&postID=4558188668692067666&from=pencil' title=…

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

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1054, Column 99: cannot generate system identifier for general entity "from"
    …7968484805077137352&postID=4558188668692067666&from=pencil' title='Edit Entri'>

    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 1054, Column 99: general entity "from" not defined and no default entity
    …7968484805077137352&postID=4558188668692067666&from=pencil' title='Edit Entri'>

    This is usually a cascading error caused by 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 1054, Column 103: reference not terminated by REFC delimiter
    …7968484805077137352&postID=4558188668692067666&from=pencil' title='Edit Entri'>

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

  • Warning Line 1054, Column 103: reference to external entity in attribute value
    …7968484805077137352&postID=4558188668692067666&from=pencil' title='Edit Entri'>

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

  • Error Line 1054, Column 103: reference to entity "from" for which no system identifier could be generated
    …7968484805077137352&postID=4558188668692067666&from=pencil' title='Edit Entri'>

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

  • Info Line 1054, Column 98: entity was defined here
    …7968484805077137352&postID=4558188668692067666&from=pencil' title='Edit Entri'>
  • Error Line 1069, Column 100: required attribute "alt" not specified
    ….blogspot.com/-2lLi4jQfNRQ/TgzlYzNFWfI/AAAAAAAABUQ/OvZZUInOpnI/s000/date.png'/>

    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 1071, Column 100: required attribute "alt" not specified
    ….blogspot.com/-8yo_CE56-IE/TgzlZPRUytI/AAAAAAAABUU/hgSO1cpJeM0/s000/user.png'/>

    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 1074, Column 112: required attribute "alt" not specified
    …m/-dpr10ZQkr_M/T-FiwiE7i4I/AAAAAAAAGpM/jG5bEr5pA58/s1600/commentfb-ds.us.png'/>

    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 1075, Column 192: element "fb:comments-count" undefined
    …2/rar-password-recovery-magic-611-full.html'></fb:comments-count> Comments </a>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1080, Column 127: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=email' targe…

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

  • Warning Line 1080, Column 127: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=email' targe…

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

  • Error Line 1080, Column 127: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=email' targe…

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

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1080, Column 154: reference not terminated by REFC delimiter
    …7352&postID=8535721442556300433&target=email' target='_blank' title='Kirimkan …

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

  • Warning Line 1080, Column 154: reference to external entity in attribute value
    …7352&postID=8535721442556300433&target=email' target='_blank' title='Kirimkan …

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

  • Error Line 1080, Column 154: reference to entity "target" for which no system identifier could be generated
    …7352&postID=8535721442556300433&target=email' target='_blank' title='Kirimkan …

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Warning Line 1082, Column 126: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=blog' onclic…

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

  • Warning Line 1082, Column 126: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=blog' onclic…

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

  • Error Line 1082, Column 126: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=blog' 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.

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1082, Column 153: reference not terminated by REFC delimiter
    …7352&postID=8535721442556300433&target=blog' onclick='window.open(this.href, "…

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

  • Warning Line 1082, Column 153: reference to external entity in attribute value
    …7352&postID=8535721442556300433&target=blog' onclick='window.open(this.href, "…

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

  • Error Line 1082, Column 153: reference to entity "target" for which no system identifier could be generated
    …7352&postID=8535721442556300433&target=blog' onclick='window.open(this.href, "…

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Warning Line 1084, Column 129: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=twitter' tar…

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

  • Warning Line 1084, Column 129: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=twitter' tar…

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

  • Error Line 1084, Column 129: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=twitter' tar…

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

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1084, Column 156: reference not terminated by REFC delimiter
    …7352&postID=8535721442556300433&target=twitter' target='_blank' title='Berbagi…

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

  • Warning Line 1084, Column 156: reference to external entity in attribute value
    …7352&postID=8535721442556300433&target=twitter' target='_blank' title='Berbagi…

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

  • Error Line 1084, Column 156: reference to entity "target" for which no system identifier could be generated
    …7352&postID=8535721442556300433&target=twitter' target='_blank' title='Berbagi…

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Warning Line 1086, Column 130: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=facebook' on…

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

  • Warning Line 1086, Column 130: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=facebook' on…

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

  • Error Line 1086, Column 130: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=facebook' on…

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

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1086, Column 157: reference not terminated by REFC delimiter
    …7352&postID=8535721442556300433&target=facebook' onclick='window.open(this.hre…

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

  • Warning Line 1086, Column 157: reference to external entity in attribute value
    …7352&postID=8535721442556300433&target=facebook' onclick='window.open(this.hre…

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

  • Error Line 1086, Column 157: reference to entity "target" for which no system identifier could be generated
    …7352&postID=8535721442556300433&target=facebook' onclick='window.open(this.hre…

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Warning Line 1088, Column 126: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=buzz' onclic…

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

  • Warning Line 1088, Column 126: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=buzz' onclic…

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

  • Error Line 1088, Column 126: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=8535721442556300433&target=buzz' 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.

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1088, Column 153: reference not terminated by REFC delimiter
    …7352&postID=8535721442556300433&target=buzz' onclick='window.open(this.href, "…

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

  • Warning Line 1088, Column 153: reference to external entity in attribute value
    …7352&postID=8535721442556300433&target=buzz' onclick='window.open(this.href, "…

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

  • Error Line 1088, Column 153: reference to entity "target" for which no system identifier could be generated
    …7352&postID=8535721442556300433&target=buzz' onclick='window.open(this.href, "…

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Error Line 1091, Column 216: element "g:plusone" undefined
    …very-magic-611-full.html' size='medium' width='300' annotation='inline'/></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 1093, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary8535721442556300433'>

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

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

  • Error Line 1095, Column 383: required attribute "alt" not specified
    …eenshots/913/913975_3.jpg" width="125"></span></a><span class="OneLinkNoTx" st…

    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 1095, Column 390: end tag for "img" omitted, but OMITTAG NO was specified
    …s/913/913975_3.jpg" width="125"></span></a><span class="OneLinkNoTx" style="ba…

    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 1095, Column 284: start tag was here
    …et MS, sans-serif; font-size: small;"><img border="0" height="125" src="http:/…
  • Error Line 1095, Column 681: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …px; padding: 0px; vertical-align: baseline;"><div style="text-align: justify;">

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

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

  • Error Line 1101, Column 124: required attribute "alt" not specified
    …AAAAABUc/V0SjgyoVO-c/s000/folder.png'/> Posted in:  <a href='http://www.dytosh…

    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 1116, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7968484805077137352&postID=8535721442556300433&from=pencil' title=…

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

  • Warning Line 1116, Column 78: reference to external entity in attribute value
    …it.g?blogID=7968484805077137352&postID=8535721442556300433&from=pencil' title=…

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

  • Error Line 1116, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7968484805077137352&postID=8535721442556300433&from=pencil' title=…

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

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1116, Column 103: reference not terminated by REFC delimiter
    …7968484805077137352&postID=8535721442556300433&from=pencil' title='Edit Entri'>

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

  • Warning Line 1116, Column 103: reference to external entity in attribute value
    …7968484805077137352&postID=8535721442556300433&from=pencil' title='Edit Entri'>

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

  • Error Line 1116, Column 103: reference to entity "from" for which no system identifier could be generated
    …7968484805077137352&postID=8535721442556300433&from=pencil' title='Edit Entri'>

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

  • Info Line 1054, Column 98: entity was defined here
    …7968484805077137352&postID=4558188668692067666&from=pencil' title='Edit Entri'>
  • Error Line 1131, Column 100: required attribute "alt" not specified
    ….blogspot.com/-2lLi4jQfNRQ/TgzlYzNFWfI/AAAAAAAABUQ/OvZZUInOpnI/s000/date.png'/>

    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 1133, Column 100: required attribute "alt" not specified
    ….blogspot.com/-8yo_CE56-IE/TgzlZPRUytI/AAAAAAAABUU/hgSO1cpJeM0/s000/user.png'/>

    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 1136, Column 112: required attribute "alt" not specified
    …m/-dpr10ZQkr_M/T-FiwiE7i4I/AAAAAAAAGpM/jG5bEr5pA58/s1600/commentfb-ds.us.png'/>

    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 1137, Column 156: element "fb:comments-count" undefined
    …ytoshare.us/2013/02/process-hacker-230.html'></fb:comments-count> Comments </a>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1142, Column 127: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=email' targe…

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

  • Warning Line 1142, Column 127: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=email' targe…

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

  • Error Line 1142, Column 127: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=email' targe…

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

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1142, Column 154: reference not terminated by REFC delimiter
    …7352&postID=1611714922607062201&target=email' target='_blank' title='Kirimkan …

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

  • Warning Line 1142, Column 154: reference to external entity in attribute value
    …7352&postID=1611714922607062201&target=email' target='_blank' title='Kirimkan …

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

  • Error Line 1142, Column 154: reference to entity "target" for which no system identifier could be generated
    …7352&postID=1611714922607062201&target=email' target='_blank' title='Kirimkan …

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Warning Line 1144, Column 126: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=blog' onclic…

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

  • Warning Line 1144, Column 126: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=blog' onclic…

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

  • Error Line 1144, Column 126: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=blog' 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.

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1144, Column 153: reference not terminated by REFC delimiter
    …7352&postID=1611714922607062201&target=blog' onclick='window.open(this.href, "…

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

  • Warning Line 1144, Column 153: reference to external entity in attribute value
    …7352&postID=1611714922607062201&target=blog' onclick='window.open(this.href, "…

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

  • Error Line 1144, Column 153: reference to entity "target" for which no system identifier could be generated
    …7352&postID=1611714922607062201&target=blog' onclick='window.open(this.href, "…

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Warning Line 1146, Column 129: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=twitter' tar…

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

  • Warning Line 1146, Column 129: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=twitter' tar…

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

  • Error Line 1146, Column 129: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=twitter' tar…

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

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1146, Column 156: reference not terminated by REFC delimiter
    …7352&postID=1611714922607062201&target=twitter' target='_blank' title='Berbagi…

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

  • Warning Line 1146, Column 156: reference to external entity in attribute value
    …7352&postID=1611714922607062201&target=twitter' target='_blank' title='Berbagi…

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

  • Error Line 1146, Column 156: reference to entity "target" for which no system identifier could be generated
    …7352&postID=1611714922607062201&target=twitter' target='_blank' title='Berbagi…

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Warning Line 1148, Column 130: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=facebook' on…

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

  • Warning Line 1148, Column 130: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=facebook' on…

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

  • Error Line 1148, Column 130: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=facebook' on…

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

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1148, Column 157: reference not terminated by REFC delimiter
    …7352&postID=1611714922607062201&target=facebook' onclick='window.open(this.hre…

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

  • Warning Line 1148, Column 157: reference to external entity in attribute value
    …7352&postID=1611714922607062201&target=facebook' onclick='window.open(this.hre…

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

  • Error Line 1148, Column 157: reference to entity "target" for which no system identifier could be generated
    …7352&postID=1611714922607062201&target=facebook' onclick='window.open(this.hre…

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Warning Line 1150, Column 126: reference not terminated by REFC delimiter
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=buzz' onclic…

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

  • Warning Line 1150, Column 126: reference to external entity in attribute value
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=buzz' onclic…

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

  • Error Line 1150, Column 126: reference to entity "postID" for which no system identifier could be generated
    …st.g?blogID=7968484805077137352&postID=1611714922607062201&target=buzz' 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.

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1150, Column 153: reference not terminated by REFC delimiter
    …7352&postID=1611714922607062201&target=buzz' onclick='window.open(this.href, "…

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

  • Warning Line 1150, Column 153: reference to external entity in attribute value
    …7352&postID=1611714922607062201&target=buzz' onclick='window.open(this.href, "…

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

  • Error Line 1150, Column 153: reference to entity "target" for which no system identifier could be generated
    …7352&postID=1611714922607062201&target=buzz' onclick='window.open(this.href, "…

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

  • Info Line 1021, Column 147: entity was defined here
    …05077137352&postID=4558188668692067666&target=email' target='_blank' title='Ki…
  • Error Line 1153, Column 198: element "g:plusone" undefined
    …/process-hacker-230.html' size='medium' width='300' annotation='inline'/></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 1155, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary1611714922607062201'>

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

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

  • Error Line 1157, Column 327: required attribute "alt" not specified
    …tSs/URX5oRLR1CI/AAAAAAAAAGY/3XNfhLMVIhg/s200/images.jpg" width="200"></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 1157, Column 331: end tag for "img" omitted, but OMITTAG NO was specified
    …tSs/URX5oRLR1CI/AAAAAAAAAGY/3XNfhLMVIhg/s200/images.jpg" width="200"></a></div>

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

  • Info Line 1157, Column 191: start tag was here
    …rgin-bottom: 1em; margin-right: 1em;"><img border="0" height="121" src="http:/…
  • Error Line 1158, Column 211: end tag for "br" omitted, but OMITTAG NO was specified
    …re untuk memanifulasi proses dan service pada PC anda, walaupun sofawre ini<br>

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

  • Info Line 1158, Column 207: start tag was here
    …re untuk memanifulasi proses dan service pada PC anda, walaupun sofawre ini<br>
  • Error Line 1161, Column 124: required attribute "alt" not specified
    …AAAAABUc/V0SjgyoVO-c/s000/folder.png'/> Posted in:  <a href='http://www.dytosh…

    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 1176, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7968484805077137352&postID=1611714922607062201&from=pencil' title=…

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

  • Warning Line 1176, Column 78: reference to external entity in attribute value
    …it.g?blogID=7968484805077137352&postID=1611714922607062201&from=pencil' title=…

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

  • Error Line 1176, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7968484805077137352&postID=1611714922607062201&from=pencil' title=…

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

  • Info Line 1021, Column 120: entity was defined here
    …hare-post.g?blogID=7968484805077137352&postID=4558188668692067666&target=email…
  • Warning Line 1176, Column 103: reference not terminated by REFC delimiter
    …7968484805077137352&postID=1611714922607062201&from=pencil' title='Edit Entri'>

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

  • Warning Line 1176, Column 103: reference to external entity in attribute value
    …7968484805077137352&postID=1611714922607062201&from=pencil' title='Edit Entri'>

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

  • Error Line 1176, Column 103: reference to entity "from" for which no system identifier could be generated
    …7968484805077137352&postID=1611714922607062201&from=pencil' title='Edit Entri'>

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

  • Info Line 1054, Column 98: entity was defined here
    …7968484805077137352&postID=4558188668692067666&from=pencil' title='Edit Entri'>
  • Error Line 1212, Column 15: element "center" undefined
    <p></p><center><a href="http://www.kotakalong.com" target="_blank"><img src="ht…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1212, Column 175: required attribute "alt" not specified
    …P2KPE/URQATN6vbnI/AAAAAAAABVU/oh3rhfsxtwQ/s1600/kotakalong.gif" /></a></center>

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

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

  • Warning Line 1217, Column 93: reference not terminated by REFC delimiter
    …?blogID=7968484805077137352&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 1217, Column 93: reference to external entity in attribute value
    …?blogID=7968484805077137352&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 1217, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7968484805077137352&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 646, Column 82: entity was defined here
    …m/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&…
  • Warning Line 1217, Column 107: reference not terminated by REFC delimiter
    …4805077137352&widgetType=HTML&widgetId=HTML10&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 1217, Column 107: reference to external entity in attribute value
    …4805077137352&widgetType=HTML&widgetId=HTML10&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 1217, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …4805077137352&widgetType=HTML&widgetId=HTML10&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 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 1217, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=sidebarright' oncl…

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

  • Warning Line 1217, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=sidebarright' oncl…

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

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

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

  • Info Line 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 1217, Column 142: reference not terminated by REFC delimiter
    …tId=HTML10&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

  • Warning Line 1217, Column 142: reference to external entity in attribute value
    …tId=HTML10&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

  • Error Line 1217, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML10&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

  • Info Line 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Error Line 1226, Column 15: element "center" undefined
    <p></p><center><form action="https://www.paypal.com/cgi-bin/webscr" method="pos…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1227, Column 52: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="cmd" value="_s-xclick" />

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

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

  • Error Line 1228, Column 2582: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …IWKNG4jBuCjpPDGXSySx30Gn/PqQcHKUacQfb9CWRZke2Ps6AterA==-----END PKCS7----- " />

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

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

  • Error Line 1229, Column 121: there is no attribute "border"
    …AIQ4/0DYqqI693p4/s1600/pp.png" border="0" name="submit" target="_blank" alt="P…

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

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

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

  • Error Line 1229, Column 146: there is no attribute "target"
    ….png" border="0" name="submit" target="_blank" alt="PayPal - The safer, easier…

    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 1229, Column 208: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …"submit" target="_blank" alt="PayPal - The safer, easier way to pay online!" />

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

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

  • Error Line 1232, Column 8: element "center" undefined
    <center>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1234, Column 76: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
     <input type="hidden" name="ap_productid" value="MueIN/yOJ4Y0TDn/p5dkIQ=="/>

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

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

  • Error Line 1235, Column 52: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
     <input type="hidden" name="ap_quantity" value="1"/>

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

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

  • Error Line 1236, Column 117: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …rc="https://secure.payza.com/PayNow/A352267F867A4BB197DB105B68C12682d2en.gif"/>

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

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

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

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

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

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

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

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

  • Info Line 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 1244, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebarright' oncl…

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

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

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

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

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

  • Info Line 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 1244, Column 141: reference not terminated by REFC delimiter
    …etId=HTML1&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

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

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

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

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

  • Info Line 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Error Line 1253, Column 143: there is no attribute "target"
    …fb/a/mailverify" method="post" target="popupwindow" onsubmit="window.open('htt…

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

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

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

  • Error Line 1254, Column 1: character data is not allowed here
    Enter Your Email Address<p></p><input type="text" style="width:150px" name="ema…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 1254, Column 85: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …xt" style="width:150px" name="email" /><p></p><input type="hidden" value="dyto…

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

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

  • Error Line 1254, Column 144: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …hidden" value="dytoshare" name="uri" /><input type="hidden" name="loc" value="…

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

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

  • Error Line 1254, Column 192: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …pe="hidden" name="loc" value="en_US" /><input type="submit" value="Subscribe" …

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

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

  • Error Line 1254, Column 233: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …nput type="submit" value="Subscribe" /></form><center><a href="http://feeds.fe…

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

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

  • Error Line 1254, Column 248: element "center" undefined
    …it" value="Subscribe" /></form><center><a href="http://feeds.feedburner.com/dy…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1259, Column 93: reference not terminated by REFC delimiter
    …?blogID=7968484805077137352&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 1259, Column 93: reference to external entity in attribute value
    …?blogID=7968484805077137352&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 1259, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7968484805077137352&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 646, Column 82: entity was defined here
    …m/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&…
  • Warning Line 1259, Column 107: reference not terminated by REFC delimiter
    …4805077137352&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=sideb…

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

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

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

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

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

  • Info Line 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 1259, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=sidebarright' oncl…

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

  • Warning Line 1259, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=sidebarright' oncl…

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

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

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

  • Info Line 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 1259, Column 141: reference not terminated by REFC delimiter
    …etId=HTML2&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

  • Warning Line 1259, Column 141: reference to external entity in attribute value
    …etId=HTML2&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

  • Error Line 1259, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML2&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

  • Info Line 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Error Line 1268, Column 1894: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …pan><div style="font-weight: normal; "><div style="font-weight: normal;"><span…

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

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

  • Error Line 1268, Column 2003: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …<span><div style="font-weight: bold; "><div style="font-weight: normal; "><cen…

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

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

  • Error Line 1268, Column 2046: element "center" undefined
    … style="font-weight: normal; "><center><div style="font-weight: normal; "><bli…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1268, Column 2095: there is no attribute "style"
    …="font-weight: normal; "><blink style="color: rgb(51, 255, 51);"><br/></blink>…

    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 1268, Column 2121: element "blink" undefined
    …blink style="color: rgb(51, 255, 51);"><br/></blink></div><div style="font-wei…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1268, Column 2215: element "blink" undefined
    …blink style="color: rgb(51, 255, 51);"><span style="font-weight: bold;"><a hre…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1273, Column 93: reference not terminated by REFC delimiter
    …?blogID=7968484805077137352&widgetType=Text&widgetId=Text1&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 1273, Column 93: reference to external entity in attribute value
    …?blogID=7968484805077137352&widgetType=Text&widgetId=Text1&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 1273, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7968484805077137352&widgetType=Text&widgetId=Text1&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 646, Column 82: entity was defined here
    …m/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&…
  • Warning Line 1273, Column 107: reference not terminated by REFC delimiter
    …4805077137352&widgetType=Text&widgetId=Text1&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 1273, Column 107: reference to external entity in attribute value
    …4805077137352&widgetType=Text&widgetId=Text1&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 1273, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …4805077137352&widgetType=Text&widgetId=Text1&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 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 1273, Column 120: reference not terminated by REFC delimiter
    …&widgetType=Text&widgetId=Text1&action=editWidget&sectionId=sidebarright' oncl…

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

  • Warning Line 1273, Column 120: reference to external entity in attribute value
    …&widgetType=Text&widgetId=Text1&action=editWidget&sectionId=sidebarright' oncl…

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

  • Error Line 1273, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=Text&widgetId=Text1&action=editWidget&sectionId=sidebarright' oncl…

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

  • Info Line 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 1273, Column 141: reference not terminated by REFC delimiter
    …etId=Text1&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

  • Warning Line 1273, Column 141: reference to external entity in attribute value
    …etId=Text1&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

  • Error Line 1273, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=Text1&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

  • Info Line 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Error Line 1282, Column 15: element "center" undefined
    <p></p><center> CS1  :  <a href="ymsgr:sendIM?dyto_ds"><img src="http://opi.yah…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1282, Column 131: required attribute "alt" not specified
    …?u=dyto_ds&amp;m=g&amp;t=1&amp;l=us" /></a> </center><center><span style=" tex…

    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 1282, Column 153: element "center" undefined
    …;t=1&amp;l=us" /></a> </center><center><span style=" text-align: left;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 1282, Column 453: required attribute "alt" not specified
    …scinema131&amp;m=g&amp;t=1&amp;l=us" /></a> | <img border="0" height="10" src=…

    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 1282, Column 593: required attribute "alt" not specified
    …lcOor6KI/AAAAAAAAISk/JT8Ce9o_L-Q/s200/bb.png" width="15" /> : 28496B00</center>

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

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

  • Warning Line 1287, Column 93: reference not terminated by REFC delimiter
    …?blogID=7968484805077137352&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 1287, Column 93: reference to external entity in attribute value
    …?blogID=7968484805077137352&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 1287, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7968484805077137352&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 646, Column 82: entity was defined here
    …m/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&…
  • Warning Line 1287, Column 107: reference not terminated by REFC delimiter
    …4805077137352&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 1287, Column 107: reference to external entity in attribute value
    …4805077137352&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 1287, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …4805077137352&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 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 1287, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=sidebarright' oncl…

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

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

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

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

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

  • Info Line 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 1287, Column 141: reference not terminated by REFC delimiter
    …etId=HTML8&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

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

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

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

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

  • Info Line 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Error Line 1296, Column 8: element "center" undefined
    <center><p></p>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1297, Column 17: element "center" undefined
    </center><center><a href="http://yahoqi.blogspot.com/2012/05/windows-7-paket-me…

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

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

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

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

  • Warning Line 1302, Column 93: reference not terminated by REFC delimiter
    …?blogID=7968484805077137352&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 1302, Column 93: reference to external entity in attribute value
    …?blogID=7968484805077137352&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 1302, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7968484805077137352&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 646, Column 82: entity was defined here
    …m/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&…
  • Warning Line 1302, Column 107: reference not terminated by REFC delimiter
    …4805077137352&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 1302, Column 107: reference to external entity in attribute value
    …4805077137352&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 1302, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …4805077137352&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 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 1302, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=sidebarright' oncl…

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

  • Warning Line 1302, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=sidebarright' oncl…

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

  • Error Line 1302, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=sidebarright' oncl…

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

  • Info Line 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 1302, Column 142: reference not terminated by REFC delimiter
    …tId=HTML12&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

  • Warning Line 1302, Column 142: reference to external entity in attribute value
    …tId=HTML12&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

  • Error Line 1302, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML12&action=editWidget&sectionId=sidebarright' onclick='return _WidgetMa…

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

  • Info Line 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Error Line 1314, Column 8: element "center" undefined
    <center><p></p>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1315, Column 17: element "center" undefined
    </center><center><a href="http://www.dytoshare.us/p/advertise-with-us.html"> <i…

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

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

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

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

  • Warning Line 1320, Column 93: reference not terminated by REFC delimiter
    …?blogID=7968484805077137352&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 1320, Column 93: reference to external entity in attribute value
    …?blogID=7968484805077137352&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 1320, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7968484805077137352&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 646, Column 82: entity was defined here
    …m/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&…
  • Warning Line 1320, Column 107: reference not terminated by REFC delimiter
    …4805077137352&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=col1'…

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

  • Warning Line 1320, Column 107: reference to external entity in attribute value
    …4805077137352&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=col1'…

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

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

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

  • Info Line 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 1320, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=col1' 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 1320, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=col1' 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 1320, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=col1' 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 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 1320, Column 141: reference not terminated by REFC delimiter
    …etId=HTML4&action=editWidget&sectionId=col1' 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 1320, Column 141: reference to external entity in attribute value
    …etId=HTML4&action=editWidget&sectionId=col1' 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 1320, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML4&action=editWidget&sectionId=col1' 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 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Error Line 1332, Column 10: ID "fb-root" already defined
    <div id="fb-root"></div><script src="http://connect.facebook.net/en_US/all.js#x…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 564, Column 10: ID "fb-root" first defined here
    <div id='fb-root'></div>
  • Error Line 1332, Column 87: required attribute "type" not specified
    …ect.facebook.net/en_US/all.js#xfbml=1"></script><fb:like-box href="http://www.…

    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 1332, Column 115: there is no attribute "href"
    …s#xfbml=1"></script><fb:like-box href="http://www.facebook.com/dytoshare" widt…

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

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

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

  • Error Line 1332, Column 157: there is no attribute "width"
    …p://www.facebook.com/dytoshare" width="280" colorscheme="dark" show_faces="tru…

    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 1332, Column 175: there is no attribute "colorscheme"
    …om/dytoshare" width="280" colorscheme="dark" show_faces="true" border_color="b…

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

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

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

  • Error Line 1332, Column 193: there is no attribute "show_faces"
    …h="280" colorscheme="dark" show_faces="true" border_color="black" stream="fals…

    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 1332, Column 213: there is no attribute "border_color"
    …"dark" show_faces="true" border_color="black" stream="false" header="true"></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 1332, Column 228: there is no attribute "stream"
    …w_faces="true" border_color="black" stream="false" header="true"></fb:like-box>

    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 1332, Column 243: there is no attribute "header"
    …w_faces="true" border_color="black" stream="false" header="true"></fb:like-box>

    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 1332, Column 249: element "fb:like-box" undefined
    …w_faces="true" border_color="black" stream="false" header="true"></fb:like-box>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1337, Column 93: reference not terminated by REFC delimiter
    …?blogID=7968484805077137352&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 1337, Column 93: reference to external entity in attribute value
    …?blogID=7968484805077137352&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 1337, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7968484805077137352&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 646, Column 82: entity was defined here
    …m/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&…
  • Warning Line 1337, Column 107: reference not terminated by REFC delimiter
    …4805077137352&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=col2'…

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

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

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

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

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

  • Info Line 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 1337, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=col2' 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 1337, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=col2' 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 1337, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=col2' 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 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 1337, Column 141: reference not terminated by REFC delimiter
    …etId=HTML3&action=editWidget&sectionId=col2' 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 1337, Column 141: reference to external entity in attribute value
    …etId=HTML3&action=editWidget&sectionId=col2' 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 1337, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML3&action=editWidget&sectionId=col2' 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 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Error Line 1349, Column 8: element "center" undefined
    <center><!-- Include the Google Friend Connect javascript library. -->

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1378, Column 93: reference not terminated by REFC delimiter
    …?blogID=7968484805077137352&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 1378, Column 93: reference to external entity in attribute value
    …?blogID=7968484805077137352&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 1378, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7968484805077137352&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 646, Column 82: entity was defined here
    …m/rearrange?blogID=7968484805077137352&widgetType=PageList&widgetId=PageList1&…
  • Warning Line 1378, Column 107: reference not terminated by REFC delimiter
    …4805077137352&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=col3'…

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

  • Warning Line 1378, Column 107: reference to external entity in attribute value
    …4805077137352&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=col3'…

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

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

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

  • Info Line 646, Column 102: entity was defined here
    …968484805077137352&widgetType=PageList&widgetId=PageList1&action=editWidget&se…
  • Warning Line 1378, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=col3' 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 1378, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=col3' 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 1378, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=col3' 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 646, Column 121: entity was defined here
    …widgetType=PageList&widgetId=PageList1&action=editWidget&sectionId=pagelistmen…
  • Warning Line 1378, Column 141: reference not terminated by REFC delimiter
    …etId=HTML6&action=editWidget&sectionId=col3' 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 1378, Column 141: reference to external entity in attribute value
    …etId=HTML6&action=editWidget&sectionId=col3' 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 1378, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML6&action=editWidget&sectionId=col3' 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 646, Column 139: entity was defined here
    …t&widgetId=PageList1&action=editWidget&sectionId=pagelistmenusblog' onclick='r…
  • Warning Line 1409, 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 1409, 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
  • 7.117 visits

In Page Analysis