شريط الأحداث الجمهورية: رسالة أوروبية قاسية وجهتها أشتون لمنصور بإلغاء لقائهما أمس الجراح: منصور هو وزير خارجية نظام سوريا وإيران وسليمان برهن عن حس وطني مصادر الجمهورية: سليمان قدم بلاغاً بالخروقات السورية كافة ...

beirutobserver.com
  • Domain Name
    beirutobserver.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #57279
  • Page Size
    62.5 KB
  • Ip Address
    216.119.146.18
  • Heading
    H1: 1, H2: 14, H3: 44, H4: 10, H5: 0, H6: 0
  • Images
    0 GIF, 36 JPG, 7 PNG

Website Meta Analysis

  • Title
    Beirut Observer | موقع إخباري يتناول الشؤون اللبنانية والعربية والدولية
  • Meta Keyword
  • Meta Description
    شريط الأحداث الجمهورية: رسالة أوروبية قاسية وجهتها أشتون لمنصور بإلغاء لقائهما أمس الجراح: منصور هو وزير خارجية نظام سوريا وإيران وسليمان برهن عن حس وطني مصادر الجمهورية: سليمان قدم بلاغاً بالخروقات السورية كافة وليس شكوى علوش: مذكرة 14 آذار ...

Technical Analysis

  • Webserver
    Apache/2.2.22
  • Ip Address
    216.119.146.18
  • Domain Age
    4 Years, 8 Months, 13 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache/2.2.22
  • x-powered-by: W3 Total Cache/0.9.3
  • last-modified: Thu, 19 Sep 2013 13:49:54 GMT
  • expires: Thu, 19 Sep 2013 14:49:54 GMT
  • pragma: public
  • cache-control: max-age=2567, public
  • content-encoding: gzip
  • vary: Accept-Encoding,User-Agent
  • x-pingback: http://www.beirutobserver.com/xmlrpc.php
  • content-type: text/html; charset=UTF-8
  • content-length: 11986
  • accept-ranges: bytes
  • date: Thu, 19 Sep 2013 14:07:07 GMT
  • x-varnish: 1889013633
  • age: 0
  • via: 1.1 varnish
  • connection: keep-alive
  • x-cache: MISS
  • x-google-cache-control: remote-fetch
No data whois for beirutobserver.com

DNS Analysis


DNS servers
ns1.siteforbiz.com [174.142.90.217]
ns2.siteforbiz.com [174.142.96.41]


DNS Records

Answer records
beirutobserver.com MX
preference: 0
exchange: beirutobserver.com
14400s
beirutobserver.com SOA
server: ns1.siteforbiz.com
email: info@siteforbiz.com
serial: 2011071706
refresh: 86400
retry: 7200
expire: 604800
minimum ttl: 86400
86400s
beirutobserver.com NS  ns2.siteforbiz.com 864s
beirutobserver.com NS  ns1.siteforbiz.com 864s
beirutobserver.com A 174.142.90.217 144s

Authority records

Additional records
beirutobserver.com A 174.142.90.217 144s
ns1.siteforbiz.com A 174.142.90.217 14400s
ns2.siteforbiz.com A 174.142.96.41 14400s

IP 216.119.146.18 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 13 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.7753572265167487
Message Error
  • Error Line 181, Column 91: document type does not allow element "link" here
    …"stylesheet" href="/templates/rt_mixxmag_j15/css/banner.css" 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 198, Column 92: end tag for "img" omitted, but OMITTAG NO was specified
    …="http://beirutobserver.com/"><img alt="" src="/images/stories/banner.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 198, Column 44: start tag was here
    …	<a href="http://beirutobserver.com/"><img alt="" src="/images/stories/banner.…
  • Error Line 366, Column 8: end tag for "br" omitted, but OMITTAG NO was specified
    			<br>

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

  • Info Line 366, Column 4: start tag was here
    			<br>
  • Error Line 388, Column 97: there is no attribute "bordercolor"
    …order-collapse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" …

    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 388, Column 144: there is no attribute "height"
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="33">

    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 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 391, 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 398, Column 19: there is no attribute "behavior"
    <marquee behavior="scroll" align="center" direction="right" height="40" scrolla…

    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 398, Column 34: there is no attribute "align"
    <marquee behavior="scroll" align="center" direction="right" height="40" scrolla…

    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 398, Column 53: there is no attribute "direction"
    …ior="scroll" align="center" direction="right" height="40" scrollamount="4" wid…

    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 398, Column 68: there is no attribute "height"
    …ign="center" direction="right" height="40" scrollamount="4" width="100%" onMou…

    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 398, Column 86: there is no attribute "scrollamount"
    …tion="right" height="40" scrollamount="4" width="100%" onMouseOver="this.stop(…

    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 398, Column 96: there is no attribute "width"
    …t" height="40" scrollamount="4" width="100%" onMouseOver="this.stop()" onMouse…

    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 398, Column 115: there is no attribute "onMouseOver"
    …llamount="4" width="100%" onMouseOver="this.stop()" onMouseOut="this.start()" …

    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 398, Column 140: there is no attribute "onMouseOut"
    …dth="100%" onMouseOver="this.stop()" onMouseOut="this.start()" loop="infinite">

    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 398, Column 160: there is no attribute "loop"
    …dth="100%" onMouseOver="this.stop()" onMouseOut="this.start()" loop="infinite">

    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 398, Column 170: element "marquee" undefined
    …dth="100%" onMouseOver="this.stop()" onMouseOut="this.start()" loop="infinite">

    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 402, Column 58: required attribute "alt" not specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&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 402, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	

    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 402, Column 8: start tag was here
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	
  • Error Line 405, Column 8: end tag for "b" omitted, but OMITTAG NO was specified
    	</span>

    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 404, Column 3: start tag was here
    		<b><a href="/index.php?option=com_content&amp;view=article&amp;id=90964:2013-…
  • Error Line 407, Column 58: required attribute "alt" not specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

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

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

  • Error Line 407, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

    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 407, Column 8: start tag was here
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>
  • Error Line 408, Column 5: end tag for element "b" which is not open
    	</b>

    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 413, Column 8: end tag for "b" omitted, but OMITTAG NO was specified
    	</span>

    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 412, Column 3: start tag was here
    		<b><a href="/index.php?option=com_content&amp;view=article&amp;id=90963:2013-…
  • Error Line 415, Column 58: required attribute "alt" not specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

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

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

  • Error Line 415, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

    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 415, Column 8: start tag was here
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>
  • Error Line 416, Column 5: end tag for element "b" which is not open
    	</b>

    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 421, Column 8: end tag for "b" omitted, but OMITTAG NO was specified
    	</span>

    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 420, Column 3: start tag was here
    		<b><a href="/index.php?option=com_content&amp;view=article&amp;id=90962:-----…
  • Error Line 423, Column 58: required attribute "alt" not specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

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

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

  • Error Line 423, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

    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 423, Column 8: start tag was here
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>
  • Error Line 424, Column 5: end tag for element "b" which is not open
    	</b>

    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 429, Column 8: end tag for "b" omitted, but OMITTAG NO was specified
    	</span>

    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 428, Column 3: start tag was here
    		<b><a href="/index.php?option=com_content&amp;view=article&amp;id=90961:---14…
  • Error Line 431, Column 58: required attribute "alt" not specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

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

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

  • Error Line 431, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

    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 431, Column 8: start tag was here
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>
  • Error Line 432, Column 5: end tag for element "b" which is not open
    	</b>

    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 437, Column 8: end tag for "b" omitted, but OMITTAG NO was specified
    	</span>

    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 436, Column 3: start tag was here
    		<b><a href="/index.php?option=com_content&amp;view=article&amp;id=90960:2013-…
  • Error Line 439, Column 58: required attribute "alt" not specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

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

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

  • Error Line 439, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

    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 439, Column 8: start tag was here
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>
  • Error Line 440, Column 5: end tag for element "b" which is not open
    	</b>

    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 445, Column 8: end tag for "b" omitted, but OMITTAG NO was specified
    	</span>

    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 444, Column 3: start tag was here
    		<b><a href="/index.php?option=com_content&amp;view=article&amp;id=90959:qq---…
  • Error Line 447, Column 58: required attribute "alt" not specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

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

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

  • Error Line 447, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

    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 447, Column 8: start tag was here
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>
  • Error Line 448, Column 5: end tag for element "b" which is not open
    	</b>

    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 453, Column 8: end tag for "b" omitted, but OMITTAG NO was specified
    	</span>

    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 452, Column 3: start tag was here
    		<b><a href="/index.php?option=com_content&amp;view=article&amp;id=90958:2013-…
  • Error Line 455, Column 58: required attribute "alt" not specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

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

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

  • Error Line 455, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

    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 455, Column 8: start tag was here
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>
  • Error Line 456, Column 5: end tag for element "b" which is not open
    	</b>

    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 461, Column 8: end tag for "b" omitted, but OMITTAG NO was specified
    	</span>

    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 460, Column 3: start tag was here
    		<b><a href="/index.php?option=com_content&amp;view=article&amp;id=90957:2013-…
  • Error Line 463, Column 58: required attribute "alt" not specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

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

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

  • Error Line 463, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

    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 463, Column 8: start tag was here
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>
  • Error Line 464, Column 5: end tag for element "b" which is not open
    	</b>

    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 469, Column 8: end tag for "b" omitted, but OMITTAG NO was specified
    	</span>

    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 468, Column 3: start tag was here
    		<b><a href="/index.php?option=com_content&amp;view=article&amp;id=90956:2013-…
  • Error Line 471, Column 58: required attribute "alt" not specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

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

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

  • Error Line 471, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

    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 471, Column 8: start tag was here
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>
  • Error Line 472, Column 5: end tag for element "b" which is not open
    	</b>

    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 477, Column 8: end tag for "b" omitted, but OMITTAG NO was specified
    	</span>

    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 476, Column 3: start tag was here
    		<b><a href="/index.php?option=com_content&amp;view=article&amp;id=90955:2013-…
  • Error Line 479, Column 58: required attribute "alt" not specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

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

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

  • Error Line 479, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>

    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 479, Column 8: start tag was here
    	&nbsp;<img src="/images/logo.gif" height="27" width="29">&nbsp;	</span>
  • Error Line 480, Column 5: end tag for element "b" which is not open
    	</b>

    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 553, Column 141: ID "container" already defined
    …1:assad&amp;catid=39:features"><span id="container"> الحوار مع اﻷسد؟</span></a>

    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 528, Column 155: ID "container" first defined here
    …1-03&amp;catid=39:features"><span id="container">محاضر التحقيق مع سماحة .. طلب…
  • Error Line 578, Column 148: ID "container" already defined
    …afeh&amp;catid=39:features"><span id="container">١٥٪ تقصي جعجع عن كرسي الرئاسة…

    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 528, Column 155: ID "container" first defined here
    …1-03&amp;catid=39:features"><span id="container">محاضر التحقيق مع سماحة .. طلب…
  • Error Line 585, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 593, Column 82: there is no attribute "width"
    …tp://www.hallab.com.lb/"><embed width="668" height="94" type="application/x-sh…

    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 593, Column 95: there is no attribute "height"
    …ab.com.lb/"><embed width="668" height="94" type="application/x-shockwave-flash…

    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 593, Column 105: there is no attribute "type"
    …"><embed width="668" height="94" type="application/x-shockwave-flash" pluginsp…

    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 593, Column 149: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" 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 593, Column 200: there is no attribute "play"
    …acromedia.com/go/getflashplayer" play="true" loop="true" menu="true" src="http…

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

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

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

  • Error Line 593, Column 212: there is no attribute "loop"
    …m/go/getflashplayer" play="true" loop="true" menu="true" src="http://beirutobs…

    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 593, Column 224: there is no attribute "menu"
    …hplayer" play="true" loop="true" menu="true" src="http://beirutobserver.com/im…

    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 593, Column 235: there is no attribute "src"
    …ay="true" loop="true" menu="true" src="http://beirutobserver.com/images/banner…

    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 593, Column 290: element "embed" undefined
    …enu="true" src="http://beirutobserver.com/images/banners/hallab.swf" /></a></p>

    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 616, Column 134: ID "AutoNumber1" already defined
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="15">

    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 388, Column 124: ID "AutoNumber1" first defined here
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="33">
  • Error Line 616, Column 158: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="15">

    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 640, Column 131: document type does not allow element "link" here
    …d_minifrontpage/css/style.css?v=1361498695" 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).

  • Warning Line 653, Column 788: cannot generate system identifier for general entity "view"
    …ref="/../index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> 	…

    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 653, Column 788: general entity "view" not defined and no default entity
    …ref="/../index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> 	…

    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 653, Column 792: reference not terminated by REFC delimiter
    …"/../index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> 				<…

    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 653, Column 792: reference to external entity in attribute value
    …"/../index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> 				<…

    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 653, Column 792: reference to entity "view" for which no system identifier could be generated
    …"/../index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> 				<…

    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 653, Column 787: entity was defined here
    …href="/../index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> …
  • Warning Line 653, Column 802: cannot generate system identifier for general entity "id"
    …/index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> 				</div>

    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 653, Column 802: general entity "id" not defined and no default entity
    …/index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> 				</div>

    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 653, Column 804: reference not terminated by REFC delimiter
    …/index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> 				</div>

    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 653, Column 804: reference to external entity in attribute value
    …/index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> 				</div>

    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 653, Column 804: reference to entity "id" for which no system identifier could be generated
    …/index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> 				</div>

    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 653, Column 801: entity was defined here
    …/index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> 				</div>
  • Error Line 678, Column 138: ID "AutoNumber1" already defined
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="15">

    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 388, Column 124: ID "AutoNumber1" first defined here
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="33">
  • Error Line 698, Column 247: element "embed" undefined
    …5XuN6BRYYvU=" type="application/x-shockwave-flash" /> </object></div>				</div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 711, Column 138: ID "AutoNumber1" already defined
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="15">

    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 388, Column 124: ID "AutoNumber1" first defined here
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="33">
  • Error Line 718, Column 33: ID "ie_1" already defined
    			<h3 class="module-title" id="ie_1"><span class="bg">لبنانيات</span>

    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 685, Column 33: ID "ie_1" first defined here
    			<h3 class="module-title" id="ie_1"><span class="bg">أبزورفر Tv</span>
  • Error Line 731, Column 131: document type does not allow element "link" here
    …d_minifrontpage/css/style.css?v=1361498695" 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).

  • Warning Line 735, Column 767: reference not terminated by REFC delimiter
    …="/../index.php?option=com_content&view=category&id=25">لبنانيات</a> 				</div>

    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 735, Column 767: reference to external entity in attribute value
    …="/../index.php?option=com_content&view=category&id=25">لبنانيات</a> 				</div>

    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 735, Column 767: reference to entity "view" for which no system identifier could be generated
    …="/../index.php?option=com_content&view=category&id=25">لبنانيات</a> 				</div>

    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 653, Column 787: entity was defined here
    …href="/../index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> …
  • Warning Line 735, Column 779: reference not terminated by REFC delimiter
    …="/../index.php?option=com_content&view=category&id=25">لبنانيات</a> 				</div>

    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 735, Column 779: reference to external entity in attribute value
    …="/../index.php?option=com_content&view=category&id=25">لبنانيات</a> 				</div>

    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 735, Column 779: reference to entity "id" for which no system identifier could be generated
    …="/../index.php?option=com_content&view=category&id=25">لبنانيات</a> 				</div>

    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 653, Column 801: entity was defined here
    …/index.php?option=com_content&view=category&id=41">أخبار ٢٤ ساعة</a> 				</div>
  • Error Line 852, Column 36: ID "gk_npro-newspro1" already defined
    	<div class="gk_npro_mainwrap" id="gk_npro-newspro1" style="width: 650px;">

    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 795, Column 36: ID "gk_npro-newspro1" first defined here
    	<div class="gk_npro_mainwrap" id="gk_npro-newspro1" style="width: 650px;">
  • Error Line 908, Column 36: ID "gk_npro-newspro1" already defined
    	<div class="gk_npro_mainwrap" id="gk_npro-newspro1" style="width: 650px;">

    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 795, Column 36: ID "gk_npro-newspro1" first defined here
    	<div class="gk_npro_mainwrap" id="gk_npro-newspro1" style="width: 650px;">
  • Error Line 972, Column 36: ID "gk_npro-newspro1" already defined
    	<div class="gk_npro_mainwrap" id="gk_npro-newspro1" style="width: 630px;">

    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 795, Column 36: ID "gk_npro-newspro1" first defined here
    	<div class="gk_npro_mainwrap" id="gk_npro-newspro1" style="width: 650px;">
  • Warning Line 1066, Column 33: character "&" is the first character of a delimiter but occurred as data
      if (typeof(Yamli) == "object" && Yamli.init( { uiLanguage: "ar" , startMode: …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1066, Column 34: character "&" is the first character of a delimiter but occurred as data
      if (typeof(Yamli) == "object" && Yamli.init( { uiLanguage: "ar" , startMode: …

    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 1074, Column 259: element "embed" undefined
    …rc="http://beirutobserver.com/images/banners/app-banner.swf" /></a></p>		</div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1074, Column 263: end tag for element "a" which is not open
    …rc="http://beirutobserver.com/images/banners/app-banner.swf" /></a></p>		</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 1100, Column 129: ID "AutoNumber1" already defined
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="15">

    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 388, Column 124: ID "AutoNumber1" first defined here
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="33">
  • Error Line 1115, Column 23: document type does not allow element "div" here; assuming missing "li" start-tag
        <div align="right">
  • Error Line 1117, Column 27: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
        <li class="latestnews">

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

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

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

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

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

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

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

    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 1173, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>				</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 1115, Column 5: start tag was here
        <div align="right">
  • Error Line 1187, Column 129: ID "AutoNumber1" already defined
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="15">

    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 388, Column 124: ID "AutoNumber1" first defined here
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="33">
  • Error Line 1202, Column 23: document type does not allow element "div" here; assuming missing "li" start-tag
        <div align="right">
  • Error Line 1204, Column 27: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
        <li class="latestnews">

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

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

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

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

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

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

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

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

  • Error Line 1253, Column 27: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
        <li class="latestnews">

    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 1260, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>				</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 1202, Column 5: start tag was here
        <div align="right">
  • Error Line 1274, Column 129: ID "AutoNumber1" already defined
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="15">

    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 388, Column 124: ID "AutoNumber1" first defined here
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="33">
  • Error Line 1304, Column 129: ID "AutoNumber1" already defined
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="15">

    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 388, Column 124: ID "AutoNumber1" first defined here
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="33">
  • Error Line 1319, Column 23: document type does not allow element "div" here; assuming missing "li" start-tag
        <div align="right">
  • Error Line 1321, Column 27: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
        <li class="latestnews">

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

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

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

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

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

    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 1363, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>				</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 1319, Column 5: start tag was here
        <div align="right">
  • Error Line 1377, Column 129: ID "AutoNumber1" already defined
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="15">

    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 388, Column 124: ID "AutoNumber1" first defined here
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="33">
  • Error Line 1392, Column 23: document type does not allow element "div" here; assuming missing "li" start-tag
        <div align="right">
  • Error Line 1394, Column 27: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
        <li class="latestnews">

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

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

    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 1415, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>				</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 1392, Column 5: start tag was here
        <div align="right">
  • Error Line 1429, Column 129: ID "AutoNumber1" already defined
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="15">

    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 388, Column 124: ID "AutoNumber1" first defined here
    …pse: collapse" bordercolor="#111111" width="100%" id="AutoNumber1" height="33">
  • Error Line 1464, Column 204: there is no attribute "mce_src"
    …ce="0" height="30" border="3" mce_src="/images/faceb.jpg" alt="" src="/images/…

    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 1480, Column 254: element "embed" undefined
    …ockwave-flash" src="http://beirutobserver.com/images/banners/dots.swf" /></div>

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

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

Visitor Analysis

Daily Visitor
  • 1.867 visits