phimqt.com

Phim Sex xnxx, Xem Phim Sex xvideos, Phim Sex Tổng Hợp Xvideos.com, phim sex lauxanh.us, phim sex xnxx.com Phim Sex Sẽ Luôn Được Cập Nhật Liên Tục. ...

This data was last updated from 22-08-2013 04:50:10  (update).

Overview Info



  • Domain Name
    phimqt.com
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    0
  • Ip Address
    173.194.78.121
  • Page Size
    58.7 KB
  • Images
    0 GIF, 8 JPG, 8 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 5 0 0 0 0

Website Meta Analysis



  • Title
    Phim Sex, Phim Sex Việt, Phim Heo, Phim xXX
  • Meta Keyword
    Phim Sex, Phim Sex Việt, Phim Heo, Phim xXX
  • Meta Description
    Phim Sex xnxx, Xem Phim Sex xvideos, Phim Sex Tổng Hợp Xvideos.com, phim sex lauxanh.us, phim sex xnxx.com Phim Sex Sẽ Luôn Được Cập Nhật Liên Tục.

Technical Analysis



  • Webserver
    GSE
  • Ip Address
    173.194.78.121
  • Domain Age
    1 Months, 19 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-type: text/html; charset=UTF-8
  • expires: Thu, 22 Aug 2013 16:50:08 GMT
  • date: Thu, 22 Aug 2013 16:50:08 GMT
  • cache-control: private, max-age=0
  • last-modified: Thu, 22 Aug 2013 09:36:03 GMT
  • etag: "cc8fe9bd-ea78-474f-a835-571eb31f1db6"
  • content-encoding: gzip
  • x-content-type-options: nosniff
  • x-xss-protection: 1; mode=block
  • content-length: 14655
  • server: GSE
  • alternate-protocol: 80:quic,80:quic
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for phimqt.com

DNS Analysis


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


DNS Records

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

Authority records

Additional records

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 96 Errors
  • 71 Warnings
Ratio Text/Html
  • 0.4261148935461855
Message Error
  • Error Line 2, Column 26: there is no attribute "itemtype"
    <html dir='ltr' itemtype='http://schema.org/Blog' xmlns='http://www.w3.org/1999…

    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 69: document type does not allow element "a" here; assuming missing "object" start-tag
    …href='https://plus.google.com/112938533680000945971' rel='author'>Nhat Pham</a>
  • Error Line 5, Column 7: document type does not allow element "title" here
    <title>Phim Sex, Phim Sex Việt, Phim Heo, Phim xXX</title>

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

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

  • Error Line 6, Column 184: document type does not allow element "meta" here
    …him sex xnxx.com Phim Sex Sẽ Luôn Được Cập Nhật Liên Tục.' name='description'/>

    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 7, Column 77: document type does not allow element "meta" here
    <meta content='Phim Sex, Phim Sex Việt, Phim Heo, Phim xXX' name='keywords'/>

    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 8, Column 45: document type does not allow element "meta" here
    <meta content='index, follow' name='robots'/>

    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 9, Column 346: document type does not allow element "meta" here
    …web.com, www.msn.com, www.netscape.com, www.nomade.com' name='Search Engines'/>

    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 10, Column 48: document type does not allow element "meta" here
    <meta content='index, follow' name='GOOGLEBOT'/>

    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 11, Column 47: document type does not allow element "meta" here
    <meta content='index, follow' name='yahooBOT'/>

    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 12, Column 47: document type does not allow element "meta" here
    <meta content='document' name='resource-type'/>

    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 13, Column 37: document type does not allow element "meta" here
    <meta content='all' name='audience'/>

    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 14, Column 39: document type does not allow element "meta" here
    <meta content='general' name='rating'/>

    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 15, Column 35: document type does not allow element "meta" here
    <meta content='all' name='robots'/>

    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 16, Column 45: document type does not allow element "meta" here
    <meta content='index, follow' name='robots'/>

    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 17, Column 36: document type does not allow element "meta" here
    <meta content='id' name='language'/>

    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 18, Column 39: document type does not allow element "meta" here
    <meta content='id' name='geo.country'/>

    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 19, Column 44: document type does not allow element "meta" here
    <meta content='global' name='distribution'/>

    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 20, Column 45: document type does not allow element "meta" here
    <meta content='1 days' name='revisit-after'/>

    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 21, Column 63: document type does not allow element "meta" here
    <meta content='IE=edge,chrome=1' http-equiv='X-UA-Compatible'/>

    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 22, Column 116: document type does not allow element "link" here
    …' href='//www.blogger.com/static/v1/widgets/103638431-widget_css_bundle.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 23, Column 122: cannot generate system identifier for general entity "zx"
    …n.css?targetBlogID=587481126229480677&zx=cc8fe9bd-ea78-474f-a835-571eb31f1db6"…

    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 23, Column 122: general entity "zx" not defined and no default entity
    …n.css?targetBlogID=587481126229480677&zx=cc8fe9bd-ea78-474f-a835-571eb31f1db6"…

    This is usually a cascading error caused by 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 23, Column 124: reference not terminated by REFC delimiter
    ….css?targetBlogID=587481126229480677&zx=cc8fe9bd-ea78-474f-a835-571eb31f1db6"/>

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

  • Warning Line 23, Column 124: reference to external entity in attribute value
    ….css?targetBlogID=587481126229480677&zx=cc8fe9bd-ea78-474f-a835-571eb31f1db6"/>

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

  • Error Line 23, Column 124: reference to entity "zx" for which no system identifier could be generated
    ….css?targetBlogID=587481126229480677&zx=cc8fe9bd-ea78-474f-a835-571eb31f1db6"/>

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

  • Info Line 23, Column 121: entity was defined here
    …on.css?targetBlogID=587481126229480677&zx=cc8fe9bd-ea78-474f-a835-571eb31f1db6…
  • Error Line 23, Column 163: document type does not allow element "link" here
    ….css?targetBlogID=587481126229480677&zx=cc8fe9bd-ea78-474f-a835-571eb31f1db6"/>

    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 24, Column 40: document type does not allow element "style" here
    <style id='page-skin-1' 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 25, Column 7: multiple comments in comment declaration
    /*-----------------------------------------------
  • Warning Line 25, Column 11: multiple comments in comment declaration
    /*-----------------------------------------------
  • Warning Line 25, Column 15: multiple comments in comment declaration
    /*-----------------------------------------------
  • Warning Line 25, Column 19: multiple comments in comment declaration
    /*-----------------------------------------------
  • Warning Line 25, Column 23: multiple comments in comment declaration
    /*-----------------------------------------------
  • Warning Line 25, Column 27: multiple comments in comment declaration
    /*-----------------------------------------------
  • Warning Line 25, Column 31: multiple comments in comment declaration
    /*-----------------------------------------------
  • Warning Line 25, Column 35: multiple comments in comment declaration
    /*-----------------------------------------------
  • Warning Line 25, Column 39: multiple comments in comment declaration
    /*-----------------------------------------------
  • Warning Line 25, Column 43: multiple comments in comment declaration
    /*-----------------------------------------------
  • Warning Line 25, Column 47: multiple comments in comment declaration
    /*-----------------------------------------------
  • Error Line 25, Column 49: invalid comment declaration: found name character outside comment but inside comment declaration
    /*-----------------------------------------------
  • Info Line 24, Column 41: comment declaration started here
    <style id='page-skin-1' type='text/css'><!--
  • Error Line 1016, Column 18: there is no attribute "language"
    <script language='javascript' 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.

  • Warning Line 1030, Column 78: cannot generate system identifier for general entity "m"
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",k="?m=1";function…

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

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

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

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

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

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

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

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

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

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

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

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

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

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

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

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

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

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

  • Info Line 1030, Column 394: entity was defined here
    …pera Mini")||-1!=a[b][c]("IEMobile")){var m=l();m&&window.location.replace(m)};
  • Error Line 1033, Column 16: end tag for "object" omitted, but OMITTAG NO was specified
    </script></head>

    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 4, Column 1: start tag was here
    <a href='https://plus.google.com/112938533680000945971' rel='author'>Nhat Pham<…
  • Error Line 1033, Column 16: end tag for "head" which is not finished
    </script></head>

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

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

  • Error Line 1034, Column 31: document type does not allow element "script" here; assuming missing "body" start-tag
    <script type='text/javascript'>
  • Error Line 1044, Column 31: document type does not allow element "body" here
    <body onclick='vtlai_popup();'>

    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 1089, Column 64: there is no attribute "placeholder"
    … class='default' name='q' placeholder='Nhập từ khóa tìm kiếm' type='text' valu…

    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 1104, Column 8: required attribute "type" not specified
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+5+"&o…

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

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

  • Error Line 1104, Column 8: document type does not allow element "script" here; assuming missing "li" start-tag
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+5+"&o…
  • Error Line 1104, Column 37: an attribute value must be a literal unless it contains only name characters
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+5+"&o…

    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 1104, Column 134: required attribute "type" not specified
    …="+5+"&orderby=published&alt=json-in-script&callback=phimtop\"><\/script>");			

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

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

  • Error Line 1104, Column 134: document type does not allow element "script" here
    …="+5+"&orderby=published&alt=json-in-script&callback=phimtop\"><\/script>");			

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

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

  • Warning Line 1104, Column 135: character "<" is the first character of a delimiter but occurred as data
    …="+5+"&orderby=published&alt=json-in-script&callback=phimtop\"><\/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 1106, Column 5: end tag for "script" omitted, but OMITTAG NO was specified
    </ul>

    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 1104, Column 1: start tag was here
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+5+"&o…
  • Error Line 1106, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    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 1104, Column 1: start tag was here
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+5+"&o…
  • Error Line 1122, Column 8: required attribute "type" not specified
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+8+"&o…

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

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

  • Error Line 1122, Column 8: document type does not allow element "script" here; assuming missing "li" start-tag
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+8+"&o…
  • Error Line 1122, Column 37: an attribute value must be a literal unless it contains only name characters
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+8+"&o…

    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 1122, Column 134: required attribute "type" not specified
    …="+8+"&orderby=published&alt=json-in-script&callback=phimhot\"><\/script>");			

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

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

  • Error Line 1122, Column 134: document type does not allow element "script" here
    …="+8+"&orderby=published&alt=json-in-script&callback=phimhot\"><\/script>");			

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

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

  • Warning Line 1122, Column 135: character "<" is the first character of a delimiter but occurred as data
    …="+8+"&orderby=published&alt=json-in-script&callback=phimhot\"><\/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 1124, Column 5: end tag for "script" omitted, but OMITTAG NO was specified
    </ul>

    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 1122, Column 1: start tag was here
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+8+"&o…
  • Error Line 1124, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    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 1122, Column 1: start tag was here
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+8+"&o…
  • Error Line 1142, Column 8: required attribute "type" not specified
    <script>document.write("<script src=\"/feeds/posts/default/-/phim lẻ?max-result…

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

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

  • Error Line 1142, Column 8: document type does not allow element "script" here; assuming missing "li" start-tag
    <script>document.write("<script src=\"/feeds/posts/default/-/phim lẻ?max-result…
  • Error Line 1142, Column 37: an attribute value must be a literal unless it contains only name characters
    <script>document.write("<script src=\"/feeds/posts/default/-/phim lẻ?max-result…

    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 1142, Column 69: "lẻ" is not a member of a group specified for any attribute
    …t src=\"/feeds/posts/default/-/phim lẻ?max-results="+20+"&orderby=published&al…
  • Error Line 1142, Column 144: required attribute "type" not specified
    …"+20+"&orderby=published&alt=json-in-script&callback=phimnew\"><\/script>");			

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

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

  • Error Line 1142, Column 144: document type does not allow element "script" here
    …"+20+"&orderby=published&alt=json-in-script&callback=phimnew\"><\/script>");			

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

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

  • Warning Line 1142, Column 145: character "<" is the first character of a delimiter but occurred as data
    …"+20+"&orderby=published&alt=json-in-script&callback=phimnew\"><\/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 1144, Column 5: end tag for "script" omitted, but OMITTAG NO was specified
    </ul>

    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 1142, Column 1: start tag was here
    <script>document.write("<script src=\"/feeds/posts/default/-/phim lẻ?max-result…
  • Error Line 1144, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    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 1142, Column 1: start tag was here
    <script>document.write("<script src=\"/feeds/posts/default/-/phim lẻ?max-result…
  • Error Line 1154, Column 8: required attribute "type" not specified
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+20+"&…

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

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

  • Error Line 1154, Column 8: document type does not allow element "script" here; assuming missing "li" start-tag
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+20+"&…
  • Error Line 1154, Column 37: an attribute value must be a literal unless it contains only name characters
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+20+"&…

    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 1154, Column 135: required attribute "type" not specified
    …"+20+"&orderby=published&alt=json-in-script&callback=phimnew\"><\/script>");			

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

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

  • Error Line 1154, Column 135: document type does not allow element "script" here
    …"+20+"&orderby=published&alt=json-in-script&callback=phimnew\"><\/script>");			

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

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

  • Warning Line 1154, Column 136: character "<" is the first character of a delimiter but occurred as data
    …"+20+"&orderby=published&alt=json-in-script&callback=phimnew\"><\/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 1156, Column 5: end tag for "script" omitted, but OMITTAG NO was specified
    </ul>

    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 1154, Column 1: start tag was here
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+20+"&…
  • Error Line 1156, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    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 1154, Column 1: start tag was here
    <script>document.write("<script src=\"/feeds/posts/default/?max-results="+20+"&…
  • Error Line 1189, Column 9: element "marquee" undefined
    <marquee><span style="font-weight:bold;">Nhấn G+1 & và Like Để Xem Phim Siêu Tố…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using 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 1189, Column 51: character "&" is the first character of a delimiter but occurred as data
    …an style="font-weight:bold;">Nhấn G+1 & và Like Để Xem Phim Siêu Tốc !</span><…

    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 1194, Column 82: cannot generate system identifier for general entity "widgetType"
    …m/rearrange?blogID=587481126229480677&widgetType=HTML&widgetId=HTML1&action=ed…

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

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

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

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

  • Error Line 1194, Column 82: general entity "widgetType" not defined and no default entity
    …m/rearrange?blogID=587481126229480677&widgetType=HTML&widgetId=HTML1&action=ed…

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

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

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

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

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

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

  • Error Line 1194, Column 98: general entity "widgetId" not defined and no default entity
    …ID=587481126229480677&widgetType=HTML&widgetId=HTML1&action=editWidget&section…

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

  • Warning Line 1194, Column 106: reference not terminated by REFC delimiter
    …1126229480677&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 1194, Column 106: reference to external entity in attribute value
    …1126229480677&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 1194, Column 106: reference to entity "widgetId" for which no system identifier could be generated
    …1126229480677&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 1194, Column 97: entity was defined here
    …gID=587481126229480677&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1194, Column 113: cannot generate system identifier for general entity "action"
    …480677&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' 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 1194, Column 113: general entity "action" not defined and no default entity
    …480677&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' 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 1194, Column 119: 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 1194, Column 119: 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 1194, Column 119: 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 1194, Column 112: entity was defined here
    …9480677&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' on…
  • Warning Line 1194, Column 131: cannot generate system identifier for general entity "sectionId"
    …HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' 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 1194, Column 131: general entity "sectionId" not defined and no default entity
    …HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' 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 1194, Column 140: 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 1194, Column 140: 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 1194, Column 140: 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 1194, Column 130: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  • Error Line 1194, Column 237: there is no attribute "target"
    …fig(document.getElementById("HTML1"));' target='configHTML1' 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 1207, Column 67: there is no attribute "border"
    …au Không Che Hàng Vip HD 2013' border='0' height='72' src='http://3.bp.blogspo…

    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 1318, Column 92: reference not terminated by REFC delimiter
    …e?blogID=587481126229480677&widgetType=PopularPosts&widgetId=PopularPosts1&act…

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

  • Warning Line 1318, Column 92: reference to external entity in attribute value
    …e?blogID=587481126229480677&widgetType=PopularPosts&widgetId=PopularPosts1&act…

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

  • Error Line 1318, Column 92: reference to entity "widgetType" for which no system identifier could be generated
    …e?blogID=587481126229480677&widgetType=PopularPosts&widgetId=PopularPosts1&act…

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

  • Info Line 1194, Column 81: entity was defined here
    …om/rearrange?blogID=587481126229480677&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1318, Column 114: reference not terminated by REFC delimiter
    …80677&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

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

  • Warning Line 1318, Column 114: reference to external entity in attribute value
    …80677&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

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

  • Error Line 1318, Column 114: reference to entity "widgetId" for which no system identifier could be generated
    …80677&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

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

  • Info Line 1194, Column 97: entity was defined here
    …gID=587481126229480677&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1318, Column 135: reference not terminated by REFC delimiter
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 1318, Column 135: reference to external entity in attribute value
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=sidebar' onclick='…

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

  • Error Line 1318, Column 135: reference to entity "action" for which no system identifier could be generated
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=sidebar' onclick='…

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

  • Info Line 1194, Column 112: entity was defined here
    …9480677&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' on…
  • Warning Line 1318, Column 156: reference not terminated by REFC delimiter
    …ularPosts1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 1318, Column 156: reference to external entity in attribute value
    …ularPosts1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

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

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

  • Info Line 1194, Column 130: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  • Error Line 1327, Column 23: there is no attribute "annotation"
    <g:plusone annotation='bubble' href='http://www.phimqt.com/' size='standard' so…

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

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

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

  • Error Line 1327, Column 37: there is no attribute "href"
    <g:plusone annotation='bubble' href='http://www.phimqt.com/' size='standard' so…

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

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

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

  • Error Line 1327, Column 67: there is no attribute "size"
    …e' href='http://www.phimqt.com/' size='standard' source='blogger:blog:plusone'…

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

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

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

  • Error Line 1327, Column 85: there is no attribute "source"
    …w.phimqt.com/' size='standard' source='blogger:blog:plusone' width='250'></g:p…

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

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

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

  • Error Line 1327, Column 114: there is no attribute "width"
    …qt.com/' size='standard' source='blogger:blog:plusone' width='250'></g:plusone>

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

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

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

  • Error Line 1327, Column 119: element "g:plusone" undefined
    …qt.com/' size='standard' source='blogger:blog:plusone' width='250'></g:plusone>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1346, Column 30: character "&" is the first character of a delimiter but occurred as data
              if (window.iframes && iframes.open) {

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1377, Column 92: reference not terminated by REFC delimiter
    …e?blogID=587481126229480677&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 1377, Column 92: reference to external entity in attribute value
    …e?blogID=587481126229480677&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 1377, Column 92: reference to entity "widgetType" for which no system identifier could be generated
    …e?blogID=587481126229480677&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 1194, Column 81: entity was defined here
    …om/rearrange?blogID=587481126229480677&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1377, Column 106: reference not terminated by REFC delimiter
    …1126229480677&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=sideb…

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

  • Warning Line 1377, Column 106: reference to external entity in attribute value
    …1126229480677&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=sideb…

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

  • Error Line 1377, Column 106: reference to entity "widgetId" for which no system identifier could be generated
    …1126229480677&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=sideb…

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

  • Info Line 1194, Column 97: entity was defined here
    …gID=587481126229480677&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1377, Column 119: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=sidebar' onclick='…

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

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

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

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

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

  • Info Line 1194, Column 112: entity was defined here
    …9480677&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' on…
  • Warning Line 1377, Column 140: reference not terminated by REFC delimiter
    …etId=HTML7&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

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

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

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

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

  • Info Line 1194, Column 130: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  • Warning Line 1390, Column 92: reference not terminated by REFC delimiter
    …e?blogID=587481126229480677&widgetType=Attribution&widgetId=Attribution1&actio…

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

  • Warning Line 1390, Column 92: reference to external entity in attribute value
    …e?blogID=587481126229480677&widgetType=Attribution&widgetId=Attribution1&actio…

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

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

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

  • Info Line 1194, Column 81: entity was defined here
    …om/rearrange?blogID=587481126229480677&widgetType=HTML&widgetId=HTML1&action=e…
  • Warning Line 1390, Column 113: reference not terminated by REFC delimiter
    …480677&widgetType=Attribution&widgetId=Attribution1&action=editWidget&sectionI…

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

  • Warning Line 1390, Column 113: reference to external entity in attribute value
    …480677&widgetType=Attribution&widgetId=Attribution1&action=editWidget&sectionI…

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

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

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

  • Info Line 1194, Column 97: entity was defined here
    …gID=587481126229480677&widgetType=HTML&widgetId=HTML1&action=editWidget&sectio…
  • Warning Line 1390, Column 133: reference not terminated by REFC delimiter
    …tribution&widgetId=Attribution1&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 1390, Column 133: reference to external entity in attribute value
    …tribution&widgetId=Attribution1&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 1390, Column 133: reference to entity "action" for which no system identifier could be generated
    …tribution&widgetId=Attribution1&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 1194, Column 112: entity was defined here
    …9480677&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' on…
  • Warning Line 1390, Column 154: reference not terminated by REFC delimiter
    …tribution1&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 1390, Column 154: reference to external entity in attribute value
    …tribution1&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 1390, Column 154: reference to entity "sectionId" for which no system identifier could be generated
    …tribution1&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 1194, Column 130: entity was defined here
    …=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  • Error Line 1409, Column 107: required attribute "type" not specified
    … số khách Online'><script id='_waumyi'>var _wau = _wau || []; _wau.push(["smal…

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

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

  • Error Line 1414, Column 8: required attribute "type" not specified
    <script>

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

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

  • Warning Line 1431, 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 1431, 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.
  • Error Line 1443, Column 7: end tag for "body" omitted, but OMITTAG NO was specified
    </html>

    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 1034, Column 1: start tag was here
    <script type='text/javascript'>

Visitor Analysis

Daily Visitor
  • 38 visits

In Page Analysis