PSB is being developed by Pooya Paridel. صفحه اصلي پيوندها نقشه سايت پست الکترونيک English  جستجو در وب‌گاه انتهاي دودكش پشت بام مي بايست مجهز به كلاهك H شكل باشد تا دود به ...

nigc.ir
  • Domain Name
    nigc.ir
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #29267
  • Page Size
    39.3 KB
  • Ip Address
    217.218.111.11
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    11 GIF, 2 JPG, 0 PNG

Website Meta Analysis

  • Title
    شركت ملي گاز ايران
  • Meta Keyword
  • Meta Description
    PSB is being developed by Pooya Paridel. صفحه اصلي پيوندها نقشه سايت پست الکترونيک English  جستجو در وب‌گاه انتهاي دودكش پشت بام مي بايست مجهز به كلاهك H شكل باشد تا دود به محيط خانه بر نگردد .         1392/7/20 انجام بيش از 2 هزار مورد كار ...

Technical Analysis

  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    217.218.111.11
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 12 Oct 2013 09:02:23 GMT
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • content-encoding: gzip
  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-length: 8820
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for nigc.ir

IP 217.218.111.11 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 205 Errors
  • 24 Warnings
Ratio Text/Html
  • 0.6250931491877391
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html dir="rtl"><head><meta http-equiv="Content-Type" content="text/html; chars…

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Warning Line 1, Column 90: NET-enabling start-tag requires SHORTTAG YES
    …e" content="text/html; charset=UTF-8" /><title>شركت ملي گاز ايران</title><link…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1, Column 91: character data is not allowed here
    …" content="text/html; charset=UTF-8" /><title>شركت ملي گاز ايران</title><link …

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 1, Column 321: required attribute "TYPE" not specified
    …cript><script src='Scripts/menurtl.js'></script><script src='menu_item.aspx?Pa…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1, Column 370: required attribute "TYPE" not specified
    …script src='menu_item.aspx?PageID=467'></script><div style="display:none">PSB …

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1, Column 783: there is no attribute "HEIGHT"
    …=0 cellpadding=0 cellspacing=0 height=31 width="100%"><tr><td onclick="window.…

    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 1, Column 2471: there is no attribute "XMLNS:MSXSL"
    …pan id="special__"><table xmlns:msxsl="urn:schemas-microsoft-com:xslt" border=…

    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 1, Column 2558: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …adding="0" cellspacing="0" width="188"><tbody><tr><td><a onclick="oSearch.styl…

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

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

  • Warning Line 1, Column 4310: NET-enabling start-tag requires SHORTTAG YES
    …a></td></tr></tbody></table></span><br/><TABLE cellSpacing=0 cellPadding=0 wid…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1, Column 4465: there is no attribute "BACKGROUND"
    …x;z-index:4" class=sidebar background=skin/sa34c0/cat_b.gif><tr><td class=side…

    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 1, Column 4469: NET-enabling start-tag requires SHORTTAG YES
    …index:4" class=sidebar background=skin/sa34c0/cat_b.gif><tr><td class=sideTop>…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1, Column 4470: character data is not allowed here
    …ndex:4" class=sidebar background=skin/sa34c0/cat_b.gif><tr><td class=sideTop><…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 1, Column 4476: end tag for "TABLE" which is not finished
    …" class=sidebar background=skin/sa34c0/cat_b.gif><tr><td class=sideTop></td></…

    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 1, Column 4476: end tag for "TABLE" which is not finished
    …" class=sidebar background=skin/sa34c0/cat_b.gif><tr><td class=sideTop></td></…

    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 1, Column 4624: required attribute "ACTION" not specified
    …arBody><tr><form method=get name=SForm><td width=5></td><td><table border=0><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 1, Column 4624: document type does not allow element "FORM" here; missing one of "TH", "TD" start-tag
    …arBody><tr><form method=get name=SForm><td width=5></td><td><table border=0><t…

    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 1, Column 4636: document type does not allow element "TD" here
    …form method=get name=SForm><td width=5></td><td><table border=0><tr><td><input…

    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 1, Column 4645: document type does not allow element "TD" here
    …od=get name=SForm><td width=5></td><td><table border=0><tr><td><input type=but…

    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 1, Column 4805: an attribute value must be a literal unless it contains only name characters
    …button onClick='SForm.submit()' value=جستجو style="width:73%"></td><td align=c…

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

  • Error Line 1, Column 5019: document type does not allow element "TD" here
    …ht"></td></tr></table></td><td width=5></td></FORM></tr></table></td></tr><tr>…

    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 1, Column 5036: end tag for "TR" which is not finished
    …able></td><td width=5></td></FORM></tr></table></td></tr><tr><td class=sideEnd…

    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.

  • Warning Line 1, Column 5119: NET-enabling start-tag requires SHORTTAG YES
    …p;جستجو در وب‌گاه</td></tr></table><br/></td><td class="s6" rowspan=2></td><td…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1, Column 5125: end tag for element "TD" which is not open
    …و در وب‌گاه</td></tr></table><br/></td><td class="s6" rowspan=2></td><td colsp…

    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 1, Column 5150: document type does not allow element "TD" here
    …ble><br/></td><td class="s6" rowspan=2></td><td colspan=4 class="s7"><table bo…

    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 1, Column 5180: document type does not allow element "TD" here
    …owspan=2></td><td colspan=4 class="s7"><table border=0 cellpadding=0 cellspaci…

    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 1, Column 5234: an attribute value must be a literal unless it contains only name characters
    … cellpadding=0 cellspacing=0 width=100%><tr><td><a class='Headline' href='#1'>…

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

  • Error Line 1, Column 5301: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … href='#1'><div style="DIRECTION: rtl"><span style="color: #0000cc">دودكش بايد…

    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 1, Column 5541: end tag for element "TR" which is not open
    …</span></b></td></tr></table></td></tr><tr><td class="s8" valign=top style="he…

    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 1, Column 5545: document type does not allow element "TR" here
    …an></b></td></tr></table></td></tr><tr><td class="s8" valign=top style="height…

    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 2, Column 90: document type does not allow element "FORM" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME" start-tag
    …="display:none"><form name="form1" method="post" action="Site.aspx" id="form1">

    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 4, Column 1: value of attribute "ID" invalid: "_" cannot start a name
    __VIEWSTATE" value="" />

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

  • Warning Line 4, Column 23: NET-enabling start-tag requires SHORTTAG YES
    __VIEWSTATE" value="" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 14, Column 77: there is no attribute "CELLPADING"
    …atacontainer'> <table dir=rtl border=0 width='100%' cellpading=0 cellspacing=0>

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

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

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

  • Warning Line 15, Column 105: cannot generate system identifier for general entity "LnkIdn"
    …/www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخد…

    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 15, Column 105: general entity "LnkIdn" not defined and no default entity
    …/www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخد…

    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.

  • Error Line 15, Column 111: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخدام شرک…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Warning Line 18, Column 177: NET-enabling start-tag requires SHORTTAG YES
    …e: solid; margin: 3px; float: right;" />مدير توسعه منابع انساني شركت ملي گاز ا…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 24, Column 4: document type does not allow element "TR" here
    <tr><td class=bodyEnd></td></tr>

    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 25, Column 5: "TR" not finished but containing element ended
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…
  • Error Line 25, Column 5: end tag for "TABLE" omitted, but its declaration does not permit this
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 14, Column 29: start tag was here
    <div class='datacontainer'> <table dir=rtl border=0 width='100%' cellpading=0 c…
  • Error Line 25, Column 5: end tag for "DIV" omitted, but its declaration does not permit this
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 14, Column 1: start tag was here
    <div class='datacontainer'> <table dir=rtl border=0 width='100%' cellpading=0 c…
  • Error Line 25, Column 5: end tag for "DIV" omitted, but its declaration does not permit this
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1, Column 5593: start tag was here
    …</tr><tr><td class="s8" valign=top style="height:700px"><div class='container'>
  • Error Line 25, Column 18: end tag for element "TABLE" which is not open
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 26, Column 94: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F11&LnkIdn=111064' class=ItemPath>مديرعامل شركت گا…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Warning Line 29, Column 160: NET-enabling start-tag requires SHORTTAG YES
    …: right; width: 100px; height: 70px;" />به گزارش روابط عمومي شركت گاز استان خر…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 33, Column 4: document type does not allow element "TR" here
    <tr><td class=bodyEnd></td></tr>

    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 34, Column 5: end tag for element "TD" which is not open
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 34, Column 10: end tag for "TR" which is not finished
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 35, Column 94: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181613&LnkIdn=111060' class=ItemPath>بهره مندي 76 درص…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Warning Line 38, Column 177: NET-enabling start-tag requires SHORTTAG YES
    …t: right; width: 83px; height: 80px;" />مدير عامل شركت گاز استان زنجان گفت: به…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 42, Column 4: document type does not allow element "TR" here
    <tr><td class=bodyEnd></td></tr>

    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 43, Column 5: end tag for element "TD" which is not open
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 43, Column 10: end tag for "TR" which is not finished
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 44, Column 92: reference to entity "LnkIdn" for which no system identifier could be generated
    … href='Site.aspx?ParTree=111816&LnkIdn=110971' class=ItemPath>برگزاري مراسم بز…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Warning Line 47, Column 155: NET-enabling start-tag requires SHORTTAG YES
    …argin: 3px; float: right;" width="64" />در مراسمي كه ظهر روز چهارشنبه مورخ 18/…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 53, Column 4: document type does not allow element "TR" here
    <tr><td class=bodyEnd></td></tr>

    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 54, Column 5: end tag for element "TD" which is not open
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 54, Column 10: end tag for "TR" which is not finished
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 55, Column 92: reference to entity "LnkIdn" for which no system identifier could be generated
    … href='Site.aspx?ParTree=111816&LnkIdn=110948' class=ItemPath>برگ زرين ديگري ب…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Warning Line 58, Column 159: NET-enabling start-tag requires SHORTTAG YES
    …gin: 3px; float: right; width: 73px;" />در بيست و ششمين جشنواره بين المللي خوا…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 62, Column 4: document type does not allow element "TR" here
    <tr><td class=bodyEnd></td></tr>

    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 63, Column 5: end tag for element "TD" which is not open
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 63, Column 10: end tag for "TR" which is not finished
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 64, Column 94: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181613&LnkIdn=110946' class=ItemPath>16   پروژه  گاز …

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Warning Line 67, Column 159: NET-enabling start-tag requires SHORTTAG YES
    …e: solid; margin: 3px; float: right;" />در عصر پنجمین روز دهه مبارک فجر طی آئی…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 71, Column 4: document type does not allow element "TR" here
    <tr><td class=bodyEnd></td></tr>

    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 72, Column 5: end tag for element "TD" which is not open
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 72, Column 10: end tag for "TR" which is not finished
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 73, Column 94: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181613&LnkIdn=110944' class=ItemPath>6 روستاي شهرستان…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Warning Line 76, Column 159: NET-enabling start-tag requires SHORTTAG YES
    …e: solid; margin: 3px; float: right;" />همزمان با دهه مبارك فجر 6 روستاي روئين…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 80, Column 4: document type does not allow element "TR" here
    <tr><td class=bodyEnd></td></tr>

    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 81, Column 5: end tag for element "TD" which is not open
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 81, Column 10: end tag for "TR" which is not finished
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 82, Column 94: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181613&LnkIdn=110939' class=ItemPath>آخرين وضعيت گازر…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Warning Line 85, Column 159: NET-enabling start-tag requires SHORTTAG YES
    …e: solid; margin: 3px; float: right;" />مهندس اسماعیل هیبتیان مدير عامل شركت گ…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 89, Column 4: document type does not allow element "TR" here
    <tr><td class=bodyEnd></td></tr>

    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 90, Column 5: end tag for element "TD" which is not open
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 90, Column 10: end tag for "TR" which is not finished
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 91, Column 94: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F14&LnkIdn=110943' class=ItemPath>صرفه جويي يك ميل…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Warning Line 94, Column 159: NET-enabling start-tag requires SHORTTAG YES
    …e: solid; margin: 3px; float: right;" />مدير منطقه يك شرکت انتقال گاز ايران از…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 98, Column 4: document type does not allow element "TR" here
    <tr><td class=bodyEnd></td></tr>

    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 99, Column 5: end tag for element "TD" which is not open
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 99, Column 10: end tag for "TR" which is not finished
    </td></tr></table></div><div class='datacontainer'> <table dir=rtl border=0 wid…

    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 100, Column 183: an attribute value must be a literal unless it contains only name characters
    …white;font-weight:bold' href=site.aspx?partree=11181F>ادامه...</a></td></tr></…

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

  • Error Line 100, Column 232: end tag for element "P" which is not open
    …old' href=site.aspx?partree=11181F>ادامه...</a></td></tr></table></p></td></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 102, Column 100: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …x;scrollbar-base-color : #c5daf3;"><li><a href='Site.aspx?ParTree=11181F13&Lnk…

    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 102, Column 143: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F13&LnkIdn=110967'>برگزاري يادواره شهدا و تجليل از…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 238: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    … در شركت پالايش گاز فجرجم </a></li><li><a href='Site.aspx?ParTree=11181F11&Lnk…

    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 102, Column 281: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F11&LnkIdn=110966'>نصب دکل هاي صاعقه گيرو چاه ارت …

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 368: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …ه هاي CGSو TBS استان بوشهر</a></li><li><a href='Site.aspx?ParTree=11181F13&Lnk…

    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 102, Column 411: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F13&LnkIdn=110965'>در ششمين روز دهه‌ي مبارك فجر؛ م…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 530: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …مديسن مجتمع گاز پارس جنوبي</a></li><li><a href='Site.aspx?ParTree=11181F11&Lnk…

    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 102, Column 573: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F11&LnkIdn=110964'>آغاز عمليات اجرايي خط انتقال گا…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 673: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …تان در استان خراسان جنوبي </a></li><li><a href='Site.aspx?ParTree=11181F11&Lnk…

    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 102, Column 716: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F11&LnkIdn=110963'>حضور پر رنگ  شركت گاز استان خوز…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 800: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …ر نمايشگاه دهه ي مبارك فجر</a></li><li><a href='Site.aspx?ParTree=11181F13&Lnk…

    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 102, Column 843: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F13&LnkIdn=110962'>در آيين افتتاح خانه بهداشت يكي …

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 967: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …عامل شركت پالايش گاز فجرجم</a></li><li><a href='Site.aspx?ParTree=11181F13&Lnk…

    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 102, Column 1010: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F13&LnkIdn=110960'>رييس روابط عمومي شركت پالايش گا…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 1125: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …ي وهنري در شهركهاي مسكوني </a></li><li><a href='Site.aspx?ParTree=11181F11&Lnk…

    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 102, Column 1168: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F11&LnkIdn=110959'>برگزاري دوره آموزشي امداد و فور…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 1267: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …توسط شرکت گاز استان بوشهر </a></li><li><a href='Site.aspx?ParTree=111814&LnkId…

    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 102, Column 1308: reference to entity "LnkIdn" for which no system identifier could be generated
    … href='Site.aspx?ParTree=111814&LnkIdn=110958'>برترين هاي مسابقات ورزشي دهه مب…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 1384: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …مبارک فجر منطقه 8 معرفي شد</a></li><li><a href='Site.aspx?ParTree=11181F13&Lnk…

    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 102, Column 1427: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F13&LnkIdn=110957'>آغاز جشن هاي دهه مبارك فجرانقلا…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 1514: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …در شركت پالايش گاز بيدبلند</a></li><li><a href='Site.aspx?ParTree=11181F13&Lnk…

    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 102, Column 1557: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F13&LnkIdn=110956'>نمايشگاه خانواده و جنگ نرم در ف…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 1654: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    … پالايش گازفجرجم افتتاح شد</a></li><li><a href='Site.aspx?ParTree=11181F11&Lnk…

    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 102, Column 1697: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F11&LnkIdn=110955'>آغاز عمليات اجرايي شبکه تغذيه و…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 1792: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …يشه و مود در خراسان جنوبي </a></li><li><a href='Site.aspx?ParTree=111814&LnkId…

    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 102, Column 1833: reference to entity "LnkIdn" for which no system identifier could be generated
    … href='Site.aspx?ParTree=111814&LnkIdn=110954'>برگزاري سومين دوره مسابقات ورزش…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 1940: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …ن؛ همزمان با دهه مبارك فجر</a></li><li><a href='Site.aspx?ParTree=11181F11&Lnk…

    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 102, Column 1983: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F11&LnkIdn=110953'>اجراي مصوبات سفر مقام معظم رهبر…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 102, Column 2051: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    … معظم رهبري وظيفه ديني است</a></li><li><a href='Site.aspx?ParTree=11181F11&Lnk…

    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 102, Column 2094: reference to entity "LnkIdn" for which no system identifier could be generated
    …ref='Site.aspx?ParTree=11181F11&LnkIdn=110952'> شركت گاز استان زنجان موفق به ت…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 105, Column 4: document type does not allow element "TR" here
    <tr><td class=bodyEnd></td></tr>

    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 106, Column 5: end tag for element "TD" which is not open
    </td></tr></table></div></div><table border=0 cellpadding=0 cellspacing=0 class…

    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 106, Column 10: end tag for "TR" which is not finished
    </td></tr></table></div></div><table border=0 cellpadding=0 cellspacing=0 class…

    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 106, Column 116: required attribute "ACTION" not specified
    …ss=lbox><FORM name=Weather method=post><tbody><tr><td style="height:71px;paddi…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 106, Column 116: document type does not allow element "FORM" here
    …ss=lbox><FORM name=Weather method=post><tbody><tr><td style="height:71px;paddi…

    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 106, Column 123: document type does not allow element "TBODY" here; assuming missing "TABLE" start-tag
    …><FORM name=Weather method=post><tbody><tr><td style="height:71px;padding:5px"…
  • Error Line 106, Column 2056: required attribute "TYPE" not specified
    …N></SELECT><SCRIPT language=javascript>function WeatherLinkCheck(){   /*window…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 106, Column 2388: end tag for "TABLE" omitted, but its declaration does not permit this
    …:5px">آب و هوا</td></tr></tbody></form></table><span style="float:right;width=…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 106, Column 117: start tag was here
    …s=lbox><FORM name=Weather method=post><tbody><tr><td style="height:71px;paddin…
  • Error Line 106, Column 2396: end tag for "TABLE" which is not finished
    … و هوا</td></tr></tbody></form></table><span style="float:right;width=2px;">&n…

    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 106, Column 2950: an attribute value must be a literal unless it contains only name characters
    …118" target="_TOP"><img src=image.ashx?/images/RSSVersion.gif border="0"></a><…

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

  • Error Line 106, Column 2984: required attribute "ALT" not specified
    …ashx?/images/RSSVersion.gif border="0"></a><BR>وبلاگ روابط عمومي / پادكست<BR><…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 106, Column 3219: end tag for element "TD" which is not open
    … عمومي الكترونيك</td></tr></table></td><td class="s9"></td><td class="s10" val…

    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 106, Column 3234: document type does not allow element "TD" here
    …ك</td></tr></table></td><td class="s9"></td><td class="s10" valign=top><table …

    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 106, Column 3266: document type does not allow element "TD" here
    …s="s9"></td><td class="s10" valign=top><table class="sidebar"  border=0 cellpa…

    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 106, Column 3805: there is no attribute "PLUGINSPAGE"
    …alue="transparent"><embed pluginspage="http://www.macromedia.com/shockwave/dow…

    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 106, Column 3858: there is no attribute "TYPE"
    …romedia.com/shockwave/download/" type="application/x-shockwave-flash" src='uti…

    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 106, Column 3894: there is no attribute "SRC"
    …e="application/x-shockwave-flash" src='utils/showadv.aspx?AdvIdn=1016' </embed…

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

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

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

  • Warning Line 106, Column 3927: unclosed start-tag requires SHORTTAG YES
    … src='utils/showadv.aspx?AdvIdn=1016' </embed></object><div></td></tr><tr><td …

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Error Line 106, Column 3927: element "EMBED" undefined
    … src='utils/showadv.aspx?AdvIdn=1016' </embed></object><div></td></tr><tr><td …

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 106, Column 3953: end tag for "DIV" omitted, but its declaration does not permit this
    …dvIdn=1016' </embed></object><div></td></tr><tr><td class=sideEnd>&nbsp;تصوير …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 106, Column 3944: start tag was here
    …dv.aspx?AdvIdn=1016' </embed></object><div></td></tr><tr><td class=sideEnd>&nb…
  • Error Line 106, Column 3953: end tag for "DIV" omitted, but its declaration does not permit this
    …dvIdn=1016' </embed></object><div></td></tr><tr><td class=sideEnd>&nbsp;تصوير …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 106, Column 3476: start tag was here
    …</tr><tr><td id="oAdv" align="center"><div class="sidebarBody"><object classid…
  • Warning Line 106, Column 4017: NET-enabling start-tag requires SHORTTAG YES
    …d>&nbsp;تصوير روز</td></tr></table><br/><script>if(oAdv.innerHTML.length>10) o…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 106, Column 4026: required attribute "TYPE" not specified
    …صوير روز</td></tr></table><br/><script>if(oAdv.innerHTML.length>10) oAdvTable.…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 106, Column 4173: an attribute value must be a literal unless it contains only name characters
    … cellspacing=0 width="201" background=/skin/sa34c0/cat_b.gif><tr><td class=sid…

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

  • Error Line 106, Column 4343: value of attribute "VALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
    …><td colspan=2 align="justify" valign=center height="30"><table align=center w…

    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 106, Column 4462: an attribute value must be a literal unless it contains only name characters
    …text-align:justify">جهت<b><font color=#CC0000 style="font-size:11px">مشاهده</f…

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

  • Error Line 106, Column 4528: an attribute value must be a literal unless it contains only name characters
    …x">مشاهده</font></b> و <b><font color=#CC0000 style="font-size:11px">پرداخت ال…

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

  • Warning Line 106, Column 4767: NET-enabling start-tag requires SHORTTAG YES
    …height="30"><FORM name=KN action=http://www.nigc.ir/customer/invoice/rep01.asp…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 106, Column 4901: NET-enabling start-tag requires SHORTTAG YES
    …stomer_tx" name="KeyN" maxlength="15" /></td><td><input type="image" height="1…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 106, Column 4939: there is no attribute "HEIGHT"
    …/></td><td><input type="image" height="17" width="40" name="btn1" src="images/…

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

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

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

  • Error Line 106, Column 4950: there is no attribute "WIDTH"
    …<input type="image" height="17" width="40" name="btn1" src="images/view.gif" a…

    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 106, Column 5003: there is no attribute "VALIGN"
    …" src="images/view.gif" alt="" valign="button" /></td></tr></table></FORM></td…

    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 106, Column 5012: NET-enabling start-tag requires SHORTTAG YES
    …ages/view.gif" alt="" valign="button" /></td></tr></table></FORM></td></tr><tr…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 106, Column 5038: end tag for element "FORM" which is not open
    …gn="button" /></td></tr></table></FORM></td></tr><tr><td align=center height="…

    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 106, Column 5147: an attribute value must be a literal unless it contains only name characters
    ….ir/gas" target="_blank" ><font color=#CC0000 style="font-size:12px">نحوه محاس…

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

  • Error Line 109, Column 16: there is no attribute "STYLE"
    <marquee style="height:160px" SCROLLAMOUNT="2" SCROLLDELAY="70" onmousemove="th…

    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 44: there is no attribute "SCROLLAMOUNT"
    …uee style="height:160px" SCROLLAMOUNT="2" SCROLLDELAY="70" onmousemove="this.s…

    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 60: there is no attribute "SCROLLDELAY"
    …t:160px" SCROLLAMOUNT="2" SCROLLDELAY="70" onmousemove="this.stop();" onmouseo…

    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 77: there is no attribute "ONMOUSEMOVE"
    …OUNT="2" SCROLLDELAY="70" onmousemove="this.stop();" onmouseout="this.start();…

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

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

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

  • Error Line 109, Column 103: there is no attribute "ONMOUSEOUT"
    …LDELAY="70" onmousemove="this.stop();" onmouseout="this.start();" direction=up>

    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 129: there is no attribute "DIRECTION"
    …LDELAY="70" onmousemove="this.stop();" onmouseout="this.start();" direction=up>

    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 131: element "MARQUEE" undefined
    …LDELAY="70" onmousemove="this.stop();" onmouseout="this.start();" direction=up>

    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 112, Column 101: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=111068')" style="cursor:hand"><li><p al…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 112, Column 135: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …kIdn=111068')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 112, Column 232: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=111068'>انتصاب مدير عامل و نايب رئيس هي…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 116, Column 101: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=111067')" style="cursor:hand"><li><p al…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 116, Column 135: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …kIdn=111067')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 116, Column 232: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=111067'>انتصاب مدير عامل و نايب رئيس هي…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 120, Column 101: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110951')" style="cursor:hand"><li><p al…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 120, Column 135: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …kIdn=110951')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 120, Column 232: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110951'>انتصاب معاون مدير عامل شرکت ملي…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 124, Column 101: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110885')" style="cursor:hand"><li><p al…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 124, Column 135: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …kIdn=110885')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 124, Column 232: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110885'>جشنواره عکس تجلي حضور "راهپيماي…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 128, Column 101: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110884')" style="cursor:hand"><li><p al…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 128, Column 135: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …kIdn=110884')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 128, Column 232: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110884'>دوره هاي ويژه آموزشي امنيت اطلا…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 132, Column 101: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110831')" style="cursor:hand"><li><p al…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 132, Column 135: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …kIdn=110831')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 132, Column 232: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110831'>جدول برنامه هاي تلويزيوني (14 ا…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 136, Column 108: reference to entity "LnkIdn" for which no system identifier could be generated
    …c.ir/Site.aspx?ParTree=111N1813&LnkIdn=110782')" style="cursor:hand"><li><p al…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 136, Column 142: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …kIdn=110782')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 136, Column 246: reference to entity "LnkIdn" for which no system identifier could be generated
    …c.ir/Site.aspx?ParTree=111N1813&LnkIdn=110782'>آغاز فرآيند ثبت نام ششمين دوره …

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 140, Column 101: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110787')" style="cursor:hand"><li><p al…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 140, Column 135: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …kIdn=110787')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 140, Column 232: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110787'>«شماره صد و چهل و دوم» گزيده تح…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 144, Column 101: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110783')" style="cursor:hand"><li><p al…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 144, Column 135: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …kIdn=110783')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 144, Column 232: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110783'>انتصاب مدير توسعه منابع انساني …

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 148, Column 101: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110592')" style="cursor:hand"><li><p al…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 148, Column 135: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …kIdn=110592')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 148, Column 232: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110592'>شماره 96 ماهنامه نداي گاز منتشر…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 152, Column 101: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110570')" style="cursor:hand"><li><p al…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 152, Column 135: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …kIdn=110570')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 152, Column 232: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110570'>شماره 93 نشريه خبري مديريت پژوه…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 156, Column 101: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110437')" style="cursor:hand"><li><p al…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 156, Column 135: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …kIdn=110437')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 156, Column 232: reference to entity "LnkIdn" for which no system identifier could be generated
    …igc.ir/Site.aspx?ParTree=11181A&LnkIdn=110437'>«شماره صد و چهلم» گزيده تحولات …

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 160, Column 103: reference to entity "LnkIdn" for which no system identifier could be generated
    …c.ir/Site.aspx?ParTree=11181F14&LnkIdn=109876')" style="cursor:hand"><li><p al…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 160, Column 137: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …kIdn=109876')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 160, Column 236: reference to entity "LnkIdn" for which no system identifier could be generated
    …c.ir/Site.aspx?ParTree=11181F14&LnkIdn=109876'>انتصاب سرپرست مديریت توسعه مناب…

    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 15, Column 104: entity was defined here
    …//www.nigc.ir/Site.aspx?ParTree=111816&LnkIdn=110972' class=ItemPath>آگهي استخ…
  • Error Line 172, Column 131: element "MARQUEE" undefined
    …LDELAY="70" onmousemove="this.stop();" onmouseout="this.start();" direction=up>

    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 175, Column 121: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …Tree=111B11')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 179, Column 121: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …Tree=111B12')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 183, Column 121: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …Tree=111B13')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 187, Column 121: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …Tree=111B15')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

    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 191, Column 121: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …Tree=111B14')" style="cursor:hand"><li><p align=justify><A class="sidebarLink"…

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

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

  • Warning Line 200, Column 131: NET-enabling start-tag requires SHORTTAG YES
    …lspacing=0 width="201" background=skin/sa34c0/cat_b.gif id="oShohadaTable" sty…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 200, Column 132: character data is not allowed here
    …spacing=0 width="201" background=skin/sa34c0/cat_b.gif id="oShohadaTable" styl…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 200, Column 138: end tag for "TABLE" which is not finished
    …g=0 width="201" background=skin/sa34c0/cat_b.gif id="oShohadaTable" style="dis…

    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 200, Column 138: end tag for "TABLE" which is not finished
    …g=0 width="201" background=skin/sa34c0/cat_b.gif id="oShohadaTable" style="dis…

    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 200, Column 192: document type does not allow element "TR" here
    …ShohadaTable" style="display:none"><tr><td class=sideTop></td></tr><tr><td id=…

    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 200, Column 224: document type does not allow element "TR" here
    …e"><tr><td class=sideTop></td></tr><tr><td id="oShohada" class="sidebarBody" a…

    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 200, Column 467: required attribute "TYPE" not specified
    …g></a>--><script language="javascript">var myDate1 = new Date;var myDate2 = ne…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 200, Column 948: end tag for element "A" which is not open
    …='"+str1+"' border='0' width='150'></a>");</script></td></tr><tr><td class=sid…

    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 200, Column 974: document type does not allow element "TR" here
    …th='150'></a>");</script></td></tr><tr><td class=sideEnd>&nbsp;شعله هاي فروزان…

    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 200, Column 1031: end tag for element "TABLE" which is not open
    …&nbsp;شعله هاي فروزان</td></tr></table><script>if(oShohada.innerHTML.length>10…

    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 200, Column 1039: required attribute "TYPE" not specified
    …له هاي فروزان</td></tr></table><script>if(oShohada.innerHTML.length>10) oShoha…

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

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

  • Warning Line 200, Column 1250: NET-enabling start-tag requires SHORTTAG YES
    …lspacing=0 width="201" background=skin/sa34c0/cat_b.gif id="oPolTable" style="…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 200, Column 1251: character data is not allowed here
    …spacing=0 width="201" background=skin/sa34c0/cat_b.gif id="oPolTable" style="d…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 200, Column 1257: end tag for "TABLE" which is not finished
    …g=0 width="201" background=skin/sa34c0/cat_b.gif id="oPolTable" style="display…

    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 200, Column 1257: end tag for "TABLE" which is not finished
    …g=0 width="201" background=skin/sa34c0/cat_b.gif id="oPolTable" style="display…

    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 200, Column 1307: document type does not allow element "TR" here
    …d="oPolTable" style="display:none"><tr><td class=sideTop></td></tr><tr><td id=…

    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 200, Column 1339: document type does not allow element "TR" here
    …e"><tr><td class=sideTop></td></tr><tr><td id="oPol" class=sidebarBody><!--Pol…

    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 200, Column 1395: document type does not allow element "TR" here
    …ss=sidebarBody><!--Pol--></td></tr><tr><td class=sideEnd>&nbsp;<a href="/pol.a…

    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 200, Column 1480: end tag for element "TABLE" which is not open
    …idn=6">نظرسنجي‌ها</a></td></tr></table><table><tr><td height=2></td></tr></tab…

    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 200, Column 1530: required attribute "TYPE" not specified
    …<td height=2></td></tr></table><script>if(oPol.innerHTML.length>10) oPolTable.…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 200, Column 1616: document type does not allow element "TD" here
    …splay="";</script></td><td class="s11"></td></tr><tr><td colspan=7 id=hfixer><…

    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 200, Column 1626: end tag for element "TR" which is not open
    …/script></td><td class="s11"></td></tr><tr><td colspan=7 id=hfixer></td></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 200, Column 1630: document type does not allow element "TR" here
    …ipt></td><td class="s11"></td></tr><tr><td colspan=7 id=hfixer></td></tr></td>…

    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 200, Column 1669: end tag for element "TD" which is not open
    …<td colspan=7 id=hfixer></td></tr></td><td class="s11"></td></tr><tr><td colsp…

    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 200, Column 1685: document type does not allow element "TD" here
    …=hfixer></td></tr></td><td class="s11"></td></tr><tr><td colspan=7 class="s13"…

    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 200, Column 1695: end tag for element "TR" which is not open
    …td></tr></td><td class="s11"></td></tr><tr><td colspan=7 class="s13"><table bo…

    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 200, Column 1699: document type does not allow element "TR" here
    …/tr></td><td class="s11"></td></tr><tr><td colspan=7 class="s13"><table border…

    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 200, Column 1993: end tag for element "TABLE" which is not open
    …يدي</td></tr></table></td></tr></table></div></div></center></body></html><scr…

    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 200, Column 1999: end tag for element "DIV" which is not open
    …d></tr></table></td></tr></table></div></div></center></body></html><script>xm…

    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 200, Column 2005: end tag for element "DIV" which is not open
    …></table></td></tr></table></div></div></center></body></html><script>xmlRende…

    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 200, Column 2036: required attribute "TYPE" not specified
    …v></div></center></body></html><script>xmlRender('special',391,40317,0);</scri…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 200, Column 2036: document type does not allow element "SCRIPT" here
    …v></div></center></body></html><script>xmlRender('special',391,40317,0);</scri…

    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 200, Column 2111: required attribute "TYPE" not specified
    …nder('special',391,40317,0);</script><script src="scripts/PooyaGB.js"></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 200, Column 2111: document type does not allow element "SCRIPT" here
    …nder('special',391,40317,0);</script><script src="scripts/PooyaGB.js"></script>

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

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

Visitor Analysis

Daily Visitor
  • 3.267 visits