toomva.com

Toomva.com là website học tiếng Anh Online qua các video phụ đề song ngữ Anh - Việt, Với lượng video phong phú, hấp dẫn bạn có thể nâng cao kỹ năng nghe, ...

This data was last updated from 28-12-2013 10:16:00  (update).

Overview Info



  • Domain Name
    toomva.com
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    2
  • Ip Address
    210.245.95.57
  • Page Size
    68.2 KB
  • Images
    0 GIF, 12 JPG, 12 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 1 5 12 0 0

Website Meta Analysis



  • Title
    Toomva - Học tiếng Anh qua bài hát - luyện nghe tiếng Anh - tiếng Anh giao tiếp
  • Meta Keyword
    hoc tieng anh, hoc tieng anh qua bai hat, luyen nghe tieng anh, tieng anh giao tiep
  • Meta Description
    Toomva.com là website học tiếng Anh Online qua các video phụ đề song ngữ Anh - Việt, Với lượng video phong phú, hấp dẫn bạn có thể nâng cao kỹ năng nghe, nói, giao tiếng tiếng Anh một cách rất nhanh và hiệu quả.

Technical Analysis



  • Webserver
    nginx/1.5.6
  • Ip Address
    210.245.95.57
  • Domain Age
    9 Months, 6 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.5.6
  • date: Sat, 28 Dec 2013 10:11:17 GMT
  • content-type: text/html; charset=ISO-8859-1
  • content-length: 16303
  • connection: keep-alive
  • x-powered-by: PHP/5.3.27
  • cache-control: private
  • pragma: private
  • content-encoding: gzip
  • vary: User-Agent
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for toomva.com

IP 210.245.95.57 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 190 Errors
  • 35 Warnings
Ratio Text/Html
  • 0.6419183965640658
Message Error
  • Error Line 90, Column 18: document type does not allow element "div" here; assuming missing "object" start-tag
    <div id="fb-root"></div>
  • Error Line 91, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 95, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/vi_VN/all.js#xfbml=1&appId=107195079475287";

    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 95, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/vi_VN/all.js#xfbml=1&appId=107195079475287";

    This is usually a cascading error caused by 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 95, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/vi_VN/all.js#xfbml=1&appId=107195079475287";

    If you meant to include an entity that starts with "&", then you should terminate it 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 95, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/vi_VN/all.js#xfbml=1&appId=107195079475287";

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

  • Info Line 95, Column 56: entity was defined here
      js.src = "//connect.facebook.net/vi_VN/all.js#xfbml=1&appId=107195079475287";
  • Error Line 101, Column 66: document type does not allow element "link" here
    <link rel="stylesheet" type="text/css" href="engine1/style.css" />

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

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

  • Error Line 105, Column 11: document type does not allow element "title" here
        <title>Toomva - H&#7885;c ti&#7871;ng Anh qua bài hát - luy&#7879;n nghe ti…

    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 107, Column 210: document type does not allow element "link" here
    …ms.css,postbit-lite.css,postlist.css,lightbox.css,overlay.css,tagcloud.css," />

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

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

  • Error Line 121, Column 136: document type does not allow element "link" here
    …styleid=1&amp;langid=2&amp;d=1386125799&amp;td=ltr&amp;sheet=additional.css" />

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

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

  • Error Line 123, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 90, Column 1: start tag was here
    <div id="fb-root"></div>
  • Error Line 123, Column 7: end tag for "head" which is not finished
    </head>

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

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

  • Error Line 228, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:2px">

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

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

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

  • Error Line 245, Column 13: element "gcse:search" undefined
    <gcse:search></gcse:search>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 631, Column 624: ID "wows1_2" already defined
    …/upload.toomva.com/anh/kecap.jpg" id="wows1_2" width="572" height="322" border…

    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 629, Column 144: ID "wows1_2" first defined here
    …mva.com/anh/the way way back.jpg" id="wows1_2" width="572" height="322" border…
  • Error Line 635, Column 571: ID "wows1_1" already defined
    ….com/anhchude/quantic%20kara.jpg" id="wows1_1" width="572" height="322" border…

    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 626, Column 885: ID "wows1_1" first defined here
    …upload.toomva.com/anh/friend.jpg" id="wows1_1" width="572" height="322" border…
  • Error Line 637, Column 467: ID "wows1_1" already defined
    ….com/anh/rooling-in-the-deep.jpg" id="wows1_1" width="572" height="322" border…

    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 626, Column 885: ID "wows1_1" first defined here
    …upload.toomva.com/anh/friend.jpg" id="wows1_1" width="572" height="322" border…
  • Error Line 639, Column 471: ID "wows1_1" already defined
    …i-tinh-o-rome-when-in-rome-2.jpg" id="wows1_1" width="572" height="322" border…

    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 626, Column 885: ID "wows1_1" first defined here
    …upload.toomva.com/anh/friend.jpg" id="wows1_1" width="572" height="322" border…
  • Error Line 641, Column 39: "I" is not a member of a group specified for any attribute
    <li><p><a class="hovertext" title=""I Lay My Love on You" là bài hát c&#7911;a …
  • Error Line 641, Column 43: "Lay" is not a member of a group specified for any attribute
    …<p><a class="hovertext" title=""I Lay My Love on You" là bài hát c&#7911;a Wes…
  • Error Line 641, Column 46: "My" is not a member of a group specified for any attribute
    …<a class="hovertext" title=""I Lay My Love on You" là bài hát c&#7911;a Westli…
  • Error Line 641, Column 51: "Love" is not a member of a group specified for any attribute
    …ass="hovertext" title=""I Lay My Love on You" là bài hát c&#7911;a Westlife, p…
  • Error Line 641, Column 54: "on" is not a member of a group specified for any attribute
    …="hovertext" title=""I Lay My Love on You" là bài hát c&#7911;a Westlife, phát…
  • Error Line 641, Column 57: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …overtext" title=""I Lay My Love on You" là bài hát c&#7911;a Westlife, phát hà…

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

  • Error Line 641, Column 653: ID "wows1_1" already defined
    …com/anh/I-Lay-My-Love-On-You.jpg" id="wows1_1" width="572" height="322" border…

    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 626, Column 885: ID "wows1_1" first defined here
    …upload.toomva.com/anh/friend.jpg" id="wows1_1" width="572" height="322" border…
  • Error Line 643, Column 347: ID "wows1_1" already defined
    …anhchude/Momy-I-don-like-you.jpg" id="wows1_1" width="572" height="322" border…

    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 626, Column 885: ID "wows1_1" first defined here
    …upload.toomva.com/anh/friend.jpg" id="wows1_1" width="572" height="322" border…
  • Error Line 645, Column 607: ID "wows1_1" already defined
    …va.com/anhchude/doyouenglish.jpg" id="wows1_1" width="572" height="322" border…

    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 626, Column 885: ID "wows1_1" first defined here
    …upload.toomva.com/anh/friend.jpg" id="wows1_1" width="572" height="322" border…
  • Error Line 646, Column 459: ID "wows1_1" already defined
    …ables%20using%20your%20hands.jpg" id="wows1_1" width="572" height="322" border…

    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 626, Column 885: ID "wows1_1" first defined here
    …upload.toomva.com/anh/friend.jpg" id="wows1_1" width="572" height="322" border…
  • Error Line 657, Column 207: end tag for "br" omitted, but OMITTAG NO was specified
    … Anh online qua Video <span>ph&#7909; &#273;&#7873; Anh Vi&#7879;t.</span><br> 

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

  • Info Line 657, Column 203: start tag was here
    … Anh online qua Video <span>ph&#7909; &#273;&#7873; Anh Vi&#7879;t.</span><br> 
  • Error Line 658, Column 277: end tag for element "br" which is not open
    …5;c theo các giáo trình nhàm chán.</br>Hãy <a href="http://toomva.com/register…

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

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

  • Error Line 658, Column 447: end tag for element "br" which is not open
    … nghi&#7879;m cùng Toomva v&#7899;i phong cách hoàn toàn m&#7899;i:</font></br>

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

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

  • Error Line 659, Column 85: end tag for element "br" which is not open
    …"#800080"><font size="2"><b>The fun way to learn !</b></font></font></br></div>

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

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

  • Error Line 662, Column 60: there is no attribute "data-annotation"
    …div class="g-plusone" data-annotation="inline" data-width="572" data-href="htt…

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

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

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

  • Error Line 662, Column 80: there is no attribute "data-width"
    …" data-annotation="inline" data-width="572" data-href="http://toomva.com"></di…

    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 662, Column 96: there is no attribute "data-href"
    …annotation="inline" data-width="572" data-href="http://toomva.com"></div></div>

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

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

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

  • Error Line 665, Column 10: ID "mangxahoi" already defined
    <div id="mangxahoi"><div class="fb-like" data-href="https://www.facebook.com/to…

    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 662, Column 10: ID "mangxahoi" first defined here
    <div id="mangxahoi"><div class="g-plusone" data-annotation="inline" data-width=…
  • Error Line 665, Column 122: there is no attribute "data-height"
    …fanpage" data-width="572" data-height="The pixel height of the plugin" data-co…

    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 665, Column 172: there is no attribute "data-colorscheme"
    …eight of the plugin" data-colorscheme="light" data-layout="standard" data-acti…

    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 665, Column 192: there is no attribute "data-layout"
    … data-colorscheme="light" data-layout="standard" data-action="like" data-show-…

    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 665, Column 215: there is no attribute "data-action"
    …t" data-layout="standard" data-action="like" data-show-faces="true" data-send=…

    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 665, Column 238: there is no attribute "data-show-faces"
    …andard" data-action="like" data-show-faces="true" data-send="true"></div></div>

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

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

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

  • Error Line 665, Column 255: there is no attribute "data-send"
    …andard" data-action="like" data-show-faces="true" data-send="true"></div></div>

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

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

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

  • Error Line 703, Column 319: end tag for "img" omitted, but OMITTAG NO was specified
    …% &#273;&#259;ng ký VIP" align="left">Like FanPage-Gi&#7843;m giá 50% &#273;&#…

    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 703, Column 186: start tag was here
    …Like-FanPage-Giam-gia-50-dang-ky-VIP"><img src="http://toomva.com/images/icons…
  • Error Line 705, Column 314: end tag for "img" omitted, but OMITTAG NO was specified
    … mua DVD song ng&#7919;" align="left">&#272;&#259;ng ký &#273;&#7863;t mua DVD…

    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 705, Column 184: start tag was here
    …Dat-mua-DVD-song-ngu?p=5698#post5698"><img src="http://www.animatedgif.net/new…
  • Error Line 707, Column 324: end tag for "img" omitted, but OMITTAG NO was specified
    …432;&#7901;ng và TK VIP" align="left">Phân bi&#7879;t tài kho&#7843;n th&#432;…

    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 707, Column 206: start tag was here
    …khoan-thuong-va-tai-khoan-VIP?p=3439"><img src="http://toomva.com/images/icons…
  • Error Line 709, Column 322: end tag for "img" omitted, but OMITTAG NO was specified
    …59;ng ký thành viên VIP" align="left">Thông báo v&#7873; &#273;&#259;ng ký thà…

    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 709, Column 188: start tag was here
    …g-bao-ve-viec-dang-ky-thanh-vien-VIP"><img src="http://toomva.com/images/icons…
  • Error Line 719, Column 70: end tag for element "br" which is not open
    <font color="blue"><b>1. H&#7894; TR&#7906; THÀNH VIÊN</b></font></br>

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

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

  • Error Line 720, Column 67: end tag for element "br" which is not open
    Gi&#7843;i &#273;áp m&#7885;i v&#7845;n &#273;&#7873; v&#7873;</br>

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

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

  • Error Line 721, Column 37: end tag for element "br" which is not open
    &#272;&#259;ng ký-Cách h&#7885;c</br>

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

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

  • Error Line 722, Column 43: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ref="ymsgr:sendim?toomva"><img border=0 src="http://opi.yahoo.com/online?u=too…
  • Warning Line 722, Column 87: cannot generate system identifier for general entity "m"
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

    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 722, Column 87: general entity "m" not defined and no default entity
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

    This is usually a cascading error caused by 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 722, Column 88: reference not terminated by REFC delimiter
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

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

  • Warning Line 722, Column 88: reference to external entity in attribute value
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

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

  • Error Line 722, Column 88: reference to entity "m" for which no system identifier could be generated
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

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

  • Info Line 722, Column 86: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Warning Line 722, Column 91: cannot generate system identifier for general entity "t"
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

    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 722, Column 91: general entity "t" not defined and no default entity
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

    This is usually a cascading error caused by 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 722, Column 92: reference not terminated by REFC delimiter
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

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

  • Warning Line 722, Column 92: reference to external entity in attribute value
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

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

  • Error Line 722, Column 92: reference to entity "t" for which no system identifier could be generated
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

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

  • Info Line 722, Column 90: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Warning Line 722, Column 95: cannot generate system identifier for general entity "l"
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

    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 722, Column 95: general entity "l" not defined and no default entity
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

    This is usually a cascading error caused by 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 722, Column 96: reference not terminated by REFC delimiter
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

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

  • Warning Line 722, Column 96: reference to external entity in attribute value
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

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

  • Error Line 722, Column 96: reference to entity "l" for which no system identifier could be generated
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

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

  • Info Line 722, Column 94: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Error Line 722, Column 100: required attribute "alt" not specified
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

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

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

  • Error Line 722, Column 104: end tag for "img" omitted, but OMITTAG NO was specified
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

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

  • Info Line 722, Column 31: start tag was here
    <a href="ymsgr:sendim?toomva"><img border=0 src="http://opi.yahoo.com/online?u=…
  • Error Line 722, Column 109: end tag for element "br" which is not open
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

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

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

  • Error Line 722, Column 114: end tag for element "br" which is not open
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>

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

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

  • Error Line 723, Column 51: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …gr:sendim?kthuong.toomva"><img border=0 src="http://opi.yahoo.com/online?u=kth…
  • Warning Line 723, Column 104: reference not terminated by REFC delimiter
    … src="http://opi.yahoo.com/online?u=kthuong.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Warning Line 723, Column 104: reference to external entity in attribute value
    … src="http://opi.yahoo.com/online?u=kthuong.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Error Line 723, Column 104: reference to entity "m" for which no system identifier could be generated
    … src="http://opi.yahoo.com/online?u=kthuong.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Info Line 722, Column 86: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Warning Line 723, Column 108: reference not terminated by REFC delimiter
    … src="http://opi.yahoo.com/online?u=kthuong.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Warning Line 723, Column 108: reference to external entity in attribute value
    … src="http://opi.yahoo.com/online?u=kthuong.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Error Line 723, Column 108: reference to entity "t" for which no system identifier could be generated
    … src="http://opi.yahoo.com/online?u=kthuong.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Info Line 722, Column 90: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Warning Line 723, Column 112: reference not terminated by REFC delimiter
    … src="http://opi.yahoo.com/online?u=kthuong.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Warning Line 723, Column 112: reference to external entity in attribute value
    … src="http://opi.yahoo.com/online?u=kthuong.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Error Line 723, Column 112: reference to entity "l" for which no system identifier could be generated
    … src="http://opi.yahoo.com/online?u=kthuong.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Info Line 722, Column 94: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Error Line 723, Column 116: required attribute "alt" not specified
    … src="http://opi.yahoo.com/online?u=kthuong.toomva&m=g&t=2&l=us"></a></br></br>

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

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

  • Error Line 723, Column 120: end tag for "img" omitted, but OMITTAG NO was specified
    … src="http://opi.yahoo.com/online?u=kthuong.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Info Line 723, Column 39: start tag was here
    <a href="ymsgr:sendim?kthuong.toomva"><img border=0 src="http://opi.yahoo.com/o…
  • Error Line 723, Column 125: end tag for element "br" which is not open
    … src="http://opi.yahoo.com/online?u=kthuong.toomva&m=g&t=2&l=us"></a></br></br>

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

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

  • Error Line 723, Column 130: end tag for element "br" which is not open
    … src="http://opi.yahoo.com/online?u=kthuong.toomva&m=g&t=2&l=us"></a></br></br>

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

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

  • Error Line 724, Column 47: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …"ymsgr:sendim?duc.toomva"><img border=0 src="http://opi.yahoo.com/online?u=duc…
  • Warning Line 724, Column 96: reference not terminated by REFC delimiter
    …er=0 src="http://opi.yahoo.com/online?u=duc.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Warning Line 724, Column 96: reference to external entity in attribute value
    …er=0 src="http://opi.yahoo.com/online?u=duc.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Error Line 724, Column 96: reference to entity "m" for which no system identifier could be generated
    …er=0 src="http://opi.yahoo.com/online?u=duc.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Info Line 722, Column 86: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Warning Line 724, Column 100: reference not terminated by REFC delimiter
    …er=0 src="http://opi.yahoo.com/online?u=duc.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Warning Line 724, Column 100: reference to external entity in attribute value
    …er=0 src="http://opi.yahoo.com/online?u=duc.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Error Line 724, Column 100: reference to entity "t" for which no system identifier could be generated
    …er=0 src="http://opi.yahoo.com/online?u=duc.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Info Line 722, Column 90: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Warning Line 724, Column 104: reference not terminated by REFC delimiter
    …er=0 src="http://opi.yahoo.com/online?u=duc.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Warning Line 724, Column 104: reference to external entity in attribute value
    …er=0 src="http://opi.yahoo.com/online?u=duc.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Error Line 724, Column 104: reference to entity "l" for which no system identifier could be generated
    …er=0 src="http://opi.yahoo.com/online?u=duc.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Info Line 722, Column 94: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Error Line 724, Column 108: required attribute "alt" not specified
    …er=0 src="http://opi.yahoo.com/online?u=duc.toomva&m=g&t=2&l=us"></a></br></br>

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

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

  • Error Line 724, Column 112: end tag for "img" omitted, but OMITTAG NO was specified
    …er=0 src="http://opi.yahoo.com/online?u=duc.toomva&m=g&t=2&l=us"></a></br></br>

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

  • Info Line 724, Column 35: start tag was here
    <a href="ymsgr:sendim?duc.toomva"><img border=0 src="http://opi.yahoo.com/onlin…
  • Error Line 724, Column 117: end tag for element "br" which is not open
    …er=0 src="http://opi.yahoo.com/online?u=duc.toomva&m=g&t=2&l=us"></a></br></br>

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

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

  • Error Line 724, Column 122: end tag for element "br" which is not open
    …er=0 src="http://opi.yahoo.com/online?u=duc.toomva&m=g&t=2&l=us"></a></br></br>

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

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

  • Error Line 725, Column 33: end tag for element "br" which is not open
    <b>&#272;T: 0904.762.089</b></br>

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

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

  • Error Line 726, Column 33: end tag for element "br" which is not open
    (gi&#7901; hành chính T2-T7)</br>

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

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

  • Error Line 728, Column 5: end tag for element "br" which is not open
    </br>

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

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

  • Error Line 729, Column 22: element "B" undefined
    <font color="blue"><B>2. GÓP Ý XÂY D&#7920;NG</B>

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

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

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

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

  • Error Line 732, Column 5: end tag for element "br" which is not open
    </br>

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

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

  • Error Line 735, Column 288: end tag for "img" omitted, but OMITTAG NO was specified
    …m video phu de anh viet" align="left"> <b>&nbsp;&#272;&#7873; Xu&#7845;t Video…

    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 735, Column 181: start tag was here
    …34-De-xuat-Video-lam-phu-de-Anh-Viet"><img src="http://toomva.com/images/butto…
  • Error Line 784, Column 42: end tag for element "br" which is not open
    <font color="white">MENU CHÍNH</font></br>

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

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

  • Error Line 785, Column 12: there is no attribute "STYLE"
    <div STYLE="FONT-SIZE:12PX; font-weight:normal"></br>

    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 785, Column 53: end tag for element "br" which is not open
    <div STYLE="FONT-SIZE:12PX; font-weight:normal"></br>

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

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

  • Error Line 786, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/2-hoc-tieng-anh-…

    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 786, Column 222: end tag for element "br" which is not open
    …e="color:#ffffff;">• H&#7885;c ti&#7871;ng anh qua bài hát</font></a></br></li>

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

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

  • Error Line 787, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/4-hoc-tieng-anh-…

    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 787, Column 235: end tag for element "br" which is not open
    …tyle="color:#ffffff;">• H&#7885;c ti&#7871;ng anh qua phim</font></a></br></li>

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

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

  • Error Line 788, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/6-tieng-anh-khoa…

    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 788, Column 258: end tag for element "br" which is not open
    …fffff;">• Ti&#7871;ng anh khoa h&#7885;c - công ngh&#7879;</font></a></br></li>

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

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

  • Error Line 789, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/9-suc-khoe-lam-d…

    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 789, Column 242: end tag for element "br" which is not open
    …tyle="color:#ffffff;">• Ti&#7871;ng anh làm &#273;&#7865;p</font></a></br></li>

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

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

  • Error Line 790, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/11-thoi-trang-di…

    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 790, Column 256: end tag for element "br" which is not open
    …olor:#ffffff;">• Ti&#7871;ng anh &#273;i&#7879;n &#7843;nh</font></a></br></li>

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

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

  • Error Line 791, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/13-tieng-anh-du-…

    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 791, Column 248: end tag for element "br" which is not open
    …font style="color:#ffffff">• Ti&#7871;ng anh du l&#7883;ch</font></a></br></li>

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

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

  • Error Line 792, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/16-tieng-anh-gia…

    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 792, Column 276: end tag for element "br" which is not open
    …lor:#ffffff;">• Ti&#7871;ng anh th&#432;&#417;ng m&#7841;i</font></a></br></li>

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

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

  • Error Line 793, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/20-hoc-tieng-anh…

    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 793, Column 267: end tag for element "br" which is not open
    …">• Ti&#7871;ng anh ng&#432;&#7901;i n&#7893;i ti&#7871;ng</font></a></br></li>

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

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

  • Error Line 794, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/22-hoc-tieng-anh…

    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 794, Column 207: end tag for element "br" which is not open
    …ont style="color:#ffffff;">• Ti&#7871;ng anh qua video hài</font></a></br></li>

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

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

  • Error Line 795, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/23-tieng-anh-gia…

    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 795, Column 256: end tag for element "br" which is not open
    …:#ffffff;">• Ti&#7871;ng anh giao ti&#7871;p gia &#273;ình</font></a></br></li>

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

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

  • Error Line 796, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/18-hoc-tieng-anh…

    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 796, Column 221: end tag for element "br" which is not open
    …style="color:#ffffff;">• Tin t&#7913;c qu&#7889;c t&#7871;</font></a></br></li>

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

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

  • Error Line 804, Column 5: end tag for element "br" which is not open
    </br>

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

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

  • Error Line 805, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/35-tieng-anh-kha…

    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 805, Column 205: end tag for element "br" which is not open
    …t style="color:#ffffff;">• Ti&#7871;ng anh khách s&#7841;n</font></a></br></li>

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

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

  • Error Line 806, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/36-tieng-anh-toa…

    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 806, Column 202: end tag for element "br" which is not open
    …nt style="color:#ffffff;">• Ti&#7871;ng anh toán h&#7885;c</font></a></br></li>

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

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

  • Error Line 807, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/37-tieng-anh-mon…

    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 807, Column 200: end tag for element "br" which is not open
    …font style="color:#ffffff;">• Ti&#7871;ng anh v&#7853;t lý</font></a></br></li>

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

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

  • Error Line 808, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/38-tieng-anh-hoa…

    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 808, Column 225: end tag for element "br" which is not open
    …ont style="color:#ffffff;">• Ti&#7871;ng anh hóa h&#7885;c</font></a></br></li>

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

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

  • Error Line 809, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/39-tieng-anh-mon…

    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 809, Column 210: end tag for element "br" which is not open
    …style="color:#ffffff;">• Ti&#7871;ng anh y d&#432;&#7907;c</font></a></br></li>

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

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

  • Error Line 810, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/40-lich-su-dia-l…

    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 810, Column 248: end tag for element "br" which is not open
    …>• Ti&#7871;ng anh l&#7883;ch s&#7917; - &#273;&#7883;a lý</font></a></br></li>

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

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

  • Error Line 811, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/41-tieng-anh-tin…

    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 811, Column 199: end tag for element "br" which is not open
    …ont style="color:#ffffff;">• Ti&#7871;ng anh tin h&#7885;c</font></a></br></li>

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

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

  • Error Line 819, Column 5: end tag for element "br" which is not open
    </br>

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

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

  • Error Line 821, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/50-hoc-tieng-anh…

    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 821, Column 214: end tag for element "br" which is not open
    …nt style="color:#ffffff;">• H&#7885;c ti&#7871;ng Anh cùng</font></a></br></li>

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

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

  • Error Line 822, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="http:/…

    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 822, Column 208: end tag for element "br" which is not open
    …h cung Mr DunCan"><font style="color:#ffffff;">- Mr.DunCan</font></a></br></li>

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

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

  • Error Line 823, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="http:/…

    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 823, Column 190: end tag for element "br" which is not open
    …Hoc tieng anh cung BBC"><font style="color:#ffffff;">- BBC</font></a></br></li>

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

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

  • Error Line 824, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="http:/…

    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 824, Column 190: end tag for element "br" which is not open
    …Hoc tieng anh cung CNN"><font style="color:#ffffff;">- CNN</font></a></br></li>

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

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

  • Error Line 825, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="http:/…

    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 825, Column 190: end tag for element "br" which is not open
    …Hoc tieng anh cung VOA"><font style="color:#ffffff;">- VOA</font></a></br></li>

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

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

  • Error Line 827, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/27-tieng-anh-tre…

    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 827, Column 202: end tag for element "br" which is not open
    …font style="color:#ffffff;">• Ti&#7871;ng anh tr&#7867; em</font></a></br></li>

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

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

  • Error Line 828, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/30-doc-bao-anh-v…

    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 828, Column 206: end tag for element "br" which is not open
    …style="color:#ffffff;">• &#272;&#7885;c báo Anh Vi&#7879;t</font></a></br></li>

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

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

  • Error Line 829, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/539-loi-dich-bai…

    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 829, Column 211: end tag for element "br" which is not open
    …font style="color:#ffffff;">• L&#7901;i d&#7883;ch bài hát</font></a></br></li>

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

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

  • Error Line 830, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/content/447-ngu-phap-tie…

    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 830, Column 252: end tag for element "br" which is not open
    … style="color:#ffffff;">• Bài gi&#7843;ng - Ng&#7919; pháp</font></a></br></li>

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

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

  • Error Line 838, Column 5: end tag for element "br" which is not open
    </br>

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

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

  • Error Line 840, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/forums/2-Thong-bao-Tin-t…

    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 840, Column 174: end tag for element "br" which is not open
    …t&#7915; Toomva"><font style="color:#ffffff;">• Thông báo </font></a></br></li>

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

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

  • Error Line 841, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/forums/31-Tin-tuc-Tong-h…

    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 841, Column 248: end tag for element "br" which is not open
    …tyle="color:#ffffff;">• Tin t&#7913;c t&#7893;ng h&#7907;p</font></a></br></li>

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

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

  • Error Line 842, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/forums/10-Thong-tin-Viec…

    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 842, Column 216: end tag for element "br" which is not open
    …ont style="color:#ffffff;">• Vi&#7879;c làm - du h&#7885;c</font></a></br></li>

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

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

  • Error Line 843, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/forums/9-Kinh-nghiem-Ky-…

    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 843, Column 281: end tag for element "br" which is not open
    …nghi&#7879;m, k&#7929; n&#259;ng h&#7885;c ti&#7871;ng Anh</font></a></br></li>

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

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

  • Error Line 844, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/forums/12-Tai-lieu-Phan-…

    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 844, Column 279: end tag for element "br" which is not open
    …i&#7879;u - Ph&#7847;n m&#7873;m h&#7885;c ti&#7871;ng Anh</font></a></br></li>

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

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

  • Error Line 845, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/forums/13-Tu-vung-tieng-…

    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 845, Column 210: end tag for element "br" which is not open
    …yle="color:#ffffff;">• T&#7915; v&#7921;ng ti&#7871;ng Anh</font></a></br></li>

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

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

  • Error Line 846, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/forums/15-Tieng-Anh-chuy…

    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 846, Column 201: end tag for element "br" which is not open
    …font style="color:#ffffff;">• Ti&#7871;ng Anh chuyên ngành</font></a></br></li>

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

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

  • Error Line 847, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="http://toomva.com/forums/30-Trung-tam-hoc-…

    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 847, Column 266: end tag for element "br" which is not open
    …ung tâm h&#7885;c ti&#7871;ng Anh - Gi&#7899;i thi&#7879;u</font></a></br></li>

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

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

  • Error Line 854, Column 5: end tag for element "br" which is not open
    </br>

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

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

  • Error Line 855, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="ymsgr:sendim?toomva" mce_href="ymsgr:sendi…

    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 855, Column 68: there is no attribute "mce_href"
    …a href="ymsgr:sendim?toomva" mce_href="ymsgr:sendim?toomva" border="0"><img sr…

    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 855, Column 97: there is no attribute "border"
    …mce_href="ymsgr:sendim?toomva" border="0"><img src="http://opi.yahoo.com/onlin…

    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 855, Column 149: reference not terminated by REFC delimiter
    …http://opi.yahoo.com/online?u=toomva&t=5" mce_src="http://opi.yahoo.com/online…

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

  • Warning Line 855, Column 149: reference to external entity in attribute value
    …http://opi.yahoo.com/online?u=toomva&t=5" mce_src="http://opi.yahoo.com/online…

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

  • Error Line 855, Column 149: reference to entity "t" for which no system identifier could be generated
    …http://opi.yahoo.com/online?u=toomva&t=5" mce_src="http://opi.yahoo.com/online…

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

  • Info Line 722, Column 90: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Error Line 855, Column 161: there is no attribute "mce_src"
    …ahoo.com/online?u=toomva&t=5" mce_src="http://opi.yahoo.com/online?u=toomva&t=…

    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 855, Column 200: reference not terminated by REFC delimiter
    …http://opi.yahoo.com/online?u=toomva&t=5"></a>   <font style="color:#ffffff;">…

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

  • Warning Line 855, Column 200: reference to external entity in attribute value
    …http://opi.yahoo.com/online?u=toomva&t=5"></a>   <font style="color:#ffffff;">…

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

  • Error Line 855, Column 200: reference to entity "t" for which no system identifier could be generated
    …http://opi.yahoo.com/online?u=toomva&t=5"></a>   <font style="color:#ffffff;">…

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

  • Info Line 722, Column 90: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Error Line 855, Column 203: required attribute "alt" not specified
    …p://opi.yahoo.com/online?u=toomva&t=5"></a>   <font style="color:#ffffff;">too…

    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 855, Column 207: end tag for "img" omitted, but OMITTAG NO was specified
    …opi.yahoo.com/online?u=toomva&t=5"></a>   <font style="color:#ffffff;">toomva<…

    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 855, Column 101: start tag was here
    …href="ymsgr:sendim?toomva" border="0"><img src="http://opi.yahoo.com/online?u=…
  • Error Line 855, Column 257: end tag for element "br" which is not open
    …nline?u=toomva&t=5"></a>   <font style="color:#ffffff;">toomva</font></br></li>

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

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

  • Error Line 857, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="ymsgr:sendim?kthuong.toomva" mce_href="yms…

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

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

  • Warning Line 857, Column 173: reference not terminated by REFC delimiter
    …pi.yahoo.com/online?u=kthuong.toomva&t=5" mce_src="http://opi.yahoo.com/online…

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

  • Warning Line 857, Column 173: reference to external entity in attribute value
    …pi.yahoo.com/online?u=kthuong.toomva&t=5" mce_src="http://opi.yahoo.com/online…

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

  • Error Line 857, Column 173: reference to entity "t" for which no system identifier could be generated
    …pi.yahoo.com/online?u=kthuong.toomva&t=5" mce_src="http://opi.yahoo.com/online…

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

  • Info Line 722, Column 90: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Warning Line 857, Column 232: reference not terminated by REFC delimiter
    …pi.yahoo.com/online?u=kthuong.toomva&t=5"></a>     <font style="color:#ffffff;…

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

  • Warning Line 857, Column 232: reference to external entity in attribute value
    …pi.yahoo.com/online?u=kthuong.toomva&t=5"></a>     <font style="color:#ffffff;…

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

  • Error Line 857, Column 232: reference to entity "t" for which no system identifier could be generated
    …pi.yahoo.com/online?u=kthuong.toomva&t=5"></a>     <font style="color:#ffffff;…

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

  • Info Line 722, Column 90: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Error Line 857, Column 235: required attribute "alt" not specified
    …yahoo.com/online?u=kthuong.toomva&t=5"></a>     <font style="color:#ffffff;">k…

    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 857, Column 239: end tag for "img" omitted, but OMITTAG NO was specified
    …o.com/online?u=kthuong.toomva&t=5"></a>     <font style="color:#ffffff;">kthuo…

    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 857, Column 117: start tag was here
    …sgr:sendim?kthuong.toomva" border="0"><img src="http://opi.yahoo.com/online?u=…
  • Error Line 857, Column 299: end tag for element "br" which is not open
    …omva&t=5"></a>     <font style="color:#ffffff;">kthuong.toomva</font></br></li>

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

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

  • Error Line 858, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a href="ymsgr:sendim?duc.toomva" mce_href="ymsgr:s…

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

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

  • Warning Line 858, Column 161: reference not terminated by REFC delimiter
    …://opi.yahoo.com/online?u=duc.toomva&t=5" mce_src="http://opi.yahoo.com/online…

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

  • Warning Line 858, Column 161: reference to external entity in attribute value
    …://opi.yahoo.com/online?u=duc.toomva&t=5" mce_src="http://opi.yahoo.com/online…

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

  • Error Line 858, Column 161: reference to entity "t" for which no system identifier could be generated
    …://opi.yahoo.com/online?u=duc.toomva&t=5" mce_src="http://opi.yahoo.com/online…

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

  • Info Line 722, Column 90: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Warning Line 858, Column 216: reference not terminated by REFC delimiter
    …://opi.yahoo.com/online?u=duc.toomva&t=5"></a>   <font style="color:#ffffff;">…

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

  • Warning Line 858, Column 216: reference to external entity in attribute value
    …://opi.yahoo.com/online?u=duc.toomva&t=5"></a>   <font style="color:#ffffff;">…

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

  • Error Line 858, Column 216: reference to entity "t" for which no system identifier could be generated
    …://opi.yahoo.com/online?u=duc.toomva&t=5"></a>   <font style="color:#ffffff;">…

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

  • Info Line 722, Column 90: entity was defined here
    …border=0 src="http://opi.yahoo.com/online?u=toomva&m=g&t=2&l=us"></a></br></br>
  • Error Line 858, Column 219: required attribute "alt" not specified
    …opi.yahoo.com/online?u=duc.toomva&t=5"></a>   <font style="color:#ffffff;">duc…

    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 858, Column 223: end tag for "img" omitted, but OMITTAG NO was specified
    …yahoo.com/online?u=duc.toomva&t=5"></a>   <font style="color:#ffffff;">duc.too…

    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 858, Column 109: start tag was here
    …="ymsgr:sendim?duc.toomva" border="0"><img src="http://opi.yahoo.com/online?u=…
  • Error Line 858, Column 277: end tag for element "br" which is not open
    …duc.toomva&t=5"></a>   <font style="color:#ffffff;">duc.toomva</font></br></li>

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

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

  • Error Line 859, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li style="padding-top:4px"><a target="_blank" href="http://toomva.com/sendmess…

    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 859, Column 190: required attribute "alt" not specified
    …com/anh/1381494257_Android-Email.png"/></a> <font style="color:#ffffff;">info@…

    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 859, Column 251: end tag for element "br" which is not open
    …-Email.png"/></a> <font style="color:#ffffff;">info@toomva.com</font></br></li>

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

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

  • Error Line 860, Column 141: required attribute "alt" not specified
    …nhduc/1381558873_Phone-Android-R.png"/> <font style="color:#ffffff;">0904.762.…

    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 860, Column 195: end tag for element "br" which is not open
    …one-Android-R.png"/> <font style="color:#ffffff;">0904.762.089</font></br></li>

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

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

  • Error Line 860, Column 200: end tag for element "li" which is not open
    …one-Android-R.png"/> <font style="color:#ffffff;">0904.762.089</font></br></li>

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

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

  • Error Line 865, Column 88: required attribute "alt" not specified
    …ight:30px; width:93px" src="http://upload.toomva.com/anh/logo-186-60.png"></br>

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

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

  • Error Line 865, Column 93: end tag for element "br" which is not open
    …ight:30px; width:93px" src="http://upload.toomva.com/anh/logo-186-60.png"></br>

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

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

  • Error Line 865, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …ight:30px; width:93px" src="http://upload.toomva.com/anh/logo-186-60.png"></br>

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

  • Info Line 865, Column 1: start tag was here
    <img style="height:30px; width:93px" src="http://upload.toomva.com/anh/logo-186…
  • Error Line 866, Column 80: end tag for element "br" which is not open
    …weight:normal">Copyright © toomva.com 2013</br>Learn English By Video Solutions

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

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

Visitor Analysis

Daily Visitor
  • 0 visits

In Page Analysis