hay88.com

hay88.com has Alexa Rank 44.995 and Google Page Rank is 1

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

Overview Info

  • Domain Name
    hay88.com
  • Favicon
  • Alexa Rank
    #44995
  • Google Page Rank
    PR 1
  • Ip Address
    74.125.128.121
  • Page Size
    127.5 KB
  • Images
    15 GIF, 19 JPG, 19 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 26 0 0 0 0

Website Meta Analysis



  • Title
    HAY88.COM - Cập nhật tin hay, giải trí và thư giãn 18+
  • Meta Keyword
    HAY88.COM - Cập nhật tin hay, giải trí và thư giãn 18+

Technical Analysis



  • Webserver
    GSE
  • Ip Address
    74.125.128.121
  • Domain Age
    2 Years, 8 Months, 15 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-type: text/html; charset=UTF-8
  • expires: Sun, 15 Sep 2013 10:47:14 GMT
  • date: Sun, 15 Sep 2013 10:47:14 GMT
  • cache-control: private, max-age=0
  • last-modified: Sun, 15 Sep 2013 09:06:43 GMT
  • etag: "7440304c-58a0-44c7-9e48-627435d1b0c9"
  • x-robots-tag: all,noodp
  • content-encoding: gzip
  • x-content-type-options: nosniff
  • x-xss-protection: 1; mode=block
  • content-length: 25864
  • server: GSE
  • alternate-protocol: 80:quic,80:quic
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for hay88.com

DNS Analysis


DNS servers
ns63.domaincontrol.com [216.69.185.42]
ns64.domaincontrol.com [208.109.255.42]


DNS Records

Answer records
hay88.com A 74.125.31.121 1800s
hay88.com MX
preference: 0
exchange: smtp.secureserver.net
3600s
hay88.com MX
preference: 10
exchange: mailstore1.secureserver.net
3600s
hay88.com NS  ns63.domaincontrol.com 3600s
hay88.com NS  ns64.domaincontrol.com 3600s
hay88.com SOA
server: ns63.domaincontrol.com
email: dns@jomax.net
serial: 2013012900
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 143 Errors
  • 38 Warnings
Ratio Text/Html
  • 0.48315630671680077
Message Error
  • Error Line 2, Column 12: there is no attribute "lang"
    <html lang='vi' xml:lang='vi' xmlns='http://www.w3.org/1999/xhtml' xmlns:b='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 4, Column 42: there is no attribute "property"
    <meta content='317804224985061' property='fb:app_id'/>

    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 5, Column 14: there is no attribute "type"
    <script type='text/javascript'>

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

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

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

  • Error Line 5, Column 31: element "script" undefined
    <script type='text/javascript'>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 20, Column 31: element "script" undefined
    <script type="text/javascript">(function() { var a=window,b="jstiming",d="tick"…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 20, 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 20, 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 20, 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 20, 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 20, 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 20, Column 265: entity was defined here
    …ing={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.performan…
  • Error Line 20, 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 20, 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 20, 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 20, 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 20, 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 20, 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 20, 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 20, 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 20, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, Column 162: entity was defined here
    …tE),j[d]("tbnd_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT()…
  • Warning Line 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, Column 212: entity was defined here
    …al&&(m=a.gtbExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&…
  • Warning Line 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 21, 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 22, 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 21, 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 22, 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 21, 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 22, 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 20, 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 40, Column 123: cannot generate system identifier for general entity "zx"
    ….css?targetBlogID=7334347819712689471&zx=5b658837-c4ca-4f93-9b75-c8783cc1e2dc"…

    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 40, Column 123: general entity "zx" not defined and no default entity
    ….css?targetBlogID=7334347819712689471&zx=5b658837-c4ca-4f93-9b75-c8783cc1e2dc"…

    This is usually a cascading error caused by 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 40, Column 125: reference not terminated by REFC delimiter
    …css?targetBlogID=7334347819712689471&zx=5b658837-c4ca-4f93-9b75-c8783cc1e2dc"/>

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

  • Warning Line 40, Column 125: reference to external entity in attribute value
    …css?targetBlogID=7334347819712689471&zx=5b658837-c4ca-4f93-9b75-c8783cc1e2dc"/>

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

  • Error Line 40, Column 125: reference to entity "zx" for which no system identifier could be generated
    …css?targetBlogID=7334347819712689471&zx=5b658837-c4ca-4f93-9b75-c8783cc1e2dc"/>

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

  • Info Line 40, Column 122: entity was defined here
    …n.css?targetBlogID=7334347819712689471&zx=5b658837-c4ca-4f93-9b75-c8783cc1e2dc…
  • Error Line 416, Column 13: there is no attribute "src"
    <script src='http://users3.jabry.com/bangtieuls1/Itechr-post.js' type='text/jav…

    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 416, Column 88: element "script" undefined
    …//users3.jabry.com/bangtieuls1/Itechr-post.js' type='text/javascript'></script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 421, Column 18: there is no attribute "language"
    <script language='javascript'>

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

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

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

  • Error Line 421, Column 30: element "script" undefined
    <script language='javascript'>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 463, Column 31: element "script" undefined
    <script type="text/javascript">var a=navigator,b="userAgent",c="indexOf",f="&m=…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 463, Column 78: cannot generate system identifier for general entity "m"
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function…

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

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

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

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

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

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

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

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

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 463, Column 284: character "&" is the first character of a delimiter but occurred as data
    …:return null}}if(-1!=a[b][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iP…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 463, Column 285: character "&" is the first character of a delimiter but occurred as data
    …return null}}if(-1!=a[b][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iPa…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 463, Column 307: character "&" is the first character of a delimiter but occurred as data
    …b][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iPad")||-1!=a[b][c]("Oper…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 463, Column 308: character "&" is the first character of a delimiter but occurred as data
    …][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iPad")||-1!=a[b][c]("Opera…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

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

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

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

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

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

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

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

  • Info Line 463, Column 394: entity was defined here
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};
  • Error Line 464, Column 40: element "script" undefined
    </script><script type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 467, Column 31: there is no attribute "onclick"
    <body class='loading' onclick='vtlai_popup();'>

    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 489, Column 31: element "script" undefined
    <script type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 495, Column 99: element "script" undefined
    … type="text/javascript" src="http://provider.ad360.vn/showads.min.js"></script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 501, Column 83: cannot generate system identifier for general entity "widgetType"
    …/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=e…

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

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

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

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

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

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

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

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

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

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

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

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

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

  • Warning Line 501, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-…

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

  • Warning Line 501, Column 107: reference to external entity in attribute value
    …7819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-…

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

  • Error Line 501, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …7819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-…

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 501, Column 115: cannot generate system identifier for general entity "action"
    …89471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onc…

    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 501, Column 115: general entity "action" not defined and no default entity
    …89471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onc…

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

    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 501, Column 133: general entity "sectionId" not defined and no default entity
    …TML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Widg…

    This is usually a cascading error caused by 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 501, Column 142: reference not terminated by REFC delimiter
    …tId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _WidgetManager…

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

  • Warning Line 501, Column 142: reference to external entity in attribute value
    …tId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _WidgetManager…

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

  • Error Line 501, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _WidgetManager…

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

  • Info Line 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 501, Column 160: there is no attribute "onclick"
    …editWidget&sectionId=top-ads' onclick='return _WidgetManager._PopupConfig(docu…

    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 501, Column 240: there is no attribute "target"
    …g(document.getElementById("HTML99"));' target='configHTML99' title='Chỉnh sửa'>

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

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

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

  • Error Line 517, Column 175: there is no attribute "border"
    …"_blank"><img alt="xinh.hay88" border="0" src="http://3.bp.blogspot.com/-CXruz…

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

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

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

  • Warning Line 522, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&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 522, Column 93: reference to external entity in attribute value
    …?blogID=7334347819712689471&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 522, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&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 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 522, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML2&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 522, Column 107: reference to external entity in attribute value
    …7819712689471&widgetType=HTML&widgetId=HTML2&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 522, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …7819712689471&widgetType=HTML&widgetId=HTML2&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 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 522, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML2&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 522, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML2&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 522, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML2&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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 522, Column 141: reference not terminated by REFC delimiter
    …etId=HTML2&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 522, Column 141: reference to external entity in attribute value
    …etId=HTML2&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 522, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML2&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 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 534, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 555, Column 100: element "script" undefined
    …ry.com/bangtieuls1/Adv-recent-label%282%29.js' type='text/javascript'></script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 558, Column 8: element "script" undefined
    <script>document.write("<script src=\"/feeds/posts/default/-/Hot?max-results="+…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 558, Column 37: an attribute value must be a literal unless it contains only name characters
    <script>document.write("<script src=\"/feeds/posts/default/-/Hot?max-results="+…

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

  • Error Line 558, Column 139: element "script" undefined
    …&orderby=published&alt=json-in-script&callback=sidenew\"><\/script>");</script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 558, Column 140: character "<" is the first character of a delimiter but occurred as data
    …&orderby=published&alt=json-in-script&callback=sidenew\"><\/script>");</script>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 560, Column 6: end tag for "script" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 558, Column 1: start tag was here
    <script>document.write("<script src=\"/feeds/posts/default/-/Hot?max-results="+…
  • Warning Line 565, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&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 565, Column 93: reference to external entity in attribute value
    …?blogID=7334347819712689471&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 565, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&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 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 565, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=main'…

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

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

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

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

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

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

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

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

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

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

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

  • Info Line 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 565, Column 141: reference not terminated by REFC delimiter
    …etId=HTML3&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

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

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

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

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

  • Info Line 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 575, Column 84: there is no attribute "onsubmit"
    …/a/mailverify' method='post' onsubmit='window.open("http://feedburner.google.c…

    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 575, Column 230: there is no attribute "target"
    …ow", "scrollbars=yes,width=550,height=520"); return true' target='popupwindow'>

    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 579, Column 65: there is no attribute "placeholder"
    …low-by-email-address' name='email' placeholder='Email address...' type='text'/>

    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 581, Column 11: there is no attribute "width"
    <td width='64px'>

    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 586, Column 47: document type does not allow element "input" here; missing one of "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    <input name='uri' type='hidden' value='hay88'/>

    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 587, Column 47: document type does not allow element "input" here; missing one of "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    <input name='loc' type='hidden' value='en_US'/>

    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 592, Column 19: document type does not allow element "div" here; assuming missing "object" start-tag
    <div class='clear'></div>
  • Warning Line 595, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&widgetType=FollowByEmail&widgetId=FollowByEmail1&a…

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

  • Warning Line 595, Column 93: reference to external entity in attribute value
    …?blogID=7334347819712689471&widgetType=FollowByEmail&widgetId=FollowByEmail1&a…

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

  • Error Line 595, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&widgetType=FollowByEmail&widgetId=FollowByEmail1&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.

  • Info Line 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 595, Column 116: reference not terminated by REFC delimiter
    …9471&widgetType=FollowByEmail&widgetId=FollowByEmail1&action=editWidget&sectio…

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

  • Warning Line 595, Column 116: reference to external entity in attribute value
    …9471&widgetType=FollowByEmail&widgetId=FollowByEmail1&action=editWidget&sectio…

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

  • Error Line 595, Column 116: reference to entity "widgetId" for which no system identifier could be generated
    …9471&widgetType=FollowByEmail&widgetId=FollowByEmail1&action=editWidget&sectio…

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 595, Column 138: reference not terminated by REFC delimiter
    …ByEmail&widgetId=FollowByEmail1&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 595, Column 138: reference to external entity in attribute value
    …ByEmail&widgetId=FollowByEmail1&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 595, Column 138: reference to entity "action" for which no system identifier could be generated
    …ByEmail&widgetId=FollowByEmail1&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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 595, Column 159: reference not terminated by REFC delimiter
    …owByEmail1&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 595, Column 159: reference to external entity in attribute value
    …owByEmail1&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 595, Column 159: reference to entity "sectionId" for which no system identifier could be generated
    …owByEmail1&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 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 601, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </span>

    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 592, Column 1: start tag was here
    <div class='clear'></div>
  • Error Line 608, 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 649, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML22&action=editWidget&…

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

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

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

  • Error Line 649, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML22&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 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 649, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML22&action=editWidget&sectionId=main…

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

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

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

  • Error Line 649, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …7819712689471&widgetType=HTML&widgetId=HTML22&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 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 649, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML22&action=editWidget&sectionId=main' onclick='ret…

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

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

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

  • Error Line 649, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML22&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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 649, Column 142: reference not terminated by REFC delimiter
    …tId=HTML22&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

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

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

  • Error Line 649, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML22&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 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 666, Column 36: there is no attribute "itemscope"
    <div class='post hentry' itemscope='itemscope' itemtype='http://schema.org/Blog…

    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 666, Column 57: there is no attribute "itemtype"
    …s='post hentry' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'>

    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 667, Column 9: there is no attribute "name"
    <a name='9049650906624935123'></a>

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

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

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

  • Error Line 668, Column 45: there is no attribute "itemprop"
    <h2 class='post-title entry-title' itemprop='name'>

    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 674, Column 82: there is no attribute "itemprop"
    …-body entry-content' id='post-body-9049650906624935123' itemprop='articleBody'>

    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 689, Column 66: there is no attribute "itemprop"
    …e.com/112148074122029489786' itemprop='author' rel='author' title='author prof…

    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 696, Column 181: there is no attribute "itemprop"
    … link'><abbr class='updated' itemprop='datePublished' title='2013-02-17T16:01:…

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

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

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

  • Warning Line 707, Column 72: cannot generate system identifier for general entity "postID"
    …ost-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil' …

    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 707, Column 72: general entity "postID" not defined and no default entity
    …ost-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil' …

    This is usually a cascading error caused by 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 707, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7334347819712689471&postID=9049650906624935123&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 707, Column 78: reference to external entity in attribute value
    …it.g?blogID=7334347819712689471&postID=9049650906624935123&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 707, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7334347819712689471&postID=9049650906624935123&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 707, Column 71: entity was defined here
    …post-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil'…
  • Warning Line 707, Column 99: cannot generate system identifier for general entity "from"
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>

    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 707, Column 99: general entity "from" not defined and no default entity
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>

    This is usually a cascading error caused by 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 707, Column 103: reference not terminated by REFC delimiter
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>

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

  • Warning Line 707, Column 103: reference to external entity in attribute value
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>

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

  • Error Line 707, Column 103: reference to entity "from" for which no system identifier could be generated
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>

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

  • Info Line 707, Column 98: entity was defined here
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>
  • Warning Line 765, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7334347819712689471&postID=4865651128414578295&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 765, Column 78: reference to external entity in attribute value
    …it.g?blogID=7334347819712689471&postID=4865651128414578295&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 765, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7334347819712689471&postID=4865651128414578295&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 707, Column 71: entity was defined here
    …post-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil'…
  • Warning Line 765, Column 103: reference not terminated by REFC delimiter
    …34347819712689471&postID=4865651128414578295&from=pencil' title='Sửa Bài đăng'>

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

  • Warning Line 765, Column 103: reference to external entity in attribute value
    …34347819712689471&postID=4865651128414578295&from=pencil' title='Sửa Bài đăng'>

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

  • Error Line 765, Column 103: reference to entity "from" for which no system identifier could be generated
    …34347819712689471&postID=4865651128414578295&from=pencil' title='Sửa Bài đăng'>

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

  • Info Line 707, Column 98: entity was defined here
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>
  • Warning Line 834, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7334347819712689471&postID=5849980388310003934&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 834, Column 78: reference to external entity in attribute value
    …it.g?blogID=7334347819712689471&postID=5849980388310003934&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 834, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7334347819712689471&postID=5849980388310003934&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 707, Column 71: entity was defined here
    …post-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil'…
  • Warning Line 834, Column 103: reference not terminated by REFC delimiter
    …34347819712689471&postID=5849980388310003934&from=pencil' title='Sửa Bài đăng'>

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

  • Warning Line 834, Column 103: reference to external entity in attribute value
    …34347819712689471&postID=5849980388310003934&from=pencil' title='Sửa Bài đăng'>

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

  • Error Line 834, Column 103: reference to entity "from" for which no system identifier could be generated
    …34347819712689471&postID=5849980388310003934&from=pencil' title='Sửa Bài đăng'>

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

  • Info Line 707, Column 98: entity was defined here
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>
  • Warning Line 893, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7334347819712689471&postID=2737484683778437090&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 893, Column 78: reference to external entity in attribute value
    …it.g?blogID=7334347819712689471&postID=2737484683778437090&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 893, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7334347819712689471&postID=2737484683778437090&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 707, Column 71: entity was defined here
    …post-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil'…
  • Warning Line 893, Column 103: reference not terminated by REFC delimiter
    …34347819712689471&postID=2737484683778437090&from=pencil' title='Sửa Bài đăng'>

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

  • Warning Line 893, Column 103: reference to external entity in attribute value
    …34347819712689471&postID=2737484683778437090&from=pencil' title='Sửa Bài đăng'>

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

  • Error Line 893, Column 103: reference to entity "from" for which no system identifier could be generated
    …34347819712689471&postID=2737484683778437090&from=pencil' title='Sửa Bài đăng'>

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

  • Info Line 707, Column 98: entity was defined here
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>
  • Warning Line 952, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7334347819712689471&postID=4529225782157832343&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 952, Column 78: reference to external entity in attribute value
    …it.g?blogID=7334347819712689471&postID=4529225782157832343&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 952, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7334347819712689471&postID=4529225782157832343&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 707, Column 71: entity was defined here
    …post-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil'…
  • Warning Line 952, Column 103: reference not terminated by REFC delimiter
    …34347819712689471&postID=4529225782157832343&from=pencil' title='Sửa Bài đăng'>

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

  • Warning Line 952, Column 103: reference to external entity in attribute value
    …34347819712689471&postID=4529225782157832343&from=pencil' title='Sửa Bài đăng'>

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

  • Error Line 952, Column 103: reference to entity "from" for which no system identifier could be generated
    …34347819712689471&postID=4529225782157832343&from=pencil' title='Sửa Bài đăng'>

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

  • Info Line 707, Column 98: entity was defined here
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>
  • Warning Line 1020, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7334347819712689471&postID=6420622209284620860&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 1020, Column 78: reference to external entity in attribute value
    …it.g?blogID=7334347819712689471&postID=6420622209284620860&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 1020, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7334347819712689471&postID=6420622209284620860&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 707, Column 71: entity was defined here
    …post-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil'…
  • Warning Line 1020, Column 103: reference not terminated by REFC delimiter
    …34347819712689471&postID=6420622209284620860&from=pencil' title='Sửa Bài đăng'>

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

  • Warning Line 1020, Column 103: reference to external entity in attribute value
    …34347819712689471&postID=6420622209284620860&from=pencil' title='Sửa Bài đăng'>

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

  • Error Line 1020, Column 103: reference to entity "from" for which no system identifier could be generated
    …34347819712689471&postID=6420622209284620860&from=pencil' title='Sửa Bài đăng'>

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

  • Info Line 707, Column 98: entity was defined here
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>
  • Warning Line 1079, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7334347819712689471&postID=72383963268779146&from=pencil' title='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 1079, Column 78: reference to external entity in attribute value
    …it.g?blogID=7334347819712689471&postID=72383963268779146&from=pencil' title='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 1079, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7334347819712689471&postID=72383963268779146&from=pencil' title='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 707, Column 71: entity was defined here
    …post-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil'…
  • Warning Line 1079, Column 101: reference not terminated by REFC delimiter
    …7334347819712689471&postID=72383963268779146&from=pencil' title='Sửa Bài đăng'>

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

  • Warning Line 1079, Column 101: reference to external entity in attribute value
    …7334347819712689471&postID=72383963268779146&from=pencil' title='Sửa Bài đăng'>

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

  • Error Line 1079, Column 101: reference to entity "from" for which no system identifier could be generated
    …7334347819712689471&postID=72383963268779146&from=pencil' title='Sửa Bài đăng'>

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

  • Info Line 707, Column 98: entity was defined here
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>
  • Warning Line 1137, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7334347819712689471&postID=5276555118399745698&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 1137, Column 78: reference to external entity in attribute value
    …it.g?blogID=7334347819712689471&postID=5276555118399745698&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 1137, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7334347819712689471&postID=5276555118399745698&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 707, Column 71: entity was defined here
    …post-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil'…
  • Warning Line 1137, Column 103: reference not terminated by REFC delimiter
    …34347819712689471&postID=5276555118399745698&from=pencil' title='Sửa Bài đăng'>

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

  • Warning Line 1137, Column 103: reference to external entity in attribute value
    …34347819712689471&postID=5276555118399745698&from=pencil' title='Sửa Bài đăng'>

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

  • Error Line 1137, Column 103: reference to entity "from" for which no system identifier could be generated
    …34347819712689471&postID=5276555118399745698&from=pencil' title='Sửa Bài đăng'>

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

  • Info Line 707, Column 98: entity was defined here
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>
  • Warning Line 1196, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7334347819712689471&postID=4273213096871304801&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 1196, Column 78: reference to external entity in attribute value
    …it.g?blogID=7334347819712689471&postID=4273213096871304801&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 1196, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7334347819712689471&postID=4273213096871304801&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 707, Column 71: entity was defined here
    …post-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil'…
  • Warning Line 1196, Column 103: reference not terminated by REFC delimiter
    …34347819712689471&postID=4273213096871304801&from=pencil' title='Sửa Bài đăng'>

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

  • Warning Line 1196, Column 103: reference to external entity in attribute value
    …34347819712689471&postID=4273213096871304801&from=pencil' title='Sửa Bài đăng'>

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

  • Error Line 1196, Column 103: reference to entity "from" for which no system identifier could be generated
    …34347819712689471&postID=4273213096871304801&from=pencil' title='Sửa Bài đăng'>

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

  • Info Line 707, Column 98: entity was defined here
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>
  • Warning Line 1254, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7334347819712689471&postID=8032157059031329339&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 1254, Column 78: reference to external entity in attribute value
    …it.g?blogID=7334347819712689471&postID=8032157059031329339&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 1254, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7334347819712689471&postID=8032157059031329339&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 707, Column 71: entity was defined here
    …post-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil'…
  • Warning Line 1254, Column 103: reference not terminated by REFC delimiter
    …34347819712689471&postID=8032157059031329339&from=pencil' title='Sửa Bài đăng'>

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

  • Warning Line 1254, Column 103: reference to external entity in attribute value
    …34347819712689471&postID=8032157059031329339&from=pencil' title='Sửa Bài đăng'>

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

  • Error Line 1254, Column 103: reference to entity "from" for which no system identifier could be generated
    …34347819712689471&postID=8032157059031329339&from=pencil' title='Sửa Bài đăng'>

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

  • Info Line 707, Column 98: entity was defined here
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>
  • Warning Line 1312, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7334347819712689471&postID=6995047459961527583&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 1312, Column 78: reference to external entity in attribute value
    …it.g?blogID=7334347819712689471&postID=6995047459961527583&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 1312, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7334347819712689471&postID=6995047459961527583&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 707, Column 71: entity was defined here
    …post-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil'…
  • Warning Line 1312, Column 103: reference not terminated by REFC delimiter
    …34347819712689471&postID=6995047459961527583&from=pencil' title='Sửa Bài đăng'>

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

  • Warning Line 1312, Column 103: reference to external entity in attribute value
    …34347819712689471&postID=6995047459961527583&from=pencil' title='Sửa Bài đăng'>

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

  • Error Line 1312, Column 103: reference to entity "from" for which no system identifier could be generated
    …34347819712689471&postID=6995047459961527583&from=pencil' title='Sửa Bài đăng'>

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

  • Info Line 707, Column 98: entity was defined here
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>
  • Warning Line 1369, Column 78: reference not terminated by REFC delimiter
    …it.g?blogID=7334347819712689471&postID=2971091443588972146&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 1369, Column 78: reference to external entity in attribute value
    …it.g?blogID=7334347819712689471&postID=2971091443588972146&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 1369, Column 78: reference to entity "postID" for which no system identifier could be generated
    …it.g?blogID=7334347819712689471&postID=2971091443588972146&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 707, Column 71: entity was defined here
    …post-edit.g?blogID=7334347819712689471&postID=9049650906624935123&from=pencil'…
  • Warning Line 1369, Column 103: reference not terminated by REFC delimiter
    …34347819712689471&postID=2971091443588972146&from=pencil' title='Sửa Bài đăng'>

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

  • Warning Line 1369, Column 103: reference to external entity in attribute value
    …34347819712689471&postID=2971091443588972146&from=pencil' title='Sửa Bài đăng'>

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

  • Error Line 1369, Column 103: reference to entity "from" for which no system identifier could be generated
    …34347819712689471&postID=2971091443588972146&from=pencil' title='Sửa Bài đăng'>

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

  • Info Line 707, Column 98: entity was defined here
    …34347819712689471&postID=9049650906624935123&from=pencil' title='Sửa Bài đăng'>
  • Error Line 1397, Column 31: element "script" undefined
    <script type='text/javascript'>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1405, Column 102: element "script" undefined
    …han-trang.googlecode.com/files/pagenavi203.js' type='text/javascript'></script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1412, Column 31: element "script" undefined
    <script type="text/javascript">window.___gcfg = {'lang': 'vi'};</script>

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

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

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

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

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1430, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write("<script src=\"http://www.hay88.com/feeds/posts/default/-/Scanda…

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

  • Error Line 1430, Column 82: "-" is not a member of a group specified for any attribute
    …y88.com/feeds/posts/default/-/Scandal - Shocking?max-results="+numposts+"&orde…
  • Error Line 1430, Column 92: "Shocking" is not a member of a group specified for any attribute
    …eds/posts/default/-/Scandal - Shocking?max-results="+numposts+"&orderby=publis…
  • Error Line 1430, Column 183: element "script" undefined
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1430, Column 184: character "<" is the first character of a delimiter but occurred as data
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1431, Column 6: end tag for "script" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 1429, Column 1: start tag was here
    <script>
  • Warning Line 1435, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&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 1435, Column 93: reference to external entity in attribute value
    …?blogID=7334347819712689471&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 1435, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&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 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1435, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=hay88…

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

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

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

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

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1435, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=hay882cleft' 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 1435, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=hay882cleft' 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 1435, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=hay882cleft' 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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1435, Column 141: reference not terminated by REFC delimiter
    …etId=HTML4&action=editWidget&sectionId=hay882cleft' 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 1435, Column 141: reference to external entity in attribute value
    …etId=HTML4&action=editWidget&sectionId=hay882cleft' 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 1435, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML4&action=editWidget&sectionId=hay882cleft' 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 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1444, Column 8: element "script" undefined
    <script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1445, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write("<script src=\"http://www.hay88.com/feeds/posts/default/-/Buon C…

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

  • Error Line 1445, Column 85: "Chuyen" is not a member of a group specified for any attribute
    ….com/feeds/posts/default/-/Buon Chuyen?max-results="+numposts+"&orderby=publis…
  • Error Line 1445, Column 176: element "script" undefined
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1445, Column 177: character "<" is the first character of a delimiter but occurred as data
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1446, Column 8: end tag for "script" omitted, but OMITTAG NO was specified
      </div>

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

  • Info Line 1444, Column 1: start tag was here
    <script>
  • Warning Line 1450, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&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 1450, Column 93: reference to external entity in attribute value
    …?blogID=7334347819712689471&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 1450, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&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 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1450, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=hay88…

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

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

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

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

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1450, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=hay882cleft' 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 1450, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=hay882cleft' 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 1450, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=hay882cleft' 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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1450, Column 141: reference not terminated by REFC delimiter
    …etId=HTML6&action=editWidget&sectionId=hay882cleft' 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 1450, Column 141: reference to external entity in attribute value
    …etId=HTML6&action=editWidget&sectionId=hay882cleft' 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 1450, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML6&action=editWidget&sectionId=hay882cleft' 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 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1459, Column 8: element "script" undefined
    <script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1460, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write("<script src=\"http://www.hay88.com/feeds/posts/default/-/Tinh Y…

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

  • Error Line 1460, Column 83: "Yeu" is not a member of a group specified for any attribute
    …88.com/feeds/posts/default/-/Tinh Yeu - Gioi Tinh?max-results="+numposts+"&ord…
  • Error Line 1460, Column 83: "-" is not a member of a group specified for any attribute
    …88.com/feeds/posts/default/-/Tinh Yeu - Gioi Tinh?max-results="+numposts+"&ord…
  • Error Line 1460, Column 90: "Gioi" is not a member of a group specified for any attribute
    …feeds/posts/default/-/Tinh Yeu - Gioi Tinh?max-results="+numposts+"&orderby=pu…
  • Error Line 1460, Column 94: "Tinh" is not a member of a group specified for any attribute
    …s/posts/default/-/Tinh Yeu - Gioi Tinh?max-results="+numposts+"&orderby=publis…
  • Error Line 1460, Column 185: element "script" undefined
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1460, Column 186: character "<" is the first character of a delimiter but occurred as data
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1461, Column 8: end tag for "script" omitted, but OMITTAG NO was specified
      </div>

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

  • Info Line 1459, Column 1: start tag was here
    <script>
  • Warning Line 1465, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&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 1465, Column 93: reference to external entity in attribute value
    …?blogID=7334347819712689471&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 1465, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&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 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1465, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=hay88…

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

  • Warning Line 1465, Column 107: reference to external entity in attribute value
    …7819712689471&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=hay88…

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

  • Error Line 1465, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …7819712689471&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=hay88…

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1465, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=hay882cleft' 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 1465, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=hay882cleft' 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 1465, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=hay882cleft' 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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1465, Column 141: reference not terminated by REFC delimiter
    …etId=HTML8&action=editWidget&sectionId=hay882cleft' 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 1465, Column 141: reference to external entity in attribute value
    …etId=HTML8&action=editWidget&sectionId=hay882cleft' 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 1465, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML8&action=editWidget&sectionId=hay882cleft' 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 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1473, Column 78: character ";" not allowed in attribute specification list
    …om/search/label/Clip Shock?&amp;max-results=8";>Clip Shock - Quay lén</a></h2> 
  • Error Line 1474, Column 8: element "script" undefined
    <script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1475, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write("<script src=\"http://www.hay88.com/feeds/posts/default/-/Clip S…

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

  • Error Line 1475, Column 84: "Shock" is not a member of a group specified for any attribute
    …8.com/feeds/posts/default/-/Clip Shock?max-results="+numposts+"&orderby=publis…
  • Error Line 1475, Column 175: element "script" undefined
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1475, Column 176: character "<" is the first character of a delimiter but occurred as data
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1476, Column 8: end tag for "script" omitted, but OMITTAG NO was specified
      </div>

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

  • Info Line 1474, Column 1: start tag was here
    <script>
  • Warning Line 1480, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&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 1480, Column 93: reference to external entity in attribute value
    …?blogID=7334347819712689471&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 1480, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&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 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1480, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=hay88…

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

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

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

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

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1480, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=hay882cleft' 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 1480, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=hay882cleft' 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 1480, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=hay882cleft' 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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1480, Column 141: reference not terminated by REFC delimiter
    …etId=HTML9&action=editWidget&sectionId=hay882cleft' 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 1480, Column 141: reference to external entity in attribute value
    …etId=HTML9&action=editWidget&sectionId=hay882cleft' 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 1480, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML9&action=editWidget&sectionId=hay882cleft' 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 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1489, Column 8: element "script" undefined
    <script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1490, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write("<script src=\"http://www.hay88.com/feeds/posts/default/-/clip?m…

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

  • Error Line 1490, Column 169: element "script" undefined
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1490, Column 170: character "<" is the first character of a delimiter but occurred as data
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1491, Column 8: end tag for "script" omitted, but OMITTAG NO was specified
      </div>

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

  • Info Line 1489, Column 1: start tag was here
    <script>
  • Warning Line 1495, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&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 1495, Column 93: reference to external entity in attribute value
    …?blogID=7334347819712689471&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 1495, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&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 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1495, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=hay8…

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

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

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

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

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1495, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=hay882cleft' 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 1495, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=hay882cleft' 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 1495, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=hay882cleft' 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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1495, Column 142: reference not terminated by REFC delimiter
    …tId=HTML10&action=editWidget&sectionId=hay882cleft' 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 1495, Column 142: reference to external entity in attribute value
    …tId=HTML10&action=editWidget&sectionId=hay882cleft' 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 1495, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML10&action=editWidget&sectionId=hay882cleft' 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 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1509, Column 8: element "script" undefined
    <script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1510, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write("<script src=\"http://www.hay88.com/feeds/posts/default/-/Thoi S…

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

  • Error Line 1510, Column 82: "Su" is not a member of a group specified for any attribute
    …y88.com/feeds/posts/default/-/Thoi Su - Xa Hoi?max-results="+numposts+"&orderb…
  • Error Line 1510, Column 82: "-" is not a member of a group specified for any attribute
    …y88.com/feeds/posts/default/-/Thoi Su - Xa Hoi?max-results="+numposts+"&orderb…
  • Error Line 1510, Column 87: "Xa" is not a member of a group specified for any attribute
    …om/feeds/posts/default/-/Thoi Su - Xa Hoi?max-results="+numposts+"&orderby=pub…
  • Error Line 1510, Column 90: "Hoi" is not a member of a group specified for any attribute
    …feeds/posts/default/-/Thoi Su - Xa Hoi?max-results="+numposts+"&orderby=publis…
  • Error Line 1510, Column 181: element "script" undefined
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1510, Column 182: character "<" is the first character of a delimiter but occurred as data
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1511, Column 8: end tag for "script" omitted, but OMITTAG NO was specified
      </div>

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

  • Info Line 1509, Column 1: start tag was here
    <script>
  • Warning Line 1515, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&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 1515, Column 93: reference to external entity in attribute value
    …?blogID=7334347819712689471&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 1515, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&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 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1515, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=hay88…

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

  • Warning Line 1515, Column 107: reference to external entity in attribute value
    …7819712689471&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=hay88…

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

  • Error Line 1515, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …7819712689471&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=hay88…

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1515, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=hay882cright' 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 1515, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=hay882cright' 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 1515, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=hay882cright' 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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1515, Column 141: reference not terminated by REFC delimiter
    …etId=HTML7&action=editWidget&sectionId=hay882cright' 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 1515, Column 141: reference to external entity in attribute value
    …etId=HTML7&action=editWidget&sectionId=hay882cright' 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 1515, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML7&action=editWidget&sectionId=hay882cright' 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 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1524, Column 8: element "script" undefined
    <script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1525, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write("<script src=\"http://www.hay88.com/feeds/posts/default/-/Ngoi S…

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

  • Error Line 1525, Column 82: "Sao" is not a member of a group specified for any attribute
    …y88.com/feeds/posts/default/-/Ngoi Sao?max-results="+numposts+"&orderby=publis…
  • Error Line 1525, Column 173: element "script" undefined
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1525, Column 174: character "<" is the first character of a delimiter but occurred as data
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1526, Column 8: end tag for "script" omitted, but OMITTAG NO was specified
      </div>

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

  • Info Line 1524, Column 1: start tag was here
    <script>
  • Warning Line 1530, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&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 1530, Column 93: reference to external entity in attribute value
    …?blogID=7334347819712689471&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 1530, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&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 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1530, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=hay88…

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

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

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

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

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1530, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=hay882cright' 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 1530, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=hay882cright' 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 1530, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=hay882cright' 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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1530, Column 141: reference not terminated by REFC delimiter
    …etId=HTML5&action=editWidget&sectionId=hay882cright' 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 1530, Column 141: reference to external entity in attribute value
    …etId=HTML5&action=editWidget&sectionId=hay882cright' 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 1530, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML5&action=editWidget&sectionId=hay882cright' 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 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1539, Column 8: element "script" undefined
    <script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1540, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write("<script src=\"http://www.hay88.com/feeds/posts/default/-/Dan Ch…

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

  • Error Line 1540, Column 82: "Choi" is not a member of a group specified for any attribute
    …y88.com/feeds/posts/default/-/Dan Choi?max-results="+numposts+"&orderby=publis…
  • Error Line 1540, Column 173: element "script" undefined
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1540, Column 174: character "<" is the first character of a delimiter but occurred as data
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1541, Column 8: end tag for "script" omitted, but OMITTAG NO was specified
      </div>

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

  • Info Line 1539, Column 1: start tag was here
    <script>
  • Warning Line 1545, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&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 1545, Column 93: reference to external entity in attribute value
    …?blogID=7334347819712689471&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 1545, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&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 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1545, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=hay8…

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

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

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

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

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1545, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=hay882cright' 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 1545, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=hay882cright' 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 1545, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=hay882cright' 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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1545, Column 142: reference not terminated by REFC delimiter
    …tId=HTML11&action=editWidget&sectionId=hay882cright' 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 1545, Column 142: reference to external entity in attribute value
    …tId=HTML11&action=editWidget&sectionId=hay882cright' 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 1545, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML11&action=editWidget&sectionId=hay882cright' 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 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1554, Column 8: element "script" undefined
    <script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1555, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write("<script src=\"http://www.hay88.com/feeds/posts/default/-/Tư&#80…

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

  • Error Line 1555, Column 86: "Sươ" is not a member of a group specified for any attribute
    …com/feeds/posts/default/-/Tư&#803; Sươ&#769;ng?max-results="+numposts+"&orderb…
  • Error Line 1555, Column 185: element "script" undefined
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1555, Column 186: character "<" is the first character of a delimiter but occurred as data
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1556, Column 8: end tag for "script" omitted, but OMITTAG NO was specified
      </div>

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

  • Info Line 1554, Column 1: start tag was here
    <script>
  • Warning Line 1560, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&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 1560, Column 93: reference to external entity in attribute value
    …?blogID=7334347819712689471&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 1560, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&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 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1560, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=hay8…

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

  • Warning Line 1560, Column 107: reference to external entity in attribute value
    …7819712689471&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=hay8…

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

  • Error Line 1560, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …7819712689471&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=hay8…

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1560, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=hay882cright' 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 1560, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=hay882cright' 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 1560, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=hay882cright' 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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1560, Column 142: reference not terminated by REFC delimiter
    …tId=HTML12&action=editWidget&sectionId=hay882cright' 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 1560, Column 142: reference to external entity in attribute value
    …tId=HTML12&action=editWidget&sectionId=hay882cright' 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 1560, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML12&action=editWidget&sectionId=hay882cright' 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 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1569, Column 8: element "script" undefined
    <script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1570, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write("<script src=\"http://www.hay88.com/feeds/posts/default/-/Chuyen…

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

  • Error Line 1570, Column 83: "La" is not a member of a group specified for any attribute
    …88.com/feeds/posts/default/-/Chuyen La?max-results="+numposts+"&orderby=publis…
  • Error Line 1570, Column 174: element "script" undefined
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1570, Column 175: character "<" is the first character of a delimiter but occurred as data
    …ublished&alt=json-in-script&callback=showrecentposts99\"><\/script>");</script>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1571, Column 8: end tag for "script" omitted, but OMITTAG NO was specified
      </div>

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

  • Info Line 1569, Column 1: start tag was here
    <script>
  • Warning Line 1575, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML13&action=editWidget&…

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

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

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

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

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

  • Info Line 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1575, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=hay8…

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

  • Warning Line 1575, Column 107: reference to external entity in attribute value
    …7819712689471&widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=hay8…

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

  • Error Line 1575, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …7819712689471&widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=hay8…

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1575, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=hay882cright' 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 1575, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=hay882cright' 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 1575, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=hay882cright' 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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1575, Column 142: reference not terminated by REFC delimiter
    …tId=HTML13&action=editWidget&sectionId=hay882cright' 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 1575, Column 142: reference to external entity in attribute value
    …tId=HTML13&action=editWidget&sectionId=hay882cright' 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 1575, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML13&action=editWidget&sectionId=hay882cright' 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 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1587, Column 87: element "script" undefined
    …://users3.jabry.com/bangtieuls1/Mobile-vcc.js' type='text/javascript'></script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1601, Column 93: reference not terminated by REFC delimiter
    …pt" src="http://www.google.com/cse/brand?form=cse-search-box&lang=vi"></script>

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

  • Error Line 1601, Column 97: element "script" undefined
    …pt" src="http://www.google.com/cse/brand?form=cse-search-box&lang=vi"></script>

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

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

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

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

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

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

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

  • Info Line 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1606, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML16&action=editWidget&sectionId=side…

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

  • Warning Line 1606, Column 107: reference to external entity in attribute value
    …7819712689471&widgetType=HTML&widgetId=HTML16&action=editWidget&sectionId=side…

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

  • Error Line 1606, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …7819712689471&widgetType=HTML&widgetId=HTML16&action=editWidget&sectionId=side…

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1606, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML16&action=editWidget&sectionId=sidebar' onclick='…

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

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

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

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

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

  • Info Line 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1606, Column 142: reference not terminated by REFC delimiter
    …tId=HTML16&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

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

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

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

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

  • Info Line 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1617, Column 5: document type does not allow element "tr" here; assuming missing "table" start-tag
    	<tr>
  • Error Line 1620, Column 6: element "left" undefined
    <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 1634, Column 31: element "script" undefined
    <script type="text/javascript"> 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1640, Column 94: element "script" undefined
    …s5.nofeehost.com/luongtoan56/Rc-post-2cot9.js" type="text/javascript"></script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1642, Column 72: document type does not allow element "div" here
    <div style="background-color: #eeeeee; color: blue; text-align: right;">

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

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

  • Info Line 1617, Column 2: start tag was here
    	<tr>
  • Warning Line 1648, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&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 1648, Column 93: reference to external entity in attribute value
    …?blogID=7334347819712689471&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 1648, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=7334347819712689471&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 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1648, Column 107: reference not terminated by REFC delimiter
    …7819712689471&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 1648, Column 107: reference to external entity in attribute value
    …7819712689471&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 1648, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …7819712689471&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 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1648, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' onclick='…

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

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

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

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

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

  • Info Line 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1648, Column 141: reference not terminated by REFC delimiter
    …etId=HTML1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

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

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

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

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

  • Info Line 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1656, 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 1705, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML15&action=editWidget&…

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

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

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

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

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

  • Info Line 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1705, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML15&action=editWidget&sectionId=side…

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

  • Warning Line 1705, Column 107: reference to external entity in attribute value
    …7819712689471&widgetType=HTML&widgetId=HTML15&action=editWidget&sectionId=side…

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

  • Error Line 1705, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …7819712689471&widgetType=HTML&widgetId=HTML15&action=editWidget&sectionId=side…

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1705, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML15&action=editWidget&sectionId=sidebar' onclick='…

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

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

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

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

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

  • Info Line 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1705, Column 142: reference not terminated by REFC delimiter
    …tId=HTML15&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

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

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

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

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

  • Info Line 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1720, Column 102: element "script" undefined
    …apis.com/ajax/libs/jquery/1.7.2/jquery.min.js' type='text/javascript'></script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1723, Column 111: element "script" undefined
    …JavaScript" src="http://users3.jabry.com/bangtieuls1/Baloon-right.js"></script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1725, Column 110: element "script" undefined
    …"JavaScript" src="http://users3.jabry.com/bangtieuls1/Baloon-left.js"></script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1728, Column 54: element "script" undefined
    <script src="http://adbroker.zing.vn/res1/crystal.js"></script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1732, Column 12: there is no attribute "src"
    <embed src="http://ngukiem.funny68.com/Bannernew/150x600hay88.swf" wmode="trans…

    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 1732, Column 74: there is no attribute "wmode"
    …com/Bannernew/150x600hay88.swf" wmode="transparent" style="margin: 0px; paddin…

    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 1732, Column 94: there is no attribute "style"
    …0hay88.swf" wmode="transparent" style="margin: 0px; padding-top: 0px;" height=…

    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 1732, Column 134: there is no attribute "height"
    …="transparent" style="margin: 0px; padding-top: 0px;" height="500" width="130">

    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 1732, Column 146: there is no attribute "width"
    …="transparent" style="margin: 0px; padding-top: 0px;" height="500" width="130">

    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 1732, Column 151: element "embed" undefined
    …="transparent" style="margin: 0px; padding-top: 0px;" height="500" width="130">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1735, Column 31: element "script" undefined
    <script type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1746, Column 17: character "<" is the first character of a delimiter but occurred as data
    	if(windowWidth < 1000){

    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 1756, Column 71: cannot generate system identifier for general entity "callback"
    …er.zing.vn/lview?loc=_adb_22_10002790&callback=crystal2.addStaticSlot"></scrip…

    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 1756, Column 71: general entity "callback" not defined and no default entity
    …er.zing.vn/lview?loc=_adb_22_10002790&callback=crystal2.addStaticSlot"></scrip…

    This is usually a cascading error caused by 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 1756, Column 79: reference not terminated by REFC delimiter
    …r.zing.vn/lview?loc=_adb_22_10002790&callback=crystal2.addStaticSlot"></script>

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

  • Warning Line 1756, Column 79: reference to external entity in attribute value
    …r.zing.vn/lview?loc=_adb_22_10002790&callback=crystal2.addStaticSlot"></script>

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

  • Error Line 1756, Column 79: reference to entity "callback" for which no system identifier could be generated
    …r.zing.vn/lview?loc=_adb_22_10002790&callback=crystal2.addStaticSlot"></script>

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

  • Info Line 1756, Column 70: entity was defined here
    …ker.zing.vn/lview?loc=_adb_22_10002790&callback=crystal2.addStaticSlot"></scri…
  • Error Line 1756, Column 103: element "script" undefined
    …r.zing.vn/lview?loc=_adb_22_10002790&callback=crystal2.addStaticSlot"></script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1762, Column 10: there is no attribute "style"
    <u style="color: white;"><b>Liên hệ quảng cáo:</b></u><b><a href="http://home.h…

    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 1762, Column 25: element "u" undefined
    <u style="color: white;"><b>Liên hệ quảng cáo:</b></u><b><a href="http://home.h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1762, Column 208: element "u" undefined
    …rget="_blank" title="Bảng Báo Giá"> <u>Bảng Báo Giá </u></a> - <a href="http:/…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1762, Column 374: element "u" undefined
    …232;" target="_blank" title="Điều khoản sử dụng"> <u>Điều khoản sử dụng</u></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).
  • Error Line 1766, Column 30: there is no attribute "align"
    <div class="smallfont" align="right" style="display:none">

    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 1766, Column 58: document type does not allow element "div" here; assuming missing "object" start-tag
    <div class="smallfont" align="right" style="display:none">
  • Error Line 1768, Column 12: there is no attribute "id"
    <script id="_wau0ra">var _wau = _wau || []; _wau.push(["small", "hay88oly", "0r…

    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 1768, Column 21: element "script" undefined
    <script id="_wau0ra">var _wau = _wau || []; _wau.push(["small", "hay88oly", "0r…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1776, Column 31: element "script" undefined
    <script type="text/javascript">document.write(unescape("%3Cscript src=%27http:/…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1777, Column 108: element "script" undefined
    …om" target="_blank" title="html hit counter" ><script  type="text/javascript" >

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1781, Column 10: element "noscript" undefined
    <noscript><a href="http://www.histats.com" target="_blank"><img src="http://sst…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1782, Column 30: end tag for "object" omitted, but OMITTAG NO was specified
    <!-- Histats.com  END  --></b>

    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 1766, Column 1: start tag was here
    <div class="smallfont" align="right" style="display:none">
  • Warning Line 1787, Column 93: reference not terminated by REFC delimiter
    …?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML14&action=editWidget&…

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

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

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

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

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

  • Info Line 501, Column 82: entity was defined here
    …m/rearrange?blogID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=…
  • Warning Line 1787, Column 107: reference not terminated by REFC delimiter
    …7819712689471&widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=foot…

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

  • Warning Line 1787, Column 107: reference to external entity in attribute value
    …7819712689471&widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=foot…

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

  • Error Line 1787, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …7819712689471&widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=foot…

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

  • Info Line 501, Column 98: entity was defined here
    …ID=7334347819712689471&widgetType=HTML&widgetId=HTML99&action=editWidget&secti…
  • Warning Line 1787, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=footer' onclick='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.

  • Warning Line 1787, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=footer' onclick='r…

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

  • Error Line 1787, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=footer' onclick='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 501, Column 114: entity was defined here
    …689471&widgetType=HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' on…
  • Warning Line 1787, Column 142: reference not terminated by REFC delimiter
    …tId=HTML14&action=editWidget&sectionId=footer' onclick='return _WidgetManager.…

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

  • Warning Line 1787, Column 142: reference to external entity in attribute value
    …tId=HTML14&action=editWidget&sectionId=footer' onclick='return _WidgetManager.…

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

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

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

  • Info Line 501, Column 132: entity was defined here
    …HTML&widgetId=HTML99&action=editWidget&sectionId=top-ads' onclick='return _Wid…
  • Error Line 1797, Column 31: element "script" undefined
    <script type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1799, Column 104: element "script" undefined
    …ript" src="//www.blogger.com/static/v1/widgets/2134638198-widgets.js"></script>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1800, Column 75: element "script" undefined
    …pt type="text/javascript" src="https://apis.google.com/js/plusone.js"></script>

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

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

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1802, 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 1802, 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
  • 3.617 visits

In Page Analysis