moi.gov.sa

Delicious Digg Facebook Google مستخدم جديد؟ | تسجيل الدخول  الرئيسية   الأفراد   الحكومة   الأعمال   الخدمات الإلكترونية  الثلاثاء 1 رمضان 1434 / 9 يوليو 2013  ديوان وزارة الداخلية   الإمارات   القطاعات  English الرئيسية > ديوان وزارة ...

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

Overview Info

  • Domain Name
    moi.gov.sa
  • Favicon
  • Alexa Rank
    #5628
  • Google Page Rank
    PR 3
  • Ip Address
    193.47.102.10
  • Page Size
    105.4 KB
  • Images
    14 GIF, 3 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 3 0 0 0 0

Website Meta Analysis



  • Title
    وزارة الداخلية المملكة العربية السعودية
  • Meta Keyword
  • Meta Description
    Delicious Digg Facebook Google مستخدم جديد؟ | تسجيل الدخول  الرئيسية   الأفراد   الحكومة   الأعمال   الخدمات الإلكترونية  الثلاثاء 1 رمضان 1434 / 9 يوليو 2013  ديوان وزارة الداخلية   الإمارات   القطاعات  English الرئيسية > ديوان وزارة الداخلية ...

Technical Analysis



  • Webserver
  • Ip Address
    193.47.102.10
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from moi.gov.sa.

HTML Analysis

  • date: Tue, 09 Jul 2013 06:24:54 GMT
  • ibm-web2-location: /wps/portal/!ut/p/b1/04_SjzQ0NDc3s7S0sNSP0I_KSyzLTE8syczPS8wB8aPM4k2dA5w9LXyNDd0DQs0NjNzMTbyczbwtDLxNgAoigQoMcABHA0L6gxOL9MP1o_AqMzGGKnB2d_QwMfcxMLDwcTc18HT0CA2yDDQ2NnCEKcDjDj-P_NxU_dyoHItgT11HABPMIvw!/dl4/d5/L2dBISEvZ0FBIS9nQSEh/
  • content-location: /wps/portal/!ut/p/b1/04_SjzQ0NDc3s7S0sNSP0I_KSyzLTE8syczPS8wB8aPM4k2dA5w9LXyNDd0DQs0NjNzMTbyczbwtDLxNgAoigQoMcABHA0L6gxOL9MP1o_AqMzGGKnB2d_QwMfcxMLDwcTc18HT0CA2yDDQ2NnCEKcDjDj-P_NxU_dyoHItgT11HABPMIvw!/dl4/d5/L2dBISEvZ0FBIS9nQSEh/
  • cache-control: no-cache, no-store, must-revalidate
  • expires: Thu, 01 Jan 1970 00:00:00 GMT
  • pragma: no-cache
  • vary: User-Agent,Cookie, Accept-Encoding
  • content-type: text/html; charset=UTF-8
  • content-language: ar
  • content-encoding: gzip
  • content-length: 29021
  • connection: Keep-Alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for moi.gov.sa

IP 193.47.102.10 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 360 Errors
  • 57 Warnings
Ratio Text/Html
  • 0.5847835147024774
Message Error
  • Error Line 48, Column 93: end tag for "link" omitted, but OMITTAG NO was specified
    …"/portal/css/style_arabic.css" rel="styleSheet" type="text/css" media="screen">

    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 48, Column 3: start tag was here
    		<link href="/portal/css/style_arabic.css" rel="styleSheet" type="text/css" me…
  • Error Line 49, Column 72: end tag for "link" omitted, but OMITTAG NO was specified
    		<link href="/portal/css/slider.css" rel="styleSheet" type="text/css">

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

  • Info Line 49, Column 3: start tag was here
    		<link href="/portal/css/slider.css" rel="styleSheet" type="text/css">
  • Error Line 50, Column 92: end tag for "link" omitted, but OMITTAG NO was specified
    …="/portal/css/menu_arabic.css" rel="styleSheet" type="text/css" media="screen">

    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 50, Column 3: start tag was here
    		<link href="/portal/css/menu_arabic.css" rel="styleSheet" type="text/css" med…
  • Error Line 51, Column 91: end tag for "link" omitted, but OMITTAG NO was specified
    …f="/portal/css/hdr_arabic.css" rel="styleSheet" type="text/css" media="screen">

    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 51, Column 3: start tag was here
    		<link href="/portal/css/hdr_arabic.css" rel="styleSheet" type="text/css" medi…
  • Error Line 52, Column 71: end tag for "link" omitted, but OMITTAG NO was specified
    		<link href="/portal/css/print.css" rel="styleSheet" type="text/css">

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

  • Info Line 52, Column 3: start tag was here
    		<link href="/portal/css/print.css" rel="styleSheet" type="text/css">
  • Error Line 64, Column 51: document type does not allow element "div" here; assuming missing "body" start-tag
    	<div id="toolsList" class="sharePost_new noPrint">
  • Error Line 84, Column 16: document type does not allow element "body" here
    <body dir="rtl"> 

    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 91, Column 87: required attribute "alt" not specified
    …s/portal/homeAR"><img src="/portal/images/theme/moinew/moi_logo_rtl.gif" /></a>

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

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

  • Error Line 131, Column 14: there is no attribute "method"
    <FORM method="POST" name="ManageSearch" action="/wps/portal/!ut/p/b1/04_Sj9CPyk…

    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 131, Column 26: there is no attribute "name"
    <FORM method="POST" name="ManageSearch" action="/wps/portal/!ut/p/b1/04_Sj9CPyk…

    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 131, Column 48: there is no attribute "action"
    …hod="POST" name="ManageSearch" action="/wps/portal/!ut/p/b1/04_Sj9CPykssy0xPLM…

    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 131, Column 440: element "FORM" undefined
    …GZsQ0dkaC9aN181Q1BDSThNMzFHOVBFMEk0UkdQQlIwMTBRNC8wL3NhLkFjdGlvblNlYXJjaA!!/"> 

    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 134, Column 31: end tag for "input" omitted, but OMITTAG NO was specified
           value="GoSearchAction">

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

  • Info Line 132, Column 5: start tag was here
    	   <input type="hidden" 
  • Error Line 140, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
    		class="input_search" id="textfield" onclick="textvaluehide();">

    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 137, Column 3: start tag was here
    		<input type="text" accesskey="d" 
  • Error Line 146, Column 9: required attribute "type" not specified
    	<script>

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

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

  • Error Line 154, Column 74: there is no attribute "height"
      	<table border="0" cellpadding="0" cellspacing="0" width="100%" height="100%">

    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 155, Column 97: required attribute "alt" not specified
    …g src="/portal/images/theme/moinew/spacer.gif" height="2" width="10"></td></tr>

    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 155, Column 102: end tag for "img" omitted, but OMITTAG NO was specified
    …g src="/portal/images/theme/moinew/spacer.gif" height="2" width="10"></td></tr>

    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 155, Column 26: start tag was here
    	<tr class="noPrint"><td><img src="/portal/images/theme/moinew/spacer.gif" heig…
  • Error Line 184, Column 23: document type does not allow element "div" here; assuming missing "li" start-tag
    	<div class="tab_wrap">
  • Error Line 185, Column 82: required attribute "alt" not specified
    …ss="tab_wht_c1"><img src="/portal/images/theme/moinew/tab_act_lft.gif" /></div>

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

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

  • Error Line 187, Column 82: required attribute "alt" not specified
    …ss="tab_wht_c2"><img src="/portal/images/theme/moinew/tab_act_rht.gif" /></div>

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

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

  • Error Line 212, Column 83: required attribute "alt" not specified
    …="tab_gry_c1"><img src="/portal/images/theme/moinew/tab_inact_lft.gif" /></div>

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

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

  • Error Line 218, Column 83: required attribute "alt" not specified
    …="tab_gry_c2"><img src="/portal/images/theme/moinew/tab_inact_rht.gif" /></div>

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

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

  • Error Line 239, Column 83: required attribute "alt" not specified
    …="tab_gry_c1"><img src="/portal/images/theme/moinew/tab_inact_lft.gif" /></div>

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

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

  • Error Line 245, Column 83: required attribute "alt" not specified
    …="tab_gry_c2"><img src="/portal/images/theme/moinew/tab_inact_rht.gif" /></div>

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

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

  • Error Line 266, Column 83: required attribute "alt" not specified
    …="tab_gry_c1"><img src="/portal/images/theme/moinew/tab_inact_lft.gif" /></div>

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

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

  • Error Line 272, Column 83: required attribute "alt" not specified
    …="tab_gry_c2"><img src="/portal/images/theme/moinew/tab_inact_rht.gif" /></div>

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

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

  • Error Line 293, Column 83: required attribute "alt" not specified
    …="tab_gry_c1"><img src="/portal/images/theme/moinew/tab_inact_lft.gif" /></div>

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

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

  • Error Line 299, Column 83: required attribute "alt" not specified
    …="tab_gry_c2"><img src="/portal/images/theme/moinew/tab_inact_rht.gif" /></div>

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

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

  • Error Line 307, Column 6: end tag for "li" omitted, but OMITTAG NO was specified
    </div></div>   

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

  • Info Line 184, Column 2: start tag was here
    	<div class="tab_wrap">
  • Error Line 307, Column 6: end tag for "ul" omitted, but OMITTAG NO was specified
    </div></div>   

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

  • Info Line 172, Column 2: start tag was here
    	<ul id="nav_dd">
  • Error Line 307, Column 12: end tag for "td" omitted, but OMITTAG NO was specified
    </div></div>   

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

  • Info Line 157, Column 3: start tag was here
    		<td colspan="2">
  • Error Line 307, Column 12: end tag for "tr" omitted, but OMITTAG NO was specified
    </div></div>   

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

  • Info Line 156, Column 2: start tag was here
    	<tr>
  • Error Line 307, Column 12: end tag for "table" omitted, but OMITTAG NO was specified
    </div></div>   

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

  • Info Line 154, Column 4: start tag was here
      	<table border="0" cellpadding="0" cellspacing="0" width="100%" height="100%">
  • Error Line 325, Column 7: end tag for element "td" which is not open
    		</td>

    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 326, Column 6: end tag for element "tr" which is not open
    	</tr>

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

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

  • Error Line 327, Column 21: document type does not allow element "tr" here; assuming missing "table" start-tag
    	<tr class="noPrint"><td colspan="2">
  • Error Line 333, Column 63: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    	  <td class="wpsPageBar" align="right" valign="bottom" nowrap>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 334, Column 78: there is no attribute "background"
    …lspacing="0" height="100%" background="/portal/images/theme/moinew/dot.gif" wi…

    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 341, Column 39: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    			<td class="wpsSelectedPage" nowrap height="18">

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 354, Column 42: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    				<td class="wpsUnSelectedPage" nowrap height="18">

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 364, Column 42: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    				<td class="wpsUnSelectedPage" nowrap height="18">

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 377, Column 32: there is no attribute "align"
    <a class="more_link_new" align="left" href="/wps/portal/!ut/p/b1/hc7LCsIwFATQL5…

    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 384, Column 120: required attribute "alt" not specified
    …g src="/portal/images/theme/moinew/spacer.gif" width="10" height="3"></td></tr>

    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 384, Column 125: end tag for "img" omitted, but OMITTAG NO was specified
    …g src="/portal/images/theme/moinew/spacer.gif" width="10" height="3"></td></tr>

    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 384, Column 49: start tag was here
    …="noPrint"><td height="3" colspan="3"><img src="/portal/images/theme/moinew/sp…
  • Error Line 423, Column 16: there is no attribute "tabIndex"
    			<a tabIndex="2" href="/wps/portal/homeAR">الرئيسية</a> &gt; 

    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 485, Column 91: document type does not allow element "link" here
    …/wps/PA_WCMLocalRendering/res/ilwwcmRTL.css" rel="styleSheet" type="text/css"/>

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

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

  • Warning Line 498, Column 40: S separator in comment declaration
    … <!-- Before Alteration contextPath -- /post migration components/MOI Home/Lef…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 498, Column 41: invalid comment declaration: found character "/" outside comment but inside comment declaration
    …<!-- Before Alteration contextPath -- /post migration components/MOI Home/Left…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 498, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/Lef…
  • Warning Line 499, Column 37: S separator in comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 499, Column 38: invalid comment declaration: found character "%" outside comment but inside comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 499, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 507, Column 27: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div id="navleft_sections">

    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 508, Column 16: value of attribute "dir" cannot be "RTL"; must be one of "ltr", "rtl"
    <table dir="RTL" bgcolor="#FFFFFF" width="140" border="0" cellspacing="0" cellp…

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

  • Error Line 511, Column 8: document type does not allow element "tr" here; assuming missing "table" start-tag
    <td><tr>
  • Error Line 530, Column 12: ID "on_highlighted_path_in_navigator_L1" already defined
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…

    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 516, Column 12: ID "on_highlighted_path_in_navigator_L1" first defined here
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…
  • Error Line 544, Column 12: ID "on_highlighted_path_in_navigator_L1" already defined
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…

    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 516, Column 12: ID "on_highlighted_path_in_navigator_L1" first defined here
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…
  • Error Line 558, Column 12: ID "on_highlighted_path_in_navigator_L1" already defined
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…

    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 516, Column 12: ID "on_highlighted_path_in_navigator_L1" first defined here
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…
  • Error Line 572, Column 12: ID "on_highlighted_path_in_navigator_L1" already defined
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…

    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 516, Column 12: ID "on_highlighted_path_in_navigator_L1" first defined here
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…
  • Error Line 586, Column 12: ID "on_highlighted_path_in_navigator_L1" already defined
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…

    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 516, Column 12: ID "on_highlighted_path_in_navigator_L1" first defined here
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…
  • Error Line 600, Column 12: ID "on_highlighted_path_in_navigator_L1" already defined
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…

    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 516, Column 12: ID "on_highlighted_path_in_navigator_L1" first defined here
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…
  • Error Line 614, Column 12: ID "on_highlighted_path_in_navigator_L1" already defined
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…

    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 516, Column 12: ID "on_highlighted_path_in_navigator_L1" first defined here
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…
  • Error Line 628, Column 12: ID "on_highlighted_path_in_navigator_L1" already defined
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…

    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 516, Column 12: ID "on_highlighted_path_in_navigator_L1" first defined here
     <span id="on_highlighted_path_in_navigator_L1" class="navleft1_link"><a href='…
  • Error Line 638, Column 5: end tag for "table" omitted, but OMITTAG NO was specified
    </td></tr>

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

  • Info Line 511, Column 5: start tag was here
    <td><tr>
  • Error Line 641, Column 6: element "BR" undefined
    <BR />

    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 642, Column 30: required attribute "type" not specified
    <script language="javascript">

    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 647, 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 647, 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 651, Column 8: required attribute "type" not specified
    <script>jslocale = "ar" ;</script>

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

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

  • Error Line 652, Column 7: required attribute "type" not specified
    <style>#right_section .right_content a:link {text-decoration:none;}</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 652, Column 7: document type does not allow element "style" here
    <style>#right_section .right_content a:link {text-decoration:none;}</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 654, Column 30: required attribute "type" not specified
    <script language="javascript">

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

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

  • Warning Line 661, Column 19: character "<" is the first character of a delimiter but occurred as data
    			for(ind=0; ind < $eventsLnks.length; ind++)

    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 677, Column 20: character "<" is the first character of a delimiter but occurred as data
    				for(ind=0; ind < $eventsLnks.length; ind++)

    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 699, Column 14: character "<" is the first character of a delimiter but occurred as data
    	for( i=0; i < $pars.length; i++ )

    This message may appear in several cases:

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

    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 725, Column 38: character "&" is the first character of a delimiter but occurred as data
    if(curLoct.indexOf("myportal") >= 0 && pLinkHref.indexOf("auth")< 0 && pLinkHre…

    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 725, Column 65: character "<" is the first character of a delimiter but occurred as data
    …al") >= 0 && pLinkHref.indexOf("auth")< 0 && pLinkHref.indexOf("myportal") < 0…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 748, Column 30: required attribute "type" not specified
    <script language="javascript">

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

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

  • Warning Line 756, Column 15: character "&" is the first character of a delimiter but occurred as data
    			if(ind > 4 && ind < 8)

    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 756, Column 16: character "&" is the first character of a delimiter but occurred as data
    			if(ind > 4 && ind < 8)

    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 756, Column 22: character "<" is the first character of a delimiter but occurred as data
    			if(ind > 4 && ind < 8)

    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 816, Column 91: document type does not allow element "link" here
    …/wps/PA_WCMLocalRendering/res/ilwwcmRTL.css" rel="styleSheet" type="text/css"/>

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

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

  • Warning Line 829, Column 40: S separator in comment declaration
    … <!-- Before Alteration contextPath -- /post migration components/MOI Home/Sid…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 829, Column 41: invalid comment declaration: found character "/" outside comment but inside comment declaration
    …<!-- Before Alteration contextPath -- /post migration components/MOI Home/Side…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 829, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/Sid…
  • Warning Line 830, Column 37: S separator in comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 830, Column 38: invalid comment declaration: found character "%" outside comment but inside comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 830, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 837, Column 99: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …pan><table cellpadding="0" cellspacing="0" style="margin-top:10px;width:140px">

    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 842, Column 10: an attribute value must be a literal unless it contains only name characters
    <img src=/wps/wcm/connect/9cbcd0ec-ce8d-4476-b1a0-47dee6cf0d7d/Social_Media.gif…

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

  • Error Line 842, Column 160: an attribute value must be a literal unless it contains only name characters
    …TO=url&CACHEID=9cbcd0ec-ce8d-4476-b1a0-47dee6cf0d7d usemap=#MOI_SOCIAL_MEDIA />

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

  • Error Line 842, Column 179: required attribute "alt" not specified
    …TO=url&CACHEID=9cbcd0ec-ce8d-4476-b1a0-47dee6cf0d7d usemap=#MOI_SOCIAL_MEDIA />

    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 843, Column 29: required attribute "id" not specified
    <map name="MOI_SOCIAL_MEDIA">

    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 844, Column 101: required attribute "alt" not specified
    ….youtube.com/user/moigovsa" shape="rect" coords="2, 2, 40, 45" target="_blank">

    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 844, Column 102: end tag for "area" omitted, but OMITTAG NO was specified
    ….youtube.com/user/moigovsa" shape="rect" coords="2, 2, 40, 45" target="_blank">

    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 844, Column 1: start tag was here
    <area href="http://www.youtube.com/user/moigovsa" shape="rect" coords="2, 2, 40…
  • Error Line 845, Column 101: required attribute "alt" not specified
    …itter.com/#!/MOIeServices" shape="rect" coords="48, 2, 88, 45" target="_blank">

    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 845, Column 102: end tag for "area" omitted, but OMITTAG NO was specified
    …itter.com/#!/MOIeServices" shape="rect" coords="48, 2, 88, 45" target="_blank">

    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 845, Column 1: start tag was here
    <area href="https://twitter.com/#!/MOIeServices" shape="rect" coords="48, 2, 88…
  • Error Line 846, Column 104: required attribute "alt" not specified
    …cebook.com/moi.eServices" shape="rect" coords="96, 2, 148, 45" target="_blank">

    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 846, Column 105: end tag for "area" omitted, but OMITTAG NO was specified
    …cebook.com/moi.eServices" shape="rect" coords="96, 2, 148, 45" target="_blank">

    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 846, Column 1: start tag was here
    <area href="http://www.facebook.com/moi.eServices" shape="rect" coords="96, 2, …
  • Error Line 848, Column 95: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 848, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 848, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 859, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 859, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 866, Column 253: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 870, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 870, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 876, Column 253: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 878, Column 95: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 878, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 878, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 884, Column 254: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 886, Column 95: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 886, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 886, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 892, Column 252: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 894, Column 95: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 894, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 894, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 900, Column 245: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 903, Column 95: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 903, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 903, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 911, Column 247: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 913, Column 95: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 913, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 913, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 920, Column 195: required attribute "alt" not specified
    …ID=e8a30ee5-53ba-4a61-aa76-1c997ac0e4f7" border="0" width="140" height="40"  />

    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 921, Column 95: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 921, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 921, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Warning Line 925, Column 446: cannot generate system identifier for general entity "WCM_GLOBAL_CONTEXT"
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/

    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 925, Column 446: general entity "WCM_GLOBAL_CONTEXT" not defined and no default entity
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/

    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 925, Column 464: reference not terminated by REFC delimiter
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/

    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 925, Column 464: reference to external entity in attribute value
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/

    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 925, Column 464: reference to entity "WCM_GLOBAL_CONTEXT" for which no system identifier could be generated
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/

    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 925, Column 445: entity was defined here
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/
  • Warning Line 926, Column 50: cannot generate system identifier for general entity "idOfFaq2Open"
    …+Diwan/MOI+Home+Content+AR/Home/FAQs/&idOfFaq2Open=a2ecbbb3-4066-4760-a383-5aa…

    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 926, Column 50: general entity "idOfFaq2Open" not defined and no default entity
    …+Diwan/MOI+Home+Content+AR/Home/FAQs/&idOfFaq2Open=a2ecbbb3-4066-4760-a383-5aa…

    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 926, Column 62: reference not terminated by REFC delimiter
    …+Home+Content+AR/Home/FAQs/&idOfFaq2Open=a2ecbbb3-4066-4760-a383-5aabcd4107b0">

    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 926, Column 62: reference to external entity in attribute value
    …+Home+Content+AR/Home/FAQs/&idOfFaq2Open=a2ecbbb3-4066-4760-a383-5aabcd4107b0">

    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 926, Column 62: reference to entity "idOfFaq2Open" for which no system identifier could be generated
    …+Home+Content+AR/Home/FAQs/&idOfFaq2Open=a2ecbbb3-4066-4760-a383-5aabcd4107b0">

    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 926, Column 49: entity was defined here
    …I+Diwan/MOI+Home+Content+AR/Home/FAQs/&idOfFaq2Open=a2ecbbb3-4066-4760-a383-5a…
  • Error Line 928, Column 255: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 930, Column 95: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 930, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 930, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 936, Column 12: syntax of attribute value does not conform to declared value
    <a target="" title="طريقة التسجيل والتفعيل" href="/wps/portal/passports/!ut/p/b…

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

  • Error Line 940, Column 95: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 940, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 940, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 945, Column 12: syntax of attribute value does not conform to declared value
    <a target="" title="مكاتب التسجيل و التفعيل" href="/wps/portal/passports/!ut/p/…

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

  • Error Line 948, Column 95: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

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

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

  • Error Line 948, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

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

  • Info Line 948, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Warning Line 952, Column 9: multiple comments in comment declaration
    <!----------- Traffic Violation Query End ------>
  • Warning Line 952, Column 43: multiple comments in comment declaration
    <!----------- Traffic Violation Query End ------>
  • Warning Line 952, Column 47: multiple comments in comment declaration
    <!----------- Traffic Violation Query End ------>
  • Error Line 956, Column 236: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 959, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 959, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Warning Line 961, Column 9: multiple comments in comment declaration
    <!----------- Traffic Violation Query End ------>
  • Warning Line 961, Column 43: multiple comments in comment declaration
    <!----------- Traffic Violation Query End ------>
  • Warning Line 961, Column 47: multiple comments in comment declaration
    <!----------- Traffic Violation Query End ------>
  • Error Line 966, Column 12: syntax of attribute value does not conform to declared value
    <a target="" title="" href="/wps/portal/publicsecurity/shomoosAR">

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

  • Error Line 969, Column 172: required attribute "alt" not specified
    …AJPERES&amp;CACHEID=3f2312804732b0daae8afeaee640ae5d/1" border="0"  title="" />

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

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

  • Error Line 972, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

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

  • Info Line 972, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 976, Column 177: required attribute "alt" not specified
    …ID=44e21c9c-1124-45e0-9d39-400783956c8d" border="0" width="140" height="40"  />

    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 980, Column 96: end tag for "hr" omitted, but OMITTAG NO was specified
    …r-style: dashed; border-color: green; border-width: 1px 0pt 0pt; height: 0pt;">

    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 980, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 1021, Column 91: document type does not allow element "link" here
    …/wps/PA_WCMLocalRendering/res/ilwwcmRTL.css" rel="styleSheet" type="text/css"/>

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

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

  • Warning Line 1034, Column 40: S separator in comment declaration
    … <!-- Before Alteration contextPath -- /post migration components/MOI Home/Ima…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1034, Column 41: invalid comment declaration: found character "/" outside comment but inside comment declaration
    …<!-- Before Alteration contextPath -- /post migration components/MOI Home/Imag…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1034, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/Ima…
  • Warning Line 1035, Column 37: S separator in comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1035, Column 38: invalid comment declaration: found character "%" outside comment but inside comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1035, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 1042, Column 31: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
          	           <span><table> <tbody> <tr> <td><script type="text/javascript"…

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

  • Warning Line 1042, Column 200: cannot generate system identifier for general entity "CACHEID"
    …ndar_moi_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d3…

    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 1042, Column 200: general entity "CACHEID" not defined and no default entity
    …ndar_moi_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d3…

    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 1042, Column 207: reference not terminated by REFC delimiter
    …i_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d3'></scr…

    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 1042, Column 207: reference to external entity in attribute value
    …i_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d3'></scr…

    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 1042, Column 207: reference to entity "CACHEID" for which no system identifier could be generated
    …i_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d3'></scr…

    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 1042, Column 199: entity was defined here
    …endar_moi_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d…
  • Error Line 1055, Column 404: an attribute value must be a literal unless it contains only name characters
    …ive/moi_news_17-02-2013a_ar'><img src=/wps/wcm/connect/8ca0e074-dbc5-43ab-b5f6…

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

  • Error Line 1055, Column 809: required attribute "alt" not specified
    …RES&CACHEID=8ca0e074-dbc5-43ab-b5f6-b38d2dea0d85 width="464" height="300"/></a>

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

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

  • Error Line 1058, Column 536: end tag for element "br" which is not open
    …_ar'>وزير الاقتصاد والتخطيط يزور مركز المعلومات الوطني بوزارة الداخلية</a></br>

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

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

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

  • Error Line 1109, Column 404: an attribute value must be a literal unless it contains only name characters
    …ive/moi_news_09-02-2013a_ar'><img src=/wps/wcm/connect/9ada02d5-ec6b-4c2f-84eb…

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

  • Error Line 1109, Column 575: required attribute "alt" not specified
    …RES&CACHEID=9ada02d5-ec6b-4c2f-84eb-99befa69f92f width="464" height="300"/></a>

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

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

  • Error Line 1112, Column 516: end tag for element "br" which is not open
    …moi_news_09-02-2013a_ar'>سمو وزير الداخلية يثمن جهود &quot;تراحم&quot;</a></br>

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

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

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

  • Error Line 1163, Column 404: an attribute value must be a literal unless it contains only name characters
    …ive/moi_news_29-01-2013a_ar'><img src=/wps/wcm/connect/8577ef9f-9283-4912-8490…

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

  • Error Line 1163, Column 1032: required attribute "alt" not specified
    …RES&CACHEID=8577ef9f-9283-4912-8490-af825ffb76ad width="464" height="300"/></a>

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

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

  • Error Line 1166, Column 563: end tag for element "br" which is not open
    …ل تخريج الأفراد الملتحقين بدورة التأهيل الفني على أعمال الدفاع المدني </a></br>

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

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

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

  • Error Line 1260, Column 91: document type does not allow element "link" here
    …/wps/PA_WCMLocalRendering/res/ilwwcmRTL.css" rel="styleSheet" type="text/css"/>

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

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

  • Warning Line 1273, Column 40: S separator in comment declaration
    … <!-- Before Alteration contextPath -- /post migration components/MOI Home/MOI…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1273, Column 41: invalid comment declaration: found character "/" outside comment but inside comment declaration
    …<!-- Before Alteration contextPath -- /post migration components/MOI Home/MOI_…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1273, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/MOI…
  • Warning Line 1274, Column 37: S separator in comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1274, Column 38: invalid comment declaration: found character "%" outside comment but inside comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1274, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 1281, Column 63: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …       <span><table cellpadding="0" cellspacing="0"><tr class="hideOnAuth"><td>

    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 1307, 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 1307, 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 1320, Column 10: ID "mid_content" already defined
    <div id="mid_content" style="margin-top:1px; padding-top:1px">

    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 1284, Column 10: ID "mid_content" first defined here
    <div id="mid_content">
  • Error Line 1368, Column 273: required attribute "alt" not specified
    …0c3b1a98-2e97-4659-a721-17a55239fbe7" border="0" width="32" height="28"  /></a>

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

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

  • Error Line 1369, Column 272: required attribute "alt" not specified
    …1a56a030-0859-423d-b574-d395434385ee" border="0" width="32" height="28"  /></a>

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

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

  • Error Line 1370, Column 275: required attribute "alt" not specified
    …08f3ab00-783d-4053-95cf-d414a1c24806" border="0" width="32" height="28"  /></a>

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

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

  • Error Line 1435, Column 91: document type does not allow element "link" here
    …/wps/PA_WCMLocalRendering/res/ilwwcmRTL.css" rel="styleSheet" type="text/css"/>

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

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

  • Warning Line 1448, Column 40: S separator in comment declaration
    … <!-- Before Alteration contextPath -- /post migration components/MOI Home/Sec…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1448, Column 41: invalid comment declaration: found character "/" outside comment but inside comment declaration
    …<!-- Before Alteration contextPath -- /post migration components/MOI Home/Sect…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1448, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/Sec…
  • Warning Line 1449, Column 37: S separator in comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1449, Column 38: invalid comment declaration: found character "%" outside comment but inside comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1449, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 1456, Column 63: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<table cellspacing="0" cellpadding="0"><tbody><tr class="hideOnAuth"><td><div …

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

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

  • Error Line 1456, Column 107: ID "mid_content" already defined
    …ng="0" cellpadding="0"><tbody><tr class="hideOnAuth"><td><div id="mid_content">

    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 1284, Column 10: ID "mid_content" first defined here
    <div id="mid_content">
  • Error Line 1462, Column 103: there is no attribute "BORDER"
    …heme/moinew/sectors_quicklaunch.jpg" BORDER="0" WIDTH="198" HEIGHT="76"/></div>

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

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

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

  • Error Line 1462, Column 113: there is no attribute "WIDTH"
    …heme/moinew/sectors_quicklaunch.jpg" BORDER="0" WIDTH="198" HEIGHT="76"/></div>

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

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

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

  • Error Line 1462, Column 126: there is no attribute "HEIGHT"
    …heme/moinew/sectors_quicklaunch.jpg" BORDER="0" WIDTH="198" HEIGHT="76"/></div>

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

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

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

  • Error Line 1462, Column 131: required attribute "alt" not specified
    …heme/moinew/sectors_quicklaunch.jpg" BORDER="0" WIDTH="198" HEIGHT="76"/></div>

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

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

  • Error Line 1468, Column 35: required attribute "action" not specified
    <form name="secform" id="secform" >

    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 1497, Column 199: required attribute "alt" not specified
    …secbtn" style="cursor:hand;display:none;" onclick="javascript:URLGo();"/></div>

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

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

  • Error Line 1502, Column 30: required attribute "type" not specified
    <script language="javascript">

    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 1543, Column 10: ID "mid_content" already defined
    <div id="mid_content" style="margin-top:1px; padding-top:1px">

    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 1284, Column 10: ID "mid_content" first defined here
    <div id="mid_content">
  • Error Line 1582, Column 232: required attribute "alt" not specified
    …r:hand;display:none;" onclick="javascript:URLGoQuickLaunch('sectors');"/></div>

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

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

  • Error Line 1618, Column 232: required attribute "alt" not specified
    …and;display:none;" onclick="javascript:URLGoQuickLaunch('emirates');"/></div>		

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

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

  • Error Line 1638, Column 254: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 1646, Column 243: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 1653, Column 12: syntax of attribute value does not conform to declared value
    <a target="" title="طريقة التسجيل والتفعيل" href="/wps/portal/passports/!ut/p/b…

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

  • Error Line 1655, Column 248: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 1661, Column 12: syntax of attribute value does not conform to declared value
    <a target="" title="مكاتب التسجيل و التفعيل" href="/wps/portal/passports/!ut/p/…

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

  • Error Line 1663, Column 248: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 1700, Column 91: document type does not allow element "link" here
    …/wps/PA_WCMLocalRendering/res/ilwwcmRTL.css" rel="styleSheet" type="text/css"/>

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

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

  • Warning Line 1713, Column 40: S separator in comment declaration
    … <!-- Before Alteration contextPath -- /post migration components/Civil Defenc…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1713, Column 41: invalid comment declaration: found character "/" outside comment but inside comment declaration
    …<!-- Before Alteration contextPath -- /post migration components/Civil Defence…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1713, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/Civil Defenc…
  • Warning Line 1714, Column 37: S separator in comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FCivil Defen…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1714, Column 38: invalid comment declaration: found character "%" outside comment but inside comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FCivil Defen…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1714, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FCivil Defen…
  • Error Line 1755, Column 91: document type does not allow element "link" here
    …/wps/PA_WCMLocalRendering/res/ilwwcmRTL.css" rel="styleSheet" type="text/css"/>

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

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

  • Warning Line 1768, Column 40: S separator in comment declaration
    … <!-- Before Alteration contextPath -- /post migration components/MOI Home/Fro…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1768, Column 41: invalid comment declaration: found character "/" outside comment but inside comment declaration
    …<!-- Before Alteration contextPath -- /post migration components/MOI Home/Fron…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1768, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/Fro…
  • Warning Line 1769, Column 37: S separator in comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1769, Column 38: invalid comment declaration: found character "%" outside comment but inside comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1769, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 1776, Column 31: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
          	           <span><table><tbody>

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

  • Warning Line 1779, Column 166: reference not terminated by REFC delimiter
    …i_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d3'></scr…

    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 1779, Column 166: reference to external entity in attribute value
    …i_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d3'></scr…

    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 1779, Column 166: reference to entity "CACHEID" for which no system identifier could be generated
    …i_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d3'></scr…

    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 1042, Column 199: entity was defined here
    …endar_moi_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d…
  • Error Line 1783, Column 37: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <h1 style="font-size:18px">مركز أبحاث مكافحة الجريمة يعقد ورشة عمل بع…

    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 1787, Column 13: end tag for element "br" which is not open
            </br>

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

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

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

  • Error Line 1868, Column 91: document type does not allow element "link" here
    …/wps/PA_WCMLocalRendering/res/ilwwcmRTL.css" rel="styleSheet" type="text/css"/>

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

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

  • Warning Line 1881, Column 40: S separator in comment declaration
    … <!-- Before Alteration contextPath -- /post migration components/MOI Home/MOI…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1881, Column 41: invalid comment declaration: found character "/" outside comment but inside comment declaration
    …<!-- Before Alteration contextPath -- /post migration components/MOI Home/MOI_…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1881, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/MOI…
  • Warning Line 1882, Column 37: S separator in comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1882, Column 38: invalid comment declaration: found character "%" outside comment but inside comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1882, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 1889, Column 31: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
          	           <span><table>

    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 1895, Column 250: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Warning Line 1900, Column 507: reference not terminated by REFC delimiter
    …970IQ9TV96B0GI0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/Command+and+Control/Co…

    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 1900, Column 507: reference to external entity in attribute value
    …970IQ9TV96B0GI0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/Command+and+Control/Co…

    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 1900, Column 507: reference to entity "WCM_GLOBAL_CONTEXT" for which no system identifier could be generated
    …970IQ9TV96B0GI0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/Command+and+Control/Co…

    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 925, Column 445: entity was defined here
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/
  • Error Line 1900, Column 791: required attribute "alt" not specified
    …540d55b4c13d/1" border="0"  title="" /></a></td><td width="10px"></td><td><a h…

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

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

  • Warning Line 1900, Column 1212: reference not terminated by REFC delimiter
    …970IQ9TV96B0GI0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/Command+and+Control/Co…

    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 1900, Column 1212: reference to external entity in attribute value
    …970IQ9TV96B0GI0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/Command+and+Control/Co…

    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 1900, Column 1212: reference to entity "WCM_GLOBAL_CONTEXT" for which no system identifier could be generated
    …970IQ9TV96B0GI0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/Command+and+Control/Co…

    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 925, Column 445: entity was defined here
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/
  • Error Line 1900, Column 1494: required attribute "alt" not specified
    …80-a6be-540d55b4c13d/2" border="0"  title="" /></a></td></tr></table></td></tr>

    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 1909, Column 12: syntax of attribute value does not conform to declared value
    <a target="" title="استعرض الكل" href="/auth/portal/4c/dpageAR?WCM_GLOBAL_CONTE…

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

  • Error Line 1909, Column 161: value of attribute "id" invalid: "4" cannot start a name
    …ol/command+and+control+ar/statments/"  id="4cNews_viewall_link">استعرض الكل</a>

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

  • Error Line 1936, Column 12: syntax of attribute value does not conform to declared value
    <a target="" title="استعرض الكل" href="/wps/portal/4c/dpageAR?WCM_GLOBAL_CONTEX…

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

  • Error Line 1936, Column 154: value of attribute "id" invalid: "4" cannot start a name
    …control/command+and+control+ar/news/"  id="4cNews_viewall_link">استعرض الكل</a>

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

  • Error Line 1936, Column 154: ID "4cNews_viewall_link" already defined
    …control/command+and+control+ar/news/"  id="4cNews_viewall_link">استعرض الكل</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 1909, Column 161: ID "4cNews_viewall_link" first defined here
    …ol/command+and+control+ar/statments/"  id="4cNews_viewall_link">استعرض الكل</a>
  • Warning Line 1941, Column 162: reference not terminated by REFC delimiter
    …B9%D8%A7%D9%85.jpg?MOD=AJPERES&CACHEID=76e5d33e-42ab-40c3-b2b0-1e4a5924e5ca" w…

    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 1941, Column 162: reference to external entity in attribute value
    …B9%D8%A7%D9%85.jpg?MOD=AJPERES&CACHEID=76e5d33e-42ab-40c3-b2b0-1e4a5924e5ca" w…

    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 1941, Column 162: reference to entity "CACHEID" for which no system identifier could be generated
    …B9%D8%A7%D9%85.jpg?MOD=AJPERES&CACHEID=76e5d33e-42ab-40c3-b2b0-1e4a5924e5ca" w…

    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 1042, Column 199: entity was defined here
    …endar_moi_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d…
  • Error Line 1941, Column 235: required attribute "alt" not specified
    …CHEID=76e5d33e-42ab-40c3-b2b0-1e4a5924e5ca" width="65" height="65" border="0"/>

    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 1953, Column 5: end tag for element "li" which is not open
    </li>

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

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

  • Error Line 1961, Column 12: syntax of attribute value does not conform to declared value
    <a target="" title="استعرض الكل" href="#"  id="events_viewall_link">استعرض الكل…

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

  • Error Line 1967, Column 33: there is no attribute "onClick"
    <span class="jFlowPrev" onClick="left_2()"> <img src="/wps/wcm/connect/cb721f00…

    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 1967, Column 214: required attribute "alt" not specified
    …b721f004548a92e8619d784e2b12f11" border="0" width="28" height="28"  /> </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 1973, Column 216: required attribute "alt" not specified
    …04548a81a8613d784e2b12f11" border="0" width="28" height="28"  /> </span> </div>

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

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

  • Error Line 1977, Column 170: required attribute "alt" not specified
    …EID=ad634c85-3347-44dd-9e91-92ce791e2b93" border="0" width="65" height="65"  />

    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 2004, Column 196: required attribute "alt" not specified
    …EID=21442bae-37b6-4a5a-b473-5e60a84a019e" border="0" width="75" height="65"  />

    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 2032, Column 30: required attribute "type" not specified
    <script language="javascript">var eventsCurrentLangParam = "AR" ;</script>

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

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

  • Error Line 2034, Column 30: required attribute "type" not specified
    <script language="javascript">

    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 2067, Column 30: required attribute "type" not specified
    <script language="javascript">

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

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

  • Warning Line 2093, Column 51: character "&" is the first character of a delimiter but occurred as data
    						var ps = ( $(this).attr("href") ).split(/\?|&/);

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

    This message may appear in several cases:

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

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

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

  • Warning Line 2204, Column 40: S separator in comment declaration
    … <!-- Before Alteration contextPath -- /post migration components/MOI Home/Emi…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 2204, Column 41: invalid comment declaration: found character "/" outside comment but inside comment declaration
    …<!-- Before Alteration contextPath -- /post migration components/MOI Home/Emir…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 2204, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/Emi…
  • Warning Line 2205, Column 37: S separator in comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 2205, Column 38: invalid comment declaration: found character "%" outside comment but inside comment declaration
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 2205, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 2212, Column 63: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
          	           <span><table cellpadding="0" cellspacing="4">

    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 2223, Column 33: required attribute "action" not specified
    <form name="emform" id="emform" >

    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 2242, Column 196: required attribute "alt" not specified
    …"embtn" style="cursor:hand;display:none;" onclick="javascript:URLGo();"/></div>

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

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

  • Error Line 2254, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </td></tr>

    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 2252, Column 1: start tag was here
    <div class="heading_events" style="width:302px; margin-right:0px; margin-top:0p…
  • Error Line 2258, Column 243: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 2272, Column 243: required attribute "alt" not specified
    …yle="margin-left: auto; margin-right: auto;display:block;text-align:center;" />

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

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

  • Error Line 2285, Column 221: required attribute "alt" not specified
    …165ad66537/1" border="0"  title="" align="left" usemap="#MOI_SOCIAL_MEDIA12" />

    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 2287, Column 31: required attribute "id" not specified
    <map name="MOI_SOCIAL_MEDIA12">

    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 2288, Column 480: required attribute "alt" not specified
    …es+AR/cva_my+data_default_ar" shape="rect" coords="1,2,152,45" target="_blank">

    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 2288, Column 481: end tag for "area" omitted, but OMITTAG NO was specified
    …es+AR/cva_my+data_default_ar" shape="rect" coords="1,2,152,45" target="_blank">

    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 2288, Column 3: start tag was here
      <area href="http://www.moi.gov.sa/wps/portal/civilaffairs/!ut/p/b1/04_Sj9CPyk…
  • Error Line 2289, Column 143: required attribute "alt" not specified
    …/AppointMentsDefault.aspx" shape="rect" coords="158,-5,309,38" target="_blank">

    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 2289, Column 144: end tag for "area" omitted, but OMITTAG NO was specified
    …/AppointMentsDefault.aspx" shape="rect" coords="158,-5,309,38" target="_blank">

    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 2289, Column 3: start tag was here
      <area href="http://eservices.moi.gov.sa/ES/Public/AppointMents/AppointMentsDe…
  • Error Line 2331, Column 16: there is no attribute "class"
    		<TABLE class="prayerPortlet" cellspacing="1" cellpadding="1">

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

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

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

  • Error Line 2331, Column 44: there is no attribute "cellspacing"
    		<TABLE class="prayerPortlet" cellspacing="1" cellpadding="1">

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

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

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

  • Error Line 2331, Column 60: there is no attribute "cellpadding"
    		<TABLE class="prayerPortlet" cellspacing="1" cellpadding="1">

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

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

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

  • Error Line 2331, Column 63: element "TABLE" undefined
    		<TABLE class="prayerPortlet" cellspacing="1" cellpadding="1">

    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 2332, Column 10: element "TBODY" undefined
    			<TBODY>

    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 2333, Column 16: there is no attribute "height"
    				<TR height="28">

    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 2333, Column 20: element "TR" undefined
    				<TR height="28">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2334, Column 18: there is no attribute "colspan"
    					<TD colspan="3" background='/wps/PA_MyPrayerTime_1/images/header_box_bg.gi…

    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 2334, Column 33: there is no attribute "background"
    					<TD colspan="3" background='/wps/PA_MyPrayerTime_1/images/header_box_bg.gi…

    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 2334, Column 82: element "TD" undefined
    … colspan="3" background='/wps/PA_MyPrayerTime_1/images/header_box_bg.gif'></TD>

    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 2335, Column 33: there is no attribute "background"
    				<td colspan="11" background='/wps/PA_MyPrayerTime_1/images/header_box_bg.gi…

    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 2335, Column 89: element "TABLE" undefined
    …n="11" background='/wps/PA_MyPrayerTime_1/images/header_box_bg.gif'><TABLE><TR>

    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 2335, Column 93: element "TR" undefined
    …n="11" background='/wps/PA_MyPrayerTime_1/images/header_box_bg.gif'><TABLE><TR>

    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 2336, Column 10: element "TD" undefined
    					<TD ><b><span id="viewns_Z7_B00E9B1A0O0080IHJ5GBO50066_:form1:text3" class…

    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 2337, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2338, Column 10: element "TD" undefined
    					<TD ><b><span id="viewns_Z7_B00E9B1A0O0080IHJ5GBO50066_:form1:text5" class…

    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 2339, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2340, Column 10: element "TD" undefined
    					<TD ><b><span id="viewns_Z7_B00E9B1A0O0080IHJ5GBO50066_:form1:text7" class…

    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 2341, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2342, Column 10: element "TD" undefined
    					<TD ><b>

    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 2344, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2345, Column 10: element "TD" undefined
    					<TD ><b><span id="viewns_Z7_B00E9B1A0O0080IHJ5GBO50066_:form1:text11" clas…

    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 2346, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2347, Column 10: element "TD" undefined
    					<TD ><b><span id="viewns_Z7_B00E9B1A0O0080IHJ5GBO50066_:form1:text13" clas…

    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 2352, Column 29: there is no attribute "bgcolor"
    				<TR height="25" bgcolor="#f8f8f8">

    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 2352, Column 38: element "TR" undefined
    				<TR height="25" bgcolor="#f8f8f8">

    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 2353, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2354, Column 10: element "TD" undefined
    					<TD ><b>الرياض</b></TD>

    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 2355, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2356, Column 9: element "TD" undefined
    					<TD>05:04</TD>

    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 2357, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2358, Column 10: element "TD" undefined
    					<TD >06:25</TD>

    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 2359, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2360, Column 10: element "TD" undefined
    					<TD >12:07</TD>

    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 2361, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2362, Column 10: element "TD" undefined
    					<TD >03:23</TD>

    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 2363, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2364, Column 10: element "TD" undefined
    					<TD >05:49</TD>

    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 2365, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2366, Column 10: element "TD" undefined
    					<TD >07:19</TD>

    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 2371, Column 38: element "TR" undefined
    				<TR height="25" bgcolor="#f8f8f8">

    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 2372, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2373, Column 10: element "TD" undefined
    					<TD ><b>المدينة المنورة</b></TD>

    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 2374, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2375, Column 9: element "TD" undefined
    					<TD>05:33</TD>

    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 2376, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2377, Column 10: element "TD" undefined
    					<TD >06:53</TD>

    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 2378, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2379, Column 10: element "TD" undefined
    					<TD >12:36</TD>

    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 2380, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2381, Column 10: element "TD" undefined
    					<TD >03:52</TD>

    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 2382, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2383, Column 10: element "TD" undefined
    					<TD >06:18</TD>

    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 2384, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2385, Column 10: element "TD" undefined
    					<TD >07:48</TD>

    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 2390, Column 38: element "TR" undefined
    				<TR height="25" bgcolor="#f8f8f8">

    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 2391, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2392, Column 10: element "TD" undefined
    					<TD ><b>مكة المكرمة</b></TD>

    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 2393, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2394, Column 9: element "TD" undefined
    					<TD>05:31</TD>

    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 2395, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2396, Column 10: element "TD" undefined
    					<TD >06:50</TD>

    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 2397, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2398, Column 10: element "TD" undefined
    					<TD >12:35</TD>

    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 2399, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2400, Column 10: element "TD" undefined
    					<TD >03:53</TD>

    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 2401, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2402, Column 10: element "TD" undefined
    					<TD >06:20</TD>

    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 2403, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2404, Column 10: element "TD" undefined
    					<TD >07:50</TD>

    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 2409, Column 38: element "TR" undefined
    				<TR height="25" bgcolor="#f8f8f8">

    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 2410, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2411, Column 10: element "TD" undefined
    					<TD ><b>الدمام</b></TD>

    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 2412, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2413, Column 9: element "TD" undefined
    					<TD>04:51</TD>

    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 2414, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2415, Column 10: element "TD" undefined
    					<TD >06:13</TD>

    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 2416, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2417, Column 10: element "TD" undefined
    					<TD >11:54</TD>

    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 2418, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2419, Column 10: element "TD" undefined
    					<TD >03:09</TD>

    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 2420, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2421, Column 10: element "TD" undefined
    					<TD >05:34</TD>

    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 2422, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2423, Column 10: element "TD" undefined
    					<TD >07:04</TD>

    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 2428, Column 38: element "TR" undefined
    				<TR height="25" bgcolor="#f8f8f8">

    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 2429, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2430, Column 10: element "TD" undefined
    					<TD ><b>جدة</b></TD>

    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 2431, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2432, Column 9: element "TD" undefined
    					<TD>05:33</TD>

    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 2433, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2434, Column 10: element "TD" undefined
    					<TD >06:52</TD>

    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 2435, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2436, Column 10: element "TD" undefined
    					<TD >12:37</TD>

    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 2437, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2438, Column 10: element "TD" undefined
    					<TD >03:55</TD>

    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 2439, Column 10: element "TD" undefined
    					<TD ></TD>

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

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

    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 2441, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2442, Column 10: element "TD" undefined
    					<TD >07:53</TD>

    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 2447, Column 38: element "TR" undefined
    				<TR height="25" bgcolor="#f8f8f8">

    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 2448, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2449, Column 10: element "TD" undefined
    					<TD ><b>القصيم</b></TD>

    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 2450, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2451, Column 9: element "TD" undefined
    					<TD>05:17</TD>

    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 2452, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2453, Column 10: element "TD" undefined
    					<TD >06:39</TD>

    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 2454, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2455, Column 10: element "TD" undefined
    					<TD >12:20</TD>

    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 2456, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2457, Column 10: element "TD" undefined
    					<TD >03:35</TD>

    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 2458, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2459, Column 10: element "TD" undefined
    					<TD >06:00</TD>

    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 2460, Column 10: element "TD" undefined
    					<TD ></TD>

    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 2461, Column 10: element "TD" undefined
    					<TD >07:30</TD>

    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 2466, Column 22: element "TR" undefined
    <TR bgcolor="#f8f8f8"><td colspan="14" align="right" class="more_link_new">

    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 2483, Column 6: end tag for element "div" which is not open
    </div>

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

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

  • Error Line 2490, Column 216: end tag for "br" omitted, but OMITTAG NO was specified
    … class="footer_logo_margin" /></a><br>الوصلات الخارجية الموجودة في البوابة هي …

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

  • Info Line 2490, Column 212: start tag was here
    …="0" class="footer_logo_margin" /></a><br>الوصلات الخارجية الموجودة في البوابة…
  • Warning Line 2497, Column 438: reference not terminated by REFC delimiter
    …1F0IQU3U4N420O0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/moi+diwan/MOI+Home+Con…

    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 2497, Column 438: reference to external entity in attribute value
    …1F0IQU3U4N420O0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/moi+diwan/MOI+Home+Con…

    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 2497, Column 438: reference to entity "WCM_GLOBAL_CONTEXT" for which no system identifier could be generated
    …1F0IQU3U4N420O0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/moi+diwan/MOI+Home+Con…

    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 925, Column 445: entity was defined here
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/
  • Warning Line 2504, Column 438: reference not terminated by REFC delimiter
    …1F0IQU3U4N420O0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/moi+diwan/MOI+Home+Con…

    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 2504, Column 438: reference to external entity in attribute value
    …1F0IQU3U4N420O0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/moi+diwan/MOI+Home+Con…

    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 2504, Column 438: reference to entity "WCM_GLOBAL_CONTEXT" for which no system identifier could be generated
    …1F0IQU3U4N420O0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/moi+diwan/MOI+Home+Con…

    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 925, Column 445: entity was defined here
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/
  • Warning Line 2511, Column 319: cannot generate system identifier for general entity "cID"
    …A0/?nID=Z6_5CPCI8M31GPU702F74JC6K80K4&cID=Z6_5CPCI8M31GPU702F74JC6K80K4">البحث…

    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 2511, Column 319: general entity "cID" not defined and no default entity
    …A0/?nID=Z6_5CPCI8M31GPU702F74JC6K80K4&cID=Z6_5CPCI8M31GPU702F74JC6K80K4">البحث…

    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 2511, Column 322: reference not terminated by REFC delimiter
    …?nID=Z6_5CPCI8M31GPU702F74JC6K80K4&cID=Z6_5CPCI8M31GPU702F74JC6K80K4">البحث</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 2511, Column 322: reference to external entity in attribute value
    …?nID=Z6_5CPCI8M31GPU702F74JC6K80K4&cID=Z6_5CPCI8M31GPU702F74JC6K80K4">البحث</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 2511, Column 322: reference to entity "cID" for which no system identifier could be generated
    …?nID=Z6_5CPCI8M31GPU702F74JC6K80K4&cID=Z6_5CPCI8M31GPU702F74JC6K80K4">البحث</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 2511, Column 318: entity was defined here
    …DA0/?nID=Z6_5CPCI8M31GPU702F74JC6K80K4&cID=Z6_5CPCI8M31GPU702F74JC6K80K4">البح…
  • Warning Line 2530, Column 440: reference not terminated by REFC delimiter
    …1F0IQU3U4N420O0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/moi+diwan/MOI+Home+Con…

    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 2530, Column 440: reference to external entity in attribute value
    …1F0IQU3U4N420O0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/moi+diwan/MOI+Home+Con…

    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 2530, Column 440: reference to entity "WCM_GLOBAL_CONTEXT" for which no system identifier could be generated
    …1F0IQU3U4N420O0_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/connect/moi+diwan/MOI+Home+Con…

    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 925, Column 445: entity was defined here
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/
  • Warning Line 2532, Column 323: reference not terminated by REFC delimiter
    …?nID=Z6_5CPCI8M31GPU702F74JC6K80K4&cID=Z6_5CPCI8M31GPU702F74JC6K80K4">خريطة ال…

    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 2532, Column 323: reference to external entity in attribute value
    …?nID=Z6_5CPCI8M31GPU702F74JC6K80K4&cID=Z6_5CPCI8M31GPU702F74JC6K80K4">خريطة ال…

    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 2532, Column 323: reference to entity "cID" for which no system identifier could be generated
    …?nID=Z6_5CPCI8M31GPU702F74JC6K80K4&cID=Z6_5CPCI8M31GPU702F74JC6K80K4">خريطة ال…

    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 2511, Column 318: entity was defined here
    …DA0/?nID=Z6_5CPCI8M31GPU702F74JC6K80K4&cID=Z6_5CPCI8M31GPU702F74JC6K80K4">البح…
  • Error Line 2537, Column 7: end tag for "body" omitted, but OMITTAG NO was specified
    </html>

    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 64, Column 2: start tag was here
    	<div id="toolsList" class="sharePost_new noPrint">

Visitor Analysis

Daily Visitor
  • 23.333 visits

In Page Analysis