trali.com.vn

Thời trang, Thời trang Trali, thời trang công sở, đầm công sở, chân juyp, váy công sở, sơ mi, thời trang khuyến mãi, đầm dạo phố ...

This data was last updated from 23-10-2013 06:38:59  (update).

Overview Info



  • Domain Name
    trali.com.vn
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    3
  • Ip Address
    112.78.6.212
  • Page Size
    78 KB
  • Images
    2 GIF, 40 JPG, 4 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    5 0 1 0 0 0

Website Meta Analysis



  • Title
    THỜI TRANG TRALI
  • Meta Keyword
    Thoi trang, Thời trang, Thoi trang cong so, Thời trang công sở, Đầm công sở, Dam cong so, thời trang khuyến mại, Thời trang, đầm, áo, quần, bộ công sở, thời trang công sở, chân juyp, đầm công sở, đầm dạ hội, đầm dạo phố, áo sơ mi, áo khoác, măng tô, áo len, áo thun, áo đi chơi, quần lửng, quần short
  • Meta Description
    Thời trang, Thời trang Trali, thời trang công sở, đầm công sở, chân juyp, váy công sở, sơ mi, thời trang khuyến mãi, đầm dạo phố

Technical Analysis



  • Webserver
    nginx
  • Ip Address
    112.78.6.212
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Wed, 23 Oct 2013 06:30:47 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.3.3
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for trali.com.vn

IP 112.78.6.212 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 130 Errors
  • 122 Warnings
Ratio Text/Html
  • 0.5721908388341246
Message Error
  • Error Line 48, Column 11: required attribute "type" not specified
        <style>

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

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

  • Error Line 157, Column 12: required attribute "type" not specified
        <script>

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

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

  • Error Line 171, Column 18: there is no attribute "topmargin"
    <body  topmargin="0" style="padding:0px;margin:0px;">

    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 175, Column 71: cannot generate system identifier for general entity "serviceMethod"
    …services.php?serviceModule=Member.SSO&serviceMethod=synchronize&checkUrl=trali…

    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 175, Column 71: general entity "serviceMethod" not defined and no default entity
    …services.php?serviceModule=Member.SSO&serviceMethod=synchronize&checkUrl=trali…

    This is usually a cascading error caused by 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 175, Column 84: reference not terminated by REFC delimiter
    …serviceModule=Member.SSO&serviceMethod=synchronize&checkUrl=trali.com.vn%2F&se…

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

  • Warning Line 175, Column 84: reference to external entity in attribute value
    …serviceModule=Member.SSO&serviceMethod=synchronize&checkUrl=trali.com.vn%2F&se…

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

  • Error Line 175, Column 84: reference to entity "serviceMethod" for which no system identifier could be generated
    …serviceModule=Member.SSO&serviceMethod=synchronize&checkUrl=trali.com.vn%2F&se…

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

  • Info Line 175, Column 70: entity was defined here
    …/services.php?serviceModule=Member.SSO&serviceMethod=synchronize&checkUrl=tral…
  • Warning Line 175, Column 97: cannot generate system identifier for general entity "checkUrl"
    …=Member.SSO&serviceMethod=synchronize&checkUrl=trali.com.vn%2F&sesid=t11vm6tdm…

    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 175, Column 97: general entity "checkUrl" not defined and no default entity
    …=Member.SSO&serviceMethod=synchronize&checkUrl=trali.com.vn%2F&sesid=t11vm6tdm…

    This is usually a cascading error caused by 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 175, Column 105: reference not terminated by REFC delimiter
    …SSO&serviceMethod=synchronize&checkUrl=trali.com.vn%2F&sesid=t11vm6tdm84u9v3e6…

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

  • Warning Line 175, Column 105: reference to external entity in attribute value
    …SSO&serviceMethod=synchronize&checkUrl=trali.com.vn%2F&sesid=t11vm6tdm84u9v3e6…

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

  • Error Line 175, Column 105: reference to entity "checkUrl" for which no system identifier could be generated
    …SSO&serviceMethod=synchronize&checkUrl=trali.com.vn%2F&sesid=t11vm6tdm84u9v3e6…

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

  • Info Line 175, Column 96: entity was defined here
    …e=Member.SSO&serviceMethod=synchronize&checkUrl=trali.com.vn%2F&sesid=t11vm6td…
  • Warning Line 175, Column 122: cannot generate system identifier for general entity "sesid"
    …=synchronize&checkUrl=trali.com.vn%2F&sesid=t11vm6tdm84u9v3e6avbhnfo01" width=…

    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 175, Column 122: general entity "sesid" not defined and no default entity
    …=synchronize&checkUrl=trali.com.vn%2F&sesid=t11vm6tdm84u9v3e6avbhnfo01" width=…

    This is usually a cascading error caused by 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 175, Column 127: reference not terminated by REFC delimiter
    …hronize&checkUrl=trali.com.vn%2F&sesid=t11vm6tdm84u9v3e6avbhnfo01" width="1" h…

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

  • Warning Line 175, Column 127: reference to external entity in attribute value
    …hronize&checkUrl=trali.com.vn%2F&sesid=t11vm6tdm84u9v3e6avbhnfo01" width="1" h…

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

  • Error Line 175, Column 127: reference to entity "sesid" for which no system identifier could be generated
    …hronize&checkUrl=trali.com.vn%2F&sesid=t11vm6tdm84u9v3e6avbhnfo01" width="1" h…

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

  • Info Line 175, Column 121: entity was defined here
    …d=synchronize&checkUrl=trali.com.vn%2F&sesid=t11vm6tdm84u9v3e6avbhnfo01" width…
  • Warning Line 187, Column 43: cannot generate system identifier for general entity "site"
     <a href="http://trali.com.vn/?page=home2&site=55">

    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 187, Column 43: general entity "site" not defined and no default entity
     <a href="http://trali.com.vn/?page=home2&site=55">

    This is usually a cascading error caused by 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 187, Column 47: reference not terminated by REFC delimiter
     <a href="http://trali.com.vn/?page=home2&site=55">

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

  • Warning Line 187, Column 47: reference to external entity in attribute value
     <a href="http://trali.com.vn/?page=home2&site=55">

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

  • Error Line 187, Column 47: reference to entity "site" for which no system identifier could be generated
     <a href="http://trali.com.vn/?page=home2&site=55">

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Error Line 189, Column 103: required attribute "alt" not specified
    …mbo/55/20120606/13389483261265403367logo1_1.png" height="100px" width="210px"/>

    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 196, Column 32: required attribute "action" not specified
     <form method="post" id="form9">

    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 206, Column 115: end tag for "img" omitted, but OMITTAG NO was specified
    …iếng Việt"><img src="/3rdparty/country/smallFlags/vi.png" alt="Tiếng Việt"></a>

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

  • Info Line 206, Column 48: start tag was here
    …"/?setLanguage=vi" title="Tiếng Việt"><img src="/3rdparty/country/smallFlags/v…
  • Error Line 208, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …tle="English"><img src="/3rdparty/country/smallFlags/en.png" alt="English"></a>

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

  • Info Line 208, Column 45: start tag was here
    …ef="/?setLanguage=en" title="English"><img src="/3rdparty/country/smallFlags/e…
  • Error Line 233, Column 15: there is no attribute "rel"
     <ul><li  rel="297346" class="first-item"><a href="http://trali.vn/?page=home2"…

    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 233, Column 1415: character "&" is the first character of a delimiter but occurred as data
    …the+press/297402.html" title="Tin tức & giải trí"><span><span>Tin tức & giải t…

    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 233, Column 1447: character "&" is the first character of a delimiter but occurred as data
    …n tức & giải trí"><span><span>Tin tức & giải trí</span></span></a><ul  style="…

    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 233, Column 1689: character "&" is the first character of a delimiter but occurred as data
    …news/1/375111.html" title="Phong cách & sao">Phong cách & sao</a></li><li  rel…

    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 233, Column 1707: character "&" is the first character of a delimiter but occurred as data
    …" title="Phong cách & sao">Phong cách & sao</a></li><li  rel="297401" ><a href…

    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 233, Column 3191: character "&" is the first character of a delimiter but occurred as data
    …r/297362/trali-sao.html" title="Trali & sao">Trali & sao</a><ul  style="displa…

    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 233, Column 3204: character "&" is the first character of a delimiter but occurred as data
    …i-sao.html" title="Trali & sao">Trali & sao</a><ul  style="display:none"><li  …

    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 233, Column 6416: character "<" is the first character of a delimiter but occurred as data
    … .html" rel="nofollow" title="Liên hệ <span style=&quot;text-decoration:none&q…

    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 233, Column 6463: character "<" is the first character of a delimiter but occurred as data
    …le=&quot;text-decoration:none&quot;>  </span>"><span><span>Liên hệ <span style…

    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 233, Column 6907: cannot generate system identifier for general entity "id"
    …ef="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng …

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

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

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

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

  • Error Line 233, Column 6907: general entity "id" not defined and no default entity
    …ef="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng …

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

  • Warning Line 233, Column 6909: reference not terminated by REFC delimiter
    …="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng cá…

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

  • Warning Line 233, Column 6909: reference to external entity in attribute value
    …="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng cá…

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

  • Error Line 233, Column 6909: reference to entity "id" for which no system identifier could be generated
    …="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng cá…

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

  • Info Line 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 233, Column 6921: reference not terminated by REFC delimiter
    …li.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng cáo">Liên hệ q…

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

  • Warning Line 233, Column 6921: reference to external entity in attribute value
    …li.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng cáo">Liên hệ q…

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

  • Error Line 233, Column 6921: reference to entity "site" for which no system identifier could be generated
    …li.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng cáo">Liên hệ q…

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Warning Line 233, Column 7042: reference not terminated by REFC delimiter
    …="http://trali.com.vn/?page=contact&id=297605&site=55" title="Liên hệ làm đại …

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

  • Warning Line 233, Column 7042: reference to external entity in attribute value
    …="http://trali.com.vn/?page=contact&id=297605&site=55" title="Liên hệ làm đại …

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

  • Error Line 233, Column 7042: reference to entity "id" for which no system identifier could be generated
    …="http://trali.com.vn/?page=contact&id=297605&site=55" title="Liên hệ làm đại …

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

  • Info Line 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 233, Column 7054: reference not terminated by REFC delimiter
    …li.com.vn/?page=contact&id=297605&site=55" title="Liên hệ làm đại lý">Liên hệ …

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

  • Warning Line 233, Column 7054: reference to external entity in attribute value
    …li.com.vn/?page=contact&id=297605&site=55" title="Liên hệ làm đại lý">Liên hệ …

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

  • Error Line 233, Column 7054: reference to entity "site" for which no system identifier could be generated
    …li.com.vn/?page=contact&id=297605&site=55" title="Liên hệ làm đại lý">Liên hệ …

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Warning Line 233, Column 7194: reference not terminated by REFC delimiter
    …="http://trali.com.vn/?page=contact&id=297606&site=55" title="Góp ý">Góp ý</a>…

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

  • Warning Line 233, Column 7194: reference to external entity in attribute value
    …="http://trali.com.vn/?page=contact&id=297606&site=55" title="Góp ý">Góp ý</a>…

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

  • Error Line 233, Column 7194: reference to entity "id" for which no system identifier could be generated
    …="http://trali.com.vn/?page=contact&id=297606&site=55" title="Góp ý">Góp ý</a>…

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

  • Info Line 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 233, Column 7206: reference not terminated by REFC delimiter
    …li.com.vn/?page=contact&id=297606&site=55" title="Góp ý">Góp ý</a></li></ul></…

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

  • Warning Line 233, Column 7206: reference to external entity in attribute value
    …li.com.vn/?page=contact&id=297606&site=55" title="Góp ý">Góp ý</a></li></ul></…

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

  • Error Line 233, Column 7206: reference to entity "site" for which no system identifier could be generated
    …li.com.vn/?page=contact&id=297606&site=55" title="Góp ý">Góp ý</a></li></ul></…

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Error Line 247, Column 53: end tag for "input" omitted, but OMITTAG NO was specified
    …hidden" name="submitFormId" value="9"><input type="hidden" name="moduleId" val…

    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 247, Column 2: start tag was here
     <input type="hidden" name="submitFormId" value="9"><input type="hidden" name="…
  • Error Line 247, Column 106: end tag for "input" omitted, but OMITTAG NO was specified
    …"submitFormId" value="9"><input type="hidden" name="moduleId" value="9"></form>

    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 247, Column 53: start tag was here
    …hidden" name="submitFormId" value="9"><input type="hidden" name="moduleId" val…
  • Error Line 255, Column 7: required attribute "type" not specified
    <style>

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

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

  • Error Line 255, Column 7: document type does not allow element "style" here
    <style>

    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 296, Column 202: required attribute "alt" not specified
    …/55/20131022/ghep63.jpg" title="Rubic of Winter" width="664" height="443"/></a>

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

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

  • Error Line 298, Column 189: required attribute "alt" not specified
    …pload/55/20131023/ghep11.jpg" title="Love Story" width="664" height="443"/></a>

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

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

  • Error Line 300, Column 203: required attribute "alt" not specified
    …55/20131022/ghep321.jpg" title="Rubic of Winter" width="664" height="443"/></a>

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

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

  • Error Line 302, Column 203: required attribute "alt" not specified
    …55/20131022/ghep681.jpg" title="Rubic of Winter" width="664" height="443"/></a>

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

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

  • Error Line 304, Column 201: required attribute "alt" not specified
    …d/55/20131022/ghep7.jpg" title="Rubic of Winter" width="664" height="443"/></a>

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

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

  • Error Line 306, Column 202: required attribute "alt" not specified
    …/55/20131023/ghep12.jpg" title="Rubic of Winter" width="664" height="443"/></a>

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

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

  • Error Line 308, Column 202: required attribute "alt" not specified
    …/55/20131023/ghep13.jpg" title="Rubic of Winter" width="664" height="443"/></a>

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

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

  • Warning Line 321, Column 160: character "&" is the first character of a delimiter but occurred as data
    …rc="/upload/Colombo/55/20121108/trali & bao chi_chuan_3 copy.jpg" width="320" …

    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 321, Column 222: there is no attribute "onerror"
    …pg" width="320" height="83px" onerror="this.src='/EStore/Default/skins/Default…

    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 390, Column 206: "Thiên" is not a member of a group specified for any attribute
    …60502025__2_m__u.jpg" alt="BST "Thiên đường mùa thu" - Món quà từ Trali" onerr…
  • Error Line 390, Column 212: "đường" is not a member of a group specified for any attribute
    …25__2_m__u.jpg" alt="BST "Thiên đường mùa thu" - Món quà từ Trali" onerror="th…
  • Error Line 390, Column 216: "mùa" is not a member of a group specified for any attribute
    …2_m__u.jpg" alt="BST "Thiên đường mùa thu" - Món quà từ Trali" onerror="this.s…
  • Error Line 390, Column 219: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …__u.jpg" alt="BST "Thiên đường mùa thu" - Món quà từ Trali" onerror="this.src=…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 390, Column 220: end tag for "img" omitted, but OMITTAG NO was specified
    …_u.jpg" alt="BST "Thiên đường mùa thu" - Món quà từ Trali" onerror="this.src='…

    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 390, Column 90: start tag was here
    …-duong-mua-thu-mon-qua-tu-trali.html"><img src="/publish/thumbnail/55/320x480x…
  • Error Line 455, Column 11: ID "detail-news-cluetip" already defined
     <div id="detail-news-cluetip" style="display:none"><span>C&aacute;c mẫu trang …

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 447, Column 11: ID "detail-news-cluetip" first defined here
     <div id="detail-news-cluetip" style="display:none"><span>Thanh lịch, sang trọn…
  • Error Line 463, Column 11: ID "detail-news-cluetip" already defined
     <div id="detail-news-cluetip" style="display:none"><span>H&atilde;ng ra mắt bộ…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 447, Column 11: ID "detail-news-cluetip" first defined here
     <div id="detail-news-cluetip" style="display:none"><span>Thanh lịch, sang trọn…
  • Error Line 471, Column 11: ID "detail-news-cluetip" already defined
     <div id="detail-news-cluetip" style="display:none"><span>M&oacute;n qu&agrave;…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 447, Column 11: ID "detail-news-cluetip" first defined here
     <div id="detail-news-cluetip" style="display:none"><span>Thanh lịch, sang trọn…
  • Warning Line 491, Column 161: character "&" is the first character of a delimiter but occurred as data
    …frame-header"><div><div><b>Phong cách & sao</b></div></div></div><div class="f…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 498, Column 292: required attribute "alt" not specified
    …31021/grab1382343664xe_dui3_4611_1382088488.jpg" width="152" height="228"/></a>

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

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

  • Error Line 512, Column 301: required attribute "alt" not specified
    …0926/grab1380168996grab1380168964HO_NGOC_HA.jpg" width="152" height="228"/></a>

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

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

  • Error Line 526, Column 293: required attribute "alt" not specified
    …0130911/grab1378887521grab1378887458image14.jpg" width="152" height="228"/></a>

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

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

  • Warning Line 530, Column 247: character "&" is the first character of a delimiter but occurred as data
    …st-xuan-2014-ready-to-wear.html">Sass & Bide giới thiệu BST Xuân 2014 Ready-to…

    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 540, Column 276: required attribute "alt" not specified
    …lt/upload/55/20130911/grab1378886946image18.jpg" width="152" height="228"/></a>

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

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

  • Error Line 554, Column 260: required attribute "alt" not specified
    …default/upload/55/20130909/sao tren tham do.JPG" width="152" height="228"/></a>

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

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

  • Error Line 568, Column 260: required attribute "alt" not specified
    …xdefault/upload/55/20130909/Erin Fetherson1.JPG" width="152" height="228"/></a>

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

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

  • Error Line 588, Column 294: required attribute "alt" not specified
    …382342901grab1382342864a1_1791_138232731388.jpg" width="152" height="228"/></a>

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

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

  • Error Line 602, Column 260: required attribute "alt" not specified
    …lt/upload/55/20131003/grab1380784386image08.jpg" width="152" height="228"/></a>

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

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

  • Error Line 616, Column 267: required attribute "alt" not specified
    …lt/upload/55/20131003/grab1380784081image01.jpg" width="152" height="228"/></a>

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

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

  • Error Line 630, Column 267: required attribute "alt" not specified
    …lt/upload/55/20130917/grab1379384351image15.jpg" width="152" height="228"/></a>

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

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

  • Error Line 644, Column 290: required attribute "alt" not specified
    …lt/upload/55/20130917/grab1379384029image11.jpg" width="152" height="228"/></a>

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

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

  • Error Line 658, Column 264: required attribute "alt" not specified
    …fault/upload/55/20130912/grab1378972005vera.jpg" width="152" height="228"/></a>

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

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

  • Error Line 671, Column 89: end tag for "div" omitted, but OMITTAG NO was specified
    …v></div></div><div class="frame-footer"><div><div></div></div></div></div></td>

    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 581, Column 85: start tag was here
    …er"><div><div></div></div></div></div><div class="frame-ribbon"><div class="fr…
  • Error Line 671, Column 89: end tag for "div" omitted, but OMITTAG NO was specified
    …v></div></div><div class="frame-footer"><div><div></div></div></div></div></td>

    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 491, Column 85: start tag was here
    …er"><div><div></div></div></div></div><div class="frame-ribbon"><div class="fr…
  • Error Line 675, Column 120: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …eight:bold; letter-spacing:0.2em"><span><h3>LIÊN HỆ VỚI TRALI</h3></span></div>

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

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

  • Error Line 737, Column 413: there is no attribute "allowfullscreen"
    …om/embed/5k_3NMoHwOM" allowfullscreen="" width="300" frameborder="0" height="3…

    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 765, Column 190: required attribute "alt" not specified
    …rc="/upload/55/20131018/grab1382080928thao1.jpg" width="105" height="160"/></a>

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

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

  • Error Line 782, Column 208: required attribute "alt" not specified
    …his.src='/EStore/Default/skins/Default/images/no-image-news.gif';" width="90"/>

    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 796, Column 204: required attribute "alt" not specified
    …his.src='/EStore/Default/skins/Default/images/no-image-news.gif';" width="90"/>

    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 819, Column 183: required attribute "alt" not specified
    …his.src='/EStore/Default/skins/Default/images/no-image-news.gif';" width="90"/>

    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 833, Column 195: required attribute "alt" not specified
    …his.src='/EStore/Default/skins/Default/images/no-image-news.gif';" width="90"/>

    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 854, Column 110: cannot generate system identifier for general entity "TINH"
    …inh-te.html" title="MAKEUP NHẸ NHÀNG &TINH TẾ" class="cluetip-data" rel="#deta…

    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 854, Column 110: general entity "TINH" not defined and no default entity
    …inh-te.html" title="MAKEUP NHẸ NHÀNG &TINH TẾ" class="cluetip-data" rel="#deta…

    This is usually a cascading error caused by 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 854, Column 114: reference not terminated by REFC delimiter
    …te.html" title="MAKEUP NHẸ NHÀNG &TINH TẾ" class="cluetip-data" rel="#detail-n…

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

  • Warning Line 854, Column 114: reference to external entity in attribute value
    …te.html" title="MAKEUP NHẸ NHÀNG &TINH TẾ" class="cluetip-data" rel="#detail-n…

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

  • Error Line 854, Column 114: reference to entity "TINH" for which no system identifier could be generated
    …te.html" title="MAKEUP NHẸ NHÀNG &TINH TẾ" class="cluetip-data" rel="#detail-n…

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

  • Info Line 854, Column 109: entity was defined here
    …tinh-te.html" title="MAKEUP NHẸ NHÀNG &TINH TẾ" class="cluetip-data" rel="#det…
  • Error Line 856, Column 190: required attribute "alt" not specified
    …his.src='/EStore/Default/skins/Default/images/no-image-news.gif';" width="90"/>

    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 858, Column 24: reference not terminated by REFC delimiter
     MAKEUP NHẸ NHÀNG &TINH TẾ</a>

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

  • Error Line 858, Column 24: reference to entity "TINH" for which no system identifier could be generated
     MAKEUP NHẸ NHÀNG &TINH TẾ</a>

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

  • Info Line 854, Column 109: entity was defined here
    …tinh-te.html" title="MAKEUP NHẸ NHÀNG &TINH TẾ" class="cluetip-data" rel="#det…
  • Error Line 870, Column 196: required attribute "alt" not specified
    …his.src='/EStore/Default/skins/Default/images/no-image-news.gif';" width="90"/>

    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 884, Column 172: required attribute "alt" not specified
    …his.src='/EStore/Default/skins/Default/images/no-image-news.gif';" width="90"/>

    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 917, Column 50: reference not terminated by REFC delimiter
    …ttp://trali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+q…

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

  • Warning Line 917, Column 50: reference to external entity in attribute value
    …ttp://trali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+q…

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

  • Error Line 917, Column 50: reference to entity "id" for which no system identifier could be generated
    …ttp://trali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+q…

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

  • Info Line 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 917, Column 58: cannot generate system identifier for general entity "title"
    …ali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1n…

    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 917, Column 58: general entity "title" not defined and no default entity
    …ali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1n…

    This is usually a cascading error caused by 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 917, Column 63: reference not terminated by REFC delimiter
    …om.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1n+%C4%…

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

  • Warning Line 917, Column 63: reference to external entity in attribute value
    …om.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1n+%C4%…

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

  • Error Line 917, Column 63: reference to entity "title" for which no system identifier could be generated
    …om.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1n+%C4%…

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

  • Info Line 917, Column 57: entity was defined here
    …rali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1…
  • Warning Line 917, Column 146: reference not terminated by REFC delimiter
    …gon+%E1%BB%9F+H%C3%A0+N%E1%BB%99i&site=55"><img style="margin:2px; border:1px …

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

  • Warning Line 917, Column 146: reference to external entity in attribute value
    …gon+%E1%BB%9F+H%C3%A0+N%E1%BB%99i&site=55"><img style="margin:2px; border:1px …

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

  • Error Line 917, Column 146: reference to entity "site" for which no system identifier could be generated
    …gon+%E1%BB%9F+H%C3%A0+N%E1%BB%99i&site=55"><img style="margin:2px; border:1px …

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Error Line 917, Column 342: required attribute "alt" not specified
    …30920/grab1379667853grab1379667813quanngon4.jpg" width="152" height="228"/></a>

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

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

  • Warning Line 921, Column 199: reference not terminated by REFC delimiter
    …ttp://trali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+q…

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

  • Warning Line 921, Column 199: reference to external entity in attribute value
    …ttp://trali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+q…

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

  • Error Line 921, Column 199: reference to entity "id" for which no system identifier could be generated
    …ttp://trali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+q…

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

  • Info Line 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 921, Column 212: reference not terminated by REFC delimiter
    …om.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1n+%C4%…

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

  • Warning Line 921, Column 212: reference to external entity in attribute value
    …om.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1n+%C4%…

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

  • Error Line 921, Column 212: reference to entity "title" for which no system identifier could be generated
    …om.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1n+%C4%…

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

  • Info Line 917, Column 57: entity was defined here
    …rali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1…
  • Warning Line 921, Column 295: reference not terminated by REFC delimiter
    …gon+%E1%BB%9F+H%C3%A0+N%E1%BB%99i&site=55">Tổng hợp quán ăn ngon ở Hà Nội</a><…

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

  • Warning Line 921, Column 295: reference to external entity in attribute value
    …gon+%E1%BB%9F+H%C3%A0+N%E1%BB%99i&site=55">Tổng hợp quán ăn ngon ở Hà Nội</a><…

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

  • Error Line 921, Column 295: reference to entity "site" for which no system identifier could be generated
    …gon+%E1%BB%9F+H%C3%A0+N%E1%BB%99i&site=55">Tổng hợp quán ăn ngon ở Hà Nội</a><…

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Warning Line 931, Column 50: reference not terminated by REFC delimiter
    …ttp://trali.com.vn/?page=newsDetail&id=738221&title=10+h%C3%B2n+%C4%91%E1%BA%A…

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

  • Warning Line 931, Column 50: reference to external entity in attribute value
    …ttp://trali.com.vn/?page=newsDetail&id=738221&title=10+h%C3%B2n+%C4%91%E1%BA%A…

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

  • Error Line 931, Column 50: reference to entity "id" for which no system identifier could be generated
    …ttp://trali.com.vn/?page=newsDetail&id=738221&title=10+h%C3%B2n+%C4%91%E1%BA%A…

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

  • Info Line 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 931, Column 63: reference not terminated by REFC delimiter
    …om.vn/?page=newsDetail&id=738221&title=10+h%C3%B2n+%C4%91%E1%BA%A3o+quy%E1%BA%…

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

  • Warning Line 931, Column 63: reference to external entity in attribute value
    …om.vn/?page=newsDetail&id=738221&title=10+h%C3%B2n+%C4%91%E1%BA%A3o+quy%E1%BA%…

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

  • Error Line 931, Column 63: reference to entity "title" for which no system identifier could be generated
    …om.vn/?page=newsDetail&id=738221&title=10+h%C3%B2n+%C4%91%E1%BA%A3o+quy%E1%BA%…

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

  • Info Line 917, Column 57: entity was defined here
    …rali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1…
  • Warning Line 931, Column 133: reference not terminated by REFC delimiter
    …y%E1%BA%BFn+r%C5%A9+du+kh%C3%A1ch&site=55"><img style="margin:2px; border:1px …

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

  • Warning Line 931, Column 133: reference to external entity in attribute value
    …y%E1%BA%BFn+r%C5%A9+du+kh%C3%A1ch&site=55"><img style="margin:2px; border:1px …

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

  • Error Line 931, Column 133: reference to entity "site" for which no system identifier could be generated
    …y%E1%BA%BFn+r%C5%A9+du+kh%C3%A1ch&site=55"><img style="margin:2px; border:1px …

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Error Line 931, Column 351: required attribute "alt" not specified
    …dao_dep_JPG_4928_1382351578_5917_1382354518.jpg" width="152" height="228"/></a>

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

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

  • Warning Line 935, Column 199: reference not terminated by REFC delimiter
    …ttp://trali.com.vn/?page=newsDetail&id=738221&title=10+h%C3%B2n+%C4%91%E1%BA%A…

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

  • Warning Line 935, Column 199: reference to external entity in attribute value
    …ttp://trali.com.vn/?page=newsDetail&id=738221&title=10+h%C3%B2n+%C4%91%E1%BA%A…

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

  • Error Line 935, Column 199: reference to entity "id" for which no system identifier could be generated
    …ttp://trali.com.vn/?page=newsDetail&id=738221&title=10+h%C3%B2n+%C4%91%E1%BA%A…

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

  • Info Line 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 935, Column 212: reference not terminated by REFC delimiter
    …om.vn/?page=newsDetail&id=738221&title=10+h%C3%B2n+%C4%91%E1%BA%A3o+quy%E1%BA%…

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

  • Warning Line 935, Column 212: reference to external entity in attribute value
    …om.vn/?page=newsDetail&id=738221&title=10+h%C3%B2n+%C4%91%E1%BA%A3o+quy%E1%BA%…

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

  • Error Line 935, Column 212: reference to entity "title" for which no system identifier could be generated
    …om.vn/?page=newsDetail&id=738221&title=10+h%C3%B2n+%C4%91%E1%BA%A3o+quy%E1%BA%…

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

  • Info Line 917, Column 57: entity was defined here
    …rali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1…
  • Warning Line 935, Column 282: reference not terminated by REFC delimiter
    …y%E1%BA%BFn+r%C5%A9+du+kh%C3%A1ch&site=55">10 hòn đảo quyến rũ du khách</a></d…

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

  • Warning Line 935, Column 282: reference to external entity in attribute value
    …y%E1%BA%BFn+r%C5%A9+du+kh%C3%A1ch&site=55">10 hòn đảo quyến rũ du khách</a></d…

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

  • Error Line 935, Column 282: reference to entity "site" for which no system identifier could be generated
    …y%E1%BA%BFn+r%C5%A9+du+kh%C3%A1ch&site=55">10 hòn đảo quyến rũ du khách</a></d…

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Warning Line 945, Column 50: reference not terminated by REFC delimiter
    …ttp://trali.com.vn/?page=newsDetail&id=693149&title=H%C3%A3y+di%E1%BB%87n+ngay…

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

  • Warning Line 945, Column 50: reference to external entity in attribute value
    …ttp://trali.com.vn/?page=newsDetail&id=693149&title=H%C3%A3y+di%E1%BB%87n+ngay…

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

  • Error Line 945, Column 50: reference to entity "id" for which no system identifier could be generated
    …ttp://trali.com.vn/?page=newsDetail&id=693149&title=H%C3%A3y+di%E1%BB%87n+ngay…

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

  • Info Line 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 945, Column 63: reference not terminated by REFC delimiter
    …om.vn/?page=newsDetail&id=693149&title=H%C3%A3y+di%E1%BB%87n+ngay+xu+h%C6%B0%E…

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

  • Warning Line 945, Column 63: reference to external entity in attribute value
    …om.vn/?page=newsDetail&id=693149&title=H%C3%A3y+di%E1%BB%87n+ngay+xu+h%C6%B0%E…

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

  • Error Line 945, Column 63: reference to entity "title" for which no system identifier could be generated
    …om.vn/?page=newsDetail&id=693149&title=H%C3%A3y+di%E1%BB%87n+ngay+xu+h%C6%B0%E…

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

  • Info Line 917, Column 57: entity was defined here
    …rali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1…
  • Warning Line 945, Column 211: reference not terminated by REFC delimiter
    …h%C3%A1i+cho+b%E1%BA%A1n+g%C3%A1i&site=55"><img style="margin:2px; border:1px …

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

  • Warning Line 945, Column 211: reference to external entity in attribute value
    …h%C3%A1i+cho+b%E1%BA%A1n+g%C3%A1i&site=55"><img style="margin:2px; border:1px …

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

  • Error Line 945, Column 211: reference to entity "site" for which no system identifier could be generated
    …h%C3%A1i+cho+b%E1%BA%A1n+g%C3%A1i&site=55"><img style="margin:2px; border:1px …

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Error Line 945, Column 375: required attribute "alt" not specified
    …55/152x228xdefault//upload/55/fck/PHU KIEN1.JPG" width="152" height="228"/></a>

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

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

  • Warning Line 949, Column 199: reference not terminated by REFC delimiter
    …ttp://trali.com.vn/?page=newsDetail&id=693149&title=H%C3%A3y+di%E1%BB%87n+ngay…

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

  • Warning Line 949, Column 199: reference to external entity in attribute value
    …ttp://trali.com.vn/?page=newsDetail&id=693149&title=H%C3%A3y+di%E1%BB%87n+ngay…

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

  • Error Line 949, Column 199: reference to entity "id" for which no system identifier could be generated
    …ttp://trali.com.vn/?page=newsDetail&id=693149&title=H%C3%A3y+di%E1%BB%87n+ngay…

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

  • Info Line 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 949, Column 212: reference not terminated by REFC delimiter
    …om.vn/?page=newsDetail&id=693149&title=H%C3%A3y+di%E1%BB%87n+ngay+xu+h%C6%B0%E…

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

  • Warning Line 949, Column 212: reference to external entity in attribute value
    …om.vn/?page=newsDetail&id=693149&title=H%C3%A3y+di%E1%BB%87n+ngay+xu+h%C6%B0%E…

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

  • Error Line 949, Column 212: reference to entity "title" for which no system identifier could be generated
    …om.vn/?page=newsDetail&id=693149&title=H%C3%A3y+di%E1%BB%87n+ngay+xu+h%C6%B0%E…

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

  • Info Line 917, Column 57: entity was defined here
    …rali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1…
  • Warning Line 949, Column 360: reference not terminated by REFC delimiter
    …h%C3%A1i+cho+b%E1%BA%A1n+g%C3%A1i&site=55">Hãy diện ngay xu hướng mùa thu này:…

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

  • Warning Line 949, Column 360: reference to external entity in attribute value
    …h%C3%A1i+cho+b%E1%BA%A1n+g%C3%A1i&site=55">Hãy diện ngay xu hướng mùa thu này:…

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

  • Error Line 949, Column 360: reference to entity "site" for which no system identifier could be generated
    …h%C3%A1i+cho+b%E1%BA%A1n+g%C3%A1i&site=55">Hãy diện ngay xu hướng mùa thu này:…

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Warning Line 959, Column 50: reference not terminated by REFC delimiter
    …ttp://trali.com.vn/?page=newsDetail&id=467894&title=10+t%C3%B4ng+m%C3%A0u+tran…

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

  • Warning Line 959, Column 50: reference to external entity in attribute value
    …ttp://trali.com.vn/?page=newsDetail&id=467894&title=10+t%C3%B4ng+m%C3%A0u+tran…

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

  • Error Line 959, Column 50: reference to entity "id" for which no system identifier could be generated
    …ttp://trali.com.vn/?page=newsDetail&id=467894&title=10+t%C3%B4ng+m%C3%A0u+tran…

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

  • Info Line 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 959, Column 63: reference not terminated by REFC delimiter
    …om.vn/?page=newsDetail&id=467894&title=10+t%C3%B4ng+m%C3%A0u+trang+%C4%91i%E1%…

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

  • Warning Line 959, Column 63: reference to external entity in attribute value
    …om.vn/?page=newsDetail&id=467894&title=10+t%C3%B4ng+m%C3%A0u+trang+%C4%91i%E1%…

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

  • Error Line 959, Column 63: reference to entity "title" for which no system identifier could be generated
    …om.vn/?page=newsDetail&id=467894&title=10+t%C3%B4ng+m%C3%A0u+trang+%C4%91i%E1%…

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

  • Info Line 917, Column 57: entity was defined here
    …rali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1…
  • Warning Line 959, Column 171: reference not terminated by REFC delimiter
    …+l%C3%AAn+ng%C3%B4i+n%C4%83m+2013&site=55"><img style="margin:2px; border:1px …

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

  • Warning Line 959, Column 171: reference to external entity in attribute value
    …+l%C3%AAn+ng%C3%B4i+n%C4%83m+2013&site=55"><img style="margin:2px; border:1px …

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

  • Error Line 959, Column 171: reference to entity "site" for which no system identifier could be generated
    …+l%C3%AAn+ng%C3%B4i+n%C4%83m+2013&site=55"><img style="margin:2px; border:1px …

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Error Line 959, Column 374: required attribute "alt" not specified
    …6122012tongmauxuhuongthoitrangtinmoi_11 (1).jpg" width="152" height="228"/></a>

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

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

  • Warning Line 963, Column 199: reference not terminated by REFC delimiter
    …ttp://trali.com.vn/?page=newsDetail&id=467894&title=10+t%C3%B4ng+m%C3%A0u+tran…

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

  • Warning Line 963, Column 199: reference to external entity in attribute value
    …ttp://trali.com.vn/?page=newsDetail&id=467894&title=10+t%C3%B4ng+m%C3%A0u+tran…

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

  • Error Line 963, Column 199: reference to entity "id" for which no system identifier could be generated
    …ttp://trali.com.vn/?page=newsDetail&id=467894&title=10+t%C3%B4ng+m%C3%A0u+tran…

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

  • Info Line 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 963, Column 212: reference not terminated by REFC delimiter
    …om.vn/?page=newsDetail&id=467894&title=10+t%C3%B4ng+m%C3%A0u+trang+%C4%91i%E1%…

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

  • Warning Line 963, Column 212: reference to external entity in attribute value
    …om.vn/?page=newsDetail&id=467894&title=10+t%C3%B4ng+m%C3%A0u+trang+%C4%91i%E1%…

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

  • Error Line 963, Column 212: reference to entity "title" for which no system identifier could be generated
    …om.vn/?page=newsDetail&id=467894&title=10+t%C3%B4ng+m%C3%A0u+trang+%C4%91i%E1%…

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

  • Info Line 917, Column 57: entity was defined here
    …rali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1…
  • Warning Line 963, Column 320: reference not terminated by REFC delimiter
    …+l%C3%AAn+ng%C3%B4i+n%C4%83m+2013&site=55">10 tông màu trang điểm hứa hẹn lên …

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

  • Warning Line 963, Column 320: reference to external entity in attribute value
    …+l%C3%AAn+ng%C3%B4i+n%C4%83m+2013&site=55">10 tông màu trang điểm hứa hẹn lên …

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

  • Error Line 963, Column 320: reference to entity "site" for which no system identifier could be generated
    …+l%C3%AAn+ng%C3%B4i+n%C4%83m+2013&site=55">10 tông màu trang điểm hứa hẹn lên …

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Warning Line 973, Column 50: reference not terminated by REFC delimiter
    …ttp://trali.com.vn/?page=newsDetail&id=738179&title=T%C3%B3c+cho+n%C3%A0ng+c%C…

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

  • Warning Line 973, Column 50: reference to external entity in attribute value
    …ttp://trali.com.vn/?page=newsDetail&id=738179&title=T%C3%B3c+cho+n%C3%A0ng+c%C…

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

  • Error Line 973, Column 50: reference to entity "id" for which no system identifier could be generated
    …ttp://trali.com.vn/?page=newsDetail&id=738179&title=T%C3%B3c+cho+n%C3%A0ng+c%C…

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

  • Info Line 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 973, Column 63: reference not terminated by REFC delimiter
    …om.vn/?page=newsDetail&id=738179&title=T%C3%B3c+cho+n%C3%A0ng+c%C3%B4ng+s%E1%B…

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

  • Warning Line 973, Column 63: reference to external entity in attribute value
    …om.vn/?page=newsDetail&id=738179&title=T%C3%B3c+cho+n%C3%A0ng+c%C3%B4ng+s%E1%B…

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

  • Error Line 973, Column 63: reference to entity "title" for which no system identifier could be generated
    …om.vn/?page=newsDetail&id=738179&title=T%C3%B3c+cho+n%C3%A0ng+c%C3%B4ng+s%E1%B…

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

  • Info Line 917, Column 57: entity was defined here
    …rali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1…
  • Warning Line 973, Column 112: reference not terminated by REFC delimiter
    …ho+n%C3%A0ng+c%C3%B4ng+s%E1%BB%9F&site=55"><img style="margin:2px; border:1px …

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

  • Warning Line 973, Column 112: reference to external entity in attribute value
    …ho+n%C3%A0ng+c%C3%B4ng+s%E1%BB%9F&site=55"><img style="margin:2px; border:1px …

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

  • Error Line 973, Column 112: reference to entity "site" for which no system identifier could be generated
    …ho+n%C3%A0ng+c%C3%B4ng+s%E1%BB%9F&site=55"><img style="margin:2px; border:1px …

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Error Line 973, Column 309: required attribute "alt" not specified
    …0911/grab1378887816CACH_LAM_TOC_CHO_CONG_SO.jpg" width="152" height="228"/></a>

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

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

  • Warning Line 977, Column 199: reference not terminated by REFC delimiter
    …ttp://trali.com.vn/?page=newsDetail&id=738179&title=T%C3%B3c+cho+n%C3%A0ng+c%C…

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

  • Warning Line 977, Column 199: reference to external entity in attribute value
    …ttp://trali.com.vn/?page=newsDetail&id=738179&title=T%C3%B3c+cho+n%C3%A0ng+c%C…

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

  • Error Line 977, Column 199: reference to entity "id" for which no system identifier could be generated
    …ttp://trali.com.vn/?page=newsDetail&id=738179&title=T%C3%B3c+cho+n%C3%A0ng+c%C…

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

  • Info Line 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 977, Column 212: reference not terminated by REFC delimiter
    …om.vn/?page=newsDetail&id=738179&title=T%C3%B3c+cho+n%C3%A0ng+c%C3%B4ng+s%E1%B…

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

  • Warning Line 977, Column 212: reference to external entity in attribute value
    …om.vn/?page=newsDetail&id=738179&title=T%C3%B3c+cho+n%C3%A0ng+c%C3%B4ng+s%E1%B…

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

  • Error Line 977, Column 212: reference to entity "title" for which no system identifier could be generated
    …om.vn/?page=newsDetail&id=738179&title=T%C3%B3c+cho+n%C3%A0ng+c%C3%B4ng+s%E1%B…

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

  • Info Line 917, Column 57: entity was defined here
    …rali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1…
  • Warning Line 977, Column 261: reference not terminated by REFC delimiter
    …%B3c+cho+n%C3%A0ng+c%C3%B4ng+s%E1%BB%9F&site=55">Tóc cho nàng công sở</a></div>

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

  • Warning Line 977, Column 261: reference to external entity in attribute value
    …%B3c+cho+n%C3%A0ng+c%C3%B4ng+s%E1%BB%9F&site=55">Tóc cho nàng công sở</a></div>

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

  • Error Line 977, Column 261: reference to entity "site" for which no system identifier could be generated
    …%B3c+cho+n%C3%A0ng+c%C3%B4ng+s%E1%BB%9F&site=55">Tóc cho nàng công sở</a></div>

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Warning Line 987, Column 50: reference not terminated by REFC delimiter
    …ttp://trali.com.vn/?page=newsDetail&id=462415&title=M%E1%BA%B9o+ch%E1%BA%A3i+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.

  • Warning Line 987, Column 50: reference to external entity in attribute value
    …ttp://trali.com.vn/?page=newsDetail&id=462415&title=M%E1%BA%B9o+ch%E1%BA%A3i+m…

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

  • Error Line 987, Column 50: reference to entity "id" for which no system identifier could be generated
    …ttp://trali.com.vn/?page=newsDetail&id=462415&title=M%E1%BA%B9o+ch%E1%BA%A3i+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 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 987, Column 63: reference not terminated by REFC delimiter
    …om.vn/?page=newsDetail&id=462415&title=M%E1%BA%B9o+ch%E1%BA%A3i+mascara+chu%E1…

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

  • Warning Line 987, Column 63: reference to external entity in attribute value
    …om.vn/?page=newsDetail&id=462415&title=M%E1%BA%B9o+ch%E1%BA%A3i+mascara+chu%E1…

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

  • Error Line 987, Column 63: reference to entity "title" for which no system identifier could be generated
    …om.vn/?page=newsDetail&id=462415&title=M%E1%BA%B9o+ch%E1%BA%A3i+mascara+chu%E1…

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

  • Info Line 917, Column 57: entity was defined here
    …rali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1…
  • Warning Line 987, Column 128: reference not terminated by REFC delimiter
    …ascara+chu%E1%BA%A9n+nh%E1%BA%A5t&site=55"><img style="margin:2px; border:1px …

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

  • Warning Line 987, Column 128: reference to external entity in attribute value
    …ascara+chu%E1%BA%A9n+nh%E1%BA%A5t&site=55"><img style="margin:2px; border:1px …

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

  • Error Line 987, Column 128: reference to entity "site" for which no system identifier could be generated
    …ascara+chu%E1%BA%A9n+nh%E1%BA%A5t&site=55"><img style="margin:2px; border:1px …

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Error Line 987, Column 292: required attribute "alt" not specified
    …55/152x228xdefault/upload/55/20130410/lon-5.jpg" width="152" height="228"/></a>

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

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

  • Warning Line 991, Column 199: reference not terminated by REFC delimiter
    …ttp://trali.com.vn/?page=newsDetail&id=462415&title=M%E1%BA%B9o+ch%E1%BA%A3i+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.

  • Warning Line 991, Column 199: reference to external entity in attribute value
    …ttp://trali.com.vn/?page=newsDetail&id=462415&title=M%E1%BA%B9o+ch%E1%BA%A3i+m…

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

  • Error Line 991, Column 199: reference to entity "id" for which no system identifier could be generated
    …ttp://trali.com.vn/?page=newsDetail&id=462415&title=M%E1%BA%B9o+ch%E1%BA%A3i+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 233, Column 6906: entity was defined here
    …ref="http://trali.com.vn/?page=contact&id=297604&site=55" title="Liên hệ quảng…
  • Warning Line 991, Column 212: reference not terminated by REFC delimiter
    …om.vn/?page=newsDetail&id=462415&title=M%E1%BA%B9o+ch%E1%BA%A3i+mascara+chu%E1…

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

  • Warning Line 991, Column 212: reference to external entity in attribute value
    …om.vn/?page=newsDetail&id=462415&title=M%E1%BA%B9o+ch%E1%BA%A3i+mascara+chu%E1…

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

  • Error Line 991, Column 212: reference to entity "title" for which no system identifier could be generated
    …om.vn/?page=newsDetail&id=462415&title=M%E1%BA%B9o+ch%E1%BA%A3i+mascara+chu%E1…

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

  • Info Line 917, Column 57: entity was defined here
    …rali.com.vn/?page=newsDetail&id=738192&title=T%E1%BB%95ng+h%E1%BB%A3p+qu%C3%A1…
  • Warning Line 991, Column 277: reference not terminated by REFC delimiter
    …ascara+chu%E1%BA%A9n+nh%E1%BA%A5t&site=55">Mẹo chải mascara chuẩn nhất</a></di…

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

  • Warning Line 991, Column 277: reference to external entity in attribute value
    …ascara+chu%E1%BA%A9n+nh%E1%BA%A5t&site=55">Mẹo chải mascara chuẩn nhất</a></di…

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

  • Error Line 991, Column 277: reference to entity "site" for which no system identifier could be generated
    …ascara+chu%E1%BA%A9n+nh%E1%BA%A5t&site=55">Mẹo chải mascara chuẩn nhất</a></di…

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Error Line 1011, Column 74: end tag for "input" omitted, but OMITTAG NO was specified
     <input type="text" name="email" id="email" size="" class="footer-email">

    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 1011, Column 2: start tag was here
     <input type="text" name="email" id="email" size="" class="footer-email">
  • Error Line 1023, Column 41: end tag for "input" omitted, but OMITTAG NO was specified
     });" value="Gửi" class="footer-submit">

    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 1013, Column 2: start tag was here
     <input type="submit" onclick="javascript:VHV.Model('CRM.Newsletter.register')({
  • Error Line 1031, Column 178: required attribute "alt" not specified
    …" width="50px" src="/EStore/Trali/skins/Default/images/facebook.gif"></a>&nbsp;

    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 1031, Column 182: end tag for "img" omitted, but OMITTAG NO was specified
    …" width="50px" src="/EStore/Trali/skins/Default/images/facebook.gif"></a>&nbsp;

    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 1031, Column 93: start tag was here
    …ali/402275686512332" class="facebook"><img height="19px" width="50px" src="/ES…
  • Error Line 1032, Column 149: required attribute "alt" not specified
    …t="19px" width="72px" src="/EStore/Trali/skins/Default/images/tweiter.gif"></a>

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

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

  • Error Line 1032, Column 153: end tag for "img" omitted, but OMITTAG NO was specified
    …t="19px" width="72px" src="/EStore/Trali/skins/Default/images/tweiter.gif"></a>

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

  • Info Line 1032, Column 65: start tag was here
    …com/thoitrangcongso" class="facebook"><img height="19px" width="72px" src="/ES…
  • Warning Line 1051, Column 69: reference not terminated by REFC delimiter
    …f="http://trali.com.vn/?page=cart&site=55"><img src="/EStore/Trali/skins/Defau…

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

  • Warning Line 1051, Column 69: reference to external entity in attribute value
    …f="http://trali.com.vn/?page=cart&site=55"><img src="/EStore/Trali/skins/Defau…

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

  • Error Line 1051, Column 69: reference to entity "site" for which no system identifier could be generated
    …f="http://trali.com.vn/?page=cart&site=55"><img src="/EStore/Trali/skins/Defau…

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Error Line 1051, Column 157: required attribute "alt" not specified
    …re/Trali/skins/Default/images/cart_icon.png" width="44" height="40"/></a></div>

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

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

  • Warning Line 1053, Column 46: reference not terminated by REFC delimiter
    …f="http://trali.com.vn/?page=cart&site=55" title="Cart"><span style="color:red…

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

  • Warning Line 1053, Column 46: reference to external entity in attribute value
    …f="http://trali.com.vn/?page=cart&site=55" title="Cart"><span style="color:red…

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

  • Error Line 1053, Column 46: reference to entity "site" for which no system identifier could be generated
    …f="http://trali.com.vn/?page=cart&site=55" title="Cart"><span style="color:red…

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Error Line 1077, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 179, Column 2: start tag was here
    	<div id="whole-page" style="width:auto">
  • Error Line 1079, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    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 1087, Column 74: document type does not allow element "script" here
    …"/3rdparty/jQuery/jquery-1.9.1.min.js"></script><script type="text/javascript"…

    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 1087, Column 128: document type does not allow element "script" here
    …y-1.9.1.min.js"></script><script type="text/javascript" src="/lib.js"></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).

  • Error Line 1090, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    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 1188, Column 19: character "&" is the first character of a delimiter but occurred as data
    if($.browser.msie && VHV.urlMode == 'ajax')

    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 1188, Column 20: character "&" is the first character of a delimiter but occurred as data
    if($.browser.msie && VHV.urlMode == 'ajax')

    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 1269, Column 41: reference not terminated by REFC delimiter
     window.location = '/?page='+page+'&site=55&keyword='+keyword;

    If you meant to include an entity that starts with "&", then you should terminate it 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 1269, Column 41: reference to entity "site" for which no system identifier could be generated
     window.location = '/?page='+page+'&site=55&keyword='+keyword;

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

  • Info Line 187, Column 42: entity was defined here
     <a href="http://trali.com.vn/?page=home2&site=55">
  • Warning Line 1269, Column 45: cannot generate system identifier for general entity "keyword"
     window.location = '/?page='+page+'&site=55&keyword='+keyword;

    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 1269, Column 45: general entity "keyword" not defined and no default entity
     window.location = '/?page='+page+'&site=55&keyword='+keyword;

    This is usually a cascading error caused by 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 1269, Column 52: reference not terminated by REFC delimiter
     window.location = '/?page='+page+'&site=55&keyword='+keyword;

    If you meant to include an entity that starts with "&", then you should terminate it 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 1269, Column 52: reference to entity "keyword" for which no system identifier could be generated
     window.location = '/?page='+page+'&site=55&keyword='+keyword;

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

  • Info Line 1269, Column 44: entity was defined here
     window.location = '/?page='+page+'&site=55&keyword='+keyword;

Visitor Analysis

Daily Visitor
  • 38 visits

In Page Analysis