bdtoday.net

bdtoday.net has Alexa Rank 16.926 and Google Page Rank is 3

Display Widget for this domain on your website. Click Here
This data was last updated from 11-08-2013 11:17:26  (update).

Overview Info

  • Domain Name
    bdtoday.net
  • Favicon
  • Alexa Rank
    #16926
  • Google Page Rank
    PR 3
  • Ip Address
    46.32.251.200
  • Page Size
    177.2 KB
  • Images
    151 GIF, 105 JPG, 17 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 16 37 15 0 0

Website Meta Analysis



  • Title
    বিডিটুডে: একটি পূর্ণাঙ্গ অনলাইন ম্যাগাজিন
  • Meta Keyword
    bdtoday, Bangla News, Bangladesh News, Bangla online news, Latest News
  • Meta Description

Technical Analysis



  • Webserver
    Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • Ip Address
    46.32.251.200
  • Domain Age
    1 Years, 5 Months, 2 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 11 Aug 2013 11:17:17 GMT
  • server: Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • x-powered-by: PHP/5.2.9
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
=-=-=-=

Registrar: FastDomain Inc.
Provider Name....: BlueHost.Com
Provider Whois...: whois.bluehost.com
Provider Homepage: http://www.bluehost.com/

Domain Name: BDTODAY.NET

Created on..............: 2012-02-16 07:39:28 GMT
Expires on..............: 2013-02-16 07:39:28 GMT
Last modified on........: 2012-07-21 09:18:06 GMT

Registrant Info: (FAST-18446916)

Domain Privacy Service
1958 South 950 East
Provo, Utah -
United States
Phone: +1.8017659400
Fax..:
Email: email
Last modified: 2012-06-11 20:32:02 GMT

Administrative Info: (FAST-18446916)

Domain Privacy Service
1958 South 950 East
Provo, Utah -
United States
Phone: +1.8017659400
Fax..:
Email: email
Last modified: 2012-06-11 20:32:02 GMT

Technical Info: (FAST-18446916)

Domain Privacy Service
1958 South 950 East
Provo, Utah -
United States
Phone: +1.8017659400
Fax..:
Email: email
Last modified: 2012-06-11 20:32:02 GMT

Status: Locked

Domain servers in listed order:

NS1.BLUEHOST.COM
NS2.BLUEHOST.COM
=-=-=-=

Now UNLIMITED Storage and UNLIMITED Bandwidth and Host UNLIMITED Domains on one account for ONLY $6.95 per month.
You also get a *FREE* DOMAIN REGISTRATION for one year when you host with http://www.bluehost.com/

DNS Analysis


DNS servers
ns2.mainnameserver.com [79.170.43.3]
ns1.mainnameserver.com [79.170.40.2]


DNS Records

Answer records
bdtoday.net A 46.32.251.200 10800s
bdtoday.net NS  ns1.mainnameserver.com 10800s
bdtoday.net NS  ns2.mainnameserver.com 10800s
bdtoday.net MX
preference: 10
exchange: mail.bdtoday.net
10800s
bdtoday.net SOA
server: ns1.mainnameserver.com
email: hostmaster@mainnameserver.com
serial: 2013013079
refresh: 86400
retry: 604800
expire: 2419200
minimum ttl: 10800
10800s

Authority records

Additional records
mail.bdtoday.net A 46.32.251.200 10800s
ns1.mainnameserver.com A 79.170.40.2 10800s
ns2.mainnameserver.com A 79.170.43.3 10800s

IP 46.32.251.200 Analysis

  • Country Code
    GB
  • Country Code3
    GBR
  • Country Name
    United Kingdom
  • City
    EU
  • Continent Code
    54° North
  • Latitude
    2.
  • Longitude
  • No whois ip data for 46.32.251.200

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 173 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.688377118036799
Message Error
  • Error Line 3, Column 15: there is no attribute "prefix"
    <head  prefix="og: http://ogp.me/ns# fb: http://ogp.me/ns/fb#    article: 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 5, Column 18: there is no attribute "property"
    	 <meta property="og:type"                 content="Magazine"/> 

    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 17, Column 67: character ";" not allowed in attribute specification list
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8"; />
  • Error Line 17, Column 68: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8"; />

    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 17, Column 1: start tag was here
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8"; />
  • Error Line 17, Column 69: character data is not allowed here
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8"; />

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 30, Column 70: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="stylesheet" href="http://www.bdtoday.net/css/csspoll.css">

    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 30, Column 1: start tag was here
    <link rel="stylesheet" href="http://www.bdtoday.net/css/csspoll.css">
  • Error Line 40, Column 87: end tag for "link" omitted, but OMITTAG NO was specified
    …el="stylesheet" type="text/css" href="http://www.bdtoday.net/css/module-t.css">

    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 40, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="http://www.bdtoday.net/css/module-…
  • Error Line 183, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

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

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

  • Error Line 333, Column 32: there is no attribute "src"
                        <embed src="http://www.bdtoday.net/flash/todayblog.swf" qua…

    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 333, Column 85: there is no attribute "quality"
    …oday.net/flash/todayblog.swf" quality="high" pluginspage="http://www.macromedi…

    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 333, Column 104: there is no attribute "pluginspage"
    …yblog.swf" quality="high" 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 333, Column 155: there is no attribute "type"
    …acromedia.com/go/getflashplayer" type="application/x-shockwave-flash" width="2…

    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 333, Column 193: there is no attribute "width"
    …shplayer" type="application/x-shockwave-flash" width="250" height="86"></embed>

    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 333, Column 206: there is no attribute "height"
    …shplayer" type="application/x-shockwave-flash" width="250" height="86"></embed>

    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 333, Column 210: element "embed" undefined
    …shplayer" type="application/x-shockwave-flash" width="250" height="86"></embed>

    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 365, Column 81: there is no attribute "onMouseOver"
    …px;" id="anActiveParent" class="d_1_0_ac" onMouseOver="changeSubMenuDiv(0,0);">

    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 391, Column 37: ID "aPassive" already defined
    					<div style="width: 105px;" id="aPassive" class="d_1_0" onMouseOver="change…

    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 380, Column 36: ID "aPassive" first defined here
    					<div style="width: 53px;" id="aPassive" class="d_1_0" onMouseOver="changeS…
  • Error Line 402, Column 36: ID "aPassive" already defined
    					<div style="width: 95px;" id="aPassive" class="d_1_0" onMouseOver="changeS…

    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 380, Column 36: ID "aPassive" first defined here
    					<div style="width: 53px;" id="aPassive" class="d_1_0" onMouseOver="changeS…
  • Error Line 424, Column 36: ID "aPassive" already defined
    					<div style="width: 72px;" id="aPassive" class="d_1_0" onMouseOver="changeS…

    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 380, Column 36: ID "aPassive" first defined here
    					<div style="width: 53px;" id="aPassive" class="d_1_0" onMouseOver="changeS…
  • Error Line 436, Column 36: ID "aPassive" already defined
    					<div style="width: 35px;" id="aPassive" class="d_1_0" onMouseOver="changeS…

    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 380, Column 36: ID "aPassive" first defined here
    					<div style="width: 53px;" id="aPassive" class="d_1_0" onMouseOver="changeS…
  • Error Line 449, Column 36: ID "aPassive" already defined
    					<div style="width: 72px;" id="aPassive" class="d_1_0" onMouseOver="changeS…

    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 380, Column 36: ID "aPassive" first defined here
    					<div style="width: 53px;" id="aPassive" class="d_1_0" onMouseOver="changeS…
  • Error Line 461, Column 36: ID "aPassive" already defined
    					<div style="width: 55px;" id="aPassive" class="d_1_0" onMouseOver="changeS…

    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 380, Column 36: ID "aPassive" first defined here
    					<div style="width: 53px;" id="aPassive" class="d_1_0" onMouseOver="changeS…
  • Error Line 472, Column 36: ID "aPassive" already defined
    					<div style="width: 60px;" id="aPassive" class="d_1_0" onMouseOver="changeS…

    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 380, Column 36: ID "aPassive" first defined here
    					<div style="width: 53px;" id="aPassive" class="d_1_0" onMouseOver="changeS…
  • Error Line 487, Column 36: ID "aPassive" already defined
    					<div style="width: 58px;" id="aPassive" class="d_1_0" onMouseOver="changeS…

    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 380, Column 36: ID "aPassive" first defined here
    					<div style="width: 53px;" id="aPassive" class="d_1_0" onMouseOver="changeS…
  • Error Line 499, Column 36: ID "aPassive" already defined
    					<div style="width: 82px;" id="aPassive" class="d_1_0" onMouseOver="changeS…

    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 380, Column 36: ID "aPassive" first defined here
    					<div style="width: 53px;" id="aPassive" class="d_1_0" onMouseOver="changeS…
  • Error Line 510, Column 36: ID "aPassive" already defined
    					<div style="width: 81px;" id="aPassive" class="d_1_0" onMouseOver="changeS…

    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 380, Column 36: ID "aPassive" first defined here
    					<div style="width: 53px;" id="aPassive" class="d_1_0" onMouseOver="changeS…
  • Error Line 522, Column 37: ID "aPassive" already defined
    					<div style="width: 100px;" id="aPassive" class="d_1_0" onMouseOver="change…

    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 380, Column 36: ID "aPassive" first defined here
    					<div style="width: 53px;" id="aPassive" class="d_1_0" onMouseOver="changeS…
  • Error Line 542, Column 73: end tag for "input" omitted, but OMITTAG NO was specified
    	<input type="hidden" id="subMenuDivOut" value="0" name="subMenuDivOut">

    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 542, Column 2: start tag was here
    	<input type="hidden" id="subMenuDivOut" value="0" name="subMenuDivOut">
  • Error Line 1009, Column 69: "onmouseover" is not a member of a group specified for any attribute
    …itle" colspan="2" valign="top" onmouseover style="width: 424px;height: 50px; ">
  • Error Line 1014, Column 155: there is no attribute "height"
    …ewsTitle0" style="display: block;" cellpadding="0" cellspacing="0" height="55">

    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 1072, Column 202: required attribute "alt" not specified
    …/records/news/201302/12457_1.jpg" border="0" width="433" height="226"></a></td>

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

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

  • Error Line 1072, Column 206: end tag for "img" omitted, but OMITTAG NO was specified
    …/records/news/201302/12457_1.jpg" border="0" width="433" height="226"></a></td>

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

  • Info Line 1072, Column 101: start tag was here
    …il/200/12457" class="georgia_head_30"><img src="http://www.bdtoday.net/records…
  • Error Line 1079, Column 89: required attribute "alt" not specified
    … style="width: 7px;"><img src="images/81006c00.jpg" width="7" height="26"></td>

    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 1079, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
    … style="width: 7px;"><img src="images/81006c00.jpg" width="7" height="26"></td>

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

  • Info Line 1079, Column 37: start tag was here
    		          <td style="width: 7px;"><img src="images/81006c00.jpg" width="7" he…
  • Error Line 1096, Column 202: required attribute "alt" not specified
    …/records/news/201302/12456_1.jpg" border="0" width="433" height="226"></a></td>

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

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

  • Error Line 1096, Column 206: end tag for "img" omitted, but OMITTAG NO was specified
    …/records/news/201302/12456_1.jpg" border="0" width="433" height="226"></a></td>

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

  • Info Line 1096, Column 101: start tag was here
    …il/200/12456" class="georgia_head_30"><img src="http://www.bdtoday.net/records…
  • Error Line 1103, Column 89: required attribute "alt" not specified
    … style="width: 7px;"><img src="images/81006c00.jpg" width="7" height="26"></td>

    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 1103, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
    … style="width: 7px;"><img src="images/81006c00.jpg" width="7" height="26"></td>

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

  • Info Line 1103, Column 37: start tag was here
    		          <td style="width: 7px;"><img src="images/81006c00.jpg" width="7" he…
  • Error Line 1120, Column 202: required attribute "alt" not specified
    …/records/news/201302/12446_1.jpg" border="0" width="433" height="226"></a></td>

    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 1120, Column 206: end tag for "img" omitted, but OMITTAG NO was specified
    …/records/news/201302/12446_1.jpg" border="0" width="433" height="226"></a></td>

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

  • Info Line 1120, Column 101: start tag was here
    …il/200/12446" class="georgia_head_30"><img src="http://www.bdtoday.net/records…
  • Error Line 1127, Column 89: required attribute "alt" not specified
    … style="width: 7px;"><img src="images/81006c00.jpg" width="7" height="26"></td>

    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 1127, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
    … style="width: 7px;"><img src="images/81006c00.jpg" width="7" height="26"></td>

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

  • Info Line 1127, Column 37: start tag was here
    		          <td style="width: 7px;"><img src="images/81006c00.jpg" width="7" he…
  • Error Line 1144, Column 202: required attribute "alt" not specified
    …/records/news/201302/12445_1.jpg" border="0" width="433" height="226"></a></td>

    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 1144, Column 206: end tag for "img" omitted, but OMITTAG NO was specified
    …/records/news/201302/12445_1.jpg" border="0" width="433" height="226"></a></td>

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

  • Info Line 1144, Column 101: start tag was here
    …il/200/12445" class="georgia_head_30"><img src="http://www.bdtoday.net/records…
  • Error Line 1151, Column 89: required attribute "alt" not specified
    … style="width: 7px;"><img src="images/81006c00.jpg" width="7" height="26"></td>

    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 1151, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
    … style="width: 7px;"><img src="images/81006c00.jpg" width="7" height="26"></td>

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

  • Info Line 1151, Column 37: start tag was here
    		          <td style="width: 7px;"><img src="images/81006c00.jpg" width="7" he…
  • Error Line 1168, Column 202: required attribute "alt" not specified
    …/records/news/201302/12444_1.jpg" border="0" width="433" height="226"></a></td>

    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 1168, Column 206: end tag for "img" omitted, but OMITTAG NO was specified
    …/records/news/201302/12444_1.jpg" border="0" width="433" height="226"></a></td>

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

  • Info Line 1168, Column 101: start tag was here
    …il/200/12444" class="georgia_head_30"><img src="http://www.bdtoday.net/records…
  • Error Line 1175, Column 89: required attribute "alt" not specified
    … style="width: 7px;"><img src="images/81006c00.jpg" width="7" height="26"></td>

    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 1175, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
    … style="width: 7px;"><img src="images/81006c00.jpg" width="7" height="26"></td>

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

  • Info Line 1175, Column 37: start tag was here
    		          <td style="width: 7px;"><img src="images/81006c00.jpg" width="7" he…
  • Error Line 1216, Column 274: required attribute "alt" not specified
    …/records/news/201302/12457_2.jpg" height="36" width="123" border="0"></a></div>

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

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

  • Error Line 1216, Column 278: end tag for "img" omitted, but OMITTAG NO was specified
    …/records/news/201302/12457_2.jpg" height="36" width="123" border="0"></a></div>

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

  • Info Line 1216, Column 101: start tag was here
    …oday.net/newsdetail/detail/200/12457"><img id="startFrom_0" onmouseover="showM…
  • Error Line 1229, Column 274: required attribute "alt" not specified
    …/records/news/201302/12456_2.jpg" height="36" width="123" border="0"></a></div>

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

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

  • Error Line 1229, Column 278: end tag for "img" omitted, but OMITTAG NO was specified
    …/records/news/201302/12456_2.jpg" height="36" width="123" border="0"></a></div>

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

  • Info Line 1229, Column 101: start tag was here
    …oday.net/newsdetail/detail/200/12456"><img id="startFrom_1" onmouseover="showM…
  • Error Line 1242, Column 274: required attribute "alt" not specified
    …/records/news/201302/12446_2.jpg" height="36" width="123" border="0"></a></div>

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

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

  • Error Line 1242, Column 278: end tag for "img" omitted, but OMITTAG NO was specified
    …/records/news/201302/12446_2.jpg" height="36" width="123" border="0"></a></div>

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

  • Info Line 1242, Column 101: start tag was here
    …oday.net/newsdetail/detail/200/12446"><img id="startFrom_2" onmouseover="showM…
  • Error Line 1255, Column 274: required attribute "alt" not specified
    …/records/news/201302/12445_2.jpg" height="36" width="123" border="0"></a></div>

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

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

  • Error Line 1255, Column 278: end tag for "img" omitted, but OMITTAG NO was specified
    …/records/news/201302/12445_2.jpg" height="36" width="123" border="0"></a></div>

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

  • Info Line 1255, Column 101: start tag was here
    …oday.net/newsdetail/detail/200/12445"><img id="startFrom_3" onmouseover="showM…
  • Error Line 1268, Column 274: required attribute "alt" not specified
    …/records/news/201302/12444_2.jpg" height="36" width="123" border="0"></a></div>

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

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

  • Error Line 1268, Column 278: end tag for "img" omitted, but OMITTAG NO was specified
    …/records/news/201302/12444_2.jpg" height="36" width="123" border="0"></a></div>

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

  • Info Line 1268, Column 101: start tag was here
    …oday.net/newsdetail/detail/200/12444"><img id="startFrom_4" onmouseover="showM…
  • Error Line 1335, Column 31: character ";" not allowed in attribute specification list
    			for(var i=0;i<headlineCount;i++){
  • Error Line 1335, Column 31: element "headlineCount" undefined
    			for(var i=0;i<headlineCount;i++){

    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 1358, Column 30: character ";" not allowed in attribute specification list
    		for(var i=0;i<headlineCount;i++){
  • Error Line 1358, Column 30: element "headlineCount" undefined
    		for(var i=0;i<headlineCount;i++){

    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 1387, Column 9: end tag for "headlineCount" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 1358, Column 16: start tag was here
    		for(var i=0;i<headlineCount;i++){
  • Error Line 1387, Column 9: end tag for "headlineCount" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 1335, Column 17: start tag was here
    			for(var i=0;i<headlineCount;i++){
  • Error Line 1411, Column 46: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …         <span><div class="image-left"><a href="http://www.bdtoday.net/videohi…

    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 1411, Column 210: required attribute "alt" not specified
    …"102" src="http://www.bdtoday.net/records/videohighlight/201302/941_1.jpg"></a>

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

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

  • Error Line 1411, Column 214: end tag for "img" omitted, but OMITTAG NO was specified
    …"102" src="http://www.bdtoday.net/records/videohighlight/201302/941_1.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 1411, Column 112: start tag was here
    ….net/videohighlightdetail/detail/941"><img width="135" height="102" src="http:…
  • Error Line 1423, Column 46: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …         <span><div class="image-left"><a href="http://www.bdtoday.net/videohi…

    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 1423, Column 210: required attribute "alt" not specified
    …"102" src="http://www.bdtoday.net/records/videohighlight/201302/940_1.jpg"></a>

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

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

  • Error Line 1423, Column 214: end tag for "img" omitted, but OMITTAG NO was specified
    …"102" src="http://www.bdtoday.net/records/videohighlight/201302/940_1.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 1423, Column 112: start tag was here
    ….net/videohighlightdetail/detail/940"><img width="135" height="102" src="http:…
  • Error Line 1435, Column 46: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …         <span><div class="image-left"><a href="http://www.bdtoday.net/videohi…

    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 1435, Column 210: required attribute "alt" not specified
    …"102" src="http://www.bdtoday.net/records/videohighlight/201302/939_1.jpg"></a>

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

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

  • Error Line 1435, Column 214: end tag for "img" omitted, but OMITTAG NO was specified
    …"102" src="http://www.bdtoday.net/records/videohighlight/201302/939_1.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 1435, Column 112: start tag was here
    ….net/videohighlightdetail/detail/939"><img width="135" height="102" src="http:…
  • Error Line 1447, Column 46: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …         <span><div class="image-left"><a href="http://www.bdtoday.net/videohi…

    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 1447, Column 210: required attribute "alt" not specified
    …"102" src="http://www.bdtoday.net/records/videohighlight/201302/938_1.jpg"></a>

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

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

  • Error Line 1447, Column 214: end tag for "img" omitted, but OMITTAG NO was specified
    …"102" src="http://www.bdtoday.net/records/videohighlight/201302/938_1.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 1447, Column 112: start tag was here
    ….net/videohighlightdetail/detail/938"><img width="135" height="102" src="http:…
  • Error Line 1950, Column 14: required attribute "type" not specified
    							<style>

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

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

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

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

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

  • Error Line 2022, Column 58: end tag for "br" omitted, but OMITTAG NO was specified
    …="width:100%;height:2px; clear:both;">........................................…

    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 2022, Column 11: start tag was here
    							   <br style="width:100%;height:2px; clear:both;">......................…
  • Error Line 2022, Column 118: end tag for element "p" which is not open
    …2px; clear:both;">.........................................................</p>

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

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

  • Error Line 2071, Column 58: end tag for "br" omitted, but OMITTAG NO was specified
    …="width:100%;height:2px; clear:both;">........................................…

    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 2071, Column 11: start tag was here
    							   <br style="width:100%;height:2px; clear:both;">......................…
  • Error Line 2071, Column 118: end tag for element "p" which is not open
    …2px; clear:both;">.........................................................</p>

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

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

  • Error Line 2184, Column 141: end tag for "input" omitted, but OMITTAG NO was specified
    …g:0px 4px 0px 4px; font-size:16px;" value="মতামত দিন " type="button" id="Send">

    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 2184, Column 4: start tag was here
    			<input style="font-family:solaimanLipi; width:80px; padding:0px 4px 0px 4px;…
  • Error Line 2205, Column 132: required attribute "alt" not specified
    ….bdtoday.net/images/quote_start.jpg" /><span>&nbsp;<a href="http://www.bdtoday…

    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 2205, Column 400: required attribute "alt" not specified
    …ন </a> </span> <span> <img src="http://www.bdtoday.net/images/quote_end.jpg" />

    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 2253, Column 113: document type does not allow element "ul" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …; line-height:25px; font-family:solaimanLipi; font-size:17px; text-align:left">

    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 2255, Column 67: required attribute "alt" not specified
    …/www.bdtoday.net/images/tipponi.gif" /> &nbsp;&nbsp;  তাহলে আপনাদের আন্দোলনের …

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

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

  • Error Line 2255, Column 187: required attribute "alt" not specified
    …/www.bdtoday.net/images/tipponi.gif" /> &nbsp;&nbsp;  আপনাদের ঘুমানোর রাস্তা ক…

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

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

  • Error Line 2271, Column 132: required attribute "alt" not specified
    ….bdtoday.net/images/quote_start.jpg" /><span>&nbsp;<a href="http://www.bdtoday…

    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 2283, Column 262: end tag for element "span" which is not open
    …ে সময় আমি ঢাকায় ছিলাম না। আমি গ্রামের বাড়ি ফরিদপুরে চলে যাই </a> </span> </div>

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

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

  • Error Line 2287, Column 14: end tag for element "span" which is not open
    							</span>

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

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

  • Error Line 2291, Column 174: required attribute "alt" not specified
    …৬/০২/২০১৩<span> <img src="http://www.bdtoday.net/images/quote_end.jpg" /></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 2291, Column 180: end tag for "span" omitted, but OMITTAG NO was specified
    …৬/০২/২০১৩<span> <img src="http://www.bdtoday.net/images/quote_end.jpg" /></div>

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

  • Info Line 2291, Column 111: start tag was here
    …e:16px;">সুত্র, কালের কন্ঠ, ০৬/০২/২০১৩<span> <img src="http://www.bdtoday.net/…
  • Error Line 2315, Column 95: document type does not allow element "link" here
    …sheet" type="text/css" href="http://www.bdtoday.net/slider_files/emythmak.css">

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

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

  • Error Line 2315, Column 96: end tag for "link" omitted, but OMITTAG NO was specified
    …sheet" type="text/css" href="http://www.bdtoday.net/slider_files/emythmak.css">

    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 2315, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="http://www.bdtoday.net/slider_file…
  • Error Line 2322, Column 110: document type does not allow element "link" here
    …www.bdtoday.net/css/jquery.jscrollpane.css" rel="stylesheet" media="all" />				

    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 2348, Column 7: required attribute "type" not specified
    <style>

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

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

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

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

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

  • Error Line 2359, Column 10: syntax of attribute value does not conform to declared value
    <div id="" class="scroll-pane" style="height:200px; text-align:left;"><ul>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 2647, Column 40: there is no attribute "data-href"
    …			<div class="fb-like-box" data-href="http://www.facebook.com/pages/bdtodayne…

    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 2647, Column 110: there is no attribute "data-width"
    …dtodaynet/417776631617312" data-width="260" data-show-faces="true" data-stream…

    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 2647, Column 132: there is no attribute "data-show-faces"
    …312" data-width="260" data-show-faces="true" data-stream="false" data-header="…

    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 2647, Column 151: there is no attribute "data-stream"
    …idth="260" data-show-faces="true" data-stream="false" data-header="true"></div>

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

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

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

  • Error Line 2647, Column 171: there is no attribute "data-header"
    …idth="260" data-show-faces="true" data-stream="false" data-header="true"></div>

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

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

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

  • Error Line 2800, Column 132: document type does not allow element "link" here
    …t/skin/blue.monday/jplayer.blue.monday.css" rel="stylesheet" type="text/css" />

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

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

  • Error Line 2881, Column 17: there is no attribute "onClick"
    				<a  onClick="window.open(this.href,this.target,'status=no,scrollbars=no,res…

    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 2881, Column 210: cannot generate system identifier for general entity "bgc"
    …heck/bengali/meta/tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img …

    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 2881, Column 210: general entity "bgc" not defined and no default entity
    …heck/bengali/meta/tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img …

    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 2881, Column 213: reference not terminated by REFC delimiter
    …k/bengali/meta/tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2881, Column 213: reference to external entity in attribute value
    …k/bengali/meta/tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2881, Column 213: reference to entity "bgc" for which no system identifier could be generated
    …k/bengali/meta/tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2881, Column 209: entity was defined here
    …check/bengali/meta/tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img…
  • Warning Line 2881, Column 225: reference not terminated by REFC delimiter
    …ta/tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" sr…

    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 2881, Column 229: cannot generate system identifier for general entity "nbram"
    …x/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="h…

    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 2881, Column 229: general entity "nbram" not defined and no default entity
    …x/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="h…

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

  • Warning Line 2881, Column 234: reference not terminated by REFC delimiter
    …g_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2881, Column 234: reference to external entity in attribute value
    …g_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2881, Column 234: reference to entity "nbram" for which no system identifier could be generated
    …g_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2881, Column 228: entity was defined here
    …tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="…
  • Warning Line 2881, Column 237: cannot generate system identifier for general entity "nbwm"
    …ul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://ww…

    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 2881, Column 237: general entity "nbwm" not defined and no default entity
    …ul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://ww…

    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 2881, Column 241: reference not terminated by REFC delimiter
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2881, Column 241: reference to external entity in attribute value
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2881, Column 241: reference to entity "nbwm" for which no system identifier could be generated
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2881, Column 236: entity was defined here
    …bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://w…
  • Error Line 2881, Column 312: required attribute "alt" not specified
    …http://www.bdtoday.net/images/bbcplay.gif" /> World News | বিশ্ব সংবাদ</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>.

  • Warning Line 2888, Column 217: reference not terminated by REFC delimiter
    …ngali/meta/tx/beng_provati?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2888, Column 217: reference to external entity in attribute value
    …ngali/meta/tx/beng_provati?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2888, Column 217: reference to entity "bgc" for which no system identifier could be generated
    …ngali/meta/tx/beng_provati?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2881, Column 209: entity was defined here
    …check/bengali/meta/tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img…
  • Warning Line 2888, Column 229: reference not terminated by REFC delimiter
    …x/beng_provati?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" sr…

    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 2888, Column 238: reference not terminated by REFC delimiter
    …ovati?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2888, Column 238: reference to external entity in attribute value
    …ovati?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2888, Column 238: reference to entity "nbram" for which no system identifier could be generated
    …ovati?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2881, Column 228: entity was defined here
    …tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="…
  • Warning Line 2888, Column 245: reference not terminated by REFC delimiter
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2888, Column 245: reference to external entity in attribute value
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2888, Column 245: reference to entity "nbwm" for which no system identifier could be generated
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2881, Column 236: entity was defined here
    …bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://w…
  • Error Line 2888, Column 316: required attribute "alt" not specified
    …" src="http://www.bdtoday.net/images/bbcplay.gif" /> Provati | প্রভাতী</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>.

  • Warning Line 2892, Column 218: reference not terminated by REFC delimiter
    …gali/meta/tx/beng_provati2?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2892, Column 218: reference to external entity in attribute value
    …gali/meta/tx/beng_provati2?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2892, Column 218: reference to entity "bgc" for which no system identifier could be generated
    …gali/meta/tx/beng_provati2?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2881, Column 209: entity was defined here
    …check/bengali/meta/tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img…
  • Warning Line 2892, Column 230: reference not terminated by REFC delimiter
    …/beng_provati2?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" sr…

    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 2892, Column 239: reference not terminated by REFC delimiter
    …vati2?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2892, Column 239: reference to external entity in attribute value
    …vati2?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2892, Column 239: reference to entity "nbram" for which no system identifier could be generated
    …vati2?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2881, Column 228: entity was defined here
    …tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="…
  • Warning Line 2892, Column 246: reference not terminated by REFC delimiter
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2892, Column 246: reference to external entity in attribute value
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2892, Column 246: reference to entity "nbwm" for which no system identifier could be generated
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2881, Column 236: entity was defined here
    …bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://w…
  • Error Line 2892, Column 317: required attribute "alt" not specified
    …c="http://www.bdtoday.net/images/bbcplay.gif" /> Prottusha | প্রত্যূষা</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>.

  • Warning Line 2894, Column 217: reference not terminated by REFC delimiter
    …ngali/meta/tx/beng_probaho?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2894, Column 217: reference to external entity in attribute value
    …ngali/meta/tx/beng_probaho?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2894, Column 217: reference to entity "bgc" for which no system identifier could be generated
    …ngali/meta/tx/beng_probaho?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2881, Column 209: entity was defined here
    …check/bengali/meta/tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img…
  • Warning Line 2894, Column 229: reference not terminated by REFC delimiter
    …x/beng_probaho?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" sr…

    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 2894, Column 238: reference not terminated by REFC delimiter
    …obaho?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2894, Column 238: reference to external entity in attribute value
    …obaho?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2894, Column 238: reference to entity "nbram" for which no system identifier could be generated
    …obaho?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2881, Column 228: entity was defined here
    …tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="…
  • Warning Line 2894, Column 245: reference not terminated by REFC delimiter
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2894, Column 245: reference to external entity in attribute value
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2894, Column 245: reference to entity "nbwm" for which no system identifier could be generated
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2881, Column 236: entity was defined here
    …bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://w…
  • Error Line 2894, Column 316: required attribute "alt" not specified
    …t" src="http://www.bdtoday.net/images/bbcplay.gif" /> Probaho | প্রবাহ</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>.

  • Warning Line 2897, Column 219: reference not terminated by REFC delimiter
    …ali/meta/tx/beng_parikrama?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2897, Column 219: reference to external entity in attribute value
    …ali/meta/tx/beng_parikrama?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2897, Column 219: reference to entity "bgc" for which no system identifier could be generated
    …ali/meta/tx/beng_parikrama?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2881, Column 209: entity was defined here
    …check/bengali/meta/tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img…
  • Warning Line 2897, Column 231: reference not terminated by REFC delimiter
    …beng_parikrama?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" sr…

    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 2897, Column 240: reference not terminated by REFC delimiter
    …krama?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2897, Column 240: reference to external entity in attribute value
    …krama?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2897, Column 240: reference to entity "nbram" for which no system identifier could be generated
    …krama?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2881, Column 228: entity was defined here
    …tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="…
  • Warning Line 2897, Column 247: reference not terminated by REFC delimiter
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2897, Column 247: reference to external entity in attribute value
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2897, Column 247: reference to entity "nbwm" for which no system identifier could be generated
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2881, Column 236: entity was defined here
    …bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://w…
  • Error Line 2897, Column 318: required attribute "alt" not specified
    …rc="http://www.bdtoday.net/images/bbcplay.gif" /> Porikroma | পরিক্রমা</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>.

  • Warning Line 2900, Column 218: reference not terminated by REFC delimiter
    …gali/meta/tx/beng_shanglap?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2900, Column 218: reference to external entity in attribute value
    …gali/meta/tx/beng_shanglap?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2900, Column 218: reference to entity "bgc" for which no system identifier could be generated
    …gali/meta/tx/beng_shanglap?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img ali…

    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 2881, Column 209: entity was defined here
    …check/bengali/meta/tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img…
  • Warning Line 2900, Column 230: reference not terminated by REFC delimiter
    …/beng_shanglap?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" sr…

    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 2900, Column 239: reference not terminated by REFC delimiter
    …nglap?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2900, Column 239: reference to external entity in attribute value
    …nglap?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2900, Column 239: reference to entity "nbram" for which no system identifier could be generated
    …nglap?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http:/…

    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 2881, Column 228: entity was defined here
    …tx/beng_bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="…
  • Warning Line 2900, Column 246: reference not terminated by REFC delimiter
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2900, Column 246: reference to external entity in attribute value
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2900, Column 246: reference to entity "nbwm" for which no system identifier could be generated
    …ize=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://www.bd…

    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 2881, Column 236: entity was defined here
    …bul?size=au&bgc=003399&lang=bn&nbram=1&nbwm=1"><img align="left" src="http://w…
  • Error Line 2900, Column 317: required attribute "alt" not specified
    …ft" src="http://www.bdtoday.net/images/bbcplay.gif" /> Songlap | সংলাপ</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 2942, Column 118: "allowfullscreen" is not a member of a group specified for any attribute
    …zeZic" frameborder="0" allowfullscreen></iframe>                              …
  • Error Line 2953, Column 101: document type does not allow element "link" here
    …heet" type="text/css" href="http://www.bdtoday.net/gallery_files/wt-rotat.css">

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

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

  • Error Line 2953, Column 102: end tag for "link" omitted, but OMITTAG NO was specified
    …heet" type="text/css" href="http://www.bdtoday.net/gallery_files/wt-rotat.css">

    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 2953, Column 6: start tag was here
    					<link rel="stylesheet" type="text/css" href="http://www.bdtoday.net/galler…
  • Error Line 2971, Column 97: required attribute "alt" not specified
    …g src="http://www.bdtoday.net/records/imagegallery/201206/41_3.jpg"></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 2971, Column 108: end tag for "img" omitted, but OMITTAG NO was specified
    …g src="http://www.bdtoday.net/records/imagegallery/201206/41_3.jpg"></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 2971, Column 27: start tag was here
                    <noscript><img src="http://www.bdtoday.net/records/imagegallery…
  • Error Line 2978, Column 184: required attribute "alt" not specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201206/41_2.jpg"></a>

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

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

  • Error Line 2978, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201206/41_2.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 2978, Column 114: start tag was here
    …llery/201206/41_3.jpg" title="temple"><img src="http://www.bdtoday.net/records…
  • Warning Line 2981, Column 66: character "&" is the first character of a delimiter but occurred as data
    …                 	Argentina vs Brazil 4-3 - All Goals & Full Highlights								

    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 2985, Column 184: required attribute "alt" not specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201206/42_2.jpg"></a>

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

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

  • Error Line 2985, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201206/42_2.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 2985, Column 114: start tag was here
    …llery/201206/42_3.jpg" title="temple"><img src="http://www.bdtoday.net/records…
  • Warning Line 2988, Column 66: character "&" is the first character of a delimiter but occurred as data
    …               	Argentina vs Brazil 4-3 - All Goals & Full Highlights 2								

    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 2992, Column 184: required attribute "alt" not specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201203/36_2.jpg"></a>

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

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

  • Error Line 2992, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201203/36_2.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 2992, Column 114: start tag was here
    …llery/201203/36_3.jpg" title="temple"><img src="http://www.bdtoday.net/records…
  • Error Line 2999, Column 184: required attribute "alt" not specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201203/37_2.jpg"></a>

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

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

  • Error Line 2999, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201203/37_2.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 2999, Column 114: start tag was here
    …llery/201203/37_3.jpg" title="temple"><img src="http://www.bdtoday.net/records…
  • Error Line 3006, Column 184: required attribute "alt" not specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201203/38_2.jpg"></a>

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

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

  • Error Line 3006, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201203/38_2.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 3006, Column 114: start tag was here
    …llery/201203/38_3.jpg" title="temple"><img src="http://www.bdtoday.net/records…
  • Error Line 3013, Column 184: required attribute "alt" not specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201202/33_2.jpg"></a>

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

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

  • Error Line 3013, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201202/33_2.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 3013, Column 114: start tag was here
    …llery/201202/33_3.jpg" title="temple"><img src="http://www.bdtoday.net/records…
  • Error Line 3020, Column 184: required attribute "alt" not specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201202/34_2.jpg"></a>

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

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

  • Error Line 3020, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201202/34_2.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 3020, Column 114: start tag was here
    …llery/201202/34_3.jpg" title="temple"><img src="http://www.bdtoday.net/records…
  • Error Line 3027, Column 184: required attribute "alt" not specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201203/35_2.jpg"></a>

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

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

  • Error Line 3027, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201203/35_2.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 3027, Column 114: start tag was here
    …llery/201203/35_3.jpg" title="temple"><img src="http://www.bdtoday.net/records…
  • Error Line 3034, Column 184: required attribute "alt" not specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201203/39_2.jpg"></a>

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

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

  • Error Line 3034, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201203/39_2.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 3034, Column 114: start tag was here
    …llery/201203/39_3.jpg" title="temple"><img src="http://www.bdtoday.net/records…
  • Error Line 3041, Column 184: required attribute "alt" not specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201203/40_2.jpg"></a>

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

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

  • Error Line 3041, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …le"><img src="http://www.bdtoday.net/records/imagegallery/201203/40_2.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 3041, Column 114: start tag was here
    …llery/201203/40_3.jpg" title="temple"><img src="http://www.bdtoday.net/records…
  • Error Line 3092, Column 123: required attribute "alt" not specified
    …eera"><img width="266" src="http://www.bdtoday.net/images/aljazeera.jpg" /></a>

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

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

  • Error Line 3099, Column 138: required attribute "alt" not specified
    ….html"><img  width="266"  src="http://www.bdtoday.net/images/dw-mod.jpg" /></a>

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

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

  • Error Line 3103, Column 143: required attribute "alt" not specified
    …asx"><img  width="266"  src="http://www.bdtoday.net/images/voa_logo.jpg" /></a>

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

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

  • Error Line 3107, Column 186: required attribute "alt" not specified
    …live"><img  width="266"  src="http://www.bdtoday.net/images/bbc-mod.jpg" /></a>

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

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

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

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

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

  • Error Line 3351, Column 284: end tag for "img" omitted, but OMITTAG NO was specified
    ….net/records/weather/12_pht.png"></div><div style="float:left;font-size:11px; …

    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 3351, Column 211: start tag was here
    …v><div style="float:left;width:48px;"><img alt="" src="http://www.bdtoday.net/…
  • Error Line 3351, Column 375: end tag for "br" omitted, but OMITTAG NO was specified
    …rial, Helvetica, sans-serif">Dhaka<br>Temp: 30.5°C, Humidity: 82.5%<br></div><…

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

  • Info Line 3351, Column 371: start tag was here
    …ly:Arial, Helvetica, sans-serif">Dhaka<br>Temp: 30.5°C, Humidity: 82.5%<br></d…
  • Error Line 3351, Column 413: end tag for "br" omitted, but OMITTAG NO was specified
    …Temp: 30.5°C, Humidity: 82.5%<br></div><div style="clear: both;"></div></div><…

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

  • Info Line 3351, Column 404: start tag was here
    …Dhaka<br>Temp: 30.5°C, Humidity: 82.5%<br></div><div style="clear: both;"></di…
  • Error Line 3359, Column 284: end tag for "img" omitted, but OMITTAG NO was specified
    ….net/records/weather/13_pht.png"></div><div style="float:left;font-size:11px; …

    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 3359, Column 211: start tag was here
    …v><div style="float:left;width:48px;"><img alt="" src="http://www.bdtoday.net/…
  • Error Line 3359, Column 376: end tag for "br" omitted, but OMITTAG NO was specified
    …ial, Helvetica, sans-serif">Khulna<br>Temp: 30.5°C, Humidity: 82.5%<br></div><…

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

  • Info Line 3359, Column 372: start tag was here
    …y:Arial, Helvetica, sans-serif">Khulna<br>Temp: 30.5°C, Humidity: 82.5%<br></d…
  • Error Line 3359, Column 414: end tag for "br" omitted, but OMITTAG NO was specified
    …Temp: 30.5°C, Humidity: 82.5%<br></div><div style="clear: both;"></div></div><…

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

  • Info Line 3359, Column 405: start tag was here
    …hulna<br>Temp: 30.5°C, Humidity: 82.5%<br></div><div style="clear: both;"></di…
  • Error Line 3447, Column 106: document type does not allow element "link" here
    …ref="http://www.bdtoday.net/css/jquery-ui-1.7.3.custom.css" rel="stylesheet" />

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

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

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

Visitor Analysis

Daily Visitor
  • 10.500 visits

In Page Analysis