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

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

Website Meta Analysis

  • Title
    وزارة الداخلية المملكة العربية السعودية
  • Meta Keyword
  • Meta Description
    Delicious Digg Facebook Google مستخدم جديد؟ | تسجيل الدخول  الرئيسية   الأفراد   الحكومة   الأعمال   الخدمات الإلكترونية  الثلاثاء 23 شعبان 1434 / 2 يوليو 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, 02 Jul 2013 15:42:53 GMT
  • ibm-web2-location: /wps/portal/!ut/p/b1/04_SjzQ0NbYwsTA0MDfVj9CPykssy0xPLMnMz0vMAfGjzOJNnQOcPS18jQ3dA0LNDYzczE28nM28LQy8TYAKIoEKDHAARwNC-oMTi_TD9aPwKjMxhipwdnf0MDH3MTCw8HE3NfB09AgNsgw0NjZwhCnA4w4_j_zcVP3cqByLYE9dRwDU0IbJ/dl4/d5/L2dBISEvZ0FBIS9nQSEh/
  • content-location: /wps/portal/!ut/p/b1/04_SjzQ0NbYwsTA0MDfVj9CPykssy0xPLMnMz0vMAfGjzOJNnQOcPS18jQ3dA0LNDYzczE28nM28LQy8TYAKIoEKDHAARwNC-oMTi_TD9aPwKjMxhipwdnf0MDH3MTCw8HE3NfB09AgNsgw0NjZwhCnA4w4_j_zcVP3cqByLYE9dRwDU0IbJ/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: 28400
  • connection: Keep-Alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for moi.gov.sa

DNS Analysis


DNS servers
ns1.saudi.net.sa [212.118.133.101]
ns2.saudi.net.sa [62.149.114.7]


DNS Records

Answer records
moi.gov.sa SOA
server: ns1.saudi.net.sa
email: hostmaster@saudi.net.sa
serial: 2012111902
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
3600s
moi.gov.sa MX
preference: 10
exchange: mail.moi.gov.sa
3600s
moi.gov.sa MX
preference: 5
exchange: mail01.moi.gov.sa
3600s
moi.gov.sa MX
preference: 5
exchange: mail02.moi.gov.sa
3600s
moi.gov.sa NS  ns2.saudi.net.sa 3600s
moi.gov.sa NS  ns1.saudi.net.sa 3600s
moi.gov.sa A 193.47.102.10 3600s

Authority records

Additional records
mail01.moi.gov.sa A 212.118.132.152 3600s
mail02.moi.gov.sa A 212.118.132.150 3600s
mail.moi.gov.sa A 212.118.132.147 3600s
ns1.saudi.net.sa A 212.118.133.101 3600s
ns2.saudi.net.sa A 62.149.114.7 3600s

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 350 Errors
  • 57 Warnings
Ratio Text/Html
  • 0.5815798681709428
Message Error
  • Error Line 44, Column 36: required attribute "type" not specified
    <head><script language="JavaScript">var pn = "CSRT"; var pv = '5770108980522048…

    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 45, Column 124: character ";" not allowed in attribute specification list
    …String.fromCharCode(c);for(var d=2;d<g;d++){var f=(parseInt(e[d]+e[d+1],16)-c)…
  • Error Line 45, Column 124: element "g" undefined
    …String.fromCharCode(c);for(var d=2;d<g;d++){var f=(parseInt(e[d]+e[d+1],16)-c)…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 46, Column 9: end tag for "g" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 45, Column 122: start tag was here
    …b=String.fromCharCode(c);for(var d=2;d<g;d++){var f=(parseInt(e[d]+e[d+1],16)-…
  • Error Line 51, 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 51, Column 3: start tag was here
    		<link href="/portal/css/style_arabic.css" rel="styleSheet" type="text/css" me…
  • Error Line 52, 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 52, Column 3: start tag was here
    		<link href="/portal/css/slider.css" rel="styleSheet" type="text/css">
  • Error Line 53, 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 53, Column 3: start tag was here
    		<link href="/portal/css/menu_arabic.css" rel="styleSheet" type="text/css" med…
  • Error Line 54, 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 54, Column 3: start tag was here
    		<link href="/portal/css/hdr_arabic.css" rel="styleSheet" type="text/css" medi…
  • Error Line 55, 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 55, Column 3: start tag was here
    		<link href="/portal/css/print.css" rel="styleSheet" type="text/css">
  • Error Line 67, Column 51: document type does not allow element "div" here; assuming missing "body" start-tag
    	<div id="toolsList" class="sharePost_new noPrint">
  • Error Line 87, 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 94, 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 134, 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 134, 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 134, 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 134, 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 137, 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 135, Column 5: start tag was here
    	   <input type="hidden" 
  • Error Line 143, 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 140, Column 3: start tag was here
    		<input type="text" accesskey="d" 
  • Error Line 149, 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 157, 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 158, 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 158, 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 158, Column 26: start tag was here
    	<tr class="noPrint"><td><img src="/portal/images/theme/moinew/spacer.gif" heig…
  • Error Line 187, Column 23: document type does not allow element "div" here; assuming missing "li" start-tag
    	<div class="tab_wrap">
  • Error Line 188, 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 190, 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 215, 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 221, 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 242, 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 248, 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 269, 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 275, 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 296, 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 302, 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 310, 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 187, Column 2: start tag was here
    	<div class="tab_wrap">
  • Error Line 310, 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 175, Column 2: start tag was here
    	<ul id="nav_dd">
  • Error Line 310, 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 160, Column 3: start tag was here
    		<td colspan="2">
  • Error Line 310, 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 159, Column 2: start tag was here
    	<tr>
  • Error Line 310, 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 157, Column 4: start tag was here
      	<table border="0" cellpadding="0" cellspacing="0" width="100%" height="100%">
  • Error Line 328, 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 329, 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 330, Column 21: document type does not allow element "tr" here; assuming missing "table" start-tag
    	<tr class="noPrint"><td colspan="2">
  • Error Line 336, 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 337, 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 344, 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 357, 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 367, 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 380, Column 32: there is no attribute "align"
    <a class="more_link_new" align="left" href="/wps/portal/!ut/p/b1/04_SjzQxtTSyMD…

    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 387, 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 387, 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 387, Column 49: start tag was here
    …="noPrint"><td height="3" colspan="3"><img src="/portal/images/theme/moinew/sp…
  • Error Line 426, 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 488, 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 501, 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 501, 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 501, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/Lef…
  • Warning Line 502, 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 502, 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 502, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 510, 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 511, 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 514, Column 8: document type does not allow element "tr" here; assuming missing "table" start-tag
    <td><tr>
  • Error Line 533, 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 519, 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 547, 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 519, 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 561, 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 519, 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 575, 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 519, 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 589, 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 519, 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 603, 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 519, 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 617, 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 519, 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 631, 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 519, 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 641, 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 514, Column 5: start tag was here
    <td><tr>
  • Error Line 644, 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 645, 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 650, 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 650, 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 654, 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 655, 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 655, 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 657, 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 664, 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 680, 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 702, 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 728, 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 728, 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 728, 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 728, 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 728, 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 728, 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 751, 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 759, 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 759, 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 759, 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 819, 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 832, 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 832, 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 832, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/Sid…
  • Warning Line 833, 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 833, 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 833, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 840, 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 845, 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 845, 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 845, 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 846, 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 847, 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 847, 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 847, Column 1: start tag was here
    <area href="http://www.youtube.com/user/moigovsa" shape="rect" coords="2, 2, 40…
  • Error Line 848, 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 848, 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 848, Column 1: start tag was here
    <area href="https://twitter.com/#!/MOIeServices" shape="rect" coords="48, 2, 88…
  • Error Line 849, 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 849, 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 849, Column 1: start tag was here
    <area href="http://www.facebook.com/moi.eServices" shape="rect" coords="96, 2, …
  • Error Line 851, 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 851, 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 851, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 862, 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 862, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 868, 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 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 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 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 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 886, 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 889, 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 889, 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 889, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 895, 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 896, 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 896, 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 896, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Warning Line 900, 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 900, 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 900, 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 900, 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 900, 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 900, Column 445: entity was defined here
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/
  • Warning Line 901, 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 901, 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 901, 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 901, 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 901, 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 901, Column 49: entity was defined here
    …I+Diwan/MOI+Home+Content+AR/Home/FAQs/&idOfFaq2Open=a2ecbbb3-4066-4760-a383-5a…
  • Error Line 903, 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 905, 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 905, 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 905, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 911, 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 915, 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 915, 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 915, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 920, 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 923, 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 923, 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 923, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Warning Line 927, Column 9: multiple comments in comment declaration
    <!----------- Traffic Violation Query End ------>
  • Warning Line 927, Column 43: multiple comments in comment declaration
    <!----------- Traffic Violation Query End ------>
  • Warning Line 927, Column 47: multiple comments in comment declaration
    <!----------- Traffic Violation Query End ------>
  • Error Line 931, 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 934, 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 934, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Warning Line 936, Column 9: multiple comments in comment declaration
    <!----------- Traffic Violation Query End ------>
  • Warning Line 936, Column 43: multiple comments in comment declaration
    <!----------- Traffic Violation Query End ------>
  • Warning Line 936, Column 47: multiple comments in comment declaration
    <!----------- Traffic Violation Query End ------>
  • Error Line 941, 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 944, 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 947, 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 947, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 951, 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 955, 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 955, Column 1: start tag was here
    <hr style="border-style: dashed; border-color: green; border-width: 1px 0pt 0pt…
  • Error Line 996, 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 1009, 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 1009, 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 1009, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/Ima…
  • Warning Line 1010, 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 1010, 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 1010, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 1017, 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 1017, 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 1017, 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 1017, 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 1017, 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 1017, 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 1017, Column 199: entity was defined here
    …endar_moi_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d…
  • Error Line 1030, 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 1030, 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 1033, 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 1039, 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 1084, Column 404: an attribute value must be a literal unless it contains only name characters
    …ive/moi_news_26-01-2013c_ar'><img src=/wps/wcm/connect/db6f3929-e66c-4c2f-8218…

    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 1084, Column 654: required attribute "alt" not specified
    …RES&CACHEID=db6f3929-e66c-4c2f-8218-eafa3a2537e7 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 1088, Column 9: 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 1094, 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 1139, Column 404: an attribute value must be a literal unless it contains only name characters
    …ive/moi_news_26-01-2013b_ar'><img src=/wps/wcm/connect/4d4e8118-bdb1-4a18-91ef…

    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 1139, Column 846: required attribute "alt" not specified
    …RES&CACHEID=4d4e8118-bdb1-4a18-91ef-fd989e7ff41c 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 1143, Column 9: 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 1149, 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 1237, 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 1250, 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 1250, 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 1250, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/MOI…
  • Warning Line 1251, 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 1251, 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 1251, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 1258, 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 1284, 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 1284, 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 1297, 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 1261, Column 10: ID "mid_content" first defined here
    <div id="mid_content">
  • Error Line 1345, 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 1346, 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 1347, 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 1412, 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 1425, 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 1425, 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 1425, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/Sec…
  • Warning Line 1426, 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 1426, 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 1426, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 1433, 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 1433, 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 1261, Column 10: ID "mid_content" first defined here
    <div id="mid_content">
  • Error Line 1439, 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 1439, 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 1439, 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 1439, 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 1445, 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 1474, 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 1479, 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 1520, 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 1261, Column 10: ID "mid_content" first defined here
    <div id="mid_content">
  • Error Line 1559, 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 1595, 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 1615, 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 1623, 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 1630, 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 1632, 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 1638, 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 1640, 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 1677, 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 1690, 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 1690, 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 1690, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/Civil Defenc…
  • Warning Line 1691, 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 1691, 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 1691, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FCivil Defen…
  • Error Line 1732, 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 1745, 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 1745, 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 1745, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/Fro…
  • Warning Line 1746, 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 1746, 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 1746, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 1753, 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 1756, 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 1756, 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 1756, 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 1017, Column 199: entity was defined here
    …endar_moi_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d…
  • Error Line 1760, 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 1764, 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 1770, 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 1845, 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 1858, 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 1858, 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 1858, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/MOI…
  • Warning Line 1859, 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 1859, 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 1859, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 1866, 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 1872, 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 1877, 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 1877, 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 1877, 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 900, Column 445: entity was defined here
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/
  • Error Line 1877, 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 1877, 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 1877, 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 1877, 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 900, Column 445: entity was defined here
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/
  • Error Line 1877, 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 1886, 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 1886, 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 1913, 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 1913, 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 1913, 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 1886, Column 161: ID "4cNews_viewall_link" first defined here
    …ol/command+and+control+ar/statments/"  id="4cNews_viewall_link">استعرض الكل</a>
  • Warning Line 1918, Column 133: reference not terminated by REFC delimiter
    …%D8%A8%D8%A9+s.jpg?MOD=AJPERES&CACHEID=4c298c2a-981c-49b1-8e4d-85cfa6cfef1b" 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 1918, Column 133: reference to external entity in attribute value
    …%D8%A8%D8%A9+s.jpg?MOD=AJPERES&CACHEID=4c298c2a-981c-49b1-8e4d-85cfa6cfef1b" 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 1918, Column 133: reference to entity "CACHEID" for which no system identifier could be generated
    …%D8%A8%D8%A9+s.jpg?MOD=AJPERES&CACHEID=4c298c2a-981c-49b1-8e4d-85cfa6cfef1b" 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 1017, Column 199: entity was defined here
    …endar_moi_dateConverter.js?MOD=AJPERES&CACHEID=a2af4a004daa8f8b86bec7890776a4d…
  • Error Line 1918, Column 206: required attribute "alt" not specified
    …CHEID=4c298c2a-981c-49b1-8e4d-85cfa6cfef1b" 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 1930, 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 1938, 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 1944, 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 1944, 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 1950, 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 1954, 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 1981, 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 2009, 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 2011, 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 2044, 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 2070, 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 2071, 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 2168, 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 2181, 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 2181, 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 2181, Column 3: comment declaration started here
      <!-- Before Alteration contextPath -- /post migration components/MOI Home/Emi…
  • Warning Line 2182, 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 2182, 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 2182, Column 1: comment declaration started here
    <!-- After Alteration contextPath -- %2Fpost migration components%2FMOI Home AR…
  • Error Line 2189, 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 2200, 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 2219, 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 2231, 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 2229, Column 1: start tag was here
    <div class="heading_events" style="width:302px; margin-right:0px; margin-top:0p…
  • Error Line 2235, 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 2249, 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 2262, 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 2264, 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 2265, 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 2265, 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 2265, Column 3: start tag was here
      <area href="http://www.moi.gov.sa/wps/portal/civilaffairs/!ut/p/b1/04_Sj9CPyk…
  • Error Line 2266, 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 2266, 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 2266, Column 3: start tag was here
      <area href="http://eservices.moi.gov.sa/ES/Public/AppointMents/AppointMentsDe…
  • Error Line 2308, 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 2308, 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 2308, 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 2308, 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 2309, 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 2310, 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 2310, 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 2311, 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 2311, 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 2311, 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 2312, 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 2312, 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 2312, 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 2313, 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 2314, 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 2315, 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 2316, 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 2317, 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 2318, 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 2319, 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 2321, 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 2322, 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 2323, 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 2324, 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 2329, 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 2329, 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 2330, 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 2331, 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 2332, 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 2333, Column 9: element "TD" undefined
    					<TD>05: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 2334, 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 2335, Column 10: element "TD" undefined
    					<TD >06: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 2336, 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 2337, 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 2338, 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 2339, Column 10: element "TD" undefined
    					<TD >03:15</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 ></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 2341, Column 10: element "TD" undefined
    					<TD >05: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 2342, 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 2343, Column 10: element "TD" undefined
    					<TD >07: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 2348, 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 2349, 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 2350, 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 2351, 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 2352, Column 9: element "TD" undefined
    					<TD>05:42</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 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 >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 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 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 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 >03:44</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 >06:06</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 >07: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 2367, 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 2368, 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 2369, 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 2370, 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 2371, Column 9: element "TD" undefined
    					<TD>05:38</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 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 >06:59</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 10: element "TD" undefined
    					<TD >12: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 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 >03:47</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 >06:10</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 >07:40</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 2386, 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 2387, 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 2388, 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 2389, 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 2390, Column 9: element "TD" undefined
    					<TD>05:01</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 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 >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 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 10: element "TD" undefined
    					<TD >11: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 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 >02:59</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 >05:21</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 >06: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 2405, 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 2406, 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 2407, 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 2408, 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 2409, Column 9: element "TD" undefined
    					<TD>05:41</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 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 >07:02</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 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 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 >03: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 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 >06:12</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 >07:42</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 2424, 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 2425, 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 2426, 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 2427, 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 2428, Column 9: element "TD" undefined
    					<TD>05:27</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 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 >06: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 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 10: element "TD" undefined
    					<TD >12: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 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 >03:26</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 >05: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 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 >07: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 2443, 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 2460, 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 2467, 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 2467, Column 212: start tag was here
    …="0" class="footer_logo_margin" /></a><br>الوصلات الخارجية الموجودة في البوابة…
  • Warning Line 2474, 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 2474, 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 2474, 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 900, Column 445: entity was defined here
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/
  • Warning Line 2481, 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 2481, 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 2481, 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 900, Column 445: entity was defined here
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/
  • Warning Line 2488, 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 2488, 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 2488, 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 2488, 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 2488, 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 2488, Column 318: entity was defined here
    …DA0/?nID=Z6_5CPCI8M31GPU702F74JC6K80K4&cID=Z6_5CPCI8M31GPU702F74JC6K80K4">البح…
  • Warning Line 2507, 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 2507, 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 2507, 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 900, Column 445: entity was defined here
    …PORTLET=PC_Z7_B00E9B1A0G9OE0IH7BJPJ71057000000_WCM&WCM_GLOBAL_CONTEXT=/wps/wcm/
  • Warning Line 2509, 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 2509, 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 2509, 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 2488, Column 318: entity was defined here
    …DA0/?nID=Z6_5CPCI8M31GPU702F74JC6K80K4&cID=Z6_5CPCI8M31GPU702F74JC6K80K4">البح…
  • Error Line 2514, 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 67, Column 2: start tag was here
    	<div id="toolsList" class="sharePost_new noPrint">

Visitor Analysis

Daily Visitor
  • 29.167 visits