tienphong.vn

Báo Tiền Phong điện tử, Tien Phong Online, tin tức cập nhật liên tục trong ngày ...

Display Widget for this domain on your website. Click Here
This data was last updated from 21-06-2013 07:54:55  (update).

Overview Info

  • Domain Name
    tienphong.vn
  • Favicon
  • Alexa Rank
    #9401
  • Google Page Rank
    PR 7
  • Ip Address
    123.30.174.195
  • Page Size
    221.4 KB
  • Images
    19 GIF, 56 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 32 4 0 0

Website Meta Analysis



  • Title
    Tiền Phong Online - Nhạy bén - Thiết thực - Tin cậy
  • Meta Keyword
    Tin mới, tin moi, tin tức, tin tuc, Việt Nam, Tiền Phong, Tien Phong, Tiền Phong Online, Tien Phong online, báo Tiền Phong, bao Tien Phong, Thời sự, Thoi su, Tin nóng, Tin nong, Pháp luật, Phap luat, vụ án, vu an, điều tra, dieu tra, Thể thao, The thao, Bóng đá, Bong da, Văn hóa, Van hoa, Quốc tế, Quoc te, Thế giới, The gioi, Giới trẻ, Gioi tre, Khoa học, giáo dục, tuyển sinh, du học, Xã hội, Phóng sự, phong su, Hoa hậu, Hoa hau, hoa-hau, Kinh doanh, kinh-doanh, Người đẹp, Nguoi dep, Kinh hoàng, Vụ án, Hồ sơ, Quốc hội, vàng, chứng khoán, đô la, hot girl, 8x, 9x, Tin nhanh, Sành điệu, Trang điểm, ảnh đẹp, anh dep , teen, học trò, đoàn viên, học sinh, sinh viên, doanh nhân, làm ăn, kiếm việc, kiếm tiền, bố cáo doanh nghiệp, quảng cáo, lửa ấm, nam châm, tri thức trẻ, tri thuc tre, bố cáo thành lập doanh nghiệp, thanh lap doanh nghiep
  • Meta Description
    Báo Tiền Phong điện tử, Tien Phong Online, tin tức cập nhật liên tục trong ngày

Technical Analysis



  • Webserver
    Microsoft-IIS/7.0
  • Ip Address
    123.30.174.195
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.0
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • date: Fri, 21 Jun 2013 08:13:33 GMT
  • content-length: 72810
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for tienphong.vn

DNS Analysis


DNS servers
hcm-server1.vnn.vn [203.162.4.1]
vdc-hn01.vnn.vn [203.162.0.11]


DNS Records

Answer records
tienphong.vn SOA
server: vdc-hn01.vnn.vn
email: postmaster@vnn.vn
serial: 2012101901
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
86400s
tienphong.vn NS  vdc-hn01.vnn.vn 86400s
tienphong.vn NS  hcm-server1.vnn.vn 86400s
tienphong.vn A 123.30.174.196 86400s
tienphong.vn A 123.30.174.195 86400s
tienphong.vn MX
preference: 30
exchange: aspmx4.googlemail.com
86400s
tienphong.vn MX
preference: 30
exchange: aspmx5.googlemail.com
86400s
tienphong.vn MX
preference: 10
exchange: aspmx.l.google.com
86400s
tienphong.vn MX
preference: 20
exchange: alt1.aspmx.l.google.com
86400s
tienphong.vn MX
preference: 20
exchange: alt2.aspmx.l.google.com
86400s
tienphong.vn MX
preference: 30
exchange: aspmx2.googlemail.com
86400s
tienphong.vn MX
preference: 30
exchange: aspmx3.googlemail.com
86400s

Authority records

Additional records
vdc-hn01.vnn.vn A 203.162.0.11 300s
hcm-server1.vnn.vn A 203.162.4.1 300s

IP 123.30.174.195 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 120 Errors
  • 48 Warnings
Ratio Text/Html
  • 0.7201660248860895
Message Error
  • Error Line 33, Column 63: required attribute "type" not specified
    ….screen.width > 1280) document.write("<style>.Menu1280{width:1280px;}</style>")

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

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

  • Error Line 33, Column 63: document type does not allow element "style" here
    ….screen.width > 1280) document.write("<style>.Menu1280{width:1280px;}</style>")

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

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

  • Warning Line 36, Column 69: cannot generate system identifier for general entity "locvn"
    …         var url = "/Page/weathergooglerequest.aspx?loc=VMXX0006&locvn=Hà Nội";

    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 36, Column 69: general entity "locvn" not defined and no default entity
    …         var url = "/Page/weathergooglerequest.aspx?loc=VMXX0006&locvn=Hà Nội";

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

  • Warning Line 36, Column 74: reference not terminated by REFC delimiter
    …         var url = "/Page/weathergooglerequest.aspx?loc=VMXX0006&locvn=Hà Nội";

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

  • Error Line 36, Column 74: reference to entity "locvn" for which no system identifier could be generated
    …         var url = "/Page/weathergooglerequest.aspx?loc=VMXX0006&locvn=Hà Nội";

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

  • Info Line 36, Column 68: entity was defined here
    …         var url = "/Page/weathergooglerequest.aspx?loc=VMXX0006&locvn=Hà Nội";
  • Error Line 64, Column 36: an attribute specification must start with a name or name token
                   document.write('<scr' + 'ipt src="' + src + '"></scr' + 'ipt>');

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 64, Column 36: element "scr" undefined
                   document.write('<scr' + 'ipt src="' + src + '"></scr' + 'ipt>');

    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 64, Column 68: delimiter "'" invalid: only S separators and TAGC allowed here
                   document.write('<scr' + 'ipt src="' + src + '"></scr' + 'ipt>');
  • Warning Line 132, Column 323: character "<" is the first character of a delimiter but occurred as data
    …one = new Array("");for (var i = 0; i < lstNone.length; i++) { if (id.toString…

    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 132, Column 747: character "<" is the first character of a delimiter but occurred as data
    …(SelectedTimerId);  for (var i = 0; i < Items.length; i++) { var itemId = docu…

    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 176, Column 21: character "<" is the first character of a delimiter but occurred as data
            if (minutes <= 9) { minutes = "0" + minutes; }

    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 177, Column 21: character "<" is the first character of a delimiter but occurred as data
            if (seconds <= 9) { seconds = "0" + seconds; }

    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 195, Column 2890: end tag for "ul" which is not finished
    …16px;" class="padLeft6 fLeft"><ul></ul></div><div id="mnu_7_ul_lv2" onmouseove…

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

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

  • Error Line 195, Column 5467: end tag for "ul" which is not finished
    …6px;" class="padLeft13 fLeft"><ul></ul></div><div id="mnu_14_ul_lv2" onmouseov…

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

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

  • Error Line 195, Column 5637: end tag for "ul" which is not finished
    …6px;" class="padLeft14 fLeft"><ul></ul></div><div id="mnu_15_ul_lv2" onmouseov…

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

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

  • Error Line 195, Column 5807: end tag for "ul" which is not finished
    …);" style="display: none; height:16px;" class="padLeft15 fLeft"><ul></ul></div>

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

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

  • Warning Line 217, Column 31: character "<" is the first character of a delimiter but occurred as data
                for (var n = 0; n < string.length; n++) {

    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 221, Column 23: character "<" is the first character of a delimiter but occurred as data
                    if (c < 128) {

    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 224, Column 36: character "&" is the first character of a delimiter but occurred as data
                    else if ((c > 127) && (c < 2048)) {

    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 224, Column 37: character "&" is the first character of a delimiter but occurred as data
                    else if ((c > 127) && (c < 2048)) {

    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 224, Column 42: character "<" is the first character of a delimiter but occurred as data
                    else if ((c > 127) && (c < 2048)) {

    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 226, Column 55: character "&" is the first character of a delimiter but occurred as data
                        utftext += String.fromCharCode((c & 63) | 128);

    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 230, Column 62: character "&" is the first character of a delimiter but occurred as data
                        utftext += String.fromCharCode(((c >> 6) & 63) | 128);

    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 231, Column 55: character "&" is the first character of a delimiter but occurred as data
                        utftext += String.fromCharCode((c & 63) | 128);

    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 245, Column 22: character "<" is the first character of a delimiter but occurred as data
                while (i < utftext.length) {

    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 249, Column 23: character "<" is the first character of a delimiter but occurred as data
                    if (c < 128) {

    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 253, Column 36: character "&" is the first character of a delimiter but occurred as data
                    else if ((c > 191) && (c < 224)) {

    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 253, Column 37: character "&" is the first character of a delimiter but occurred as data
                    else if ((c > 191) && (c < 224)) {

    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 253, Column 42: character "<" is the first character of a delimiter but occurred as data
                    else if ((c > 191) && (c < 224)) {

    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 255, Column 55: character "&" is the first character of a delimiter but occurred as data
                        string += String.fromCharCode(((c & 31) << 6) | (c2 & 63));

    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 255, Column 61: character "<" is the first character of a delimiter but occurred as data
                        string += String.fromCharCode(((c & 31) << 6) | (c2 & 63));

    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 255, Column 62: character "<" is the first character of a delimiter but occurred as data
                        string += String.fromCharCode(((c & 31) << 6) | (c2 & 63));

    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 255, Column 73: character "&" is the first character of a delimiter but occurred as data
                        string += String.fromCharCode(((c & 31) << 6) | (c2 & 63));

    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 261, Column 55: character "&" is the first character of a delimiter but occurred as data
    …    string += String.fromCharCode(((c & 15) << 12) | ((c2 & 63) << 6) | (c3 & …

    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 261, Column 61: character "<" is the first character of a delimiter but occurred as data
    …string += String.fromCharCode(((c & 15) << 12) | ((c2 & 63) << 6) | (c3 & 63));

    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 261, Column 62: character "<" is the first character of a delimiter but occurred as data
    …string += String.fromCharCode(((c & 15) << 12) | ((c2 & 63) << 6) | (c3 & 63));

    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 261, Column 75: character "&" is the first character of a delimiter but occurred as data
    …string += String.fromCharCode(((c & 15) << 12) | ((c2 & 63) << 6) | (c3 & 63));

    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 261, Column 81: character "<" is the first character of a delimiter but occurred as data
    …string += String.fromCharCode(((c & 15) << 12) | ((c2 & 63) << 6) | (c3 & 63));

    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 261, Column 82: character "<" is the first character of a delimiter but occurred as data
    …string += String.fromCharCode(((c & 15) << 12) | ((c2 & 63) << 6) | (c3 & 63));

    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 261, Column 93: character "&" is the first character of a delimiter but occurred as data
    …string += String.fromCharCode(((c & 15) << 12) | ((c2 & 63) << 6) | (c3 & 63));

    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 271, Column 37: character "&" is the first character of a delimiter but occurred as data
            var regex = new RegExp("[\\?&]" + key + "=([^&#]*)");

    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 271, Column 54: character "&" is the first character of a delimiter but occurred as data
            var regex = new RegExp("[\\?&]" + key + "=([^&#]*)");

    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 282, Column 35: character "&" is the first character of a delimiter but occurred as data
            if (txtSearch.val() != '' && txtSearch.val() != 'Tìm kiếm ...') {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 282, Column 36: character "&" is the first character of a delimiter but occurred as data
            if (txtSearch.val() != '' && txtSearch.val() != 'Tìm kiếm ...') {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 405, Column 397: required attribute "alt" not specified
    …/a><img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></h4>

    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 429, Column 692: there is no attribute "height"
    …high" name="quality" /> <embed height="90px" width="688px" align="middle" plug…

    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 429, Column 705: there is no attribute "width"
    …uality" /> <embed height="90px" width="688px" align="middle" pluginspage="http…

    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 429, Column 719: there is no attribute "align"
    …bed height="90px" width="688px" align="middle" pluginspage="http://www.macrome…

    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 429, Column 740: there is no attribute "pluginspage"
    …th="688px" align="middle" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 429, Column 791: there is no attribute "type"
    …acromedia.com/go/getflashplayer" type="application/x-shockwave-flash" allowscr…

    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 429, Column 841: there is no attribute "allowscriptaccess"
    …/x-shockwave-flash" allowscriptaccess="always" flashvars="link=http%3A//i1.log…

    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 429, Column 860: there is no attribute "flashvars"
    … allowscriptaccess="always" flashvars="link=http%3A//i1.logging.admicro.vn/_ad…

    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 429, Column 1092: there is no attribute "name"
    …e%20do%26adm_random%3D271644047" name=" helloWorld" wmode="transparent" qualit…

    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 429, Column 1112: there is no attribute "wmode"
    …3D271644047" name=" helloWorld" wmode="transparent" quality="high" src="http:/…

    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 429, Column 1134: there is no attribute "quality"
    …lloWorld" wmode="transparent" quality="high" src="http://upload.tienphong.vn/U…

    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 429, Column 1145: there is no attribute "src"
    …mode="transparent" quality="high" src="http://upload.tienphong.vn/Uploads/Adve…

    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 429, Column 1211: element "embed" undefined
    …d.tienphong.vn/Uploads/Advertisements/HIENPHAP.swf" /></object></li></ul></div>

    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 506, Column 172: required attribute "alt" not specified
    …7px; padding-left:4px;" src="/App_Themes/TPO/images/rssTitle.jpg" /></a></span>

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

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

  • Error Line 515, Column 115: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …' title='Không có vùng cấm xử lý 'chạy' công chức' src="http://www.tienphong.v…

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

  • Error Line 515, Column 116: end tag for "img" omitted, but OMITTAG NO was specified
    … title='Không có vùng cấm xử lý 'chạy' công chức' src="http://www.tienphong.vn…

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

  • Info Line 515, Column 17: start tag was here
                    <img alt='Chạy chức, Công chức, Tham nhũng, Hà Nội, Thành ủy' t…
  • Error Line 585, Column 172: required attribute "alt" not specified
    …7px; padding-left:4px;" src="/App_Themes/TPO/images/rssTitle.jpg" /></a></span>

    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 659, Column 172: required attribute "alt" not specified
    …7px; padding-left:4px;" src="/App_Themes/TPO/images/rssTitle.jpg" /></a></span>

    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 738, Column 172: required attribute "alt" not specified
    …7px; padding-left:4px;" src="/App_Themes/TPO/images/rssTitle.jpg" /></a></span>

    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 747, Column 101: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …n' title='Lối sống của teen Việt 'hỏng' do mạng xã hội?' src="http://www.tienp…

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

  • Error Line 747, Column 102: end tag for "img" omitted, but OMITTAG NO was specified
    …' title='Lối sống của teen Việt 'hỏng' do mạng xã hội?' src="http://www.tienph…

    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 747, Column 17: start tag was here
                    <img alt='Teen việt, đạo đức đi xuống, Đốt tiền' title='Lối sốn…
  • Error Line 812, Column 173: required attribute "alt" not specified
    …7px; padding-left:4px;" src="/App_Themes/TPO/images/rssTitle.jpg" /></a></span>

    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 881, Column 173: required attribute "alt" not specified
    …7px; padding-left:4px;" src="/App_Themes/TPO/images/rssTitle.jpg" /></a></span>

    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 890, Column 78: "hai" is not a member of a group specified for any attribute
    … đá, quen thuộc' title='Đội bóng 'hai tên'' src="http://www.tienphong.vn/Cache…
  • Error Line 890, Column 81: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …, quen thuộc' title='Đội bóng 'hai tên'' src="http://www.tienphong.vn/Cache/95…

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

  • Error Line 890, Column 82: end tag for "img" omitted, but OMITTAG NO was specified
    … quen thuộc' title='Đội bóng 'hai tên'' src="http://www.tienphong.vn/Cache/95/…

    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 890, Column 17: start tag was here
                    <img alt='sự thật, bóng đá, quen thuộc' title='Đội bóng 'hai tê…
  • Error Line 934, Column 172: required attribute "alt" not specified
    …7px; padding-left:4px;" src="/App_Themes/TPO/images/rssTitle.jpg" /></a></span>

    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 943, Column 191: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …i thể thao Thùy Linh' title='Nhặt 'sạn' đêm đầu tiên Cặp đôi hoàn hảo' src="ht…

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

  • Error Line 943, Column 192: end tag for "img" omitted, but OMITTAG NO was specified
    … thể thao Thùy Linh' title='Nhặt 'sạn' đêm đầu tiên Cặp đôi hoàn hảo' src="htt…

    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 943, Column 17: start tag was here
                    <img alt='Cặp Đôi Hoàn Hảo, Dương Triệu Vũ, Thanh Thúy, Phan Đi…
  • Error Line 1003, Column 173: required attribute "alt" not specified
    …7px; padding-left:4px;" src="/App_Themes/TPO/images/rssTitle.jpg" /></a></span>

    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 1069, Column 354: required attribute "alt" not specified
    …a><img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></div>

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

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

  • Error Line 1131, Column 174: required attribute "alt" not specified
    …7px; padding-left:4px;" src="/App_Themes/TPO/images/rssTitle.jpg" /></a></span>

    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 1140, Column 117: "chuyện" is not a member of a group specified for any attribute
    …le='Xóa tan những ngộ nhận về 'chuyện y'' src="http://www.tienphong.vn/Cache/…
  • Error Line 1140, Column 119: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …='Xóa tan những ngộ nhận về 'chuyện ấy'' src="http://www.tienphong.vn/Cache/81…

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

  • Error Line 1140, Column 120: end tag for "img" omitted, but OMITTAG NO was specified
    …'Xóa tan những ngộ nhận về 'chuyện ấy'' src="http://www.tienphong.vn/Cache/819…

    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 1140, Column 17: start tag was here
                    <img alt='rụng trứng, tinh trùng, tình trường, tránh thai' titl…
  • Error Line 1210, Column 173: required attribute "alt" not specified
    …7px; padding-left:4px;" src="/App_Themes/TPO/images/rssTitle.jpg" /></a></span>

    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 1219, Column 88: "đốt" is not a member of a group specified for any attribute
    …g nghệ, thế giới' title='Sau thú 'đốt tiền’ của trùm công nghệ' src="http://ww…
  • Error Line 1219, Column 92: "tiền" is not a member of a group specified for any attribute
    …hệ, thế giới' title='Sau thú 'đốt tiền của trùm công nghệ' src="http://www.ti…
  • Error Line 1219, Column 98: "của" is not a member of a group specified for any attribute
    …ế giới' title='Sau thú 'đốt tiền’ của trùm công nghệ' src="http://www.tienphon…
  • Error Line 1219, Column 103: "trùm" is not a member of a group specified for any attribute
    …i' title='Sau thú 'đốt tiền’ của trùm công nghệ' src="http://www.tienphong.vn/…
  • Error Line 1219, Column 108: "công" is not a member of a group specified for any attribute
    …tle='Sau thú 'đốt tiền’ của trùm công nghệ' src="http://www.tienphong.vn/Cache…
  • Error Line 1219, Column 112: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …'Sau thú 'đốt tiền’ của trùm công nghệ' src="http://www.tienphong.vn/Cache/196…

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

  • Error Line 1219, Column 113: end tag for "img" omitted, but OMITTAG NO was specified
    …Sau thú 'đốt tiền’ của trùm công nghệ' src="http://www.tienphong.vn/Cache/196/…

    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 1219, Column 17: start tag was here
                    <img alt='đốt tiền, ông trùm, công nghệ, thế giới' title='Sau t…
  • Error Line 1263, Column 174: required attribute "alt" not specified
    …7px; padding-left:4px;" src="/App_Themes/TPO/images/rssTitle.jpg" /></a></span>

    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 1316, Column 173: required attribute "alt" not specified
    …7px; padding-left:4px;" src="/App_Themes/TPO/images/rssTitle.jpg" /></a></span>

    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 1338, Column 128: required attribute "alt" not specified
    …a> <img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></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 1369, Column 174: required attribute "alt" not specified
    …7px; padding-left:4px;" src="/App_Themes/TPO/images/rssTitle.jpg" /></a></span>

    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 1378, Column 87: "siêu" is not a member of a group specified for any attribute
    … ngầm, Quân sự' title='Kế hoạch 'siêu tàu ngầm' của Mỹ' src="http://www.tienph…
  • Error Line 1378, Column 91: "tàu" is not a member of a group specified for any attribute
    …m, Quân sự' title='Kế hoạch 'siêu tàu ngầm' của Mỹ' src="http://www.tienphong.…
  • Error Line 1378, Column 95: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …uân sự' title='Kế hoạch 'siêu tàu ngầm' của Mỹ' src="http://www.tienphong.vn/C…

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

  • Error Line 1378, Column 96: end tag for "img" omitted, but OMITTAG NO was specified
    …ân sự' title='Kế hoạch 'siêu tàu ngầm' của Mỹ' src="http://www.tienphong.vn/Ca…

    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 1378, Column 17: start tag was here
                    <img alt='Tàu ngầm, Mỹ, Siêu tàu ngầm, Quân sự' title='Kế hoạch…
  • Error Line 1394, Column 149: required attribute "alt" not specified
    …a> <img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></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 1397, Column 149: required attribute "alt" not specified
    …a> <img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></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 1423, Column 61: there is no attribute "controlbar"
    …ication/x-shockwave-flash" controlbar='false' allowfullscreen="true"  quality=…

    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 1423, Column 85: there is no attribute "allowfullscreen"
    …on/x-shockwave-flash" controlbar='false' allowfullscreen="true"  quality="high"

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

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

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

  • Warning Line 1425, Column 123: reference not terminated by REFC delimiter
    …fd9c329eed98c3c59f0b330266d8.FLV&image=http://www.tienphong.vn/Cache/351/27835…

    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 1425, Column 173: element "embed" undefined
    …98c3c59f0b330266d8.FLV&image=http://www.tienphong.vn/Cache/351/278351_255.jpg">

    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 1449, Column 182: end tag for "img" omitted, but OMITTAG NO was specified
    …tại, Chủ nhật đỏ" class="imgKm imgcontent" src="/Cache/962/278962_164.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 1449, Column 29: start tag was here
                                <img title="Á hậu, ca sỹ hội tụ tại Chủ nhật Đỏ" al…
  • Error Line 1452, Column 183: end tag for "img" omitted, but OMITTAG NO was specified
    …g long, quái thú" class="imgKm imgcontent" src="/Cache/315/278315_164.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 1452, Column 29: start tag was here
                                <img title="‘Khủng long 6 sừng’ quái nhất thế giới"…
  • Error Line 1455, Column 214: end tag for "img" omitted, but OMITTAG NO was specified
    …n, Lạnh, Giá rét" class="imgKm imgcontent" src="/Cache/212/276212_164.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 1455, Column 29: start tag was here
                                <img title="Những đôi chân trẻ vùng cao nứt nẻ giữa…
  • Warning Line 1500, Column 70: reference not terminated by REFC delimiter
            var url = "/Page/weathergooglerequest.aspx?loc=VMXX0006&locvn=Hà Nội";

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

  • Error Line 1500, Column 70: reference to entity "locvn" for which no system identifier could be generated
            var url = "/Page/weathergooglerequest.aspx?loc=VMXX0006&locvn=Hà Nội";

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

  • Info Line 36, Column 68: entity was defined here
    …         var url = "/Page/weathergooglerequest.aspx?loc=VMXX0006&locvn=Hà Nội";
  • Error Line 1512, Column 135: document type does not allow element "div" here
    …rtical-align:top; padding-top:40px;  text-align:center;" id="loading"></div>');

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

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

  • Warning Line 1521, Column 25: character "&" is the first character of a delimiter but occurred as data
            if (locID != "" && locID.options[locID.options.selectedIndex].value != …

    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 1521, Column 26: character "&" is the first character of a delimiter but occurred as data
            if (locID != "" && locID.options[locID.options.selectedIndex].value != …

    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 1524, Column 75: reference not terminated by REFC delimiter
    …        var url = '/Page/weathergooglerequest.aspx?loc=' + loc+'&locvn='+locvn;

    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 1524, Column 75: reference to entity "locvn" for which no system identifier could be generated
    …        var url = '/Page/weathergooglerequest.aspx?loc=' + loc+'&locvn='+locvn;

    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 36, Column 68: entity was defined here
    …         var url = "/Page/weathergooglerequest.aspx?loc=VMXX0006&locvn=Hà Nội";
  • Error Line 1614, Column 34: document type does not allow element "div" here; assuming missing "li" start-tag
                <div class="clearfix">
  • Error Line 1616, Column 13: 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 1614, Column 13: start tag was here
                <div class="clearfix">
  • Error Line 1645, Column 30: document type does not allow element "div" here; assuming missing "li" start-tag
            <div class="clearfix">
  • Error Line 1647, Column 13: 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 1645, Column 9: start tag was here
            <div class="clearfix">
  • Error Line 1665, Column 365: required attribute "alt" not specified
    …Diệm<img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></a>

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

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

  • Error Line 1672, Column 357: required attribute "alt" not specified
    …tuổi<img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></a>

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

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

  • Error Line 1677, Column 34: document type does not allow element "div" here; assuming missing "li" start-tag
                <div class="clearfix">
  • Error Line 1679, Column 13: 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 1677, Column 13: start tag was here
                <div class="clearfix">
  • Error Line 1683, Column 124: value of attribute "frameborder" cannot be "no"; must be one of "1", "0"
    …c/tienphong" height="370" width="180" frameborder="no" scrolling="no"></iframe>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 1693, Column 25: ID "paginate-slider4" already defined
                    <ul id="paginate-slider4" class="listItemArrKMDV">

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

  • Info Line 1459, Column 25: ID "paginate-slider4" first defined here
                    <ul id="paginate-slider4" class="listItemArr">
  • Error Line 1734, Column 340: required attribute "alt" not specified
    …Maya<img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></a>

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

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

  • Error Line 1739, Column 34: document type does not allow element "div" here; assuming missing "li" start-tag
                <div class="clearfix">
  • Error Line 1741, Column 13: 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 1739, Column 13: start tag was here
                <div class="clearfix">
  • Error Line 1759, Column 379: required attribute "alt" not specified
    … cãi<img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></a>

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

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

  • Error Line 1771, Column 34: document type does not allow element "div" here; assuming missing "li" start-tag
                <div class="clearfix">
  • Error Line 1773, Column 13: 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 1771, Column 13: start tag was here
                <div class="clearfix">
  • Error Line 1791, Column 345: required attribute "alt" not specified
    … cảm<img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></a>

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

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

  • Error Line 1798, Column 359: required attribute "alt" not specified
    …trần<img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></a>

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

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

  • Error Line 1803, Column 34: document type does not allow element "div" here; assuming missing "li" start-tag
                <div class="clearfix">
  • Error Line 1805, Column 13: 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 1803, Column 13: start tag was here
                <div class="clearfix">
  • Error Line 1846, Column 80: end tag for "img" omitted, but OMITTAG NO was specified
                    &nbsp;&nbsp;<img alt="" src="/App_Themes/TPO/images/arrow.gif">

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

  • Info Line 1846, Column 29: start tag was here
                    &nbsp;&nbsp;<img alt="" src="/App_Themes/TPO/images/arrow.gif">
  • Error Line 1861, Column 138: required attribute "alt" not specified
    …/a><img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></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 1864, Column 127: required attribute "alt" not specified
    …/a><img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></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 1966, Column 341: required attribute "alt" not specified
    …rong<img class="iconVdeo"  src="/App_Themes/Default/icon/photo_icon.gif" /></a>

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

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

  • Error Line 2025, Column 30: document type does not allow element "div" here; assuming missing "li" start-tag
            <div class="clearfix">
  • Error Line 2027, Column 13: 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 2025, Column 9: start tag was here
            <div class="clearfix">
  • Error Line 2090, Column 30: document type does not allow element "div" here; assuming missing "li" start-tag
            <div class="clearfix">
  • Error Line 2092, Column 13: 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 2090, Column 9: start tag was here
            <div class="clearfix">
  • Warning Line 2100, Column 27: character "<" is the first character of a delimiter but occurred as data
            for (var i = 0; i < arrTabs.length; i++) {

    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 2109, Column 106: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …portant; margin-bottom:0px!important;"><a href="" title="an_phan_bao_tien_phon…

    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 2109, Column 290: required attribute "alt" not specified
    …nphong.vn/Uploads/Advertisements/an_pham_bao_tien_phong1.jpg" /></a></li></div>

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

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

  • Error Line 2158, Column 106: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …portant; margin-bottom:0px!important;"><a href="" title="antoangiaothong300_25…

    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 2158, Column 284: required attribute "alt" not specified
    …ad.tienphong.vn/Uploads/Advertisements/transerco17_16_44.gif" /></a></li></div>

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

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

  • Error Line 2194, Column 1188: element "embed" undefined
    …g.vn/Uploads/Advertisements/tan_hoang_minh_300_160.swf" /></object></div></div>

    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 2228, Column 106: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …portant; margin-bottom:0px!important;"><a href="http://hssv.tienphong.vn" titl…

    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 2228, Column 288: required attribute "alt" not specified
    …="http://upload.tienphong.vn/Uploads/Advertisements/hssv.jpg" /></a></li></div>

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

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

  • Error Line 2263, Column 106: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …portant; margin-bottom:0px!important;"><a href="http://www.tienphong.vn/hanh-t…

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

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

  • Error Line 2263, Column 340: required attribute "alt" not specified
    …ienphong.vn/Uploads/Advertisements/hanh-trang-nguoi-linh.gif" /></a></li></div>

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

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

  • Error Line 2299, Column 1240: element "embed" undefined
    …s/tu_van_truc_tiep14_51_4115_19_0809_57_3710_42_11.swf" /></object></div></div>

    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 2334, Column 1160: element "embed" undefined
    …pload.tienphong.vn/Uploads/Advertisements/Svic 250.swf" /></object></div></div>

    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 2440, Column 34: document type does not allow element "div" here; assuming missing "li" start-tag
                <div class="clearfix">
  • Error Line 2442, Column 13: 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 2440, Column 13: start tag was here
                <div class="clearfix">
  • Warning Line 2475, Column 27: character "<" is the first character of a delimiter but occurred as data
                for (i = 0; i < document.forms[0].elements.length; i++) {

    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 2491, Column 35: character "<" is the first character of a delimiter but occurred as data
                    for (var i = 0; i < listCheckBox.length; i++) {

    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 2528, Column 130: cannot generate system identifier for general entity "SurveyDetailID"
    …ww.tienphong.vn/Page/SurveyResult.aspx?SurveyID=51&SurveyDetailID=',850,300);">

    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 2528, Column 130: general entity "SurveyDetailID" not defined and no default entity
    …ww.tienphong.vn/Page/SurveyResult.aspx?SurveyID=51&SurveyDetailID=',850,300);">

    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 2528, Column 144: reference not terminated by REFC delimiter
    …ww.tienphong.vn/Page/SurveyResult.aspx?SurveyID=51&SurveyDetailID=',850,300);">

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

  • Warning Line 2528, Column 144: reference to external entity in attribute value
    …ww.tienphong.vn/Page/SurveyResult.aspx?SurveyID=51&SurveyDetailID=',850,300);">

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

  • Error Line 2528, Column 144: reference to entity "SurveyDetailID" for which no system identifier could be generated
    …ww.tienphong.vn/Page/SurveyResult.aspx?SurveyID=51&SurveyDetailID=',850,300);">

    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 2528, Column 129: entity was defined here
    …ww.tienphong.vn/Page/SurveyResult.aspx?SurveyID=51&SurveyDetailID=',850,300);">
  • Error Line 2548, Column 47: character """ is not allowed in the value of attribute "name"
    …    var embeddedCode = "<iframe name='" + _name + "' id='" + _id + "' border='…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2548, Column 48: value of attribute "name" must be a single token
    …   var embeddedCode = "<iframe name='" + _name + "' id='" + _id + "' border='0…

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

  • Error Line 2548, Column 49: character "+" is not allowed in the value of attribute "name"
    …  var embeddedCode = "<iframe name='" + _name + "' id='" + _id + "' border='0'…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2548, Column 57: character "+" is not allowed in the value of attribute "name"
    …beddedCode = "<iframe name='" + _name + "' id='" + _id + "' border='0' framebo…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2548, Column 59: character """ is not allowed in the value of attribute "name"
    …ddedCode = "<iframe name='" + _name + "' id='" + _id + "' border='0' framebord…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2548, Column 66: character """ is not allowed in the value of attribute "id"
    …e = "<iframe name='" + _name + "' id='" + _id + "' border='0' frameborder='0' …

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2548, Column 67: value of attribute "id" must be a single token
    … = "<iframe name='" + _name + "' id='" + _id + "' border='0' frameborder='0'  …

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

  • Error Line 2548, Column 68: character "+" is not allowed in the value of attribute "id"
    …= "<iframe name='" + _name + "' id='" + _id + "' border='0' frameborder='0'  m…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2548, Column 74: character "+" is not allowed in the value of attribute "id"
    …rame name='" + _name + "' id='" + _id + "' border='0' frameborder='0'  marginw…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2548, Column 76: character """ is not allowed in the value of attribute "id"
    …me name='" + _name + "' id='" + _id + "' border='0' frameborder='0'  marginwid…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2548, Column 86: there is no attribute "border"
    … + _name + "' id='" + _id + "' border='0' frameborder='0'  marginwidth='0' mar…

    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 2548, Column 155: an attribute specification must start with a name or name token
    … border='0' frameborder='0'  marginwidth='0' marginheight='0' scrolling='no' ";

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 2548, Column 155: document type does not allow element "iframe" here
    … border='0' frameborder='0'  marginwidth='0' marginheight='0' scrolling='no' ";

    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 2576, Column 73: required attribute "alt" not specified
    …                     <img src="/App_Themes/TPO/images/homeFter.jpg" /></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 2631, Column 42: invalid comment declaration: found name character outside comment but inside comment declaration
        <!--- Popup Ads by Ambient Digital --->
  • Info Line 2631, Column 5: comment declaration started here
        <!--- Popup Ads by Ambient Digital --->
  • Error Line 2637, Column 194: required attribute "alt" not specified
    …ery.adnetwork.vn/247/noscript/zid_1345621435/wid_1280901653/" /></a></noscript>

    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 2638, Column 38: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- Popup Ads by Ambient Digital --->
  • Info Line 2638, Column 1: comment declaration started here
    <!--- Popup Ads by Ambient Digital --->
  • Error Line 2642, Column 31: document type does not allow element "script" here
    <script type="text/javascript">document.write(unescape("%3Cscript src=%27http:/…

    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 2643, Column 75: document type does not allow element "a" here
    …om" target="_blank" title="counter hit make" ><script  type="text/javascript" >

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

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

  • Error Line 2647, Column 10: document type does not allow element "noscript" here
    <noscript><a href="http://www.histats.com" target="_blank"><img  src="http://ss…

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

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

  • Warning Line 2647, Column 112: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?1397538&101" alt="counter hit make" border="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 2647, Column 155: end tag for "img" omitted, but OMITTAG NO was specified
    …istats.com/0.gif?1397538&101" alt="counter hit make" border="0"></a></noscript>

    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 2647, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img  src="http://sstatic1.histats.com/0…
  • Error Line 2652, Column 37: document type does not allow element "div" here
    <div id='div-gpt-ad-1350382827291-0'>

    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).

Visitor Analysis

Daily Visitor
  • 16.683 visits
Daily Visitor

In Page Analysis