ساعت و تقویم رسمی ایران ...

time.ir
  • Domain Name
    time.ir
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #25246
  • Page Size
    129.1 KB
  • Ip Address
    94.232.172.250
  • Heading
    H1: 4, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    6 GIF, 0 JPG, 5 PNG

Website Meta Analysis

  • Title
    ساعت و تقویم رسمی ایران | Time.ir
  • Meta Keyword
    ساعت و تقویم رسمی ایران
  • Meta Description
    ساعت و تقویم رسمی ایران

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    94.232.172.250
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 4.0.30319
  • x-powered-by: ASP.NET
  • x-powered-by-plesk: PleskWin
  • date: Thu, 31 Jan 2013 05:23:22 GMT
  • content-length: 18888
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% This is the IRNIC Whois server v1.6.2.
% Available on web at http://whois.nic.ir/
% Find the terms and conditions of use on http://www.nic.ir/
%
% This server uses UTF-8 as the encoding for requests and responses.

% NOTE: This output has been filtered.

% Information related to 'time.ir'


domain: time.ir
ascii: time.ir
remarks: (Domain Holder) Rahborde Danesh va Karbordhaye Moasser Rayane (Radcom)
remarks: (Domain Holder Address) Unit 7 and 8, No. 48, Eftekhar Alley, Motahari St., Valiasr St.,, Tehran, Tehran, IR
holder-c: ra51-irnic
admin-c: ht76-irnic
tech-c: ht76-irnic
bill-c: ra51-irnic
nserver: ns1.parsihost.com
nserver: ns2.parsihost.com
last-updated: 2012-02-04
expire-date: 2017-03-03
source: IRNIC # Filtered

nic-hdl: ra51-irnic
org: Rahborde Danesh va Karbordhaye Moasser Rayane (Radcom)
e-mail: email
address: Unit 7 and 8, No. 48, Eftekhar Alley, Motahari St., Valiasr St.,, Tehran, Tehran, IR
phone: +98 21 8892 6503
fax-no: +98 21 8892 6986
source: IRNIC # Filtered

nic-hdl: ht76-irnic
person: Hamidreza Taherian
e-mail: email
address: 4th unit, 3rd fl., Eftekhar Ally, Vali asr st. (by the Motahhari st.), Tehran, Iran., Tehran, Tehran, IR
phone: 88926503
source: IRNIC # Filtered

DNS Analysis


DNS servers
ns1.parsihost.com
ns2.parsihost.com [67.212.67.245]


DNS Records

Answer records
time.ir SOA
server: ns1.parsihost.com
email: support@radcom.ir
serial: 1358694186
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
10800s
time.ir NS  ns1.parsihost.com 10800s
time.ir NS  ns2.parsihost.com 10800s
time.ir A 94.232.172.250 10800s
time.ir MX
preference: 10
exchange: mail.time.ir
10800s
time.ir TXT v=spf1 mx -all 10800s

Authority records

Additional records
ns1.parsihost.com A 62.193.12.226 10800s
ns2.parsihost.com A 67.212.67.245 10800s
mail.time.ir A 94.232.172.250 10800s

IP 94.232.172.250 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 104 Errors
  • 10 Warnings
Ratio Text/Html
  • 0.5693288753063632
Message Error
  • Error Line 3, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 33, Column 118: required attribute "alt" not specified
    …g id="ctl00_imgLogo" class="topLogo" src="/image/Transparent.gif" border="0" />

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

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

  • Error Line 44, Column 108: required attribute "alt" not specified
    …       <img id="ctl00_imgLastMessage" src="Image/transparent.gif" border="0" />

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

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

  • Error Line 50, Column 207: required attribute "alt" not specified
    …age&#39;).style.display = &#39;none&#39;;" src="/Image/Close.png" border="0" />

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

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

  • Error Line 67, Column 351: there is no attribute "border"
    …ng&#39;" src="/App_Themes/Default-fa-IR/Images/Search/Button.png" border="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.

  • Error Line 70, Column 169: there is no attribute "OnClick"
    …Search" class="searchTextBox" OnClick="if (this.value==&#39;جستجو ...&#39;) {t…

    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 70, Column 277: there is no attribute "OnBlur"
    …style.color = &#39;black&#39;" OnBlur="if(this.value==&#39;&#39;){this.value =…

    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 208, Column 71: required attribute "alt" not specified
            <img id="hours" src="/Components/Time/Style/Image/Hours.png" /></div>

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

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

  • Error Line 210, Column 75: required attribute "alt" not specified
    …      <img id="minutes" src="/Components/Time/Style/Image/Minutes.png" /></div>

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

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

  • Error Line 212, Column 75: required attribute "alt" not specified
    …      <img id="seconds" src="/Components/Time/Style/Image/Seconds.png" /></div>

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

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

  • Error Line 213, Column 60: required attribute "alt" not specified
        <img src="/Components/Time/Style/Image/ClockFace.png" />

    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 269, Column 15: character "<" is the first character of a delimiter but occurred as data
            m = m < 10 ? "0" + m : m;

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 271, Column 15: character "<" is the first character of a delimiter but occurred as data
            s = s < 10 ? "0" + s : s;

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 273, Column 15: character "<" is the first character of a delimiter but occurred as data
            h = h < 10 ? "0" + h : h;

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 426, Column 160: value of attribute "align" cannot be "Center"; must be one of "left", "center", "right"
    …cing="0" cellpadding="0" align="Center" border="0" width="210" style="directio…

    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 430, Column 392: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …calendar_dates" width="100%"><a class=calendar_day_J href="javascript:showDate…
  • Error Line 430, Column 531: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …1606;</a><a id="pickerYearLink" class=calendar_day_J href="javascript:showDate…
  • Error Line 430, Column 623: end tag for "br" omitted, but OMITTAG NO was specified
    …">&#1777;&#1779;&#1785;&#1777;</a><br><span class=calendar_day_M>January - Feb…

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

  • Info Line 430, Column 619: start tag was here
    …ar')">&#1777;&#1779;&#1785;&#1777;</a><br><span class=calendar_day_M>January -…
  • Error Line 430, Column 635: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …779;&#1785;&#1777;</a><br><span class=calendar_day_M>January - February 2013</…
  • Error Line 430, Column 684: end tag for "br" omitted, but OMITTAG NO was specified
    …y_M>January - February 2013</span><br><span class=calendar_day_Q>&#1585;&#1576…

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

  • Info Line 430, Column 680: start tag was here
    …r_day_M>January - February 2013</span><br><span class=calendar_day_Q>&#1585;&#…
  • Error Line 430, Column 696: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …- February 2013</span><br><span class=calendar_day_Q>&#1585;&#1576;&#1610;&#15…
  • Error Line 435, Column 174: value of attribute "align" cannot be "Center"; must be one of "left", "center", "right"
    …dle_1380_tMonthName" cellspacing="0" cellpadding="0" align="Center" border="0">

    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 437, Column 144: value of attribute "id" invalid: "1" cannot start a name
    …="#EDEDED" width="10"><a href='#' id='1' onclick='javascript:selectedMonth(thi…

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

  • Error Line 437, Column 404: value of attribute "id" invalid: "2" cannot start a name
    …="#EDEDED" width="10"><a href='#' id='2' onclick='javascript:selectedMonth(thi…

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

  • Error Line 437, Column 671: value of attribute "id" invalid: "3" cannot start a name
    …="#EDEDED" width="10"><a href='#' id='3' onclick='javascript:selectedMonth(thi…

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

  • Error Line 439, Column 144: value of attribute "id" invalid: "4" cannot start a name
    …="#EDEDED" width="10"><a href='#' id='4' onclick='javascript:selectedMonth(thi…

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

  • Error Line 439, Column 376: value of attribute "id" invalid: "5" cannot start a name
    …="#EDEDED" width="10"><a href='#' id='5' onclick='javascript:selectedMonth(thi…

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

  • Error Line 439, Column 622: value of attribute "id" invalid: "6" cannot start a name
    …="#EDEDED" width="10"><a href='#' id='6' onclick='javascript:selectedMonth(thi…

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

  • Error Line 441, Column 144: value of attribute "id" invalid: "7" cannot start a name
    …="#EDEDED" width="10"><a href='#' id='7' onclick='javascript:selectedMonth(thi…

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

  • Error Line 441, Column 376: value of attribute "id" invalid: "8" cannot start a name
    …="#EDEDED" width="10"><a href='#' id='8' onclick='javascript:selectedMonth(thi…

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

  • Error Line 441, Column 615: value of attribute "id" invalid: "9" cannot start a name
    …="#EDEDED" width="10"><a href='#' id='9' onclick='javascript:selectedMonth(thi…

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

  • Error Line 443, Column 145: value of attribute "id" invalid: "1" cannot start a name
    …="#EDEDED" width="10"><a href='#' id='10' onclick='javascript:selectedMonth(th…

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

  • Error Line 443, Column 372: value of attribute "id" invalid: "1" cannot start a name
    …="#EDEDED" width="10"><a href='#' id='11' onclick='javascript:selectedMonth(th…

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

  • Error Line 443, Column 613: value of attribute "id" invalid: "1" cannot start a name
    …="#EDEDED" width="10"><a href='#' id='12' onclick='javascript:selectedMonth(th…

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

  • Error Line 451, Column 537: there is no attribute "OnClientClicked"
    …ss="datePickerButton" OnClientClicked="if (typeof(Page_ClientValidate) == &#39…

    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 460, Column 29: reference not terminated by REFC delimiter
    							<td width="23">&#1588</td><td width="23">&#1740</td><td width="23">&#158…

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

  • Warning Line 460, Column 55: reference not terminated by REFC delimiter
    …="23">&#1588</td><td width="23">&#1740</td><td width="23">&#1583</td><td width…

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

  • Warning Line 460, Column 81: reference not terminated by REFC delimiter
    …="23">&#1740</td><td width="23">&#1583</td><td width="23">&#1587</td><td width…

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

  • Warning Line 460, Column 107: reference not terminated by REFC delimiter
    …="23">&#1583</td><td width="23">&#1587</td><td width="23">&#1670</td><td width…

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

  • Warning Line 460, Column 133: reference not terminated by REFC delimiter
    …="23">&#1587</td><td width="23">&#1670</td><td width="23">&#1662</td><td width…

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

  • Warning Line 460, Column 159: reference not terminated by REFC delimiter
    …><td width="23">&#1670</td><td width="23">&#1662</td><td width="23">&#1580</td>

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

  • Warning Line 460, Column 185: reference not terminated by REFC delimiter
    …><td width="23">&#1670</td><td width="23">&#1662</td><td width="23">&#1580</td>

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

  • Error Line 462, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 462, Column 258: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 462, Column 470: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 462, Column 629: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 462, Column 841: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 462, Column 1000: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 462, Column 1219: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 462, Column 1378: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 462, Column 1597: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 462, Column 1756: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 462, Column 1975: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 462, Column 2138: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_holiday_M_small'>…

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

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

  • Error Line 464, Column 79: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 464, Column 238: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 464, Column 457: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 464, Column 616: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 464, Column 835: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 464, Column 994: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 464, Column 1213: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 464, Column 1384: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_holiday_M_small'>…

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

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

  • Error Line 464, Column 1611: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 464, Column 1778: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 464, Column 1997: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarToday><tr><td valign='bottom' al…
  • Error Line 464, Column 2166: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 464, Column 2385: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 464, Column 2556: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_holiday_M_small'>…

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

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

  • Error Line 466, Column 79: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 466, Column 246: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 466, Column 465: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 466, Column 632: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 466, Column 851: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 466, Column 1018: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 466, Column 1237: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 466, Column 1404: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 466, Column 1623: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 466, Column 1790: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 466, Column 2009: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 466, Column 2176: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 466, Column 2395: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 466, Column 2566: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_holiday_M_small'>…

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

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

  • Error Line 468, Column 79: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 468, Column 246: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 468, Column 465: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 468, Column 636: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_holiday_M_small'>…

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

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

  • Error Line 468, Column 863: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 468, Column 1030: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 468, Column 1249: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 468, Column 1416: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 468, Column 1628: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 468, Column 1795: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 468, Column 2007: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 468, Column 2174: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 468, Column 2386: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 468, Column 2557: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_holiday_M_small'>…

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

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

  • Error Line 470, Column 79: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 470, Column 246: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 470, Column 458: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 470, Column 625: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 470, Column 837: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cellpadding='0' cellspacing='0' class=calendarDay><tr><td valign='bottom' alig…
  • Error Line 470, Column 1004: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …></td></tr><tr><td valign='top' nowrap><span class='calendar_day_M_small'>&nbs…

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

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

  • Error Line 484, Column 19: ID "ctl00_ctl00_cphMiddle_SAMPARL_Web_View_EventUI_EventCalendarCustomized10cphMiddle_1380_tCalendarHeaderPanel" already defined
    			</div><div id="ctl00_ctl00_cphMiddle_SAMPARL_Web_View_EventUI_EventCalendarC…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 425, Column 30: ID "ctl00_ctl00_cphMiddle_SAMPARL_Web_View_EventUI_EventCalendarCustomized10cphMiddle_1380_tCalendarHeaderPanel" first defined here
                        <div id="ctl00_ctl00_cphMiddle_SAMPARL_Web_View_EventUI_Eve…
  • Error Line 486, Column 19: ID "ctl00_ctl00_cphMiddle_SAMPARL_Web_View_EventUI_EventCalendarCustomized10cphMiddle_1380_tCalendarFooterPanel" already defined
    			</div><div id="ctl00_ctl00_cphMiddle_SAMPARL_Web_View_EventUI_EventCalendarC…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 476, Column 26: ID "ctl00_ctl00_cphMiddle_SAMPARL_Web_View_EventUI_EventCalendarCustomized10cphMiddle_1380_tCalendarFooterPanel" first defined here
                    <div id="ctl00_ctl00_cphMiddle_SAMPARL_Web_View_EventUI_EventCa…
  • Error Line 488, Column 19: ID "ctl00_ctl00_cphMiddle_SAMPARL_Web_View_EventUI_EventCalendarCustomized10cphMiddle_1380_tCalendarPanel" already defined
    			</div><div id="ctl00_ctl00_cphMiddle_SAMPARL_Web_View_EventUI_EventCalendarC…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 457, Column 26: ID "ctl00_ctl00_cphMiddle_SAMPARL_Web_View_EventUI_EventCalendarCustomized10cphMiddle_1380_tCalendarPanel" first defined here
                    <div id="ctl00_ctl00_cphMiddle_SAMPARL_Web_View_EventUI_EventCa…
  • Error Line 507, Column 62: required attribute "alt" not specified
    		<td><img src="/image/transparent.gif" width="1" height="10"></td>

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

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

  • Error Line 507, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    		<td><img src="/image/transparent.gif" width="1" height="10"></td>

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

  • Info Line 507, Column 7: start tag was here
    		<td><img src="/image/transparent.gif" width="1" height="10"></td>
  • Error Line 775, Column 149: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"><span class='content'><table class='content' cellspacing="5" cellpadding="5">

    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 1001, Column 151: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ntent'><table class='content' cellspacing="10" cellpadding="10" align="center">

    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 1005, Column 72: end tag for "br" omitted, but OMITTAG NO was specified
    …ter">لحظه تحویل سال ۱۳۹۲هجری شمسی <br>ساعت 14:31:56 <br><span lang="FA">روز چه…

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

  • Info Line 1005, Column 68: start tag was here
    …"center">لحظه تحویل سال ۱۳۹۲هجری شمسی <br>ساعت 14:31:56 <br><span lang="FA">رو…
  • Error Line 1005, Column 90: end tag for "br" omitted, but OMITTAG NO was specified
    …ل ۱۳۹۲هجری شمسی <br>ساعت 14:31:56 <br><span lang="FA">روز چهارشنبه 30 اسفند 13…

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

  • Info Line 1005, Column 86: start tag was here
    …ل سال ۱۳۹۲هجری شمسی <br>ساعت 14:31:56 <br><span lang="FA">روز چهارشنبه 30 اسفن…
  • Error Line 1006, Column 159: end tag for "img" omitted, but OMITTAG NO was specified
    …t/media/image/2013/01/5_thum.jpeg"></a>&nbsp;&nbsp;</td></tr></tbody></table><…

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

  • Info Line 1006, Column 83: start tag was here
    …/articles/47236.aspx" target="_blank"><img border="0" alt="مار" src="/Content/…
  • Error Line 1025, Column 8: end tag for "table" which is not finished
    </table>

    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 1048, Column 96: required attribute "alt" not specified
    …                   <img src="/image/Transparent.gif" class="Logo" border="0" />

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

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

Visitor Analysis

Daily Visitor
  • 9.333 visits
Daily Visitor