sbank.ir

اين صفحه اصلي است ...

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

Overview Info

  • Domain Name
    sbank.ir
  • Favicon
  • Alexa Rank
    #49835
  • Google Page Rank
    PR 5
  • Ip Address
    77.237.91.61
  • Page Size
    87.1 KB
  • Images
    9 GIF, 14 JPG, 40 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    پورتال بانك سرمايه:: صفحه اصلي
  • Meta Keyword
    , اين صفحه اصلي است,, این صفحه اصلی است,
  • Meta Description
    اين صفحه اصلي است

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    77.237.91.61
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from sbank.ir.

HTML Analysis

  • date: Fri, 15 Feb 2013 14:35:20 GMT
  • server: Apache
  • x-powered-by: sisRapid Framework
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: cache
  • pragma: no-cache
  • content-length: 81874
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% This is the IRNIC Whois server v1.6.2.
% Available on web at http://whois.nic.ir/
% Find the terms and conditions of use on http://www.nic.ir/
%
% This server uses UTF-8 as the encoding for requests and responses.

% NOTE: This output has been filtered.

% Information related to 'sbank.ir'


domain: sbank.ir
ascii: sbank.ir
remarks: (Domain Holder) Bank Sarmaye
remarks: (Domain Holder Address) Sarmaye Bank Building, No 24, Arak St., Gharani Ave., Tehran, Iran, Tehran, Tehran, IR
holder-c: ba65-irnic
admin-c: ba65-irnic
tech-c: ba65-irnic
nserver: dns0.hostiran.net
nserver: dns1.hostiran.net
nserver: dns2.hostiran.net
nserver: dns3.hostiran.net
last-updated: 2012-05-29
expire-date: 2017-04-23
source: IRNIC # Filtered

nic-hdl: ba65-irnic
org: Bank Sarmaye
e-mail: email
address: Sarmaye Bank Building, No 24, Arak St., Gharani Ave., Tehran, Iran, Tehran, Tehran, IR
phone: 88900763
fax-no: 84261454
source: IRNIC # Filtered

DNS Analysis


DNS servers
dns0.hostiran.net
dns1.hostiran.net
dns2.hostiran.net [208.80.126.2]
dns3.hostiran.net

DNS Records

Answer records
sbank.ir SOA
server: dns0.hostiran.net
email: admin@hostiran.net
serial: 2004011741
refresh: 43200
retry: 3600
expire: 1209600
minimum ttl: 3600
86400s
sbank.ir NS  dns4.hostiran.net 86400s
sbank.ir NS  dns3.hostiran.net 86400s
sbank.ir NS  dns0.hostiran.net 86400s
sbank.ir NS  86400s
sbank.ir NS  dns1.hostiran.net 86400s
sbank.ir NS  dns2.hostiran.net 86400s
sbank.ir A 77.237.91.61 180s
sbank.ir MX
preference: 10
exchange: mail.sbank.ir
1800s

Authority records

Additional records
mail.sbank.ir A 77.237.91.59 1800s

IP 77.237.91.61 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 297 Errors
  • 74 Warnings
Ratio Text/Html
  • 0.578171587419015
Message Error
  • Error Line 27, Column 31: 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 43, Column 31: 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 53, Column 13: there is no attribute "id"
    <bgsound id="alert_sound" loop=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 53, Column 32: there is no attribute "loop"
    <bgsound id="alert_sound" loop=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 53, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <bgsound id="alert_sound" loop=1>
  • Error Line 53, Column 33: element "bgsound" undefined
    <bgsound id="alert_sound" loop=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 70, Column 95: there is no attribute "quick_search_param"
    … <input type="hidden" quick_search_param='1' name="active_polling" value="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 108, Column 234: required attribute "alt" not specified
    …_menu/right_side.png' style='margin:0px;padding:0px;' class='hmenu_img' /></td>

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

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

  • Error Line 109, Column 22: there is no attribute "onMouseOver"
    					<td onMouseOver='showDiv3(0)'  id='td_0' class='hmenu_unselected_td' style…

    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 109, Column 304: required attribute "alt" not specified
    …3/0.png' class='hmenu_unselected_img'/></a></td><td onMouseOver='onMouseFunc(t…

    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 109, Column 669: required attribute "alt" not specified
    …3/1.png' class='hmenu_unselected_img'/></a></td><td onMouseOver='onMouseFunc(t…

    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 109, Column 1054: required attribute "alt" not specified
    …3/2.png' class='hmenu_unselected_img'/></a></td><td onMouseOver='onMouseFunc(t…

    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 109, Column 1408: required attribute "alt" not specified
    …3/3.png' class='hmenu_unselected_img'/></a></td><td onMouseOver='onMouseFunc(t…

    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 109, Column 1762: required attribute "alt" not specified
    …3/4.png' class='hmenu_unselected_img'/></a></td><td onMouseOver='onMouseFunc(t…

    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 109, Column 2121: required attribute "alt" not specified
    …3/5.png' class='hmenu_unselected_img'/></a></td><td onMouseOver='onMouseFunc(t…

    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 109, Column 2487: required attribute "alt" not specified
    …3/6.png' class='hmenu_unselected_img'/></a></td><td onMouseOver='showDiv3(7)' …

    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 109, Column 2797: required attribute "alt" not specified
    …r/images/far/horizontal_menu/363/7.png' class='hmenu_unselected_img'/></a></td>

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

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

  • Error Line 110, Column 233: required attribute "alt" not specified
    …0px;padding:0px;' class='hmenu_img2' /></td></tr></table><div id='sub_1'   sty…

    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 113, Column 153: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …;background-repeat:repeat-y;' rowspan=2><img src='http://sbank.ir/images/far/h…
  • Error Line 113, Column 268: required attribute "alt" not specified
    …izontal_menu/s10.png' style='padding:0px;margin:0px;vertical-align:top' /></td>

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

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

  • Error Line 115, Column 154: there is no attribute "valign"
    …tyle='padding:0px;margin:0px;' valign='bottom' style='vertical-align:top;' /><…

    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 115, Column 169: duplicate specification of attribute "style"
    …e='padding:0px;margin:0px;' valign='bottom' style='vertical-align:top;' /></td>

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 115, Column 192: required attribute "alt" not specified
    …e='padding:0px;margin:0px;' valign='bottom' style='vertical-align:top;' /></td>

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

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

  • Error Line 151, Column 238: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s2.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 155, Column 110: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s8.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 157, Column 110: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s4.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 164, Column 153: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …;background-repeat:repeat-y;' rowspan=2><img src='http://sbank.ir/images/far/h…
  • Error Line 164, Column 268: required attribute "alt" not specified
    …izontal_menu/s10.png' style='padding:0px;margin:0px;vertical-align:top' /></td>

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

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

  • Error Line 166, Column 169: duplicate specification of attribute "style"
    …e='padding:0px;margin:0px;' valign='bottom' style='vertical-align:top;' /></td>

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 166, Column 192: required attribute "alt" not specified
    …e='padding:0px;margin:0px;' valign='bottom' style='vertical-align:top;' /></td>

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

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

  • Error Line 198, Column 238: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s2.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 202, Column 110: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s8.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 204, Column 110: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s4.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 211, Column 153: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …;background-repeat:repeat-y;' rowspan=2><img src='http://sbank.ir/images/far/h…
  • Error Line 211, Column 268: required attribute "alt" not specified
    …izontal_menu/s10.png' style='padding:0px;margin:0px;vertical-align:top' /></td>

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

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

  • Error Line 213, Column 169: duplicate specification of attribute "style"
    …e='padding:0px;margin:0px;' valign='bottom' style='vertical-align:top;' /></td>

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 213, Column 192: required attribute "alt" not specified
    …e='padding:0px;margin:0px;' valign='bottom' style='vertical-align:top;' /></td>

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

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

  • Error Line 247, Column 9: end tag for "tr" which is not finished
    				</tr>

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

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

  • Error Line 259, Column 238: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s2.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 263, Column 110: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s8.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 265, Column 110: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s4.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 272, Column 150: required attribute "alt" not specified
    …ir/images/far/horizontal_menu/s111.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 274, Column 152: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …;background-repeat:repeat-y;' rowspan=2><img src='http://sbank.ir/images/far/h…
  • Error Line 274, Column 268: required attribute "alt" not specified
    …zontal_menu/s101.png' style='padding:0px;margin:0px;vertical-align:top' /></td>

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

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

  • Error Line 277, Column 240: required attribute "alt" not specified
    …s/far/horizontal_menu/s21.png' style='padding:0px;margin:0px;' /></td>									

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

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

  • Error Line 314, Column 110: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s8.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 316, Column 110: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s4.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 323, Column 150: required attribute "alt" not specified
    …ir/images/far/horizontal_menu/s111.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 325, Column 152: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …;background-repeat:repeat-y;' rowspan=2><img src='http://sbank.ir/images/far/h…
  • Error Line 325, Column 268: required attribute "alt" not specified
    …zontal_menu/s101.png' style='padding:0px;margin:0px;vertical-align:top' /></td>

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

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

  • Error Line 328, Column 240: required attribute "alt" not specified
    …s/far/horizontal_menu/s21.png' style='padding:0px;margin:0px;' /></td>									

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

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

  • Error Line 364, Column 110: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s8.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 366, Column 110: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s4.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 373, Column 150: required attribute "alt" not specified
    …ir/images/far/horizontal_menu/s111.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 375, Column 152: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …;background-repeat:repeat-y;' rowspan=2><img src='http://sbank.ir/images/far/h…
  • Error Line 375, Column 268: required attribute "alt" not specified
    …zontal_menu/s101.png' style='padding:0px;margin:0px;vertical-align:top' /></td>

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

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

  • Error Line 378, Column 240: required attribute "alt" not specified
    …s/far/horizontal_menu/s21.png' style='padding:0px;margin:0px;' /></td>									

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

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

  • Error Line 410, Column 110: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s8.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 412, Column 110: required attribute "alt" not specified
    …k.ir/images/far/horizontal_menu/s4.png' style='padding:0px;margin:0px;' /></td>

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

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

  • Error Line 417, 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 449, Column 37: character ";" not allowed in attribute specification list
    			for(var menuI=0;menuI <menu_count;menuI++){
  • Error Line 449, Column 37: element "menu_count" undefined
    			for(var menuI=0;menuI <menu_count;menuI++){

    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).
  • Warning Line 471, Column 30: character "&" is the first character of a delimiter but occurred as data
    					mouseX > tabOffset.left && 

    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 471, Column 31: character "&" is the first character of a delimiter but occurred as data
    					mouseX > tabOffset.left && 

    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 472, Column 13: character "<" is the first character of a delimiter but occurred as data
    					mouseX < (tabOffset.left+tabWidth) && 

    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 472, Column 41: character "&" is the first character of a delimiter but occurred as data
    					mouseX < (tabOffset.left+tabWidth) && 

    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 472, Column 42: character "&" is the first character of a delimiter but occurred as data
    					mouseX < (tabOffset.left+tabWidth) && 

    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 473, Column 29: character "&" is the first character of a delimiter but occurred as data
    					mouseY > tabOffset.top && 

    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 473, Column 30: character "&" is the first character of a delimiter but occurred as data
    					mouseY > tabOffset.top && 

    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 474, Column 13: character "<" is the first character of a delimiter but occurred as data
    					mouseY < (tabOffset.top+tabHeight)

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

    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).
  • Warning Line 571, Column 31: character "&" is the first character of a delimiter but occurred as data
    			if(mouseX > divOffset.left && mouseX < (divOffset.left+divWidth) && mouseY >…

    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 571, Column 32: character "&" is the first character of a delimiter but occurred as data
    			if(mouseX > divOffset.left && mouseX < (divOffset.left+divWidth) && mouseY >…

    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 571, Column 41: character "<" is the first character of a delimiter but occurred as data
    …	if(mouseX > divOffset.left && mouseX < (divOffset.left+divWidth) && mouseY > …

    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 571, Column 69: character "&" is the first character of a delimiter but occurred as data
    …&& mouseX < (divOffset.left+divWidth) && mouseY > divOffset.top && mouseY < (d…

    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 571, Column 70: character "&" is the first character of a delimiter but occurred as data
    …& mouseX < (divOffset.left+divWidth) && mouseY > divOffset.top && mouseY < (di…

    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 571, Column 95: character "&" is the first character of a delimiter but occurred as data
    …eft+divWidth) && mouseY > divOffset.top && mouseY < (divOffset.top+divHeight)){

    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 571, Column 96: character "&" is the first character of a delimiter but occurred as data
    …eft+divWidth) && mouseY > divOffset.top && mouseY < (divOffset.top+divHeight)){

    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 571, Column 105: character "<" is the first character of a delimiter but occurred as data
    …eft+divWidth) && mouseY > divOffset.top && mouseY < (divOffset.top+divHeight)){

    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 575, Column 31: character "&" is the first character of a delimiter but occurred as data
    			if(mouseX > tabOffset.left && mouseX < (tabOffset.left+tabWidth) && mouseY >…

    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 575, Column 32: character "&" is the first character of a delimiter but occurred as data
    			if(mouseX > tabOffset.left && mouseX < (tabOffset.left+tabWidth) && mouseY >…

    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 575, Column 41: character "<" is the first character of a delimiter but occurred as data
    …	if(mouseX > tabOffset.left && mouseX < (tabOffset.left+tabWidth) && mouseY > …

    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 575, Column 69: character "&" is the first character of a delimiter but occurred as data
    …&& mouseX < (tabOffset.left+tabWidth) && mouseY > tabOffset.top && mouseY < (t…

    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 575, Column 70: character "&" is the first character of a delimiter but occurred as data
    …& mouseX < (tabOffset.left+tabWidth) && mouseY > tabOffset.top && mouseY < (ta…

    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 575, Column 95: character "&" is the first character of a delimiter but occurred as data
    …eft+tabWidth) && mouseY > tabOffset.top && mouseY < (tabOffset.top+tabHeight)){

    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 575, Column 96: character "&" is the first character of a delimiter but occurred as data
    …eft+tabWidth) && mouseY > tabOffset.top && mouseY < (tabOffset.top+tabHeight)){

    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 575, Column 105: character "<" is the first character of a delimiter but occurred as data
    …eft+tabWidth) && mouseY > tabOffset.top && mouseY < (tabOffset.top+tabHeight)){

    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 605, Column 31: character "&" is the first character of a delimiter but occurred as data
    			if(mouseX > divOffset.left && mouseX < (divOffset.left+divWidth) && mouseY >…

    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 605, Column 32: character "&" is the first character of a delimiter but occurred as data
    			if(mouseX > divOffset.left && mouseX < (divOffset.left+divWidth) && mouseY >…

    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 605, Column 41: character "<" is the first character of a delimiter but occurred as data
    …	if(mouseX > divOffset.left && mouseX < (divOffset.left+divWidth) && mouseY > …

    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 605, Column 69: character "&" is the first character of a delimiter but occurred as data
    …&& mouseX < (divOffset.left+divWidth) && mouseY > divOffset.top && mouseY < (d…

    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 605, Column 70: character "&" is the first character of a delimiter but occurred as data
    …& mouseX < (divOffset.left+divWidth) && mouseY > divOffset.top && mouseY < (di…

    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 605, Column 95: character "&" is the first character of a delimiter but occurred as data
    …left+divWidth) && mouseY > divOffset.top && mouseY < (divOffset.top+divHeight))

    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 605, Column 96: character "&" is the first character of a delimiter but occurred as data
    …left+divWidth) && mouseY > divOffset.top && mouseY < (divOffset.top+divHeight))

    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 605, Column 105: character "<" is the first character of a delimiter but occurred as data
    …left+divWidth) && mouseY > divOffset.top && mouseY < (divOffset.top+divHeight))

    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 607, Column 31: character "&" is the first character of a delimiter but occurred as data
    			if(mouseX > tabOffset.left && mouseX < (tabOffset.left+tabWidth) && mouseY >…

    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 607, Column 32: character "&" is the first character of a delimiter but occurred as data
    			if(mouseX > tabOffset.left && mouseX < (tabOffset.left+tabWidth) && mouseY >…

    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 607, Column 41: character "<" is the first character of a delimiter but occurred as data
    …	if(mouseX > tabOffset.left && mouseX < (tabOffset.left+tabWidth) && mouseY > …

    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 607, Column 69: character "&" is the first character of a delimiter but occurred as data
    …&& mouseX < (tabOffset.left+tabWidth) && mouseY > tabOffset.top && mouseY < (t…

    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 607, Column 70: character "&" is the first character of a delimiter but occurred as data
    …& mouseX < (tabOffset.left+tabWidth) && mouseY > tabOffset.top && mouseY < (ta…

    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 607, Column 95: character "&" is the first character of a delimiter but occurred as data
    …left+tabWidth) && mouseY > tabOffset.top && mouseY < (tabOffset.top+tabHeight))

    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 607, Column 96: character "&" is the first character of a delimiter but occurred as data
    …left+tabWidth) && mouseY > tabOffset.top && mouseY < (tabOffset.top+tabHeight))

    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 607, Column 105: character "<" is the first character of a delimiter but occurred as data
    …left+tabWidth) && mouseY > tabOffset.top && mouseY < (tabOffset.top+tabHeight))

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

    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 656, Column 10: end tag for "menu_count" 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 623, Column 26: start tag was here
    			for(var menuI=0;menuI <menu_count;menuI++){
  • Error Line 656, Column 10: end tag for "menu_count" 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 513, Column 26: start tag was here
    			for(var menuI=0;menuI <menu_count;menuI++){
  • Error Line 656, Column 10: end tag for "menu_count" 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 449, Column 26: start tag was here
    			for(var menuI=0;menuI <menu_count;menuI++){
  • Error Line 657, Column 8: 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 657, Column 8: 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 688, Column 105: there is no attribute "class1"
    …0%" cellpadding="0px" cellspacing="0px" style="margin-top:0px;" class1="Block">

    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 688, Column 112: document type does not allow element "table" here; assuming missing "li" start-tag
    …0%" cellpadding="0px" cellspacing="0px" style="margin-top:0px;" class1="Block">
  • Error Line 698, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td colspan=2 valign=top>
  • Error Line 698, Column 22: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td colspan=2 valign=top>
  • Error Line 703, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td valign=top width="25%" style="padding-left:10px">
  • Error Line 710, Column 96: there is no attribute "onMouseover"
    ….action" target="_blank"  onMouseover="document.arrow.src='/parameters/sbank/m…

    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 710, Column 226: there is no attribute "onMouseout"
    …_internetbank4-hover.jpg'" onMouseout="document.arrow.src='/parameters/sbank/m…

    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 720, Column 12: "DOCTYPE" declaration not allowed in instance
            	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http:/…
  • Error Line 721, Column 43: document type does not allow element "html" here
    <html xmlns="http://www.w3.org/1999/xhtml">

    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 746, Column 141: required attribute "alt" not specified
    …"><img src="/parameters/sbank/themes/saman/images/electronic_system.jpg"/></td>

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

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

  • Error Line 809, Column 24: syntax of attribute value does not conform to declared value
            	<form target="" method="post" action="" name="content_search_form_bloc…

    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 809, Column 123: there is no attribute "onSubmit"
    …d="content_search_form_block" onSubmit="return checkForm()" style="margin:0px">

    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 820, Column 28: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    <option value="0"  selected>همه استانها</option>

    "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 858, Column 61: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …value="1" name="R1"  id="rial" checked /><span lang="fa">شعبه ريالي</span><br/>

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

  • Warning Line 879, Column 93: cannot generate system identifier for general entity "page_id"
    …action=basePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_…

    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 879, Column 93: general entity "page_id" not defined and no default entity
    …action=basePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_…

    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 879, Column 100: reference not terminated by REFC delimiter
    …basePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pr…

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

  • Error Line 879, Column 100: reference to entity "page_id" for which no system identifier could be generated
    …basePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pr…

    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 879, Column 92: entity was defined here
    ….action=basePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro…
  • Warning Line 879, Column 104: cannot generate system identifier for general entity "id"
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 104: general entity "id" not defined and no default entity
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 106: reference not terminated by REFC delimiter
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id

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

  • Error Line 879, Column 106: reference to entity "id" for which no system identifier could be generated
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 103: entity was defined here
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_i…
  • Warning Line 879, Column 109: cannot generate system identifier for general entity "branchname"
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 109: general entity "branchname" not defined and no default entity
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 119: reference not terminated by REFC delimiter
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id

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

  • Error Line 879, Column 119: reference to entity "branchname" for which no system identifier could be generated
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 108: entity was defined here
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id
  • Warning Line 879, Column 129: cannot generate system identifier for general entity "pro_id"
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 129: general entity "pro_id" not defined and no default entity
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 135: reference not terminated by REFC delimiter
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id

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

  • Error Line 879, Column 135: reference to entity "pro_id" for which no system identifier could be generated
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 128: entity was defined here
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id
  • Warning Line 881, Column 100: reference not terminated by REFC delimiter
    …basePath+"index.php?module=pmk&page_id=42&id=1&branchname="+name+"&pro_id="+pr…

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

  • Error Line 881, Column 100: reference to entity "page_id" for which no system identifier could be generated
    …basePath+"index.php?module=pmk&page_id=42&id=1&branchname="+name+"&pro_id="+pr…

    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 879, Column 92: entity was defined here
    ….action=basePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro…
  • Warning Line 881, Column 106: reference not terminated by REFC delimiter
    …ePath+"index.php?module=pmk&page_id=42&id=1&branchname="+name+"&pro_id="+pro_id

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

  • Error Line 881, Column 106: reference to entity "id" for which no system identifier could be generated
    …ePath+"index.php?module=pmk&page_id=42&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 103: entity was defined here
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_i…
  • Warning Line 881, Column 119: reference not terminated by REFC delimiter
    …ePath+"index.php?module=pmk&page_id=42&id=1&branchname="+name+"&pro_id="+pro_id

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

  • Error Line 881, Column 119: reference to entity "branchname" for which no system identifier could be generated
    …ePath+"index.php?module=pmk&page_id=42&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 108: entity was defined here
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id
  • Warning Line 881, Column 135: reference not terminated by REFC delimiter
    …ePath+"index.php?module=pmk&page_id=42&id=1&branchname="+name+"&pro_id="+pro_id

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

  • Error Line 881, Column 135: reference to entity "pro_id" for which no system identifier could be generated
    …ePath+"index.php?module=pmk&page_id=42&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 128: entity was defined here
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id
  • Warning Line 883, Column 100: reference not terminated by REFC delimiter
    …basePath+"index.php?module=pmk&page_id=43&id=1&branchname="+name+"&pro_id="+pr…

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

  • Error Line 883, Column 100: reference to entity "page_id" for which no system identifier could be generated
    …basePath+"index.php?module=pmk&page_id=43&id=1&branchname="+name+"&pro_id="+pr…

    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 879, Column 92: entity was defined here
    ….action=basePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro…
  • Warning Line 883, Column 106: reference not terminated by REFC delimiter
    …ePath+"index.php?module=pmk&page_id=43&id=1&branchname="+name+"&pro_id="+pro_id

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

  • Error Line 883, Column 106: reference to entity "id" for which no system identifier could be generated
    …ePath+"index.php?module=pmk&page_id=43&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 103: entity was defined here
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_i…
  • Warning Line 883, Column 119: reference not terminated by REFC delimiter
    …ePath+"index.php?module=pmk&page_id=43&id=1&branchname="+name+"&pro_id="+pro_id

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

  • Error Line 883, Column 119: reference to entity "branchname" for which no system identifier could be generated
    …ePath+"index.php?module=pmk&page_id=43&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 108: entity was defined here
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id
  • Warning Line 883, Column 135: reference not terminated by REFC delimiter
    …ePath+"index.php?module=pmk&page_id=43&id=1&branchname="+name+"&pro_id="+pro_id

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

  • Error Line 883, Column 135: reference to entity "pro_id" for which no system identifier could be generated
    …ePath+"index.php?module=pmk&page_id=43&id=1&branchname="+name+"&pro_id="+pro_id

    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 879, Column 128: entity was defined here
    …ePath+"index.php?module=pmk&page_id=41&id=1&branchname="+name+"&pro_id="+pro_id
  • Error Line 895, Column 59: document type does not allow element "div" here; assuming missing "li" start-tag
    <div align="center" style="float:right;padding-bottom:5px">
  • Error Line 897, Column 3: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    <a>

    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 898, Column 6: end tag for "a" omitted, but OMITTAG NO was specified
    </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 897, Column 1: start tag was here
    <a>
  • Error Line 898, Column 6: end tag for "a" omitted, but OMITTAG NO was specified
    </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 896, Column 1: start tag was here
    <a href="http://sbank.ir/forms/offer/add/"><img  src="/parameters/sbank/modules…
  • Error Line 900, Column 12: end tag for "li" omitted, but OMITTAG NO was specified
           </ul>

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

  • Info Line 895, Column 1: start tag was here
    <div align="center" style="float:right;padding-bottom:5px">
  • Error Line 904, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td valign=top width="75%">
  • Error Line 905, Column 40: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table style="width: 100%" cellpadding=0px cellspacing=0px>
  • Error Line 905, Column 56: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table style="width: 100%" cellpadding=0px cellspacing=0px>
  • Error Line 907, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    								<td colspan="2" valign=top>
  • Error Line 915, Column 16: there is no attribute "type"
    		<SCRIPT type=text/javascript >

    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 915, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<SCRIPT type=text/javascript >
  • Error Line 915, Column 21: NET-enabling start-tag not immediately followed by null end-tag
    		<SCRIPT type=text/javascript >

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 915, Column 21: element "SCRIPT" undefined
    		<SCRIPT type=text/javascript >

    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 922, Column 11: end tag for element "SCRIPT" which is not open
    		</SCRIPT>

    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 923, Column 47: there is no attribute "height"
    …ble align='center' width='720' height='200' cellspacing='0' cellpadding='0' st…

    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 926, Column 17: there is no attribute "style"
    					<DIV style='BACKGROUND-IMAGE: url("parameters/sbank/images/change_image/lo…

    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 926, Column 276: there is no attribute "class"
    … HEIGHT:200px; VERTICAL-ALIGN: top; PADDING-TOP: 0px' class=bannerContainer>		 

    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 926, Column 276: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … HEIGHT:200px; VERTICAL-ALIGN: top; PADDING-TOP: 0px' class=bannerContainer>		 
  • Error Line 926, Column 291: element "DIV" undefined
    … HEIGHT:200px; VERTICAL-ALIGN: top; PADDING-TOP: 0px' class=bannerContainer>		 

    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 927, Column 11: element "DIV" undefined
    					<DIV ></DIV></DIV>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 928, Column 16: there is no attribute "style"
    					<UL style='DISPLAY: none;padding:0px;margin:0px;' id=NShomeBanner><LI><A r…

    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 928, Column 59: there is no attribute "id"
    …LAY: none;padding:0px;margin:0px;' id=NShomeBanner><LI><A rel="parameters/sban…

    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 928, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …LAY: none;padding:0px;margin:0px;' id=NShomeBanner><LI><A rel="parameters/sban…
  • Error Line 928, Column 71: element "UL" undefined
    …dding:0px;margin:0px;' id=NShomeBanner><LI><A rel="parameters/sbank/images/cha…

    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 928, Column 75: element "LI" undefined
    …g:0px;margin:0px;' id=NShomeBanner><LI><A rel="parameters/sbank/images/change_…

    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 928, Column 83: there is no attribute "rel"
    …rgin:0px;' id=NShomeBanner><LI><A rel="parameters/sbank/images/change_image/HR…

    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 928, Column 170: there is no attribute "title"
    …ll_charge__web_banner_z[1].jpg" title="خدمت جديد بانك سرمايه براي ايرانسلي ها"…

    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 928, Column 216: there is no attribute "href"
    …يد بانك سرمايه براي ايرانسلي ها" href="" >1</A><LI><A rel="parameters/sbank/im…

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

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

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

  • Error Line 928, Column 219: element "A" undefined
    …بانك سرمايه براي ايرانسلي ها" href="" >1</A><LI><A rel="parameters/sbank/image…

    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 928, Column 228: element "LI" undefined
    …يه براي ايرانسلي ها" href="" >1</A><LI><A rel="parameters/sbank/images/change_…

    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 928, Column 397: element "A" undefined
    …ه تا پايان سال جاري تمديد شد" href="" >1</A><LI><A rel="parameters/sbank/image…

    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 928, Column 406: element "LI" undefined
    …ن سال جاري تمديد شد" href="" >1</A><LI><A rel="parameters/sbank/images/change_…

    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 928, Column 531: element "A" undefined
    …شترك بانك هاي سرمايه و تجارت" href="" >1</A><LI><A rel="parameters/sbank/image…

    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 928, Column 540: element "LI" undefined
    … هاي سرمايه و تجارت" href="" >1</A><LI><A rel="parameters/sbank/images/change_…

    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 928, Column 664: element "A" undefined
    … آني كارت در شعب بانك سرمايه" href="" >1</A><LI><A rel="parameters/sbank/image…

    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 928, Column 673: element "LI" undefined
    … در شعب بانك سرمايه" href="" >1</A><LI><A rel="parameters/sbank/images/change_…

    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 928, Column 781: element "A" undefined
    …image/5SMS_Bank_sarmaye05.jpg" title="اس ام اس بانك سرمايه" href="" >1</A></LI>

    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 929, Column 10: end tag for "LI" omitted, but OMITTAG NO was specified
    					</UL>       

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

  • Info Line 928, Column 537: start tag was here
    …انك هاي سرمايه و تجارت" href="" >1</A><LI><A rel="parameters/sbank/images/chan…
  • Error Line 929, Column 10: end tag for "LI" omitted, but OMITTAG NO was specified
    					</UL>       

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

  • Info Line 928, Column 403: start tag was here
    …ايان سال جاري تمديد شد" href="" >1</A><LI><A rel="parameters/sbank/images/chan…
  • Error Line 929, Column 10: end tag for "LI" omitted, but OMITTAG NO was specified
    					</UL>       

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

  • Info Line 928, Column 225: start tag was here
    …رمايه براي ايرانسلي ها" href="" >1</A><LI><A rel="parameters/sbank/images/chan…
  • Error Line 929, Column 10: end tag for "LI" omitted, but OMITTAG NO was specified
    					</UL>       

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

  • Info Line 928, Column 72: start tag was here
    …ding:0px;margin:0px;' id=NShomeBanner><LI><A rel="parameters/sbank/images/chan…
  • Error Line 959, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    								<td colspan="2" valign=top>
  • Error Line 960, Column 41: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    								<table width="100%" cellpadding=0px cellspacing=0px>
  • Error Line 960, Column 57: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    								<table width="100%" cellpadding=0px cellspacing=0px>
  • Error Line 962, Column 28: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    																<td valign=top width="50%" >
  • Error Line 973, Column 125: document type does not allow element "link" here
    …saman/sisRapid/styles/mainstyle.css" /><link  rel="stylesheet" type="text/css"…

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

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

  • Error Line 973, Column 250: document type does not allow element "link" here
    …http://sbank.ir/parameters/sbank/themes/saman/sisRapid/styles/mainstyle.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 975, Column 1045: cannot generate system identifier for general entity "func"
    …"http://sbank.ir/index.php?module=cdk&func=loadlibmodule&system=cdk&sismodule=…

    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 975, Column 1045: general entity "func" not defined and no default entity
    …"http://sbank.ir/index.php?module=cdk&func=loadlibmodule&system=cdk&sismodule=…

    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 975, Column 1049: reference not terminated by REFC delimiter
    …p://sbank.ir/index.php?module=cdk&func=loadlibmodule&system=cdk&sismodule=";va…

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

  • Error Line 975, Column 1049: reference to entity "func" for which no system identifier could be generated
    …p://sbank.ir/index.php?module=cdk&func=loadlibmodule&system=cdk&sismodule=";va…

    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 975, Column 1044: entity was defined here
    … "http://sbank.ir/index.php?module=cdk&func=loadlibmodule&system=cdk&sismodule…
  • Warning Line 975, Column 1064: cannot generate system identifier for general entity "system"
    …dex.php?module=cdk&func=loadlibmodule&system=cdk&sismodule=";var sisOBJWRAPPER…

    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 975, Column 1064: general entity "system" not defined and no default entity
    …dex.php?module=cdk&func=loadlibmodule&system=cdk&sismodule=";var sisOBJWRAPPER…

    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 975, Column 1070: reference not terminated by REFC delimiter
    …p?module=cdk&func=loadlibmodule&system=cdk&sismodule=";var sisOBJWRAPPER_URL =…

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

  • Error Line 975, Column 1070: reference to entity "system" for which no system identifier could be generated
    …p?module=cdk&func=loadlibmodule&system=cdk&sismodule=";var sisOBJWRAPPER_URL =…

    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 975, Column 1063: entity was defined here
    …ndex.php?module=cdk&func=loadlibmodule&system=cdk&sismodule=";var sisOBJWRAPPE…
  • Warning Line 975, Column 1075: cannot generate system identifier for general entity "sismodule"
    …ule=cdk&func=loadlibmodule&system=cdk&sismodule=";var sisOBJWRAPPER_URL = "htt…

    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 975, Column 1075: general entity "sismodule" not defined and no default entity
    …ule=cdk&func=loadlibmodule&system=cdk&sismodule=";var sisOBJWRAPPER_URL = "htt…

    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 975, Column 1084: reference not terminated by REFC delimiter
    …unc=loadlibmodule&system=cdk&sismodule=";var sisOBJWRAPPER_URL = "http:___/sba…

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

  • Error Line 975, Column 1084: reference to entity "sismodule" for which no system identifier could be generated
    …unc=loadlibmodule&system=cdk&sismodule=";var sisOBJWRAPPER_URL = "http:___/sba…

    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 975, Column 1074: entity was defined here
    …dule=cdk&func=loadlibmodule&system=cdk&sismodule=";var sisOBJWRAPPER_URL = "ht…
  • Warning Line 975, Column 1155: reference not terminated by REFC delimiter
    …___/sbank.ir/index.php?module=cdk&func=loadobject&system=cdk&sismodule=";var s…

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

  • Error Line 975, Column 1155: reference to entity "func" for which no system identifier could be generated
    …___/sbank.ir/index.php?module=cdk&func=loadobject&system=cdk&sismodule=";var s…

    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 975, Column 1044: entity was defined here
    … "http://sbank.ir/index.php?module=cdk&func=loadlibmodule&system=cdk&sismodule…
  • Warning Line 975, Column 1173: reference not terminated by REFC delimiter
    ….php?module=cdk&func=loadobject&system=cdk&sismodule=";var sisWIZARDPATH_HTTP …

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

  • Error Line 975, Column 1173: reference to entity "system" for which no system identifier could be generated
    ….php?module=cdk&func=loadobject&system=cdk&sismodule=";var sisWIZARDPATH_HTTP …

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

  • Info Line 975, Column 1063: entity was defined here
    …ndex.php?module=cdk&func=loadlibmodule&system=cdk&sismodule=";var sisOBJWRAPPE…
  • Warning Line 975, Column 1187: reference not terminated by REFC delimiter
    …k&func=loadobject&system=cdk&sismodule=";var sisWIZARDPATH_HTTP = "";var sisLo…

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

  • Error Line 975, Column 1187: reference to entity "sismodule" for which no system identifier could be generated
    …k&func=loadobject&system=cdk&sismodule=";var sisWIZARDPATH_HTTP = "";var sisLo…

    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 975, Column 1074: entity was defined here
    …dule=cdk&func=loadlibmodule&system=cdk&sismodule=";var sisOBJWRAPPER_URL = "ht…
  • Error Line 985, 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 997, Column 98: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …e="form_" action="#form_" method="POST" onSubmit="return ChkFormform_(this);" …

    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 997, Column 146: syntax of attribute value does not conform to declared value
    …="return ChkFormform_(this);" target="" onkeydown="keydownForm(this);" onmouse…

    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 997, Column 254: there is no attribute "onfocus"
    …yle="margin:0px;padding:0px;" onfocus="focusForm(this);"  onblur="blurFrom(thi…

    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 997, Column 281: there is no attribute "onblur"
    …;" onfocus="focusForm(this);"  onblur="blurFrom(this);" ><div align="" class="…

    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 997, Column 312: syntax of attribute value does not conform to declared value
    …onblur="blurFrom(this);" ><div align="" class="" style="height:0px;font-size:1…

    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 997, Column 312: value of attribute "align" cannot be ""; must be one of "left", "center", "right", "justify"
    …onblur="blurFrom(this);" ><div align="" class="" style="height:0px;font-size:1…

    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 997, Column 419: end tag for "input" omitted, but OMITTAG NO was specified
    …="activeFormName" value="form_" ></div><table width='100%'><tr><td colspan='1'…

    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 997, Column 356: start tag was here
    …s="" style="height:0px;font-size:1px"><input type="hidden" name="activeFormNam…
  • Error Line 998, Column 144: there is no attribute "form"
    …اركي جهت افتتاح حساب لازم است؟"  form="form_" onfocus="try{keydownForm(documen…

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

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

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

  • Warning Line 1009, Column 24: character "<" is the first character of a delimiter but occurred as data
    				 for(var idx=0; idx< sisDetailContainers.length; idx++) {

    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 1027, Column 10: end tag for "li" omitted, but OMITTAG NO was specified
        </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 965, Column 65: start tag was here
    …SubZoneItemContainer" id="view_ul_68"><li class="Container" id="block865" styl…
  • Error Line 1027, Column 10: end tag for "ul" omitted, but OMITTAG NO was specified
        </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 965, Column 9: start tag was here
    								<ul class="pmkUserSubZoneItemContainer" id="view_ul_68"><li class="Cont…
  • Error Line 1027, Column 10: end tag for "li" omitted, but OMITTAG NO was specified
        </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 964, Column 8: start tag was here
    							<li>
  • Error Line 1027, Column 10: end tag for "ul" omitted, but OMITTAG NO was specified
        </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 963, Column 17: start tag was here
    																<ul class="pmkUserZoneItemContainer">
  • Error Line 1027, Column 10: end tag for "td" omitted, but OMITTAG NO was specified
        </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 962, Column 17: start tag was here
    																<td valign=top width="50%" >
  • Error Line 1027, Column 10: end tag for "tr" omitted, but OMITTAG NO was specified
        </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 961, Column 13: start tag was here
    												<tr>
  • Error Line 1027, Column 10: end tag for "table" omitted, but OMITTAG NO was specified
        </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 960, Column 9: start tag was here
    								<table width="100%" cellpadding=0px cellspacing=0px>
  • Error Line 1027, Column 10: end tag for "td" omitted, but OMITTAG NO was specified
        </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 959, Column 9: start tag was here
    								<td colspan="2" valign=top>
  • Error Line 1027, Column 10: end tag for "tr" omitted, but OMITTAG NO was specified
        </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 958, Column 5: start tag was here
    				<tr>
  • Error Line 1027, Column 10: end tag for "table" omitted, but OMITTAG NO was specified
        </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 905, Column 1: start tag was here
    <table style="width: 100%" cellpadding=0px cellspacing=0px>
  • Error Line 1027, Column 10: end tag for "td" omitted, but OMITTAG NO was specified
        </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 904, Column 1: start tag was here
    <td valign=top width="75%">
  • Error Line 1027, Column 10: end tag for "tr" omitted, but OMITTAG NO was specified
        </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 702, Column 1: start tag was here
    <tr>
  • Error Line 1027, Column 10: end tag for "table" omitted, but OMITTAG NO was specified
        </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 695, Column 1: start tag was here
    <table width="100%" cellspacing="0" cellpadding="0">
  • Error Line 1027, Column 10: end tag for "td" omitted, but OMITTAG NO was specified
        </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 690, Column 9: start tag was here
    								<td>
  • Error Line 1027, Column 10: end tag for "tr" omitted, but OMITTAG NO was specified
        </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 689, Column 8: start tag was here
    							<tr>
  • Error Line 1027, Column 10: end tag for "table" omitted, but OMITTAG NO was specified
        </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 688, Column 7: start tag was here
    						<table border="0" width="100%" cellpadding="0px" cellspacing="0px" style=…
  • Error Line 1027, Column 10: end tag for "li" omitted, but OMITTAG NO was specified
        </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 688, Column 7: start tag was here
    						<table border="0" width="100%" cellpadding="0px" cellspacing="0px" style=…
  • Error Line 1027, Column 10: end tag for "ul" omitted, but OMITTAG NO was specified
        </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 687, Column 21: start tag was here
                        <ul class="CententBlockContainerMaster" id="ul2" style="wid…
  • Error Line 1030, Column 12: 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 1031, Column 14: end tag for element "ul" which is not open
    					  	 </ul></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 1031, Column 19: end tag for element "td" which is not open
    					  	 </ul></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 1032, Column 28: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    																<td valign=top width="50%" style="padding-right:5px">
  • Error Line 1032, Column 69: document type does not allow element "td" here
    																<td valign=top width="50%" style="padding-right:5px">

    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 1043, 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 1055, Column 98: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …e="form_" action="#form_" method="POST" onSubmit="return ChkFormform_(this);" …

    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 1055, Column 146: syntax of attribute value does not conform to declared value
    …="return ChkFormform_(this);" target="" onkeydown="keydownForm(this);" onmouse…

    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 1055, Column 312: syntax of attribute value does not conform to declared value
    …onblur="blurFrom(this);" ><div align="" class="" style="height:0px;font-size:1…

    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 1055, Column 312: value of attribute "align" cannot be ""; must be one of "left", "center", "right", "justify"
    …onblur="blurFrom(this);" ><div align="" class="" style="height:0px;font-size:1…

    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 1055, Column 419: end tag for "input" omitted, but OMITTAG NO was specified
    …="activeFormName" value="form_" ></div><table width='100%'><tr><td colspan='1'…

    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 1055, Column 356: start tag was here
    …s="" style="height:0px;font-size:1px"><input type="hidden" name="activeFormNam…
  • Warning Line 1067, Column 24: character "<" is the first character of a delimiter but occurred as data
    				 for(var idx=0; idx< sisDetailContainers.length; idx++) {

    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 1085, Column 10: end tag for "li" omitted, but OMITTAG NO was specified
        </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 1035, Column 65: start tag was here
    …SubZoneItemContainer" id="view_ul_69"><li class="Container" id="block866" styl…
  • Error Line 1085, Column 10: end tag for "ul" omitted, but OMITTAG NO was specified
        </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 1035, Column 9: start tag was here
    								<ul class="pmkUserSubZoneItemContainer" id="view_ul_69"><li class="Cont…
  • Error Line 1085, Column 10: end tag for "li" omitted, but OMITTAG NO was specified
        </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 1034, Column 8: start tag was here
    							<li>
  • Error Line 1085, Column 10: end tag for "ul" omitted, but OMITTAG NO was specified
        </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 1033, Column 17: start tag was here
    																<ul class="pmkUserZoneItemContainer">
  • Error Line 1085, Column 10: end tag for "td" omitted, but OMITTAG NO was specified
        </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 1032, Column 17: start tag was here
    																<td valign=top width="50%" style="padding-right:5px">
  • Error Line 1086, 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 1087, Column 5: end tag for element "ul" which is not open
    </ul>

    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 1088, Column 12: 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 1089, Column 14: end tag for element "ul" which is not open
    					  	 </ul></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 1089, Column 19: end tag for element "td" which is not open
    					  	 </ul></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 1090, Column 17: 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 1091, Column 16: end tag for element "table" which is not open
    								</table>

    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 1092, Column 13: 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 1093, Column 9: 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 1094, Column 8: document type does not allow element "tr" here; assuming missing "table" start-tag
    				<tr>
  • Error Line 1095, Column 28: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    				<td colspan="2" valign=top><ul class="pmkUserZoneItemContainer">
  • Error Line 1100, Column 193: there is no attribute "onMouseOver"
    …;margin:0px;cursor:hand;' onMouseOver='return show_tab(305);' id='img_305' src…

    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 1100, Column 322: required attribute "alt" not specified
    …ages/far/composite_tab/305_over.jpg' /></td><td class='unselected_tab' id='td_…

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

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

  • Error Line 1100, Column 567: required attribute "alt" not specified
    …an/images/far/composite_tab/306.jpg' /></td><td class='unselected_tab' id='td_…

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

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

  • Error Line 1100, Column 812: required attribute "alt" not specified
    …an/images/far/composite_tab/307.jpg' /></td><td class='unselected_tab' id='td_…

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

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

  • Error Line 1100, Column 1057: required attribute "alt" not specified
    …an/images/far/composite_tab/308.jpg' /></td><td class='unselected_tab' id='td_…

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

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

  • Error Line 1100, Column 1302: required attribute "alt" not specified
    …an/images/far/composite_tab/309.jpg' /></td><td class='unselected_tab' id='td_…

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

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

  • Error Line 1100, Column 1547: required attribute "alt" not specified
    …an/images/far/composite_tab/310.jpg' /></td></tr></table> <div  class='div_are…

    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 1155, Column 145: required attribute "alt" not specified
    …c="http://sbank.ir/parameters/sbank/themes/saman/images/netbank_tab.jpg"/></td>

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

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

  • Error Line 1162, Column 12: 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 1177, Column 59: document type does not allow element "center" here
    …entById('div_area').innerHTML="<center><img id='loading_icon' src='http://sban…

    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 1177, Column 178: required attribute "alt" not specified
    …loading.gif' width='32px' height='32px' style='padding-top:30px;' /></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 1185, Column 29: character ";" not allowed in attribute specification list
        		for(i=0;i<links.length;i++)
  • Error Line 1185, Column 29: element "links.length" undefined
        		for(i=0;i<links.length;i++)

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1187, Column 27: character ";" not allowed in attribute specification list
    			for(i=0;i<links2.length;i++)
  • Error Line 1187, Column 27: element "links2.length" undefined
    			for(i=0;i<links2.length;i++)

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1209, Column 47: cannot generate system identifier for general entity "type"
    …leAjax(host+'/index.php'+'?module=pmk&type=user&func=showBlock&bid='+old_bid+'…

    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 1209, Column 47: general entity "type" not defined and no default entity
    …leAjax(host+'/index.php'+'?module=pmk&type=user&func=showBlock&bid='+old_bid+'…

    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 1209, Column 51: reference not terminated by REFC delimiter
    …ax(host+'/index.php'+'?module=pmk&type=user&func=showBlock&bid='+old_bid+'&sta…

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

  • Error Line 1209, Column 51: reference to entity "type" for which no system identifier could be generated
    …ax(host+'/index.php'+'?module=pmk&type=user&func=showBlock&bid='+old_bid+'&sta…

    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 1209, Column 46: entity was defined here
    …pleAjax(host+'/index.php'+'?module=pmk&type=user&func=showBlock&bid='+old_bid+…
  • Warning Line 1209, Column 61: reference not terminated by REFC delimiter
    …index.php'+'?module=pmk&type=user&func=showBlock&bid='+old_bid+'&standalone=1'…

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

  • Error Line 1209, Column 61: reference to entity "func" for which no system identifier could be generated
    …index.php'+'?module=pmk&type=user&func=showBlock&bid='+old_bid+'&standalone=1'…

    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 975, Column 1044: entity was defined here
    … "http://sbank.ir/index.php?module=cdk&func=loadlibmodule&system=cdk&sismodule…
  • Warning Line 1209, Column 72: cannot generate system identifier for general entity "bid"
    …'?module=pmk&type=user&func=showBlock&bid='+old_bid+'&standalone=1','GET', '',…

    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 1209, Column 72: general entity "bid" not defined and no default entity
    …'?module=pmk&type=user&func=showBlock&bid='+old_bid+'&standalone=1','GET', '',…

    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 1209, Column 75: reference not terminated by REFC delimiter
    …odule=pmk&type=user&func=showBlock&bid='+old_bid+'&standalone=1','GET', '', sh…

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

  • Error Line 1209, Column 75: reference to entity "bid" for which no system identifier could be generated
    …odule=pmk&type=user&func=showBlock&bid='+old_bid+'&standalone=1','GET', '', sh…

    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 1209, Column 71: entity was defined here
    …+'?module=pmk&type=user&func=showBlock&bid='+old_bid+'&standalone=1','GET', ''…
  • Warning Line 1209, Column 88: cannot generate system identifier for general entity "standalone"
    …e=user&func=showBlock&bid='+old_bid+'&standalone=1','GET', '', showTabContent,…

    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 1209, Column 88: general entity "standalone" not defined and no default entity
    …e=user&func=showBlock&bid='+old_bid+'&standalone=1','GET', '', showTabContent,…

    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 1209, Column 98: reference not terminated by REFC delimiter
    …c=showBlock&bid='+old_bid+'&standalone=1','GET', '', showTabContent, 'xmlReque…

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

  • Error Line 1209, Column 98: reference to entity "standalone" for which no system identifier could be generated
    …c=showBlock&bid='+old_bid+'&standalone=1','GET', '', showTabContent, 'xmlReque…

    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 1209, Column 87: entity was defined here
    …pe=user&func=showBlock&bid='+old_bid+'&standalone=1','GET', '', showTabContent…
  • Error Line 1224, Column 13: end tag for "links2.length" 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 1187, Column 13: start tag was here
    			for(i=0;i<links2.length;i++)
  • Error Line 1224, Column 13: end tag for "links.length" 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 1185, Column 16: start tag was here
        		for(i=0;i<links.length;i++)
  • Error Line 1225, Column 11: 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 1225, Column 11: 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 1289, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    								<td valign=top width="70%" style="padding-left:10px;padding-right:5px">…
  • Error Line 1305, Column 47: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ss="newsBlockItem"><table cellpadding=2 cellspaceing=0><tr><td><a href="http:/…
  • Error Line 1305, Column 62: there is no attribute "cellspaceing"
    …em"><table cellpadding=2 cellspaceing=0><tr><td><a href="http://sbank.ir/news/…

    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 1305, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …em"><table cellpadding=2 cellspaceing=0><tr><td><a href="http://sbank.ir/news/…
  • Error Line 1305, Column 379: end tag for "img" omitted, but OMITTAG NO was specified
    …اول در مبارزه با پول شويي" title="كسب رتبه اول در مبارزه با پول شويي"></a></td>

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

  • Info Line 1305, Column 143: start tag was here
    …42-کسب-رتبه-اول-مبارزه-پول-شويي.html"><img class="newsImage" src="http://sbank…
  • Error Line 1306, Column 152: there is no attribute "alt"
    …سب-رتبه-اول-مبارزه-پول-شويي.html" alt="كسب رتبه اول در مبارزه با پول شويي" tit…

    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 1313, Column 42: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …v style="padding:10px;"><table border=0 cellspacing="2" width="100%" class="ov…
  • Error Line 1313, Column 163: value of attribute "align" cannot be "center"; must be one of "top", "middle", "bottom", "left", "right"
    …tical-align:middle'><img align='center' src='http://sbank.ir/parameters/sbank/…

    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 1313, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    …ign='center' src='http://sbank.ir/parameters/sbank/images/bb.gif' alt='' ></td>

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

  • Info Line 1313, Column 145: start tag was here
    …h='5px' style='vertical-align:middle'><img align='center' src='http://sbank.ir…
  • Error Line 1316, Column 69: value of attribute "align" cannot be "center"; must be one of "top", "middle", "bottom", "left", "right"
    …tical-align:middle'><img align='center' src='http://sbank.ir/parameters/sbank/…

    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 1316, Column 136: end tag for "img" omitted, but OMITTAG NO was specified
    …ign='center' src='http://sbank.ir/parameters/sbank/images/bb.gif' alt='' ></td>

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

  • Info Line 1316, Column 51: start tag was here
    …h='5px' style='vertical-align:middle'><img align='center' src='http://sbank.ir…
  • Error Line 1319, Column 69: value of attribute "align" cannot be "center"; must be one of "top", "middle", "bottom", "left", "right"
    …tical-align:middle'><img align='center' src='http://sbank.ir/parameters/sbank/…

    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 1319, Column 136: end tag for "img" omitted, but OMITTAG NO was specified
    …ign='center' src='http://sbank.ir/parameters/sbank/images/bb.gif' alt='' ></td>

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

  • Info Line 1319, Column 51: start tag was here
    …h='5px' style='vertical-align:middle'><img align='center' src='http://sbank.ir…
  • Error Line 1322, Column 69: value of attribute "align" cannot be "center"; must be one of "top", "middle", "bottom", "left", "right"
    …tical-align:middle'><img align='center' src='http://sbank.ir/parameters/sbank/…

    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 1322, Column 136: end tag for "img" omitted, but OMITTAG NO was specified
    …ign='center' src='http://sbank.ir/parameters/sbank/images/bb.gif' alt='' ></td>

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

  • Info Line 1322, Column 51: start tag was here
    …h='5px' style='vertical-align:middle'><img align='center' src='http://sbank.ir…
  • Error Line 1325, Column 69: value of attribute "align" cannot be "center"; must be one of "top", "middle", "bottom", "left", "right"
    …tical-align:middle'><img align='center' src='http://sbank.ir/parameters/sbank/…

    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 1325, Column 136: end tag for "img" omitted, but OMITTAG NO was specified
    …ign='center' src='http://sbank.ir/parameters/sbank/images/bb.gif' alt='' ></td>

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

  • Info Line 1325, Column 51: start tag was here
    …h='5px' style='vertical-align:middle'><img align='center' src='http://sbank.ir…
  • Error Line 1327, Column 80: value of attribute "align" cannot be "center"; must be one of "top", "middle", "bottom", "left", "right"
    …iddle' width='18px'><img align='center' src='http://sbank.ir/parameters/sbank/…

    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 1327, Column 156: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='http://sbank.ir/parameters/sbank/images/special_far.gif' alt='' ></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 1327, Column 62: start tag was here
    …='vertical-align:middle' width='18px'><img align='center' src='http://sbank.ir…
  • Error Line 1328, Column 5: end tag for "table" omitted, but OMITTAG NO was specified
    </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 1313, Column 28: start tag was here
    <div style="padding:10px;"><table border=0 cellspacing="2" width="100%" class="…
  • Error Line 1328, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </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 1313, Column 1: start tag was here
    <div style="padding:10px;"><table border=0 cellspacing="2" width="100%" class="…
  • Error Line 1328, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </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 1312, Column 1: start tag was here
    <td style="vertical-align:top;padding-right:10px;">
  • Error Line 1330, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        			<td align=left style="vertical-align:bottom" colspan=3>
  • Error Line 1330, Column 61: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        			<td align=left style="vertical-align:bottom" colspan=3>
  • Error Line 1339, Column 58: required attribute "alt" not specified
    <img src="/parameters/sbank/themes/saman/images/rss1.gif"> 

    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 1339, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
    <img src="/parameters/sbank/themes/saman/images/rss1.gif"> 

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

  • Info Line 1339, Column 1: start tag was here
    <img src="/parameters/sbank/themes/saman/images/rss1.gif"> 
  • Error Line 1343, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 1292, Column 5: start tag was here
        <div class="BlockNews" style="">
  • Error Line 1343, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 1291, Column 65: start tag was here
    …kUserSubZoneItemContainer" id="view_ul_72"><li class="Container" id="block436">
  • Error Line 1343, Column 5: end tag for "ul" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 1291, Column 9: start tag was here
    								<ul class="pmkUserSubZoneItemContainer" id="view_ul_72"><li class="Cont…
  • Error Line 1343, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 1290, Column 8: start tag was here
    							<li>
  • Error Line 1343, Column 5: end tag for "ul" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 1289, Column 80: start tag was here
    …yle="padding-left:10px;padding-right:5px"><ul class="pmkUserZoneItemContainer">
  • Error Line 1348, Column 10: 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 1349, 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 1350, Column 5: end tag for element "ul" which is not open
    </ul>

    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 1351, Column 12: 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 1352, Column 14: end tag for element "ul" which is not open
    					  	 </ul></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 1352, Column 19: end tag for element "td" which is not open
    					  	 </ul></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 1353, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    								<td valign=top width="30%"><ul class="pmkUserZoneItemContainer">
  • Error Line 1376, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 1371, Column 1: start tag was here
    <li>
  • Error Line 1387, Column 155: end tag for "area" omitted, but OMITTAG NO was specified
    …hape="rect" alt="صرافي سرمايه" title="صرافي سرمايه" coords="144, 22, 207, 103">

    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 1387, Column 1: start tag was here
    <area href="http://sbank.ir/services/partner/1354-شرکت-صرافي-سرمايه.html" shape…
  • Error Line 1388, Column 191: end tag for "area" omitted, but OMITTAG NO was specified
    …توسعه ساختمان سرمايه " title="توسعه ساختمان سرمايه " coords="73, 23, 136, 103">

    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 1388, Column 1: start tag was here
    <area href="http://sbank.ir/services/partner/1433-شرکت-توسعه-ساختمان-سرمايه-سها…
  • Error Line 1389, Column 184: end tag for "area" omitted, but OMITTAG NO was specified
    …ارت الكترونيك سرمايه " title="تجارت الكترونيك سرمايه " coords="3, 22, 66, 102">

    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 1389, Column 1: start tag was here
    <area href="http://sbank.ir/services/partner/1434-شرکت-تجارت-الکترونيک-سرمايه.h…
  • Error Line 1390, Column 101: required attribute "alt" not specified
    …s/sbank/themes/saman/images/far/sherkathaye_tabee.jpg" usemap="#FPMap0"   ></p>

    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 1390, Column 105: end tag for "img" omitted, but OMITTAG NO was specified
    …s/sbank/themes/saman/images/far/sherkathaye_tabee.jpg" usemap="#FPMap0"   ></p>

    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 1390, Column 7: start tag was here
    </map><img src="/parameters/sbank/themes/saman/images/far/sherkathaye_tabee.jpg…
  • Error Line 1397, Column 9: 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 1398, Column 8: end tag for element "table" which is not open
    </table>

    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 1399, Column 5: 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 1400, Column 5: 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 1401, Column 8: end tag for element "table" which is not open
    </table>

    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 1403, Column 13: 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 1404, Column 12: 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 1405, Column 14: end tag for element "table" which is not open
    						</table>

    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 1406, Column 25: end tag for element "ul" which is not open
                        </ul>

    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 1407, Column 22: 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 1408, Column 17: 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 1409, Column 13: end tag for element "ul" which is not open
            </ul>

    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 1425, Column 146: required attribute "alt" not specified
    …"http://sbank.ir/parameters/sbank/themes/saman/images/far/formicon.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 1433, Column 10: 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 1434, Column 10: 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 1450, Column 7: end tag for "bgsound" omitted, but OMITTAG NO was specified
    </body>

    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 1: start tag was here
    <bgsound id="alert_sound" loop=1>

Visitor Analysis

Daily Visitor
  • 3.033 visits
Daily Visitor

In Page Analysis