xemphimon.com

xem phim online, xem phim hd nhanh: xemphimon luôn update các phim mới 2013 nhiều thể loại phim 18, phim tâm lý, phim tình cảm ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    xemphimon.com
  • Favicon
  • Alexa Rank
    #48998
  • Google Page Rank
    PR 2
  • Ip Address
    123.30.140.136
  • Page Size
    41.6 KB
  • Images
    1 GIF, 44 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 1 6 1 0 0

Website Meta Analysis



  • Title
    Xem Phim Online, Xem phim HD nhanh
  • Meta Keyword
    xem phim online, xem phim, phim nhanh, xem phim online nhanh
  • Meta Description
    xem phim online, xem phim hd nhanh: xemphimon luôn update các phim mới 2013 nhiều thể loại phim 18, phim tâm lý, phim tình cảm

Technical Analysis



  • Webserver
    S140-136-SUNDATA
  • Ip Address
    123.30.140.136
  • Domain Age
    1 Years, 9 Months, 11 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-type: text/html; charset=UTF-8
  • content-length: 9874
  • accept-ranges: bytes
  • date: Mon, 16 Sep 2013 20:42:08 GMT
  • connection: keep-alive
  • server: S140-136-SUNDATA
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for xemphimon.com

IP 123.30.140.136 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 25 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.8451741526914507
Message Error
  • Error Line 7, Column 83: end tag for "link" omitted, but OMITTAG NO was specified
    …nk rel="alternate" type="application/rss+xml" href="http://xemphimon.com/rss/">

    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 7, Column 1: start tag was here
    <link rel="alternate" type="application/rss+xml" href="http://xemphimon.com/rss…
  • Error Line 9, Column 53: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="language" content="Vietnamese, English">

    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 9, Column 1: start tag was here
    <meta name="language" content="Vietnamese, English">
  • Error Line 10, Column 58: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="RATING" content="search engine optimization">

    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 10, Column 1: start tag was here
    <meta name="RATING" content="search engine optimization">
  • Error Line 12, Column 80: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="abstract" content="Xem Phim Online | Phim Chiếu Rạp HD | Phim 18+">

    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 12, Column 1: start tag was here
    <meta name="abstract" content="Xem Phim Online | Phim Chiếu Rạp HD | Phim 18+">
  • Error Line 15, Column 179: end tag for "meta" omitted, but OMITTAG NO was specified
    …i hàng ngàn bộ phim hay lôi cuốn và hấp dẫn nhất mời các bạn cùng thưởng thức">

    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 15, Column 1: start tag was here
    <meta name="classification" content="Website xem phim nhanh chất lượng HD với k…
  • Error Line 19, Column 46: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="pragma" content="no-cache"> 

    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 19, Column 1: start tag was here
    <meta http-equiv="pragma" content="no-cache"> 
  • Error Line 20, Column 40: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="expires" content="0"> 

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

  • Info Line 20, Column 1: start tag was here
    <meta http-equiv="expires" content="0"> 
  • Error Line 21, Column 53: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="cache-control" content="no-cache"> 

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

  • Info Line 21, Column 1: start tag was here
    <meta http-equiv="cache-control" content="no-cache"> 
  • Error Line 22, Column 48: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta content="INDEX, FOLLOW" name="GOOGLEBOT"> 

    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 22, Column 1: start tag was here
    <meta content="INDEX, FOLLOW" name="GOOGLEBOT"> 
  • Error Line 23, Column 47: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta content="INDEX, FOLLOW" name="yahooBOT"> 

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

  • Info Line 23, Column 1: start tag was here
    <meta content="INDEX, FOLLOW" name="yahooBOT"> 
  • Error Line 24, Column 35: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="rating" content="All"> 

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

  • Info Line 24, Column 1: start tag was here
    <meta name="rating" content="All"> 
  • Error Line 35, Column 54: required attribute "type" not specified
    <script src="http://adbroker.zing.vn/res1/crystal.js"></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 106, Column 47: there is no attribute "onSubmit"
    …m id="search_form" name="search" onSubmit="return do_search();"  method="post">

    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 106, Column 83: required attribute "action" not specified
    …m id="search_form" name="search" onSubmit="return do_search();"  method="post">

    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 108, Column 59: there is no attribute "autocomplete"
    …t"><input name="keyword" autocomplete="off" class="default" type="text" id="ke…

    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 110, Column 31: end tag for "ul" which is not finished
    <ul id="show-search-auto"></ul>

    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 122, Column 111: end tag for "param" omitted, but OMITTAG NO was specified
    …h.net/banner/bathien_980x100.swf?clickTAG=http://bathien.nega.vn" name="movie">

    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 122, Column 6: start tag was here
    					<param value="http://gocanh.net/banner/bathien_980x100.swf?clickTAG=http:/…
  • Error Line 123, Column 41: end tag for "param" omitted, but OMITTAG NO was specified
    					<param value="high" name="quality">

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

  • Info Line 123, Column 6: start tag was here
    					<param value="high" name="quality">
  • Error Line 124, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    					<param value="#000000" name="bgcolor">

    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 124, Column 6: start tag was here
    					<param value="#000000" name="bgcolor">
  • Error Line 125, Column 38: end tag for "param" omitted, but OMITTAG NO was specified
    					<param value="true" name="play">

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

  • Info Line 125, Column 6: start tag was here
    					<param value="true" name="play">
  • Error Line 126, Column 38: end tag for "param" omitted, but OMITTAG NO was specified
    					<param value="true" name="loop">

    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 126, Column 6: start tag was here
    					<param value="true" name="loop">
  • Error Line 127, Column 46: end tag for "param" omitted, but OMITTAG NO was specified
    					<param value="transparent" name="wmode">

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

  • Info Line 127, Column 6: start tag was here
    					<param value="transparent" name="wmode">
  • Error Line 128, Column 42: end tag for "param" omitted, but OMITTAG NO was specified
    					<param value="showall" name="scale">

    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 128, Column 6: start tag was here
    					<param value="showall" name="scale">
  • Error Line 129, Column 38: end tag for "param" omitted, but OMITTAG NO was specified
    					<param value="true" name="menu">

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

  • Info Line 129, Column 6: start tag was here
    					<param value="true" name="menu">
  • Error Line 130, Column 45: end tag for "param" omitted, but OMITTAG NO was specified
    					<param value="false" name="devicefont">

    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 130, Column 6: start tag was here
    					<param value="false" name="devicefont">
  • Error Line 131, Column 36: end tag for "param" omitted, but OMITTAG NO was specified
    					<param value="" name="salign">

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

  • Info Line 131, Column 6: start tag was here
    					<param value="" name="salign">
  • Error Line 132, Column 57: end tag for "param" omitted, but OMITTAG NO was specified
    					<param value="sameDomain" name="allowScriptAccess">

    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 132, Column 6: start tag was here
    					<param value="sameDomain" name="allowScriptAccess">
  • Error Line 134, Column 119: end tag for "img" omitted, but OMITTAG NO was specified
    …src="http://www.adobe.com/images/shared/download_buttons/get_flash_player.gif">

    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 134, Column 6: start tag was here
    					<img alt="Get Adobe Flash player" src="http://www.adobe.com/images/shared/…
  • Error Line 140, Column 36: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                	<div class="title"><li>*</li><h2>Phim chiếu rạp</h2></div>

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

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

  • Error Line 143, Column 44: document type does not allow element "div" here; assuming missing "li" start-tag
    					<div class="movie-row" id="topx_video">
  • Error Line 144, Column 9: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    				<li>

    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 148, Column 229: required attribute "alt" not specified
    …12/04/10/10/05/1334027111855607755_574_574.jpg" width="120" height="160" /></a>

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

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

  • Error Line 153, Column 10: end tag for element "tr" which is not open
    </li></tr><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 153, Column 14: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    </li></tr><li>

    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 157, Column 220: required attribute "alt" not specified
    …himon.com/images/film/xemphimon-NguoiNhen4.jpg" width="120" height="160" /></a>

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

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

  • Error Line 162, Column 10: end tag for element "tr" which is not open
    </li></tr><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 162, Column 14: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    </li></tr><li>

    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 166, Column 182: required attribute "alt" not specified
    …/xemphimon.com/images/film/Nhat-Dai-Ton-Su.jpg" width="120" height="160" /></a>

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

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

  • Error Line 171, Column 10: end tag for element "tr" which is not open
    </li></tr><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 171, Column 14: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    </li></tr><li>

    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 175, Column 164: required attribute "alt" not specified
    …://xemphimon.com/images/film/the-host-2013.jpg" width="120" height="160" /></a>

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

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

  • Error Line 180, Column 10: end tag for element "tr" which is not open
    </li></tr>

    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 183, Column 9: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    				<li>

    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 187, Column 199: required attribute "alt" not specified
    …mon.com/film/2013/01/31/chang-beo-cuu-tinh.jpg" width="120" height="160" /></a>

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

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

  • Error Line 192, Column 10: end tag for element "tr" which is not open
    </li></tr><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 192, Column 14: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    </li></tr><li>

    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 196, Column 176: required attribute "alt" not specified
    …ack.us/img804/5876/batlaiposter20120302120.jpg" width="120" height="160" /></a>

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

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

  • Error Line 201, Column 10: end tag for element "tr" which is not open
    </li></tr><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 201, Column 14: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    </li></tr><li>

    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 202, Column 128: required attribute "alt" not specified
    …><img src="http://xemphimon.com/images/chatluong-hot.png" /></a></span></div>		

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

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

  • Error Line 202, Column 132: end tag for element "a" which is not open
    …><img src="http://xemphimon.com/images/chatluong-hot.png" /></a></span></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 205, Column 235: required attribute "alt" not specified
    …AAAAAAAIPQ/T-JYAqA1oN8/Vu-Dieu-Duong-Pho-2.jpg" width="120" height="160" /></a>

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

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

  • Error Line 210, Column 10: end tag for element "tr" which is not open
    </li></tr><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 210, Column 14: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    </li></tr><li>

    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 211, Column 128: required attribute "alt" not specified
    …><img src="http://xemphimon.com/images/chatluong-hot.png" /></a></span></div>		

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

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

  • Error Line 211, Column 132: end tag for element "a" which is not open
    …><img src="http://xemphimon.com/images/chatluong-hot.png" /></a></span></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 214, Column 232: required attribute "alt" not specified
    …2/03/02/18/46/13306887631425264762_574_574.jpg" width="120" height="160" /></a>

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

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

  • Error Line 219, Column 10: end tag for element "tr" which is not open
    </li></tr>

    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 220, Column 32: ID "topx_video_1" already defined
    				<div class="movie-row" id="topx_video_1" style="display:none"></div>

    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 182, Column 32: ID "topx_video_1" first defined here
    				<div class="movie-row" id="topx_video_1" style="display:none">
  • Error Line 222, Column 25: end tag for "div" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 182, Column 5: start tag was here
    				<div class="movie-row" id="topx_video_1" style="display:none">
  • Error Line 222, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 143, Column 6: start tag was here
    					<div class="movie-row" id="topx_video">
  • Error Line 229, Column 26: element "li1" undefined
    		<div class="title"><li1></li1><h2>PHIM ĐIỆN ẢNH MỚI</h2> 

    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 238, Column 201: required attribute "alt" not specified
    …mphimon.com/images/film/xemphimon-ngayhenb.jpg" width="120" height="160" /></a>

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

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

  • Error Line 247, Column 192: required attribute "alt" not specified
    …imon.com/images/film/xemphimon-Boot-Tracks.jpg" width="120" height="160" /></a>

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

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

  • Error Line 256, Column 229: required attribute "alt" not specified
    …12/04/10/10/05/1334027111855607755_574_574.jpg" width="120" height="160" /></a>

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

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

  • Error Line 265, Column 220: required attribute "alt" not specified
    …himon.com/images/film/xemphimon-NguoiNhen4.jpg" width="120" height="160" /></a>

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

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

  • Error Line 274, Column 226: required attribute "alt" not specified
    …Ewo/sC5ZXHrc7JY/s450/xemphimon_lua-han-thu.jpg" width="120" height="160" /></a>

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

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

  • Error Line 283, Column 243: required attribute "alt" not specified
    …TVLJ3IP8c/s807/xemphimon_nguoi-tinh-quy-am.jpg" width="120" height="160" /></a>

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

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

  • Error Line 292, Column 244: required attribute "alt" not specified
    …W-voNZ1w/s3508/xemphimon_giua-hai-the-gioi.jpg" width="120" height="160" /></a>

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

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

  • Error Line 301, Column 205: required attribute "alt" not specified
    …ilm/2013/02/10/xemphimon_yeu-lam-chong-ban.jpg" width="120" height="160" /></a>

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

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

  • Error Line 310, Column 243: required attribute "alt" not specified
    …KpuXJDFXU/s353/xemphimon_nhung-ngay-ben-em.jpg" width="120" height="160" /></a>

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

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

  • Error Line 319, Column 205: required attribute "alt" not specified
    …ilm/2013/02/10/xemphimon_huyen-thoai-kamui.jpg" width="120" height="160" /></a>

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

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

  • Error Line 328, Column 170: required attribute "alt" not specified
    …phimon.com/film/2013/02/10/xemphimon_ninja.jpg" width="120" height="160" /></a>

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

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

  • Error Line 337, Column 288: required attribute "alt" not specified
    …xemphimon_cao-boi-va-nguoi-ngoai-hanh-tinh.jpg" width="120" height="160" /></a>

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

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

  • Error Line 346, Column 241: required attribute "alt" not specified
    …giYln61mpk/s755/xemphimon_cong-ty-lau-chui.jpg" width="120" height="160" /></a>

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

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

  • Error Line 355, Column 241: required attribute "alt" not specified
    …iAF0jD2Cgs/s297/xemphimon_anh-em-song-sinh.jpg" width="120" height="160" /></a>

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

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

  • Error Line 364, Column 262: required attribute "alt" not specified
    …zh8/s450/xemphimon_ke-hoach-phi-ung-phan-2.jpg" width="120" height="160" /></a>

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

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

  • Error Line 373, Column 212: required attribute "alt" not specified
    …m/2013/02/10/xemphimon_ao-thuat-gia-tai-ba.jpg" width="120" height="160" /></a>

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

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

  • Error Line 385, Column 26: element "li1" undefined
    		<div class="title"><li1></li1><h2>Phim bộ mới cập nhập</h2>

    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 394, Column 244: required attribute "alt" not specified
    …13/02/06/me-chong-vui-ve-nang-dau-xinh-dep.jpg" width="120" height="160" /></a>

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

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

  • Error Line 403, Column 211: required attribute "alt" not specified
    …com/film/2013/02/03/tan-tieu-ngao-giang-ho.jpg" width="120" height="160" /></a>

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

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

  • Error Line 412, Column 219: required attribute "alt" not specified
    …12/04/11/1/55/13340841571955140570_574_574.jpg" width="120" height="160" /></a>

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

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

  • Error Line 421, Column 258: required attribute "alt" not specified
    …3_IM/s400/xemphimon_tan-y-thien-do-long-ky.jpg" width="120" height="160" /></a>

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

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

  • Error Line 430, Column 247: required attribute "alt" not specified
    …rOGbUrB4/s700/xemphimon_y-thien-do-long-ky.jpg" width="120" height="160" /></a>

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

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

  • Error Line 439, Column 250: required attribute "alt" not specified
    …uLbJlNU/s320/xemphimon_dieu-valse-mua-xuan.jpg" width="120" height="160" /></a>

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

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

  • Error Line 448, Column 244: required attribute "alt" not specified
    …KPGnjeAn8/s320/xemphimon_vo-ngua-tay-phong.jpg" width="120" height="160" /></a>

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

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

  • Error Line 457, Column 232: required attribute "alt" not specified
    …2/03/24/11/38/13325639341013771208_574_574.jpg" width="120" height="160" /></a>

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

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

  • Error Line 466, Column 247: required attribute "alt" not specified
    …O8Xk3YvA/s320/xemphimon_cuoc-song-tuoi-dep.jpg" width="120" height="160" /></a>

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

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

  • Error Line 475, Column 253: required attribute "alt" not specified
    …8n_GSA/s400/xemphimon_dam-trai-dep-nha-toi.jpg" width="120" height="160" /></a>

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

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

  • Error Line 484, Column 189: required attribute "alt" not specified
    …com/images/film/xemphimon-longdinhtranhba1.jpg" width="120" height="160" /></a>

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

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

  • Error Line 493, Column 247: required attribute "alt" not specified
    …3RNg_8AA/s604/xemphimon_xung-danh-tai-nu-3.jpg" width="120" height="160" /></a>

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

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

  • Error Line 515, Column 22: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<div><div><b style= color: rgb(255, 255, 255); ><i>Yh ads1: ads.xemphimon - Đt…
  • Error Line 515, Column 32: "rgb" is not a member of a group specified for any attribute
    	<div><div><b style= color: rgb(255, 255, 255); ><i>Yh ads1: ads.xemphimon - Đt…
  • Error Line 515, Column 38: "255" is not a member of a group specified for any attribute
    	<div><div><b style= color: rgb(255, 255, 255); ><i>Yh ads1: ads.xemphimon - Đt…
  • Error Line 515, Column 43: "255" is not a member of a group specified for any attribute
    …v><div><b style= color: rgb(255, 255, 255); ><i>Yh ads1: ads.xemphimon - Đt:&n…
  • Error Line 515, Column 128: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …3.991.741</i></b></div><div><b style= color: rgb(255, 255, 255); ><i>Yh ads2: …
  • Error Line 515, Column 138: "rgb" is not a member of a group specified for any attribute
    …/i></b></div><div><b style= color: rgb(255, 255, 255); ><i>Yh ads2: tuan_wonbi…
  • Error Line 515, Column 144: "255" is not a member of a group specified for any attribute
    …></div><div><b style= color: rgb(255, 255, 255); ><i>Yh ads2: tuan_wonbi - Đt:…
  • Error Line 515, Column 149: "255" is not a member of a group specified for any attribute
    …v><div><b style= color: rgb(255, 255, 255); ><i>Yh ads2: tuan_wonbi - Đt:&nbsp…
  • Error Line 515, Column 235: an attribute value must be a literal unless it contains only name characters
    …6.6148</i></b></div><div><font color= #ffffff ><b><i>Mail: ads.xemphimon@gmail…

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

  • Error Line 515, Column 324: an attribute value must be a literal unless it contains only name characters
    …></font></div></div><div><font color= #ffffff ><b><i><br></i></b></font></div>…

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

  • Error Line 515, Column 346: end tag for "br" omitted, but OMITTAG NO was specified
    …div><font color= #ffffff ><b><i><br></i></b></font></div><font color= #ffffff >

    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 515, Column 339: start tag was here
    …/div><div><font color= #ffffff ><b><i><br></i></b></font></div><font color= #f…
  • Error Line 515, Column 377: an attribute value must be a literal unless it contains only name characters
    …div><font color= #ffffff ><b><i><br></i></b></font></div><font color= #ffffff >

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

  • Error Line 516, Column 29: an attribute value must be a literal unless it contains only name characters
    - </font><i><b><font color= #0066ff >Phim Nào Bị Lỗi Các Bạn Có Thể Chụp Lại Ản…

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

  • Error Line 516, Column 160: end tag for "br" omitted, but OMITTAG NO was specified
    … Đó Và Gửi Qua Mail: ads.xemphimon@gmail.com Để Được Hỗ Trợ.<br></font></b></i>

    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 516, Column 150: start tag was here
    … Đó Và Gửi Qua Mail: ads.xemphimon@gmail.com Để Được Hỗ Trợ.<br></font></b></i>
  • Error Line 517, Column 6: end tag for "br" omitted, but OMITTAG NO was specified
     <br><center style= text-align: left; ><div id="fb-root"></div>

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

  • Info Line 517, Column 2: start tag was here
     <br><center style= text-align: left; ><div id="fb-root"></div>
  • Error Line 517, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
     <br><center style= text-align: left; ><div id="fb-root"></div>
  • Error Line 517, Column 37: "left" is not a member of a group specified for any attribute
     <br><center style= text-align: left; ><div id="fb-root"></div>
  • Error Line 518, 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 522, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/vi_VN/all.js#xfbml=1&appId=380424188658579";

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

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

    If you meant to include an entity that starts with "&", then you should terminate it 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 522, 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=380424188658579";

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

  • Info Line 522, Column 56: entity was defined here
      js.src = "//connect.facebook.net/vi_VN/all.js#xfbml=1&appId=380424188658579";
  • Error Line 525, Column 32: there is no attribute "data-href"
    <div class="fb-like" data-href="http://xemphimon.com/" data-send="true" data-la…

    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 525, Column 66: there is no attribute "data-send"
    …ref="http://xemphimon.com/" data-send="true" data-layout="button_count" data-w…

    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 525, Column 85: there is no attribute "data-layout"
    …on.com/" data-send="true" data-layout="button_count" data-width="10" 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 525, Column 111: there is no attribute "data-width"
    …data-layout="button_count" data-width="10" data-show-faces="true" data-font="v…

    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 525, Column 132: there is no attribute "data-show-faces"
    …on_count" data-width="10" data-show-faces="true" data-font="verdana"></div><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 525, Column 149: there is no attribute "data-font"
    …on_count" data-width="10" data-show-faces="true" data-font="verdana"></div><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 525, Column 169: end tag for "br" omitted, but OMITTAG NO was specified
    …on_count" data-width="10" data-show-faces="true" data-font="verdana"></div><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 525, Column 165: start tag was here
    …on_count" data-width="10" data-show-faces="true" data-font="verdana"></div><br>
  • Error Line 526, Column 122: required attribute "alt" not specified
    …t/pvwhcfqji1ed" width="0" height="0" border="0" title="User Online" /></center>

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

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

  • Error Line 533, Column 113: duplicate specification of attribute "title"
    …e="13/01/2012 -&gt; 13/02/2013" title="13/01/2012 -&gt; 13/02/2013"><img src="…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Warning Line 533, Column 237: cannot generate system identifier for general entity "gadget"
    …ent.com/gadgets/proxy?container=focus&gadget=a&rewriteMime=image/*&url=https:/…

    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 533, Column 237: general entity "gadget" not defined and no default entity
    …ent.com/gadgets/proxy?container=focus&gadget=a&rewriteMime=image/*&url=https:/…

    This is usually a cascading error caused by 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 533, Column 243: reference not terminated by REFC delimiter
    …m/gadgets/proxy?container=focus&gadget=a&rewriteMime=image/*&url=https://lh3.g…

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

  • Warning Line 533, Column 243: reference to external entity in attribute value
    …m/gadgets/proxy?container=focus&gadget=a&rewriteMime=image/*&url=https://lh3.g…

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

  • Error Line 533, Column 243: reference to entity "gadget" for which no system identifier could be generated
    …m/gadgets/proxy?container=focus&gadget=a&rewriteMime=image/*&url=https://lh3.g…

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

  • Info Line 533, Column 236: entity was defined here
    …tent.com/gadgets/proxy?container=focus&gadget=a&rewriteMime=image/*&url=https:…
  • Warning Line 533, Column 246: cannot generate system identifier for general entity "rewriteMime"
    …adgets/proxy?container=focus&gadget=a&rewriteMime=image/*&url=https://lh3.goog…

    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 533, Column 246: general entity "rewriteMime" not defined and no default entity
    …adgets/proxy?container=focus&gadget=a&rewriteMime=image/*&url=https://lh3.goog…

    This is usually a cascading error caused by 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 533, Column 257: reference not terminated by REFC delimiter
    …y?container=focus&gadget=a&rewriteMime=image/*&url=https://lh3.googleuserconte…

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

  • Warning Line 533, Column 257: reference to external entity in attribute value
    …y?container=focus&gadget=a&rewriteMime=image/*&url=https://lh3.googleuserconte…

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

  • Error Line 533, Column 257: reference to entity "rewriteMime" for which no system identifier could be generated
    …y?container=focus&gadget=a&rewriteMime=image/*&url=https://lh3.googleuserconte…

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

  • Info Line 533, Column 245: entity was defined here
    …gadgets/proxy?container=focus&gadget=a&rewriteMime=image/*&url=https://lh3.goo…
  • Warning Line 533, Column 266: cannot generate system identifier for general entity "url"
    …er=focus&gadget=a&rewriteMime=image/*&url=https://lh3.googleusercontent.com/-9…

    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 533, Column 266: general entity "url" not defined and no default entity
    …er=focus&gadget=a&rewriteMime=image/*&url=https://lh3.googleusercontent.com/-9…

    This is usually a cascading error caused by 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 533, Column 269: reference not terminated by REFC delimiter
    …focus&gadget=a&rewriteMime=image/*&url=https://lh3.googleusercontent.com/-9rvJ…

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

  • Warning Line 533, Column 269: reference to external entity in attribute value
    …focus&gadget=a&rewriteMime=image/*&url=https://lh3.googleusercontent.com/-9rvJ…

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

  • Error Line 533, Column 269: reference to entity "url" for which no system identifier could be generated
    …focus&gadget=a&rewriteMime=image/*&url=https://lh3.googleusercontent.com/-9rvJ…

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

  • Info Line 533, Column 265: entity was defined here
    …ner=focus&gadget=a&rewriteMime=image/*&url=https://lh3.googleusercontent.com/-…
  • Error Line 533, Column 478: end tag for "img" omitted, but OMITTAG NO was specified
    …2 -&gt; 13/02/2013" title="13/01/2012 -&gt; 13/02/2013"></a><br></center></div>

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

  • Info Line 533, Column 143: start tag was here
    …" title="13/01/2012 -&gt; 13/02/2013"><img src="http://images2-focus-opensocia…
  • Error Line 533, Column 491: end tag for "br" omitted, but OMITTAG NO was specified
    …2 -&gt; 13/02/2013" title="13/01/2012 -&gt; 13/02/2013"></a><br></center></div>

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

  • Info Line 533, Column 479: start tag was here
    …2 -&gt; 13/02/2013" title="13/01/2012 -&gt; 13/02/2013"></a><br></center></div>
  • Error Line 544, Column 67: required attribute "alt" not specified
    <img src="http://xemphimon.com/skin/sieudinh/images/list_01.gif" />&nbsp;

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

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

  • Error Line 548, Column 67: required attribute "alt" not specified
    <img src="http://xemphimon.com/skin/sieudinh/images/list_01.gif" />&nbsp;

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

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

  • Error Line 554, Column 67: required attribute "alt" not specified
    <img src="http://xemphimon.com/skin/sieudinh/images/list_01.gif" />&nbsp;

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

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

  • Error Line 559, Column 67: required attribute "alt" not specified
    <img src="http://xemphimon.com/skin/sieudinh/images/list_01.gif" />&nbsp;

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

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

  • Error Line 565, Column 67: required attribute "alt" not specified
    <img src="http://xemphimon.com/skin/sieudinh/images/list_01.gif" />&nbsp;

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

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

  • Error Line 570, Column 90: required attribute "alt" not specified
    …xemphimon.com/skin/sieudinh/images/list_01.gif" title="Phim Hoạt Hình" />&nbsp;

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

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

  • Error Line 576, Column 90: required attribute "alt" not specified
    …xemphimon.com/skin/sieudinh/images/list_01.gif" title="Phim Phiêu Lưu" />&nbsp;

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

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

  • Error Line 581, Column 89: required attribute "alt" not specified
    …/xemphimon.com/skin/sieudinh/images/list_01.gif" title="Phim Võ Thuật" />&nbsp;

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

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

  • Error Line 587, Column 88: required attribute "alt" not specified
    …//xemphimon.com/skin/sieudinh/images/list_01.gif" title="Phim Âm Nhạc" />&nbsp;

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

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

  • Error Line 592, Column 89: required attribute "alt" not specified
    …/xemphimon.com/skin/sieudinh/images/list_01.gif" title="Phim Hài Hước" />&nbsp;

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

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

  • Error Line 598, Column 87: required attribute "alt" not specified
    …://xemphimon.com/skin/sieudinh/images/list_01.gif" title="Phim Tâm Lý" />&nbsp;

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

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

  • Error Line 603, Column 91: required attribute "alt" not specified
    …emphimon.com/skin/sieudinh/images/list_01.gif" title="Phim Viễn Tưỡng" />&nbsp;

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

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

  • Error Line 609, Column 91: required attribute "alt" not specified
    …emphimon.com/skin/sieudinh/images/list_01.gif" title="Phim Thần Thoại" />&nbsp;

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

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

  • Error Line 614, Column 92: required attribute "alt" not specified
    …mphimon.com/skin/sieudinh/images/list_01.gif" title="Phim Chiến Tranh" />&nbsp;

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

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

  • Error Line 620, Column 89: required attribute "alt" not specified
    …/xemphimon.com/skin/sieudinh/images/list_01.gif" title="Phim Thể Thao" />&nbsp;

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

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

  • Error Line 625, Column 88: required attribute "alt" not specified
    …//xemphimon.com/skin/sieudinh/images/list_01.gif" title="Phim Hình Sự" />&nbsp;

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

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

  • Error Line 631, Column 86: required attribute "alt" not specified
    …p://xemphimon.com/skin/sieudinh/images/list_01.gif" title="Phim Dã Sữ" />&nbsp;

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

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

  • Error Line 636, Column 84: required attribute "alt" not specified
    …ttp://xemphimon.com/skin/sieudinh/images/list_01.gif" title="Phim 18+" />&nbsp;

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

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

  • Error Line 652, Column 84: required attribute "alt" not specified
    …ttp://xemphimon.com/skin/sieudinh/images/list_01.gif" title="Xem Phim" />&nbsp;

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

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

  • Error Line 657, Column 84: required attribute "alt" not specified
    …ttp://xemphimon.com/skin/sieudinh/images/list_01.gif" title="Xem Phim" />&nbsp;

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

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

  • Error Line 663, Column 84: required attribute "alt" not specified
    …ttp://xemphimon.com/skin/sieudinh/images/list_01.gif" title="Xem Phim" />&nbsp;

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

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

  • Error Line 668, Column 84: required attribute "alt" not specified
    …ttp://xemphimon.com/skin/sieudinh/images/list_01.gif" title="Xem Phim" />&nbsp;

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

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

  • Error Line 674, Column 84: required attribute "alt" not specified
    …ttp://xemphimon.com/skin/sieudinh/images/list_01.gif" title="Xem Phim" />&nbsp;

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

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

  • Error Line 679, Column 84: required attribute "alt" not specified
    …ttp://xemphimon.com/skin/sieudinh/images/list_01.gif" title="Xem Phim" />&nbsp;

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

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

  • Error Line 685, Column 84: required attribute "alt" not specified
    …ttp://xemphimon.com/skin/sieudinh/images/list_01.gif" title="Xem Phim" />&nbsp;

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

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

  • Error Line 690, Column 84: required attribute "alt" not specified
    …ttp://xemphimon.com/skin/sieudinh/images/list_01.gif" title="Xem Phim" />&nbsp;

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

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

  • Error Line 696, Column 84: required attribute "alt" not specified
    …ttp://xemphimon.com/skin/sieudinh/images/list_01.gif" title="Xem Phim" />&nbsp;

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

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

  • Error Line 701, Column 84: required attribute "alt" not specified
    …ttp://xemphimon.com/skin/sieudinh/images/list_01.gif" title="Xem Phim" />&nbsp;

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

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

  • Error Line 740, Column 30: value of attribute "id" must be a single token
                <div id="menu_shd png"></div>

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 746, Column 10: end tag for element "div" which is not open
        </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 747, Column 6: end tag for element "div" which is not open
    </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 761, Column 222: required attribute "alt" not specified
    ….hdonline.vn/banner/ads/vosongkiem.gif" width="130px" height="550px"></a></div>

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

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

  • Error Line 761, Column 226: end tag for "img" omitted, but OMITTAG NO was specified
    ….hdonline.vn/banner/ads/vosongkiem.gif" width="130px" height="550px"></a></div>

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

  • Info Line 761, Column 136: start tag was here
    …//www.vosongkiem.net" target="_blank"><img src="http://i.hdonline.vn/banner/ad…
  • Warning Line 763, Column 71: cannot generate system identifier for general entity "callback"
    …er.zing.vn/lview?loc=_adb_22_10002608&callback=crystal2.addStaticSlot"></scrip…

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

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

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

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

  • Error Line 763, Column 71: general entity "callback" not defined and no default entity
    …er.zing.vn/lview?loc=_adb_22_10002608&callback=crystal2.addStaticSlot"></scrip…

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

  • Warning Line 763, Column 79: reference not terminated by REFC delimiter
    …r.zing.vn/lview?loc=_adb_22_10002608&callback=crystal2.addStaticSlot"></script>

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

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

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

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

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

  • Info Line 763, Column 70: entity was defined here
    …ker.zing.vn/lview?loc=_adb_22_10002608&callback=crystal2.addStaticSlot"></scri…
  • Error Line 763, Column 103: required attribute "type" not specified
    …r.zing.vn/lview?loc=_adb_22_10002608&callback=crystal2.addStaticSlot"></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>.

Visitor Analysis

Daily Visitor
  • 1.890 visits

In Page Analysis