Trang thông tin cập nhật liên tục về các vấn đề thời sự, gia đình, xã hội tại Việt Nam và thế giới. Báo điện tử của Báo Gia đình và Xã hội ...

giadinh.net.vn
  • Domain Name
    giadinh.net.vn
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #15886
  • Page Size
    95.5 KB
  • Ip Address
    222.255.27.167
  • Heading
    H1: 1, H2: 24, H3: 29, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 40 JPG, 1 PNG

Website Meta Analysis

  • Title
    Báo Gia đình & Xã hội | giadinh.net.vn
  • Meta Keyword
  • Meta Description
    Trang thông tin cập nhật liên tục về các vấn đề thời sự, gia đình, xã hội tại Việt Nam và thế giới. Báo điện tử của Báo Gia đình và Xã hội - Giadinh.net.vn.

Technical Analysis

  • Webserver
    gd-rp
  • Ip Address
    222.255.27.167
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from giadinh.net.vn.

HTML Analysis

  • date: Tue, 07 Oct 2014 12:32:28 GMT
  • content-type: text/html
  • content-length: 24995
  • connection: close
  • server: gd-rp
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for giadinh.net.vn

DNS Analysis


DNS servers
ns7.synerfy.com [203.162.1.109]
ns6.synerfy.com [74.52.71.179]


DNS Records

Answer records
giadinh.net.vn A 222.255.27.167 3600s
giadinh.net.vn NS  ns8.synerfy.com 3600s
giadinh.net.vn NS  ns6.synerfy.com 3600s
giadinh.net.vn NS  ns7.synerfy.com 3600s
giadinh.net.vn SOA
server: c27919-64818
email: hostmaster
serial: 114
refresh: 900
retry: 600
expire: 86400
minimum ttl: 3600
3600s
giadinh.net.vn MX
preference: 10
exchange: aspmx.l.google.com
3600s
giadinh.net.vn MX
preference: 30
exchange: aspmx2.googlemail.com
3600s
giadinh.net.vn MX
preference: 30
exchange: aspmx4.googlemail.com
3600s
giadinh.net.vn MX
preference: 30
exchange: aspmx3.googlemail.com
3600s
giadinh.net.vn MX
preference: 20
exchange: alt1.aspmx.l.google.com
3600s
giadinh.net.vn MX
preference: 20
exchange: alt2.aspmx.l.google.com
3600s

Authority records

Additional records

IP 222.255.27.167 Analysis

  • Country Code
    VN
  • Country Code3
    VNM
  • Country Name
    Vietnam
  • City
    Hanoi
  • Continent Code
    AS
  • Latitude
    21.0333
  • Longitude
    105.85
  • % [whois.apnic.net node-7]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 222.255.7.0 - 222.255.71.255
    netname: VDC-NET
    country: vn
    descr: VietNam Data Communication Company
    admin-c: VIG1-AP
    tech-c: VIG1-AP
    status: ALLOCATED NON-PORTABLE
    changed: hm-changed@vnnic.net.vn 20090325
    mnt-by: MAINT-VN-VNPT
    source: APNIC

    route: 222.255.0.0/19
    descr: VietNam Post and Telecom Corporation (VNPT)
    descr: VNPT-AS-AP
    country: VN
    origin: AS7643
    remarks: mailto: noc@vnn.vn
    notify: hm-changed@vnnic.net.vn
    mnt-by: MAINT-VN-VNPT
    changed: hm-changed@vnnic.net.vn 20100118
    source: APNIC

    role: VDC IPADMIN GROUP
    address: Internet Building, Block II, Thang Long Inter Village
    address: Nguyen Phong Sac str, Cau Giay Dist, Ha Noi
    country: VN
    phone: +84-912-800008
    fax-no: +84-4-9430427
    e-mail: hathm@vdc.com.vn
    remarks: send spam reports to abuse@vdc.com.vn
    remarks: and abuse reports to abuse@vnn.vn
    admin-c: THMH1-AP
    tech-c: THMH1-AP
    nic-hdl: VIG1-AP
    notify: hm-changed@vnnic.net.vn
    mnt-by: MAINT-VN-VNPT
    changed: hm-changed@vnnic.net.vn 20090325
    source: APNIC
    changed: hm-changed@apnic.net 20111114


In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 71 Errors
  • 88 Warnings
Ratio Text/Html
  • 0.6699738155633745
Message Error
  • Warning Line 7, Column 15: character "&" is the first character of a delimiter but occurred as data
    	Báo Gia đình & Xã hội | giadinh.net.vn

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 8, Column 92: there is no attribute "property"
    …/html;charset=utf-8" /><meta property="og:type" content="article" /><meta prop…

    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 8, Column 227: required attribute "content" not specified
    …ctl00_idOgIitle" property="og:title" /><meta id="ctl00_idOgImg" property="og:i…

    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 8, Column 274: required attribute "content" not specified
    …="ctl00_idOgImg" property="og:image" /><meta id="ctl00_idOgDes" property="og:d…

    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 8, Column 327: required attribute "content" not specified
    …0_idOgDes" property="og:description" /><meta property="fb:app_id" content="387…

    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 8, Column 450: required attribute "content" not specified
    …e" property="article:published_time" /><meta id="ctl00_modified_time" property…

    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 8, Column 516: required attribute "content" not specified
    …me" property="article:modified_time" /><meta id="ctl00_expiration_time" proper…

    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 8, Column 586: required attribute "content" not specified
    …" property="article:expiration_time" /><meta property="article:section" conten…

    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 61, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 96, Column 99: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>TRANG CHỦ</p><span class="conner-right …

    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 97, Column 117: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>TIN TRONG NGÀY</p><span class="conner-r…

    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 98, Column 137: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …fl"></span><p style="padding-left:3px">XÃ HỘI</p><span class="conner-right fl"…

    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 99, Column 114: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>GIA ĐÌNH</p><span class="conner-right f…

    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 100, Column 113: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>CHIA SẺ</p><span class="conner-right fl…

    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 101, Column 110: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>BLOG</p><span class="conner-right fl"><…

    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 102, Column 114: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>SỨC KHỎE</p><span class="conner-right f…

    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 103, Column 113: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>VĂN HÓA</p><span class="conner-right fl…

    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 104, Column 114: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>THẾ GIỚI</p><span class="conner-right f…

    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 105, Column 118: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>NUÔI DẠY CON</p><span class="conner-rig…

    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 106, Column 115: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>PHÁP LUẬT</p><span class="conner-right …

    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 107, Column 114: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>ĐỜI SỐNG</p><span class="conner-right f…

    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 108, Column 113: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>MUA SẮM</p><span class="conner-right fl…

    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 109, Column 113: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>LÀM ĐẸP</p><span class="conner-right fl…

    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 110, Column 112: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>DÂN SỐ</p><span class="conner-right fl"…

    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 111, Column 110: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>Y TẾ</p><span class="conner-right fl"><…

    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 112, Column 114: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span class="conner-left fl"></span><p>VIDEO</p><span class="conner-right fl">…

    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 126, Column 112: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>DÒNG SỰ KIỆN</p><span class="sub-conner…

    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 127, Column 132: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Trang thơ Tết</p><span class="sub-conne…

    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 127, Column 327: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>B&#225;o Tết 2013</p><span class="sub-c…

    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 127, Column 535: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>M&#243;n ngon ng&#224;y đ&#244;ng</p><s…

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

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

  • Error Line 130, Column 146: required attribute "alt" not specified
    … src="http://staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/li-rss.gif" /></a>

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

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

  • Warning Line 168, Column 13: character "<" is the first character of a delimiter but occurred as data
        if(hour < 10) hour = "0" + hour ;

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 178, Column 130: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Thời sự</p><span class="sub-conner-righ…

    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 179, Column 134: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Phóng sự</p><span class="sub-conner-rig…

    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 180, Column 134: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Giáo dục</p><span class="sub-conner-rig…

    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 183, Column 138: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Sống chung</p><span class="sub-conner-r…

    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 184, Column 139: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Chuyện tình</p><span class="sub-conner-…

    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 185, Column 137: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Phòng the</p><span class="sub-conner-ri…

    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 186, Column 143: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Thâm cung bí sử</p><span class="sub-con…

    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 189, Column 136: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Góc khuất</p><span class="sub-conner-ri…

    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 190, Column 141: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Cộng đồng mạng</p><span class="sub-conn…

    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 191, Column 143: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Làm báo cùng GDN</p><span class="sub-co…

    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 194, Column 142: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Thuốc quanh ta</p><span class="sub-conn…

    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 195, Column 138: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Dinh dưỡng</p><span class="sub-conner-r…

    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 137: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Sống khỏe</p><span class="sub-conner-ri…

    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 199, Column 137: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Chuyện sao</p><span class="sub-conner-r…

    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 200, Column 135: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Nhiệt kế</p><span class="sub-conner-rig…

    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 201, Column 139: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Xem nghe đọc</p><span class="sub-conner…

    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 205, Column 148: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Cuộc sống bốn phương</p><span class="su…

    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 206, Column 137: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Chuyện lạ</p><span class="sub-conner-ri…

    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 207, Column 133: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Hồ sơ</p><span class="sub-conner-right …

    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 210, Column 138: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Bà bầu</p><span class="sub-conner-right…

    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 145: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Nuôi con khỏe</p><span class="sub-conne…

    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 212, Column 145: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Dạy con ngoan</p><span class="sub-conne…

    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 215, Column 144: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Đằng sau tội ác</p><span class="sub-con…

    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 216, Column 137: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Điều tra</p><span class="sub-conner-rig…

    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 217, Column 135: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Tư vấn</p><span class="sub-conner-right…

    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 221, Column 136: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Món ngon</p><span class="sub-conner-rig…

    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 222, Column 135: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Nhà đẹp</p><span class="sub-conner-righ…

    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 223, Column 135: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Mẹo hay</p><span class="sub-conner-righ…

    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 226, Column 137: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Thị trường</p><span class="sub-conner-r…

    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 227, Column 139: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Sản phẩm mới</p><span class="sub-conner…

    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 228, Column 138: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Đồ Hightech</p><span class="sub-conner-…

    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 229, Column 133: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Xe đẹp</p><span class="sub-conner-right…

    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 232, Column 138: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Đẹp công sở</p><span class="sub-conner-…

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

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

  • Error Line 233, Column 139: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Đẹp cùng sao</p><span class="sub-conner…

    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 234, Column 135: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Xu hướng</p><span class="sub-conner-rig…

    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 237, Column 141: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Tin tức - Sự kiện</p><span class="sub-c…

    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 238, Column 131: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>KHHGĐ</p><span class="sub-conner-right …

    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 239, Column 146: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Chất lượng cuộc sống</p><span class="su…

    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 240, Column 147: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Gương sáng CTV dân số</p><span class="s…

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

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

  • Error Line 241, Column 146: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Đường lối - Chính sách</p><span class="…

    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 242, Column 145: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Nghiên cứu - Trao đổi</p><span class="s…

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

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

  • Error Line 246, Column 139: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Tin tức - Sự kiện</p><span class="sub-c…

    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 247, Column 139: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Y học cổ truyền</p><span class="sub-con…

    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 248, Column 144: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Đường lối - Chính sách</p><span class="…

    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 249, Column 136: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Dịch vụ Y tế</p><span class="sub-conner…

    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 250, Column 139: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Thành tựu y học</p><span class="sub-con…

    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 251, Column 143: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="sub-conner-left sprite fl"></span><p>Nghiên cứu - Trao đổi</p><span class="s…

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

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

  • Error Line 254, Column 168: required attribute "alt" not specified
    … src="http://staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/li-rss.gif" /></a>

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

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

  • Warning Line 293, Column 13: character "<" is the first character of a delimiter but occurred as data
        if(hour < 10) hour = "0" + hour ;

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 362, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 388, Column 179: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …erl sprite fl"></span><p class="pd5lr">Tiêu điểm</p> <span class="connerr spri…

    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 389, Column 205: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …mal sprite fl"></span><p class="pd5lr">Đọc nhiều nhất</p> <span class="connerr…

    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 390, Column 187: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …mal sprite fl"></span><p class="pd5lr"><img src="http://staticpress.vcmedia.vn…

    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 390, Column 290: required attribute "alt" not specified
    …/cm-head.png" style="padding-top:1px"/></p> <span class="connerr-nomal sprite …

    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 394, Column 50: there is no attribute "tabindex"
            	        <ul class="tinnb-list" tabindex='1'>

    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 395, Column 767: required attribute "alt" not specified
    …Images/Giadinhv8/listvideo/photo2.png"></a></li><li><a href="/the-gioi/tat-aci…

    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 395, Column 771: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Giadinhv8/listvideo/photo2.png"></a></li><li><a href="/the-gioi/tat-acid-va…

    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 395, Column 664: start tag was here
    …en nhau để tận mắt xem khai quật mổ cổ<img class="icon_img" src="http://static…
  • Error Line 395, Column 1293: required attribute "alt" not specified
    …Images/Giadinhv8/listvideo/photo2.png"></a></li><li><a href="/xa-hoi/co-be-tru…

    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 395, Column 1297: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Giadinhv8/listvideo/photo2.png"></a></li><li><a href="/xa-hoi/co-be-truong-…

    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 395, Column 1190: start tag was here
    …đ&#232;n treo nghệ thuật s&#225;ng tạo<img class="icon_img" src="http://static…
  • Error Line 398, Column 482: required attribute "alt" not specified
    …Images/Giadinhv8/listvideo/photo2.png"></a></li><li><a href="/van-hoa/ennifer-…

    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 398, Column 486: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Giadinhv8/listvideo/photo2.png"></a></li><li><a href="/van-hoa/ennifer-pham…

    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 398, Column 379: start tag was here
    …25;i">T&#243;c cuộn qu&#253; ph&#225;i<img class="icon_img" src="http://static…
  • Error Line 398, Column 2110: required attribute "alt" not specified
    …Images/Giadinhv8/listvideo/video2.png"></a></li><li><a href="/suc-khoe/nhung-t…

    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 398, Column 2114: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Giadinhv8/listvideo/video2.png"></a></li><li><a href="/suc-khoe/nhung-thoi-…

    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 398, Column 2007: start tag was here
    …n xứ H&#224;n ăn cua sống rau r&#225;u<img class="icon_img" src="http://static…
  • Error Line 398, Column 2582: required attribute "alt" not specified
    …staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></li>

    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 398, Column 2586: end tag for "img" omitted, but OMITTAG NO was specified
    …staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></li>

    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 398, Column 2479: start tag was here
    … bụng bầu">Vũ Thu Phương khoe bụng bầu<img class="icon_img" src="http://static…
  • Error Line 409, Column 25: document type does not allow element "div" here; assuming missing "li" start-tag
                        <div><li><a href="/van-hoa/kim-oanh-gay-soc-khi-doi-day-ban…
  • Error Line 409, Column 29: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                        <div><li><a href="/van-hoa/kim-oanh-gay-soc-khi-doi-day-ban…

    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 409, Column 788: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …t; ban gi&#225;m khảo</a></h2></li><li><a href="/van-hoa/con-gai-hiep-ga-giong…

    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 409, Column 1475: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …giống bố như đ&#250;c</a></h2></li><li><a href="/gia-dinh/cach-cung-sao-giai-h…

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

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

  • Error Line 409, Column 2044: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    … sao giải hạn đầu năm</a></h2></li><li><a href="/dan-so/gltt-de-xuat-cac-giai-…

    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 409, Column 3290: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …5;i&quot; </a></h2></li></div><div><li><a href="/xa-hoi/nhung-con-lai-goc-viet…

    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 409, Column 3976: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …236;m lại cha mẹ ruột</a></h2></li><li><a href="/van-hoa/vo-chong-ennifer-tinh…

    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 409, Column 4585: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …;nh tứ tr&#234;n biển</a></h2></li><li><a href="/gia-dinh/tham-cung-bi-su-412-…

    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 409, Column 5491: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …;o t&#236;nh y&#234;u</a></h2></li><li><a href="/van-hoa/len-xem-hanh-phuc-cua…

    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 409, Column 6222: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …224;i Việt</a></h2></li></div><div><li><a href="/gia-dinh/voi-vang-gai-e-phai-…

    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 409, Column 6845: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …phải trả gi&#225; đắt</a></h2></li><li><a href="/gia-dinh/khi-chong-phong-thu-…

    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 409, Column 7506: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    … tài chính với vợ</a></h2></li><li><a href="/suc-khoe/7-chieu-giup-day-lui…

    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 409, Column 8171: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …9;i bệnh gan nhiễm mỡ</a></h2></li><li><a href="/van-hoa/nghe-si-dau-buon-khi-…

    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 409, Column 8937: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …39; tử nạn</a></h2></li></div><div><li><a href="/xa-hoi/vu-chay-no-chet-10-ngu…

    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 409, Column 9789: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    … để tiếp tục điều tra</a></h2></li><li><a href="/xa-hoi/phan-thi-bich-hang-chi…

    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 409, Column 10555: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …gười c&#245;i &#226;m</a></h2></li><li><a href="/van-hoa/vu-hoang-viet-tay-tro…

    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 409, Column 11255: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …m phim với tỷ phủ U50</a></h2></li><li><a href="/van-hoa/ha-tang-sanh-dieu-di-…

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

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

  • Error Line 410, Column 21: 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 409, Column 21: start tag was here
                        <div><li><a href="/van-hoa/kim-oanh-gay-soc-khi-doi-day-ban…
  • Error Line 453, Column 62: document type does not allow element "a" here
            //return '<a href="#" class="listico2 sprite fl mgr5">'+(idx+1)+'</a>';

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

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

  • Error Line 454, Column 53: document type does not allow element "a" here
            return '<a href="#" class="listico2 fl mgr5">'+(idx+1)+'</a>';

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

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

  • Error Line 482, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 492, Column 133: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Xã hội</p> <span class="connerr sprite …

    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 499, Column 287: required attribute "alt" not specified
    …staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></h3>

    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 499, Column 291: end tag for "img" omitted, but OMITTAG NO was specified
    …staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></h3>

    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 499, Column 184: start tag was here
    …en nhau để tận mắt xem khai quật mổ cổ<img class="icon_img" src="http://static…
  • Error Line 511, Column 619: required attribute "alt" not specified
    …cpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></h4></li>

    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 511, Column 623: end tag for "img" omitted, but OMITTAG NO was specified
    …cpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></h4></li>

    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 511, Column 516: start tag was here
    … ở lễ hội ch&#249;a B&#225;i Đ&#237;nh<img class="icon_img" src="http://static…
  • Error Line 519, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 528, Column 1306: required attribute "alt" not specified
    …staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></li>

    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 528, Column 1310: end tag for "img" omitted, but OMITTAG NO was specified
    …staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></li>

    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 528, Column 1203: start tag was here
    …en nhau để tận mắt xem khai quật mổ cổ<img class="icon_img" src="http://static…
  • Error Line 540, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 550, Column 135: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Gia đình</p> <span class="connerr sprit…

    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 579, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 617, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 627, Column 134: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Chia sẻ</p> <span class="connerr sprite…

    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 658, Column 505: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …h kinh ho&#224;ng!" width="210px" /><p>Lột truồng, tr&#243;i con giữa đường: N…

    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 672, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 682, Column 135: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Sức khỏe</p> <span class="connerr sprit…

    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 712, Column 456: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ị dậy th&#236; sớm" width="210px" /><p>Giải ph&#225;p tăng chiều cao khi bị dậ…

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

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

  • Error Line 727, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 737, Column 134: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Văn hóa</p> <span class="connerr sprite…

    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 756, Column 609: required attribute "alt" not specified
    …cpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></h4></li>

    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 756, Column 613: end tag for "img" omitted, but OMITTAG NO was specified
    …cpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></h4></li>

    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 756, Column 506: start tag was here
    …g của Phương &quot;kh&#243;i lửa&quot;<img class="icon_img" src="http://static…
  • Error Line 765, Column 184: required attribute "alt" not specified
    …rc="http://staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/Bao TETsua.jpg"></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 765, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …rc="http://staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/Bao TETsua.jpg"></a>

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

  • Info Line 765, Column 86: start tag was here
    ….vn/chuyen-de/0/bao-tet-2013-366.htm"><img class="mgtam6 fl" src="http://stati…
  • Error Line 776, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 786, Column 135: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Thế giới</p> <span class="connerr sprit…

    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 800, Column 557: required attribute "alt" not specified
    …cpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/video2.png"></a></h4></li>

    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 800, Column 561: end tag for "img" omitted, but OMITTAG NO was specified
    …cpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/video2.png"></a></h4></li>

    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 800, Column 454: start tag was here
    …p l&#225;i, xe bu&#253;t n&#225;o loạn<img class="icon_img" src="http://static…
  • Error Line 805, Column 337: required attribute "alt" not specified
    …Images/Giadinhv8/listvideo/photo2.png"></a></h4></li><li><h4><a href="/the-gio…

    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 805, Column 341: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Giadinhv8/listvideo/photo2.png"></a></h4></li><li><h4><a href="/the-gioi/kh…

    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 805, Column 234: start tag was here
    … của người phụ nữ bị chồng xẻo mất mũi<img class="icon_img" src="http://static…
  • Error Line 814, Column 161: required attribute "alt" not specified
    …a.vn/GiaDinh/Images/Giadinhv8/banner Night Happy.jpg" class="mgtam10 fl" /></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 824, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 834, Column 139: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Nuôi dạy con</p> <span class="connerr s…

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

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

  • Error Line 867, Column 318: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …anh thật kh&#243;!" width="201px" /><p>L&#224;m anh thật kh&#243;!</p></a></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 867, Column 815: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … nhỏ nhất thế giới" width="201px" /><p>H&#233; lộ b&#237; mật về &#39;b&#224; …

    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 867, Column 994: required attribute "alt" not specified
    …Images/Giadinhv8/listvideo/photo2.png"></p></a></li><li><a href="/nuoi-day-con…

    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 867, Column 998: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Giadinhv8/listvideo/photo2.png"></p></a></li><li><a href="/nuoi-day-con/cho…

    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 867, Column 891: start tag was here
    …; gi&#224; Noel&#39; nhỏ nhất thế giới<img class="icon_img" src="http://static…
  • Error Line 867, Column 1431: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …shoot đầy biểu cảm" width="201px" /><p>Cho&#225;ng với 2 mẫu nh&#237; diễn pho…

    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 867, Column 1594: required attribute "alt" not specified
    …Images/Giadinhv8/listvideo/photo2.png"></p></a></li><li><a href="/nuoi-day-con…

    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 867, Column 1598: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Giadinhv8/listvideo/photo2.png"></p></a></li><li><a href="/nuoi-day-con/be-…

    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 867, Column 1491: start tag was here
    … nh&#237; diễn photoshoot đầy biểu cảm<img class="icon_img" src="http://static…
  • Error Line 867, Column 2012: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …&#234;... con trai" width="201px" /><p>B&#233; Ch&#237;ch B&#244;ng: B&#250;p …

    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 867, Column 2174: required attribute "alt" not specified
    …Images/Giadinhv8/listvideo/photo2.png"></p></a></li><li><a href="/nuoi-day-con…

    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 867, Column 2178: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Giadinhv8/listvideo/photo2.png"></p></a></li><li><a href="/nuoi-day-con/nu-…

    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 867, Column 2071: start tag was here
    …&#244;ng: B&#250;p b&#234;... con trai<img class="icon_img" src="http://static…
  • Error Line 867, Column 2527: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … thần của Đức Hiền" width="201px" /><p>Nụ cười thi&#234;n thần của Đức Hiền<im…

    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 867, Column 2667: required attribute "alt" not specified
    …icpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></p></a></li>

    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 867, Column 2671: end tag for "img" omitted, but OMITTAG NO was specified
    …icpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></p></a></li>

    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 867, Column 2564: start tag was here
    …p>Nụ cười thi&#234;n thần của Đức Hiền<img class="icon_img" src="http://static…
  • Error Line 894, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 904, Column 136: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Pháp luật</p> <span class="connerr spri…

    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 931, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 941, Column 135: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Đời sống</p> <span class="connerr sprit…

    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 948, Column 309: required attribute "alt" not specified
    …staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></h3>

    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 948, Column 313: end tag for "img" omitted, but OMITTAG NO was specified
    …staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></h3>

    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 948, Column 206: start tag was here
    …đ&#232;n treo nghệ thuật s&#225;ng tạo<img class="icon_img" src="http://static…
  • Error Line 955, Column 258: required attribute "alt" not specified
    …Images/Giadinhv8/listvideo/video2.png"></a></h4></li><li><h4><a href="/doi-son…

    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 955, Column 262: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Giadinhv8/listvideo/video2.png"></a></h4></li><li><h4><a href="/doi-song/ng…

    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 955, Column 155: start tag was here
    …u kho tộ">C&#225; b&#244;ng lau kho tộ<img class="icon_img" src="http://static…
  • Error Line 955, Column 543: required attribute "alt" not specified
    …cpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/video2.png"></a></h4></li>

    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 955, Column 547: end tag for "img" omitted, but OMITTAG NO was specified
    …cpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/video2.png"></a></h4></li>

    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 955, Column 440: start tag was here
    …gon miệng c&#225; trứng ng&#226;m giấm<img class="icon_img" src="http://static…
  • Error Line 972, Column 100: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …n.htm" title="Bảo vệ các sở vô tư "xin" tiền dân"><img src="http://video-thumb…

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

  • Error Line 972, Column 263: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …d24.jpg" alt="Bảo vệ các sở vô tư "xin" tiền dân" title="Bảo vệ các sở vô tư "…

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

  • Error Line 972, Column 264: end tag for "img" omitted, but OMITTAG NO was specified
    …24.jpg" alt="Bảo vệ các sở vô tư "xin" tiền dân" title="Bảo vệ các sở vô tư "x…

    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 972, Column 112: start tag was here
    …="Bảo vệ các sở vô tư "xin" tiền dân"><img src="http://video-thumbs.vcmedia.vn…
  • Error Line 972, Column 320: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …Bảo vệ các sở vô tư "xin" tiền dân"><p>Bảo vệ các sở vô tư "xin" tiền dân<img …

    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 972, Column 534: required attribute "alt" not specified
    …x;float:left;padding-left:2px;padding-top:3px;position:absolute;"></p></a></li>

    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 972, Column 538: end tag for "img" omitted, but OMITTAG NO was specified
    …x;float:left;padding-left:2px;padding-top:3px;position:absolute;"></p></a></li>

    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 972, Column 355: start tag was here
    …><p>Bảo vệ các sở vô tư "xin" tiền dân<img src="http://staticpress.vcmedia.vn/…
  • Error Line 975, Column 320: end tag for "img" omitted, but OMITTAG NO was specified
    …le="Khám phá vụ giết người ở Từ Liêm"><p>Khám phá vụ giết người ở Từ Liêm<img …

    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 975, Column 110: start tag was here
    …le="Khám phá vụ giết người ở Từ Liêm"><img src="http://video-thumbs.vcmedia.vn…
  • Error Line 975, Column 322: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="Khám phá vụ giết người ở Từ Liêm"><p>Khám phá vụ giết người ở Từ Liêm<img sr…

    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 975, Column 534: required attribute "alt" not specified
    …x;float:left;padding-left:2px;padding-top:3px;position:absolute;"></p></a></li>

    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 975, Column 538: end tag for "img" omitted, but OMITTAG NO was specified
    …x;float:left;padding-left:2px;padding-top:3px;position:absolute;"></p></a></li>

    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 975, Column 355: start tag was here
    …m"><p>Khám phá vụ giết người ở Từ Liêm<img src="http://staticpress.vcmedia.vn/…
  • Error Line 978, Column 257: end tag for "img" omitted, but OMITTAG NO was specified
    …au kho tộ" title="Cá bông lau kho tộ"><p>Cá bông lau kho tộ<img src="http://st…

    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 978, Column 83: start tag was here
    …ho-to.htm" title="Cá bông lau kho tộ"><img src="http://video-thumbs.vcmedia.vn…
  • Error Line 978, Column 259: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … kho tộ" title="Cá bông lau kho tộ"><p>Cá bông lau kho tộ<img src="http://stat…

    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 978, Column 457: required attribute "alt" not specified
    …x;float:left;padding-left:2px;padding-top:3px;position:absolute;"></p></a></li>

    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 978, Column 461: end tag for "img" omitted, but OMITTAG NO was specified
    …x;float:left;padding-left:2px;padding-top:3px;position:absolute;"></p></a></li>

    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 978, Column 278: start tag was here
    …bông lau kho tộ"><p>Cá bông lau kho tộ<img src="http://staticpress.vcmedia.vn/…
  • Error Line 981, Column 312: end tag for "img" omitted, but OMITTAG NO was specified
    …e="Gã say cướp lái, xe buýt náo loạn"><p>Gã say cướp lái, xe buýt náo loạn<img…

    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 981, Column 111: start tag was here
    …e="Gã say cướp lái, xe buýt náo loạn"><img src="http://video-thumbs.vcmedia.vn…
  • Error Line 981, Column 314: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"Gã say cướp lái, xe buýt náo loạn"><p>Gã say cướp lái, xe buýt náo loạn<img s…

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

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

  • Error Line 981, Column 527: required attribute "alt" not specified
    …x;float:left;padding-left:2px;padding-top:3px;position:absolute;"></p></a></li>

    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 981, Column 531: end tag for "img" omitted, but OMITTAG NO was specified
    …x;float:left;padding-left:2px;padding-top:3px;position:absolute;"></p></a></li>

    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 981, Column 348: start tag was here
    …"><p>Gã say cướp lái, xe buýt náo loạn<img src="http://staticpress.vcmedia.vn/…
  • Error Line 984, Column 326: end tag for "img" omitted, but OMITTAG NO was specified
    …ô tô lạ lùn tịt lướt trên phố Hà Nội"><p>Mô tô lạ lùn tịt lướt trên phố Hà Nộ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 984, Column 120: start tag was here
    …ô tô lạ lùn tịt lướt trên phố Hà Nội"><img src="http://video-thumbs.vcmedia.vn…
  • Error Line 984, Column 328: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …tô lạ lùn tịt lướt trên phố Hà Nội"><p>Mô tô lạ lùn tịt lướt trên phố Hà Nội<i…

    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 984, Column 545: required attribute "alt" not specified
    …x;float:left;padding-left:2px;padding-top:3px;position:absolute;"></p></a></li>

    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 984, Column 549: end tag for "img" omitted, but OMITTAG NO was specified
    …x;float:left;padding-left:2px;padding-top:3px;position:absolute;"></p></a></li>

    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 984, Column 366: start tag was here
    …>Mô tô lạ lùn tịt lướt trên phố Hà Nội<img src="http://staticpress.vcmedia.vn/…
  • Error Line 995, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 1005, Column 134: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Mua sắm</p> <span class="connerr sprite…

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

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

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

  • Error Line 1072, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 1082, Column 134: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Làm đẹp</p> <span class="connerr sprite…

    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 1089, Column 249: required attribute "alt" not specified
    …staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></h3>

    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 1089, Column 253: end tag for "img" omitted, but OMITTAG NO was specified
    …staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></h3>

    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 1089, Column 146: start tag was here
    …25;i">T&#243;c cuộn qu&#253; ph&#225;i<img class="icon_img" src="http://static…
  • Error Line 1096, Column 561: required attribute "alt" not specified
    …cpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></h4></li>

    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 1096, Column 565: end tag for "img" omitted, but OMITTAG NO was specified
    …cpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/photo2.png"></a></h4></li>

    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 1096, Column 458: start tag was here
    …3;c tết hoa cho buổi hẹn l&#227;ng mạn<img class="icon_img" src="http://static…
  • Error Line 1101, Column 289: required attribute "alt" not specified
    …Images/Giadinhv8/listvideo/video2.png"></a></h4></li><li><h4><a href="/lam-dep…

    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 1101, Column 293: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Giadinhv8/listvideo/video2.png"></a></h4></li><li><h4><a href="/lam-dep/lan…

    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 1101, Column 186: start tag was here
    …>Quyến rũ với mẫu t&#243;c xoắn mới lạ<img class="icon_img" src="http://static…
  • Error Line 1101, Column 573: required attribute "alt" not specified
    …cpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/video2.png"></a></h4></li>

    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 1101, Column 577: end tag for "img" omitted, but OMITTAG NO was specified
    …cpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/listvideo/video2.png"></a></h4></li>

    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 1101, Column 470: start tag was here
    …&#227;ng mạn với kiểu t&#243;c vintage<img class="icon_img" src="http://static…
  • Error Line 1111, Column 100: required attribute "alt" not specified
    …//staticpress.vcmedia.vn/GiaDinh/Images/Giadinhv8/img2.png" class="fl mgt16" />

    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 1191, Column 23: document type does not allow element "style" here
    <style type="text/css"> 

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

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

  • Error Line 1198, Column 142: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Dân số</p> <span class="connerr sprite …

    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 1199, Column 368: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rọng nam, khinh nữ" width="317px" /><p>Gỡ bỏ quan niệm trọng nam, khinh nữ</p>…

    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 1209, Column 23: document type does not allow element "style" here
    <style type="text/css"> 

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

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

  • Error Line 1216, Column 159: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Dữ liệu dân số</p> <span class="connerr…

    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 1217, Column 587: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … h&#243;a chủ động" width="317px" /><p>Chăm s&#243;c, ph&#225;t huy vai tr&#24…

    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 1227, Column 23: document type does not allow element "style" here
    <style type="text/css"> 

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

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

  • Error Line 1234, Column 140: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rl sprite fl"></span><p class="pd17lr">Y tế</p> <span class="connerr sprite fl…

    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 1235, Column 382: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …4;y đo&#225;n bệnh" width="317px" /><p>Nh&#236;n l&#244;ng m&#224;y đo&#225;n …

    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 1253, Column 23: document type does not allow element "style" here
    <style type="text/css"> 

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

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

  • Error Line 1278, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …t Nam" style="position:absolute; top: 104px; width: 108px; right: 0;border: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 1278, Column 21: start tag was here
                        <img src="http://admicro2.vcmedia.vn/logo/runbyvcc.v.png" a…
  • Warning Line 1287, Column 24: character "&" is the first character of a delimiter but occurred as data
                    Hỗ trợ & CSKH: 01268 269 779 (Ms.Thơm)<br />

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1289, Column 128: end tag for "br" omitted, but OMITTAG NO was specified
    …et="_blank" title="phụ nữ, gia đình, làm đẹp">phụ nữ, gia đình, làm đẹp</a><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 1289, Column 124: start tag was here
    …et="_blank" title="phụ nữ, gia đình, làm đẹp">phụ nữ, gia đình, làm đẹp</a><br>
  • Error Line 1298, Column 35: there is no attribute "scr"
    <script language="javascript" scr="http://admicro1.vcmedia.vn/core/adm_tracking…

    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 1298, Column 84: required attribute "type" not specified
    …ge="javascript" scr="http://admicro1.vcmedia.vn/core/adm_tracking.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>.

  • Warning Line 1308, Column 243: character "&" is the first character of a delimiter but occurred as data
    …replace(/\+/g,' ');var args=qs.split('&');for(var i=0;i<args.length;i++){var p…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1308, Column 272: character ";" not allowed in attribute specification list
    …s.split('&');for(var i=0;i<args.length;i++){var pair=args[i].split('=');var na…
  • Error Line 1308, Column 272: element "args.length" undefined
    …s.split('&');for(var i=0;i<args.length;i++){var pair=args[i].split('=');var na…

    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 1313, Column 1774: character ";" not allowed in attribute specification list
    …kie.split(';');for(var i=0;i<ca.length;i++){c=ca[i];while(c.charAt(0)==' ')c=c…
  • Error Line 1313, Column 1774: element "ca.length" undefined
    …kie.split(';');for(var i=0;i<ca.length;i++){c=ca[i];while(c.charAt(0)==' ')c=c…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1313, Column 2024: cannot generate system identifier for general entity "dd"
    …giadinh.net.vn/Handler.ashx?'+query+'&dd='+(new Date).getTime();var img=new Im…

    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 1313, Column 2024: general entity "dd" not defined and no default entity
    …giadinh.net.vn/Handler.ashx?'+query+'&dd='+(new Date).getTime();var img=new Im…

    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 1313, Column 2026: reference not terminated by REFC delimiter
    …adinh.net.vn/Handler.ashx?'+query+'&dd='+(new Date).getTime();var img=new Imag…

    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 1313, Column 2026: reference to entity "dd" for which no system identifier could be generated
    …adinh.net.vn/Handler.ashx?'+query+'&dd='+(new Date).getTime();var img=new Imag…

    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 1313, Column 2023: entity was defined here
    ….giadinh.net.vn/Handler.ashx?'+query+'&dd='+(new Date).getTime();var img=new I…
  • Error Line 1313, Column 3422: character ";" not allowed in attribute specification list
    …Okw[27]="q";for(var i=0;i<_uOsr.length;i++) if(referrer.toLowerCase().indexOf(…
  • Error Line 1313, Column 3422: element "_uOsr.length" undefined
    …Okw[27]="q";for(var i=0;i<_uOsr.length;i++) if(referrer.toLowerCase().indexOf(…

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

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1313, Column 4435: cannot generate system identifier for general entity "newsId"
    …eSpan_Persistance);} if(newsId!=null&&newsId!=''&&newsId!='-1') {cookieName='G…

    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 1313, Column 4435: general entity "newsId" not defined and no default entity
    …eSpan_Persistance);} if(newsId!=null&&newsId!=''&&newsId!='-1') {cookieName='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.

  • Warning Line 1313, Column 4441: reference not terminated by REFC delimiter
    …Persistance);} if(newsId!=null&&newsId!=''&&newsId!='-1') {cookieName='GiaDinh…

    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 1313, Column 4441: reference to entity "newsId" for which no system identifier could be generated
    …Persistance);} if(newsId!=null&&newsId!=''&&newsId!='-1') {cookieName='GiaDinh…

    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 1313, Column 4434: entity was defined here
    …meSpan_Persistance);} if(newsId!=null&&newsId!=''&&newsId!='-1') {cookieName='…
  • Warning Line 1313, Column 4445: character "&" is the first character of a delimiter but occurred as data
    …istance);} if(newsId!=null&&newsId!=''&&newsId!='-1') {cookieName='GiaDinhNet.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1313, Column 4453: reference not terminated by REFC delimiter
    …;} if(newsId!=null&&newsId!=''&&newsId!='-1') {cookieName='GiaDinhNet.Logger.p…

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

  • Error Line 1313, Column 4453: reference to entity "newsId" for which no system identifier could be generated
    …;} if(newsId!=null&&newsId!=''&&newsId!='-1') {cookieName='GiaDinhNet.Logger.p…

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

  • Info Line 1313, Column 4434: entity was defined here
    …meSpan_Persistance);} if(newsId!=null&&newsId!=''&&newsId!='-1') {cookieName='…
  • Error Line 1313, Column 4750: character ";" not allowed in attribute specification list
    …plit(',');var i=0;for(i=0;i<tem.length;i++) {if(tem[i].indexOf(newsId+'_')==0)…
  • Error Line 1313, Column 4750: element "tem.length" undefined
    …plit(',');var i=0;for(i=0;i<tem.length;i++) {if(tem[i].indexOf(newsId+'_')==0)…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1313, Column 5250: character "&" is the first character of a delimiter but occurred as data
    …meSpan_Persistance);}}} if(catId!=null&&catId!=''&&catId!='-1') {cookieName='G…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1313, Column 5252: cannot generate system identifier for general entity "catId"
    …Span_Persistance);}}} if(catId!=null&&catId!=''&&catId!='-1') {cookieName='Gia…

    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 1313, Column 5252: general entity "catId" not defined and no default entity
    …Span_Persistance);}}} if(catId!=null&&catId!=''&&catId!='-1') {cookieName='Gia…

    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 1313, Column 5257: reference not terminated by REFC delimiter
    …Persistance);}}} if(catId!=null&&catId!=''&&catId!='-1') {cookieName='GiaDinhN…

    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 1313, Column 5257: reference to entity "catId" for which no system identifier could be generated
    …Persistance);}}} if(catId!=null&&catId!=''&&catId!='-1') {cookieName='GiaDinhN…

    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 1313, Column 5251: entity was defined here
    …eSpan_Persistance);}}} if(catId!=null&&catId!=''&&catId!='-1') {cookieName='Gi…
  • Warning Line 1313, Column 5261: character "&" is the first character of a delimiter but occurred as data
    …istance);}}} if(catId!=null&&catId!=''&&catId!='-1') {cookieName='GiaDinhNet.L…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1313, Column 5268: reference not terminated by REFC delimiter
    …);}}} if(catId!=null&&catId!=''&&catId!='-1') {cookieName='GiaDinhNet.Logger.c…

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

  • Error Line 1313, Column 5268: reference to entity "catId" for which no system identifier could be generated
    …);}}} if(catId!=null&&catId!=''&&catId!='-1') {cookieName='GiaDinhNet.Logger.c…

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

  • Info Line 1313, Column 5251: entity was defined here
    …eSpan_Persistance);}}} if(catId!=null&&catId!=''&&catId!='-1') {cookieName='Gi…
  • Error Line 1313, Column 5560: character ";" not allowed in attribute specification list
    …plit(',');var i=0;for(i=0;i<tem.length;i++) {if(tem[i].indexOf(catId+'_')==0) …
  • Error Line 1313, Column 5560: element "tem.length" undefined
    …plit(',');var i=0;for(i=0;i<tem.length;i++) {if(tem[i].indexOf(catId+'_')==0) …

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1313, Column 6137: cannot generate system identifier for general entity "articleTitle"
    …\t/g,' ');query='articleId='+newsId+'&articleTitle='+encodeURIComponent(newsTi…

    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 1313, Column 6137: general entity "articleTitle" not defined and no default entity
    …\t/g,' ');query='articleId='+newsId+'&articleTitle='+encodeURIComponent(newsTi…

    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 1313, Column 6149: reference not terminated by REFC delimiter
    …ery='articleId='+newsId+'&articleTitle='+encodeURIComponent(newsTitle?newsTitl…

    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 1313, Column 6149: reference to entity "articleTitle" for which no system identifier could be generated
    …ery='articleId='+newsId+'&articleTitle='+encodeURIComponent(newsTitle?newsTitl…

    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 1313, Column 6136: entity was defined here
    …/\t/g,' ');query='articleId='+newsId+'&articleTitle='+encodeURIComponent(newsT…
  • Warning Line 1313, Column 6202: reference not terminated by REFC delimiter
    …ponent(newsTitle?newsTitle:'')+'&catId='+catId+'&catName='+encodeURIComponent(…

    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 1313, Column 6202: reference to entity "catId" for which no system identifier could be generated
    …ponent(newsTitle?newsTitle:'')+'&catId='+catId+'&catName='+encodeURIComponent(…

    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 1313, Column 5251: entity was defined here
    …eSpan_Persistance);}}} if(catId!=null&&catId!=''&&catId!='-1') {cookieName='Gi…
  • Warning Line 1313, Column 6213: cannot generate system identifier for general entity "catName"
    …Title?newsTitle:'')+'&catId='+catId+'&catName='+encodeURIComponent(catName?cat…

    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 1313, Column 6213: general entity "catName" not defined and no default entity
    …Title?newsTitle:'')+'&catId='+catId+'&catName='+encodeURIComponent(catName?cat…

    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 1313, Column 6220: reference not terminated by REFC delimiter
    …ewsTitle:'')+'&catId='+catId+'&catName='+encodeURIComponent(catName?catName:''…

    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 1313, Column 6220: reference to entity "catName" for which no system identifier could be generated
    …ewsTitle:'')+'&catId='+catId+'&catName='+encodeURIComponent(catName?catName:''…

    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 1313, Column 6212: entity was defined here
    …sTitle?newsTitle:'')+'&catId='+catId+'&catName='+encodeURIComponent(catName?ca…
  • Warning Line 1313, Column 6264: cannot generate system identifier for general entity "hostName"
    …odeURIComponent(catName?catName:'')+'&hostName='+encodeURIComponent(host)+'&ur…

    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 1313, Column 6264: general entity "hostName" not defined and no default entity
    …odeURIComponent(catName?catName:'')+'&hostName='+encodeURIComponent(host)+'&ur…

    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 1313, Column 6272: reference not terminated by REFC delimiter
    …mponent(catName?catName:'')+'&hostName='+encodeURIComponent(host)+'&urlRef='+e…

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

  • Error Line 1313, Column 6272: reference to entity "hostName" for which no system identifier could be generated
    …mponent(catName?catName:'')+'&hostName='+encodeURIComponent(host)+'&urlRef='+e…

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

  • Info Line 1313, Column 6263: entity was defined here
    …codeURIComponent(catName?catName:'')+'&hostName='+encodeURIComponent(host)+'&u…
  • Warning Line 1313, Column 6302: cannot generate system identifier for general entity "urlRef"
    …hostName='+encodeURIComponent(host)+'&urlRef='+encodeURIComponent(ref)+'&brows…

    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 1313, Column 6302: general entity "urlRef" not defined and no default entity
    …hostName='+encodeURIComponent(host)+'&urlRef='+encodeURIComponent(ref)+'&brows…

    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 1313, Column 6308: reference not terminated by REFC delimiter
    …me='+encodeURIComponent(host)+'&urlRef='+encodeURIComponent(ref)+'&browser='+e…

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

  • Error Line 1313, Column 6308: reference to entity "urlRef" for which no system identifier could be generated
    …me='+encodeURIComponent(host)+'&urlRef='+encodeURIComponent(ref)+'&browser='+e…

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

  • Info Line 1313, Column 6301: entity was defined here
    …&hostName='+encodeURIComponent(host)+'&urlRef='+encodeURIComponent(ref)+'&brow…
  • Warning Line 1313, Column 6337: cannot generate system identifier for general entity "browser"
    …+'&urlRef='+encodeURIComponent(ref)+'&browser='+encodeURIComponent(browser)+'&…

    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 1313, Column 6337: general entity "browser" not defined and no default entity
    …+'&urlRef='+encodeURIComponent(ref)+'&browser='+encodeURIComponent(browser)+'&…

    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 1313, Column 6344: reference not terminated by REFC delimiter
    …ef='+encodeURIComponent(ref)+'&browser='+encodeURIComponent(browser)+'&os='+en…

    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 1313, Column 6344: reference to entity "browser" for which no system identifier could be generated
    …ef='+encodeURIComponent(ref)+'&browser='+encodeURIComponent(browser)+'&os='+en…

    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 1313, Column 6336: entity was defined here
    …)+'&urlRef='+encodeURIComponent(ref)+'&browser='+encodeURIComponent(browser)+'…
  • Warning Line 1313, Column 6377: cannot generate system identifier for general entity "os"
    …owser='+encodeURIComponent(browser)+'&os='+encodeURIComponent(os)+'&keyword='+…

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

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

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

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

  • Error Line 1313, Column 6377: general entity "os" not defined and no default entity
    …owser='+encodeURIComponent(browser)+'&os='+encodeURIComponent(os)+'&keyword='+…

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

  • Warning Line 1313, Column 6379: reference not terminated by REFC delimiter
    …ser='+encodeURIComponent(browser)+'&os='+encodeURIComponent(os)+'&keyword='+en…

    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 1313, Column 6379: reference to entity "os" for which no system identifier could be generated
    …ser='+encodeURIComponent(browser)+'&os='+encodeURIComponent(os)+'&keyword='+en…

    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 1313, Column 6376: entity was defined here
    …rowser='+encodeURIComponent(browser)+'&os='+encodeURIComponent(os)+'&keyword='…
  • Warning Line 1313, Column 6407: cannot generate system identifier for general entity "keyword"
    …wser)+'&os='+encodeURIComponent(os)+'&keyword='+encodeURIComponent(keyword)+'&…

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

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

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

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

  • Error Line 1313, Column 6407: general entity "keyword" not defined and no default entity
    …wser)+'&os='+encodeURIComponent(os)+'&keyword='+encodeURIComponent(keyword)+'&…

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

  • Warning Line 1313, Column 6414: reference not terminated by REFC delimiter
    …&os='+encodeURIComponent(os)+'&keyword='+encodeURIComponent(keyword)+'&isWebsi…

    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 1313, Column 6414: reference to entity "keyword" for which no system identifier could be generated
    …&os='+encodeURIComponent(os)+'&keyword='+encodeURIComponent(keyword)+'&isWebsi…

    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 1313, Column 6406: entity was defined here
    …owser)+'&os='+encodeURIComponent(os)+'&keyword='+encodeURIComponent(keyword)+'…
  • Warning Line 1313, Column 6447: cannot generate system identifier for general entity "isWebsiteVisit"
    …yword='+encodeURIComponent(keyword)+'&isWebsiteVisit='+isWebsiteVisit+'&isWebs…

    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 1313, Column 6447: general entity "isWebsiteVisit" not defined and no default entity
    …yword='+encodeURIComponent(keyword)+'&isWebsiteVisit='+isWebsiteVisit+'&isWebs…

    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 1313, Column 6461: reference not terminated by REFC delimiter
    …URIComponent(keyword)+'&isWebsiteVisit='+isWebsiteVisit+'&isWebsiteNewVisitor=…

    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 1313, Column 6461: reference to entity "isWebsiteVisit" for which no system identifier could be generated
    …URIComponent(keyword)+'&isWebsiteVisit='+isWebsiteVisit+'&isWebsiteNewVisitor=…

    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 1313, Column 6446: entity was defined here
    …eyword='+encodeURIComponent(keyword)+'&isWebsiteVisit='+isWebsiteVisit+'&isWeb…
  • Warning Line 1313, Column 6481: cannot generate system identifier for general entity "isWebsiteNewVisitor"
    …)+'&isWebsiteVisit='+isWebsiteVisit+'&isWebsiteNewVisitor='+isWebsiteNewVisito…

    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 1313, Column 6481: general entity "isWebsiteNewVisitor" not defined and no default entity
    …)+'&isWebsiteVisit='+isWebsiteVisit+'&isWebsiteNewVisitor='+isWebsiteNewVisito…

    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 1313, Column 6500: reference not terminated by REFC delimiter
    …'+isWebsiteVisit+'&isWebsiteNewVisitor='+isWebsiteNewVisitor+'&isArticleVisit=…

    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 1313, Column 6500: reference to entity "isWebsiteNewVisitor" for which no system identifier could be generated
    …'+isWebsiteVisit+'&isWebsiteNewVisitor='+isWebsiteNewVisitor+'&isArticleVisit=…

    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 1313, Column 6480: entity was defined here
    …d)+'&isWebsiteVisit='+isWebsiteVisit+'&isWebsiteNewVisitor='+isWebsiteNewVisit…
  • Warning Line 1313, Column 6525: cannot generate system identifier for general entity "isArticleVisit"
    …iteNewVisitor='+isWebsiteNewVisitor+'&isArticleVisit='+isArticleVisit+'&isCatV…

    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 1313, Column 6525: general entity "isArticleVisit" not defined and no default entity
    …iteNewVisitor='+isWebsiteNewVisitor+'&isArticleVisit='+isArticleVisit+'&isCatV…

    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 1313, Column 6539: reference not terminated by REFC delimiter
    …'+isWebsiteNewVisitor+'&isArticleVisit='+isArticleVisit+'&isCatVisit='+isCatVi…

    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 1313, Column 6539: reference to entity "isArticleVisit" for which no system identifier could be generated
    …'+isWebsiteNewVisitor+'&isArticleVisit='+isArticleVisit+'&isCatVisit='+isCatVi…

    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 1313, Column 6524: entity was defined here
    …siteNewVisitor='+isWebsiteNewVisitor+'&isArticleVisit='+isArticleVisit+'&isCat…
  • Warning Line 1313, Column 6559: cannot generate system identifier for general entity "isCatVisit"
    …r+'&isArticleVisit='+isArticleVisit+'&isCatVisit='+isCatVisit+'&website='+enco…

    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 1313, Column 6559: general entity "isCatVisit" not defined and no default entity
    …r+'&isArticleVisit='+isArticleVisit+'&isCatVisit='+isCatVisit+'&website='+enco…

    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 1313, Column 6569: reference not terminated by REFC delimiter
    …cleVisit='+isArticleVisit+'&isCatVisit='+isCatVisit+'&website='+encodeURICompo…

    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 1313, Column 6569: reference to entity "isCatVisit" for which no system identifier could be generated
    …cleVisit='+isArticleVisit+'&isCatVisit='+isCatVisit+'&website='+encodeURICompo…

    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 1313, Column 6558: entity was defined here
    …or+'&isArticleVisit='+isArticleVisit+'&isCatVisit='+isCatVisit+'&website='+enc…
  • Warning Line 1313, Column 6585: cannot generate system identifier for general entity "website"
    …icleVisit+'&isCatVisit='+isCatVisit+'&website='+encodeURIComponent(log_website…

    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 1313, Column 6585: general entity "website" not defined and no default entity
    …icleVisit+'&isCatVisit='+isCatVisit+'&website='+encodeURIComponent(log_website…

    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 1313, Column 6592: reference not terminated by REFC delimiter
    …it+'&isCatVisit='+isCatVisit+'&website='+encodeURIComponent(log_website)+'&res…

    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 1313, Column 6592: reference to entity "website" for which no system identifier could be generated
    …it+'&isCatVisit='+isCatVisit+'&website='+encodeURIComponent(log_website)+'&res…

    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 1313, Column 6584: entity was defined here
    …ticleVisit+'&isCatVisit='+isCatVisit+'&website='+encodeURIComponent(log_websit…
  • Warning Line 1313, Column 6629: cannot generate system identifier for general entity "resolution"
    …e='+encodeURIComponent(log_website)+'&resolution='+encodeURIComponent(resoluti…

    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 1313, Column 6629: general entity "resolution" not defined and no default entity
    …e='+encodeURIComponent(log_website)+'&resolution='+encodeURIComponent(resoluti…

    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 1313, Column 6639: reference not terminated by REFC delimiter
    …URIComponent(log_website)+'&resolution='+encodeURIComponent(resolution);Log_se…

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

  • Error Line 1313, Column 6639: reference to entity "resolution" for which no system identifier could be generated
    …URIComponent(log_website)+'&resolution='+encodeURIComponent(resolution);Log_se…

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

  • Info Line 1313, Column 6628: entity was defined here
    …te='+encodeURIComponent(log_website)+'&resolution='+encodeURIComponent(resolut…
  • Error Line 1315, Column 9: end tag for "tem.length" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 1313, Column 5549: start tag was here
    …okieValue.split(',');var i=0;for(i=0;i<tem.length;i++) {if(tem[i].indexOf(catI…
  • Error Line 1315, Column 9: end tag for "tem.length" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 1313, Column 4739: start tag was here
    …okieValue.split(',');var i=0;for(i=0;i<tem.length;i++) {if(tem[i].indexOf(news…
  • Error Line 1315, Column 9: end tag for "_uOsr.length" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 1313, Column 3409: start tag was here
    …]="search";_uOkw[27]="q";for(var i=0;i<_uOsr.length;i++) if(referrer.toLowerCa…
  • Error Line 1315, Column 9: end tag for "ca.length" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 1313, Column 1764: start tag was here
    …cument.cookie.split(';');for(var i=0;i<ca.length;i++){c=ca[i];while(c.charAt(0…
  • Error Line 1315, Column 9: end tag for "args.length" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 1308, Column 260: start tag was here
    …);var args=qs.split('&');for(var i=0;i<args.length;i++){var pair=args[i].split…

Visitor Analysis

Daily Visitor
  • 9.800 visits