دانلود کليپ موبايل, بازي موبايل, برنامه موبايل, کتاب موبايل, تم موبايل, زنگ موبايل , ترفند موبايل , نرم افزار ...

ariamobile.net
  • Domain Name
    ariamobile.net
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #28849
  • Page Size
    81.5 KB
  • Ip Address
    199.167.138.18
  • Heading
    H1: 1, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    79 GIF, 9 JPG, 3 PNG

Website Meta Analysis

  • Title
    Ariamobile.Net | آریا موبایل
  • Meta Keyword
    موبايل, گوشي موبايل, نوکيا,سوني اريکسون , بازي موبايل, برنامه موبايل, تم موبايل, زنگ موبايل, والپيپر موبايل, جاوا
  • Meta Description
    دانلود کليپ موبايل, بازي موبايل, برنامه موبايل, کتاب موبايل, تم موبايل, زنگ موبايل , ترفند موبايل , نرم افزار

Technical Analysis

  • Webserver
    LiteSpeed
  • Ip Address
    199.167.138.18
  • Domain Age
    5 Years, 0 Months, 9 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from ariamobile.net.

HTML Analysis

  • content-encoding: gzip
  • vary: Accept-Encoding
  • date: Sat, 03 Aug 2013 12:04:15 GMT
  • server: LiteSpeed
  • connection: close
  • x-powered-by: PHP/5.2.17
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: ARIAMOBILE.NET

Registrant:
hosein
afshar ( email )
Tehran
tehran
Tehran,9821
IR
Tel. +98.8754125

Creation Date: 21-Jul-2008
Expiration Date: 21-Jul-2013

Domain servers in listed order:
ns19.hostdl.com
ns20.hostdl.com


Administrative Contact:
hosein
afshar ( email )
Tehran
tehran
Tehran,9821
IR
Tel. +98.8754125

Technical Contact:
hosein
afshar ( email )
Tehran
tehran
Tehran,9821
IR
Tel. +98.8754125

Billing Contact:
hosein
afshar ( email )
Tehran
tehran
Tehran,9821
IR
Tel. +98.8754125

Status:ACTIVE

DNS Analysis


DNS servers
ns31.hostdl.com [199.167.138.23]
ns32.hostdl.com [199.167.138.19]


DNS Records

Answer records
ariamobile.net TXT v=spf1 +a +mx +ip4:199.167.138.18 ?all 14400s
ariamobile.net MX
preference: 0
exchange: ariamobile.net
14400s
ariamobile.net SOA
server: ns31.hostdl.com
email: hostdl@gmail.com
serial: 2013011800
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
ariamobile.net NS  ns32.hostdl.com 86400s
ariamobile.net NS  ns31.hostdl.com 86400s
ariamobile.net A 199.167.138.18 14400s

Authority records

Additional records
ariamobile.net A 199.167.138.18 14400s
ns31.hostdl.com A 199.167.138.23 14400s
ns32.hostdl.com A 199.167.138.19 14400s

IP 199.167.138.18 Analysis

  • Country Code
    CA
  • Country Code3
    CAN
  • Country Name
    Canada
  • City
    NA
  • Continent Code
    60° North
  • Latitude
    95.
  • Longitude
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 199.167.138.18"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=199.167.138.18?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 199.167.136.0 - 199.167.139.255
    CIDR: 199.167.136.0/22
    OriginAS:
    NetName: YESUP-COM
    NetHandle: NET-199-167-136-0-1
    Parent: NET-199-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2011-06-06
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-199-167-136-0-1

    OrgName: Yesup Ecommerce Solutions Inc.
    OrgId: YESUP
    Address: 565 Gordon Baker Road
    City: North York
    StateProv: ON
    PostalCode: M2H-2W2
    Country: CA
    RegDate: 2009-10-29
    Updated: 2011-09-24
    Ref: http://whois.arin.net/rest/org/YESUP

    OrgAbuseHandle: PCCK-ARIN
    OrgAbuseName: Kok, Peter C C
    OrgAbusePhone: +1-416-499-8009
    OrgAbuseEmail: peterk@yesup.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/PCCK-ARIN

    OrgTechHandle: PCCK-ARIN
    OrgTechName: Kok, Peter C C
    OrgTechPhone: +1-416-499-8009
    OrgTechEmail: peterk@yesup.com
    OrgTechRef: http://whois.arin.net/rest/poc/PCCK-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 306 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.6757449458656701
Message Error
  • Error Line 5, Column 68: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

    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 5, Column 1: start tag was here
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  • Error Line 7, Column 91: end tag for "link" omitted, but OMITTAG NO was specified
    …"http://www.ariamobile.net/images/style.css?" type="text/css" rel="stylesheet">

    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 7, Column 1: start tag was here
    <link href="http://www.ariamobile.net/images/style.css?" type="text/css" rel="s…
  • Error Line 8, Column 105: end tag for "link" omitted, but OMITTAG NO was specified
    …"application/rsd+xml" title="RSD" href="http://www.ariamobile.net.com/rsd.xml">

    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 8, Column 1: start tag was here
    <link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://www.ari…
  • Error Line 19, Column 42: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="author" content="ariamobile">

    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 19, Column 1: start tag was here
    <meta name="author" content="ariamobile">
  • Error Line 28, Column 6: end tag for "br" omitted, but OMITTAG NO was specified
     <br>

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

  • Info Line 28, Column 2: start tag was here
     <br>
  • Error Line 93, Column 141: required attribute "alt" not specified
    … padding-bottom:5px;padding-top:4px " src="http://ariamobile.net/ads/Ads-.gif">

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

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

  • Error Line 93, Column 142: end tag for "img" omitted, but OMITTAG NO was specified
    … padding-bottom:5px;padding-top:4px " src="http://ariamobile.net/ads/Ads-.gif">

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

  • Info Line 93, Column 1: start tag was here
    <img style="border-style: dashed; border-width:0;color:CCE8FE; padding-bottom:5…
  • Error Line 103, Column 9: end tag for element "center" which is not open
    </center>

    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 115, Column 221: end tag for element "a" which is not open
    …s/">نرم افزار مطالعه کتاب های الکترونیکی با Good Reader - آی او اس</a></li></a>

    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 117, Column 276: end tag for element "a" which is not open
    … فایل های فشرده در موبایل AndroZip Pro File Manager v4.6 - آندروید</a></li></a>

    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 119, Column 223: end tag for element "a" which is not open
    …apk/">بازی اکشن استراتژی Guns'n'Glory WW2 Premium v1.4.2 - آندروید</a></li></a>

    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 121, Column 250: end tag for element "a" which is not open
    …شین سواری توربو اسکیدی Turbo Skiddy Racing Pro v1.0 - بازی آندروید</a></li></a>

    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 123, Column 224: end tag for element "a" which is not open
    …">بازی کامیون داران جاده های برفی Ice Road Truckers v1.0 - آندروید</a></li></a>

    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 125, Column 207: end tag for element "a" which is not open
    …-3d-apk/">بازی ماشین ها و اسلحه ها Cars And Guns 3D v1.5 - آندروید</a></li></a>

    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 127, Column 207: end tag for element "a" which is not open
    …ator-hd-ios/">نرم افزار مترجم متن The Translator HD 1.0 - آی او اس</a></li></a>

    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 129, Column 235: end tag for element "a" which is not open
    …/">نرم افزار ساعت هشدار دهنده Bedside Alarm Clock v1.3.4 - آندروید</a></li></a>

    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 131, Column 245: end tag for element "a" which is not open
    …افزار نمایش مالتی مدیا ezPDF Reader Multimedia PDF 2.0.5 - آندروید</a></li></a>

    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 133, Column 216: end tag for element "a" which is not open
    …apk/">بازی مسابقات ماشین کنترلی Mini Motor Racing v1.7.1 - آندروید</a></li></a>

    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 135, Column 174: end tag for element "a" which is not open
    …e-game/trex-hunt-apk/">بازی شکارچی تی رکس TRex Hunt v1.2 - آندروید</a></li></a>

    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 137, Column 182: end tag for element "a" which is not open
    …l-of-mini-brawlers-apk/">بازی Call of Mini Brawlers v1.1 - آندروید</a></li></a>

    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 139, Column 171: end tag for element "a" which is not open
    …ile-game/silibili-apk/">بازی سیلی و بیلی SiliBili v1.0.9 - آندروید</a></li></a>

    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 141, Column 244: end tag for element "a" which is not open
    …le/">نرم افزار استودیو میکس Mixx Machine Studio - سیمبیان^3 آنا بل</a></li></a>

    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 143, Column 258: end tag for element "a" which is not open
    … عکس در موبایل TouchUp Pro-Photo Editor v2.8.5 - نرم افزار آندروید</a></li></a>

    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.

  • Warning Line 159, Column 54: character "&" is the first character of a delimiter but occurred as data
    …a title="بازی استراتژیک جنگی  Command & Conquer 4 Tiberian Twilight" href="htt…

    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 159, Column 205: character "&" is the first character of a delimiter but occurred as data
    …berian-tw/">بازی استراتژیک جنگی  Command & Conquer 4 Tiberian Twilight</a></li>

    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 222, Column 8: required attribute "type" not specified
    <script>function GoTo (c) {if (c != '#')window.location = c;}</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 225, Column 7: element "FORM" undefined
    <FORM >

    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 227, Column 15: there is no attribute "style"
    <SELECT style=" 

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

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

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

  • Error Line 232, Column 62: there is no attribute "NAME"
    …tbgi.gif) repeat scroll 0% 50%;" NAME="clicklist"  onChange="top.location.href…

    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 232, Column 84: there is no attribute "onChange"
    …l 0% 50%;" NAME="clicklist"  onChange="top.location.href=this.form.clicklist.o…

    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 232, Column 172: element "SELECT" undefined
    …ion.href=this.form.clicklist.options[this.form.clicklist.selectedIndex].value">

    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 233, Column 18: "selected" is not a member of a group specified for any attribute
    <OPTION selected style="background:White url(txtbgi.gif) repeat scroll 0% 50%;"…
  • Error Line 233, Column 24: there is no attribute "style"
    <OPTION selected style="background:White url(txtbgi.gif) repeat scroll 0% 50%;"…

    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 233, Column 81: element "OPTION" undefined
    …e="background:White url(txtbgi.gif) repeat scroll 0% 50%;" >انتخاب ماه</option>

    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 233, Column 100: end tag for element "option" which is not open
    …e="background:White url(txtbgi.gif) repeat scroll 0% 50%;" >انتخاب ماه</option>

    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 236, Column 15: there is no attribute "class"
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2013/02/">February 2013</o…

    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 236, Column 27: there is no attribute "VALUE"
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2013/02/">February 2013</o…

    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 236, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2013/02/">February 2013</option>

    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 236, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2013/02/">February 2013</option>

    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 240, Column 63: element "OPTION" undefined
    …ON class="txt" VALUE="http://www.ariamobile.net/2013/01/">January 2013</option>

    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 240, Column 84: end tag for element "option" which is not open
    …ON class="txt" VALUE="http://www.ariamobile.net/2013/01/">January 2013</option>

    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 244, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2012/12/">December 2012</option>

    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 244, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2012/12/">December 2012</option>

    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 248, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2012/11/">November 2012</option>

    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 248, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2012/11/">November 2012</option>

    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 252, Column 63: element "OPTION" undefined
    …ON class="txt" VALUE="http://www.ariamobile.net/2012/10/">October 2012</option>

    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 252, Column 84: end tag for element "option" which is not open
    …ON class="txt" VALUE="http://www.ariamobile.net/2012/10/">October 2012</option>

    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 256, Column 63: element "OPTION" undefined
    … class="txt" VALUE="http://www.ariamobile.net/2012/09/">September 2012</option>

    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 256, Column 86: end tag for element "option" which is not open
    … class="txt" VALUE="http://www.ariamobile.net/2012/09/">September 2012</option>

    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 260, Column 63: element "OPTION" undefined
    …ION class="txt" VALUE="http://www.ariamobile.net/2012/08/">August 2012</option>

    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 260, Column 83: end tag for element "option" which is not open
    …ION class="txt" VALUE="http://www.ariamobile.net/2012/08/">August 2012</option>

    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 264, Column 63: element "OPTION" undefined
    …PTION class="txt" VALUE="http://www.ariamobile.net/2012/07/">July 2012</option>

    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 264, Column 81: end tag for element "option" which is not open
    …PTION class="txt" VALUE="http://www.ariamobile.net/2012/07/">July 2012</option>

    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 268, Column 63: element "OPTION" undefined
    …PTION class="txt" VALUE="http://www.ariamobile.net/2012/06/">June 2012</option>

    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 268, Column 81: end tag for element "option" which is not open
    …PTION class="txt" VALUE="http://www.ariamobile.net/2012/06/">June 2012</option>

    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 272, Column 63: element "OPTION" undefined
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/05/">May 2012</option>

    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 272, Column 80: end tag for element "option" which is not open
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/05/">May 2012</option>

    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 276, Column 63: element "OPTION" undefined
    …TION class="txt" VALUE="http://www.ariamobile.net/2012/04/">April 2012</option>

    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 276, Column 82: end tag for element "option" which is not open
    …TION class="txt" VALUE="http://www.ariamobile.net/2012/04/">April 2012</option>

    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 280, Column 63: element "OPTION" undefined
    …TION class="txt" VALUE="http://www.ariamobile.net/2012/03/">March 2012</option>

    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 280, Column 82: end tag for element "option" which is not open
    …TION class="txt" VALUE="http://www.ariamobile.net/2012/03/">March 2012</option>

    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 284, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2012/02/">February 2012</option>

    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 284, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2012/02/">February 2012</option>

    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 288, Column 63: element "OPTION" undefined
    …ON class="txt" VALUE="http://www.ariamobile.net/2012/01/">January 2012</option>

    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 288, Column 84: end tag for element "option" which is not open
    …ON class="txt" VALUE="http://www.ariamobile.net/2012/01/">January 2012</option>

    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 292, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2011/12/">December 2011</option>

    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 292, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2011/12/">December 2011</option>

    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 296, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2011/11/">November 2011</option>

    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 296, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2011/11/">November 2011</option>

    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 300, Column 63: element "OPTION" undefined
    …ON class="txt" VALUE="http://www.ariamobile.net/2011/10/">October 2011</option>

    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 300, Column 84: end tag for element "option" which is not open
    …ON class="txt" VALUE="http://www.ariamobile.net/2011/10/">October 2011</option>

    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 304, Column 63: element "OPTION" undefined
    … class="txt" VALUE="http://www.ariamobile.net/2011/09/">September 2011</option>

    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 304, Column 86: end tag for element "option" which is not open
    … class="txt" VALUE="http://www.ariamobile.net/2011/09/">September 2011</option>

    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 308, Column 63: element "OPTION" undefined
    …ION class="txt" VALUE="http://www.ariamobile.net/2011/08/">August 2011</option>

    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 308, Column 83: end tag for element "option" which is not open
    …ION class="txt" VALUE="http://www.ariamobile.net/2011/08/">August 2011</option>

    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 312, Column 63: element "OPTION" undefined
    …PTION class="txt" VALUE="http://www.ariamobile.net/2011/07/">July 2011</option>

    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 312, Column 81: end tag for element "option" which is not open
    …PTION class="txt" VALUE="http://www.ariamobile.net/2011/07/">July 2011</option>

    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 316, Column 63: element "OPTION" undefined
    …PTION class="txt" VALUE="http://www.ariamobile.net/2011/06/">June 2011</option>

    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 316, Column 81: end tag for element "option" which is not open
    …PTION class="txt" VALUE="http://www.ariamobile.net/2011/06/">June 2011</option>

    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 320, Column 63: element "OPTION" undefined
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/05/">May 2011</option>

    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 320, Column 80: end tag for element "option" which is not open
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/05/">May 2011</option>

    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 324, Column 63: element "OPTION" undefined
    …TION class="txt" VALUE="http://www.ariamobile.net/2011/04/">April 2011</option>

    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 324, Column 82: end tag for element "option" which is not open
    …TION class="txt" VALUE="http://www.ariamobile.net/2011/04/">April 2011</option>

    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 328, Column 63: element "OPTION" undefined
    …TION class="txt" VALUE="http://www.ariamobile.net/2011/03/">March 2011</option>

    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 328, Column 82: end tag for element "option" which is not open
    …TION class="txt" VALUE="http://www.ariamobile.net/2011/03/">March 2011</option>

    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 332, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2011/02/">February 2011</option>

    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 332, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2011/02/">February 2011</option>

    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 336, Column 63: element "OPTION" undefined
    …ON class="txt" VALUE="http://www.ariamobile.net/2011/01/">January 2011</option>

    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 336, Column 84: end tag for element "option" which is not open
    …ON class="txt" VALUE="http://www.ariamobile.net/2011/01/">January 2011</option>

    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 340, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2010/12/">December 2010</option>

    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 340, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2010/12/">December 2010</option>

    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 344, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2010/11/">November 2010</option>

    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 344, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2010/11/">November 2010</option>

    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 348, Column 63: element "OPTION" undefined
    …ON class="txt" VALUE="http://www.ariamobile.net/2010/10/">October 2010</option>

    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 348, Column 84: end tag for element "option" which is not open
    …ON class="txt" VALUE="http://www.ariamobile.net/2010/10/">October 2010</option>

    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 352, Column 63: element "OPTION" undefined
    … class="txt" VALUE="http://www.ariamobile.net/2010/09/">September 2010</option>

    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 352, Column 86: end tag for element "option" which is not open
    … class="txt" VALUE="http://www.ariamobile.net/2010/09/">September 2010</option>

    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 356, Column 63: element "OPTION" undefined
    …ION class="txt" VALUE="http://www.ariamobile.net/2010/08/">August 2010</option>

    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 356, Column 83: end tag for element "option" which is not open
    …ION class="txt" VALUE="http://www.ariamobile.net/2010/08/">August 2010</option>

    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 360, Column 63: element "OPTION" undefined
    …PTION class="txt" VALUE="http://www.ariamobile.net/2010/07/">July 2010</option>

    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 360, Column 81: end tag for element "option" which is not open
    …PTION class="txt" VALUE="http://www.ariamobile.net/2010/07/">July 2010</option>

    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 364, Column 63: element "OPTION" undefined
    …PTION class="txt" VALUE="http://www.ariamobile.net/2010/06/">June 2010</option>

    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 364, Column 81: end tag for element "option" which is not open
    …PTION class="txt" VALUE="http://www.ariamobile.net/2010/06/">June 2010</option>

    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 368, Column 63: element "OPTION" undefined
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/05/">May 2010</option>

    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 368, Column 80: end tag for element "option" which is not open
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/05/">May 2010</option>

    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 372, Column 63: element "OPTION" undefined
    …TION class="txt" VALUE="http://www.ariamobile.net/2010/04/">April 2010</option>

    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 372, Column 82: end tag for element "option" which is not open
    …TION class="txt" VALUE="http://www.ariamobile.net/2010/04/">April 2010</option>

    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 376, Column 63: element "OPTION" undefined
    …TION class="txt" VALUE="http://www.ariamobile.net/2010/03/">March 2010</option>

    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 376, Column 82: end tag for element "option" which is not open
    …TION class="txt" VALUE="http://www.ariamobile.net/2010/03/">March 2010</option>

    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 380, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2010/02/">February 2010</option>

    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 380, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2010/02/">February 2010</option>

    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 384, Column 63: element "OPTION" undefined
    …ON class="txt" VALUE="http://www.ariamobile.net/2010/01/">January 2010</option>

    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 384, Column 84: end tag for element "option" which is not open
    …ON class="txt" VALUE="http://www.ariamobile.net/2010/01/">January 2010</option>

    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 388, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2009/12/">December 2009</option>

    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 388, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2009/12/">December 2009</option>

    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 392, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2009/11/">November 2009</option>

    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 392, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2009/11/">November 2009</option>

    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 396, Column 63: element "OPTION" undefined
    …ON class="txt" VALUE="http://www.ariamobile.net/2009/10/">October 2009</option>

    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 396, Column 84: end tag for element "option" which is not open
    …ON class="txt" VALUE="http://www.ariamobile.net/2009/10/">October 2009</option>

    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 400, Column 63: element "OPTION" undefined
    … class="txt" VALUE="http://www.ariamobile.net/2009/09/">September 2009</option>

    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 400, Column 86: end tag for element "option" which is not open
    … class="txt" VALUE="http://www.ariamobile.net/2009/09/">September 2009</option>

    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 404, Column 63: element "OPTION" undefined
    …ION class="txt" VALUE="http://www.ariamobile.net/2009/08/">August 2009</option>

    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 404, Column 83: end tag for element "option" which is not open
    …ION class="txt" VALUE="http://www.ariamobile.net/2009/08/">August 2009</option>

    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 408, Column 63: element "OPTION" undefined
    …PTION class="txt" VALUE="http://www.ariamobile.net/2009/07/">July 2009</option>

    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 408, Column 81: end tag for element "option" which is not open
    …PTION class="txt" VALUE="http://www.ariamobile.net/2009/07/">July 2009</option>

    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 412, Column 63: element "OPTION" undefined
    …PTION class="txt" VALUE="http://www.ariamobile.net/2009/06/">June 2009</option>

    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 412, Column 81: end tag for element "option" which is not open
    …PTION class="txt" VALUE="http://www.ariamobile.net/2009/06/">June 2009</option>

    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 416, Column 63: element "OPTION" undefined
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/05/">May 2009</option>

    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 416, Column 80: end tag for element "option" which is not open
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/05/">May 2009</option>

    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 420, Column 63: element "OPTION" undefined
    …TION class="txt" VALUE="http://www.ariamobile.net/2009/04/">April 2009</option>

    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 420, Column 82: end tag for element "option" which is not open
    …TION class="txt" VALUE="http://www.ariamobile.net/2009/04/">April 2009</option>

    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 424, Column 63: element "OPTION" undefined
    …TION class="txt" VALUE="http://www.ariamobile.net/2009/03/">March 2009</option>

    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 424, Column 82: end tag for element "option" which is not open
    …TION class="txt" VALUE="http://www.ariamobile.net/2009/03/">March 2009</option>

    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 428, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2009/02/">February 2009</option>

    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 428, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2009/02/">February 2009</option>

    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 432, Column 63: element "OPTION" undefined
    …ON class="txt" VALUE="http://www.ariamobile.net/2009/01/">January 2009</option>

    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 432, Column 84: end tag for element "option" which is not open
    …ON class="txt" VALUE="http://www.ariamobile.net/2009/01/">January 2009</option>

    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 436, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2008/12/">December 2008</option>

    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 436, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2008/12/">December 2008</option>

    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 440, Column 63: element "OPTION" undefined
    …N class="txt" VALUE="http://www.ariamobile.net/2008/11/">November 2008</option>

    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 440, Column 85: end tag for element "option" which is not open
    …N class="txt" VALUE="http://www.ariamobile.net/2008/11/">November 2008</option>

    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 444, Column 63: element "OPTION" undefined
    …ON class="txt" VALUE="http://www.ariamobile.net/2008/10/">October 2008</option>

    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 444, Column 84: end tag for element "option" which is not open
    …ON class="txt" VALUE="http://www.ariamobile.net/2008/10/">October 2008</option>

    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 448, Column 63: element "OPTION" undefined
    … class="txt" VALUE="http://www.ariamobile.net/2008/09/">September 2008</option>

    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 448, Column 86: end tag for element "option" which is not open
    … class="txt" VALUE="http://www.ariamobile.net/2008/09/">September 2008</option>

    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 452, Column 63: element "OPTION" undefined
    …ION class="txt" VALUE="http://www.ariamobile.net/2008/08/">August 2008</option>

    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 452, Column 83: end tag for element "option" which is not open
    …ION class="txt" VALUE="http://www.ariamobile.net/2008/08/">August 2008</option>

    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 456, Column 63: element "OPTION" undefined
    …PTION class="txt" VALUE="http://www.ariamobile.net/2008/07/">July 2008</option>

    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 456, Column 81: end tag for element "option" which is not open
    …PTION class="txt" VALUE="http://www.ariamobile.net/2008/07/">July 2008</option>

    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 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 456, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2008/07/">July 2008</optio…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 452, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2008/08/">August 2008</opt…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 448, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2008/09/">September 2008</…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 444, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2008/10/">October 2008</op…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 440, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2008/11/">November 2008</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 436, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2008/12/">December 2008</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 432, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/01/">January 2009</op…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 428, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/02/">February 2009</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 424, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/03/">March 2009</opti…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 420, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/04/">April 2009</opti…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 416, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/05/">May 2009</option>
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 412, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/06/">June 2009</optio…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 408, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/07/">July 2009</optio…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 404, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/08/">August 2009</opt…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 400, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/09/">September 2009</…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 396, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/10/">October 2009</op…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 392, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/11/">November 2009</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 388, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2009/12/">December 2009</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 384, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/01/">January 2010</op…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 380, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/02/">February 2010</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 376, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/03/">March 2010</opti…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 372, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/04/">April 2010</opti…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 368, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/05/">May 2010</option>
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 364, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/06/">June 2010</optio…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 360, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/07/">July 2010</optio…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 356, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/08/">August 2010</opt…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 352, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/09/">September 2010</…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 348, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/10/">October 2010</op…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 344, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/11/">November 2010</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 340, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2010/12/">December 2010</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 336, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/01/">January 2011</op…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 332, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/02/">February 2011</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 328, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/03/">March 2011</opti…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 324, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/04/">April 2011</opti…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 320, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/05/">May 2011</option>
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 316, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/06/">June 2011</optio…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 312, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/07/">July 2011</optio…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 308, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/08/">August 2011</opt…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 304, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/09/">September 2011</…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 300, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/10/">October 2011</op…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 296, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/11/">November 2011</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 292, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2011/12/">December 2011</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 288, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/01/">January 2012</op…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 284, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/02/">February 2012</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 280, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/03/">March 2012</opti…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 276, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/04/">April 2012</opti…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 272, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/05/">May 2012</option>
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 268, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/06/">June 2012</optio…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 264, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/07/">July 2012</optio…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 260, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/08/">August 2012</opt…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 256, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/09/">September 2012</…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 252, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/10/">October 2012</op…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 248, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/11/">November 2012</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 244, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2012/12/">December 2012</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 240, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2013/01/">January 2013</op…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 236, Column 1: start tag was here
    <OPTION class="txt" VALUE="http://www.ariamobile.net/2013/02/">February 2013</o…
  • Error Line 460, Column 9: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </SELECT><P>

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

  • Info Line 233, Column 1: start tag was here
    <OPTION selected style="background:White url(txtbgi.gif) repeat scroll 0% 50%;"…
  • Error Line 460, Column 12: element "P" undefined
    </SELECT><P>

    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 461, Column 7: end tag for "P" omitted, but OMITTAG NO was specified
    </FORM>

    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 460, Column 10: start tag was here
    </SELECT><P>
  • Error Line 462, Column 9: end tag for element "CENTER" which is not open
    </CENTER>

    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 463, Column 12: end tag for "center" omitted, but OMITTAG NO was specified
          </div>    

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

  • Info Line 224, Column 1: start tag was here
    <center>
  • Error Line 480, Column 185: required attribute "alt" not specified
    …ttp://www.ariamobile.net/ads/chargeha/chargeha.gif"  width="120" height="240" >

    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 480, Column 186: end tag for "img" omitted, but OMITTAG NO was specified
    …ttp://www.ariamobile.net/ads/chargeha/chargeha.gif"  width="120" height="240" >

    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 480, Column 1: start tag was here
    <img style="border-style: dashed; border-width:0;color:CCE8FE; padding-bottom:5…
  • Error Line 630, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="cat-list-item">

    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 1023, Column 7: required attribute "type" not specified
    <style>

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

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

  • Error Line 1023, Column 7: document type does not allow element "style" here
    <style>

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

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

  • Error Line 1046, Column 13: there is no attribute "href"
    <li><A href="http://www.thailand12.com" target=_blank>

    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 1046, Column 48: there is no attribute "target"
    <li><A href="http://www.thailand12.com" target=_blank>

    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 1046, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <li><A href="http://www.thailand12.com" target=_blank>
  • Error Line 1046, Column 54: element "A" undefined
    <li><A href="http://www.thailand12.com" target=_blank>

    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 1047, Column 114: required attribute "alt" not specified
    …border-width:0;color:CCE8FE;" src="http://www.ariamobile.net/ads/bamaaa/1.gif">

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

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

  • Error Line 1047, Column 115: end tag for "img" omitted, but OMITTAG NO was specified
    …border-width:0;color:CCE8FE;" src="http://www.ariamobile.net/ads/bamaaa/1.gif">

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

  • Info Line 1047, Column 1: start tag was here
    <img  style="border-style: dashed; border-width:0;color:CCE8FE;" src="http://ww…
  • Error Line 1048, Column 4: end tag for element "a" which is not open
    </a></li>

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

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

  • Error Line 1048, Column 9: end tag for "A" omitted, but OMITTAG NO was specified
    </a></li>

    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 1046, Column 5: start tag was here
    <li><A href="http://www.thailand12.com" target=_blank>
  • Error Line 1049, Column 44: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <li><A href="http://www.bamaaa.com" target=_blank>
  • Error Line 1049, Column 50: element "A" undefined
    <li><A href="http://www.bamaaa.com" target=_blank>

    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 1050, Column 115: required attribute "alt" not specified
    …order-width:0;color:CCE8FE;" src="http://www.ariamobile.net/ads/bamaaa/2.gif" >

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

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

  • Error Line 1050, Column 116: end tag for "img" omitted, but OMITTAG NO was specified
    …order-width:0;color:CCE8FE;" src="http://www.ariamobile.net/ads/bamaaa/2.gif" >

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

  • Info Line 1050, Column 1: start tag was here
    <img  style="border-style: dashed; border-width:0;color:CCE8FE;" src="http://ww…
  • Error Line 1051, Column 4: end tag for element "a" which is not open
    </a></li>

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

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

  • Error Line 1051, Column 9: end tag for "A" omitted, but OMITTAG NO was specified
    </a></li>

    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 1049, Column 5: start tag was here
    <li><A href="http://www.bamaaa.com" target=_blank>
  • Warning Line 1112, Column 75: unclosed start-tag requires SHORTTAG YES
    …ink/4560.php" target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobi…

    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 1112, Column 89: end tag for element "MTIfNotEmpty" which is not open
    …target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobile.net/MT4/mt-…

    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 1112, Column 170: required attribute "alt" not specified
    …tic/themes/cityscape-paris/rll.gif"  />راهنمای تنظیم گوشی های آندروید برای اتص…

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

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

  • Error Line 1114, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    </a><br>

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

  • Info Line 1114, Column 5: start tag was here
    </a><br>
  • Warning Line 1117, Column 75: unclosed start-tag requires SHORTTAG YES
    …ink/4558.php" target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobi…

    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 1117, Column 89: end tag for element "MTIfNotEmpty" which is not open
    …target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobile.net/MT4/mt-…

    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 1117, Column 170: required attribute "alt" not specified
    …tic/themes/cityscape-paris/rll.gif"  />تیم کوک می‌گوید نمایشگر بزرگ‌تر برای گو…

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

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

  • Error Line 1119, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    </a><br>

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

  • Info Line 1119, Column 5: start tag was here
    </a><br>
  • Warning Line 1122, Column 75: unclosed start-tag requires SHORTTAG YES
    …ink/4557.php" target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobi…

    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 1122, Column 89: end tag for element "MTIfNotEmpty" which is not open
    …target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobile.net/MT4/mt-…

    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 1122, Column 170: required attribute "alt" not specified
    …tic/themes/cityscape-paris/rll.gif"  />سامسونگ از تبلت 10.1 اینچ گلکسی تب 3 و …

    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 1124, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    </a><br>

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

  • Info Line 1124, Column 5: start tag was here
    </a><br>
  • Warning Line 1127, Column 75: unclosed start-tag requires SHORTTAG YES
    …ink/4532.php" target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobi…

    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 1127, Column 89: end tag for element "MTIfNotEmpty" which is not open
    …target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobile.net/MT4/mt-…

    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 1127, Column 170: required attribute "alt" not specified
    …/mt-static/themes/cityscape-paris/rll.gif"  />راهکارهایی امنیتی برای گوشی‌بازها

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

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

  • Error Line 1129, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    </a><br>

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

  • Info Line 1129, Column 5: start tag was here
    </a><br>
  • Warning Line 1132, Column 75: unclosed start-tag requires SHORTTAG YES
    …ink/4514.php" target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobi…

    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 1132, Column 89: end tag for element "MTIfNotEmpty" which is not open
    …target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobile.net/MT4/mt-…

    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 1132, Column 170: required attribute "alt" not specified
    …tic/themes/cityscape-paris/rll.gif"  />چگونگی اتصال یک صفحه کلید USB به تلفن ا…

    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 1134, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    </a><br>

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

  • Info Line 1134, Column 5: start tag was here
    </a><br>
  • Warning Line 1137, Column 75: unclosed start-tag requires SHORTTAG YES
    …ink/4505.php" target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobi…

    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 1137, Column 89: end tag for element "MTIfNotEmpty" which is not open
    …target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobile.net/MT4/mt-…

    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 1137, Column 170: required attribute "alt" not specified
    …tic/themes/cityscape-paris/rll.gif"  />فروش آنلاین شارژ ایرانسل , همراه اول و …

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

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

  • Error Line 1139, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    </a><br>

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

  • Info Line 1139, Column 5: start tag was here
    </a><br>
  • Warning Line 1142, Column 75: unclosed start-tag requires SHORTTAG YES
    …ink/4503.php" target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobi…

    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 1142, Column 89: end tag for element "MTIfNotEmpty" which is not open
    …target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobile.net/MT4/mt-…

    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 1142, Column 170: required attribute "alt" not specified
    …atic/themes/cityscape-paris/rll.gif"  />آموزش تعویض لوگوی اوپراتور بدون جیلبریک

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

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

  • Error Line 1144, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    </a><br>

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

  • Info Line 1144, Column 5: start tag was here
    </a><br>
  • Warning Line 1147, Column 75: unclosed start-tag requires SHORTTAG YES
    …ink/4502.php" target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobi…

    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 1147, Column 89: end tag for element "MTIfNotEmpty" which is not open
    …target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobile.net/MT4/mt-…

    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 1147, Column 170: required attribute "alt" not specified
    …tic/themes/cityscape-paris/rll.gif"  />نخستین تصویر رسمی از تلفن اکسپریا Z سون…

    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 1149, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    </a><br>

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

  • Info Line 1149, Column 5: start tag was here
    </a><br>
  • Warning Line 1152, Column 75: unclosed start-tag requires SHORTTAG YES
    …ink/4476.php" target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobi…

    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 1152, Column 89: end tag for element "MTIfNotEmpty" which is not open
    …target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobile.net/MT4/mt-…

    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 1152, Column 170: required attribute "alt" not specified
    …tic/themes/cityscape-paris/rll.gif"  />سایت پیشوازها  - مرکز آهنگ پیشواز در ای…

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

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

  • Error Line 1154, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    </a><br>

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

  • Info Line 1154, Column 5: start tag was here
    </a><br>
  • Warning Line 1157, Column 75: unclosed start-tag requires SHORTTAG YES
    …ink/4464.php" target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobi…

    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 1157, Column 89: end tag for element "MTIfNotEmpty" which is not open
    …target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobile.net/MT4/mt-…

    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 1157, Column 170: required attribute "alt" not specified
    …-static/themes/cityscape-paris/rll.gif"  />خرید آنلاین شارژ ایرانسل و همراه اول

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

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

  • Error Line 1159, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    </a><br>

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

  • Info Line 1159, Column 5: start tag was here
    </a><br>
  • Warning Line 1162, Column 75: unclosed start-tag requires SHORTTAG YES
    …ink/4452.php" target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobi…

    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 1162, Column 89: end tag for element "MTIfNotEmpty" which is not open
    …target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobile.net/MT4/mt-…

    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 1162, Column 170: required attribute "alt" not specified
    …tic/themes/cityscape-paris/rll.gif"  />تماشای فیلم های یوتیوب در آیفون بصورت س…

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

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

  • Error Line 1164, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    </a><br>

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

  • Info Line 1164, Column 5: start tag was here
    </a><br>
  • Warning Line 1167, Column 75: unclosed start-tag requires SHORTTAG YES
    …ink/4449.php" target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobi…

    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 1167, Column 89: end tag for element "MTIfNotEmpty" which is not open
    …target="_blank" title=""</MTIfNotEmpty><img src="http://ariamobile.net/MT4/mt-…

    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 1167, Column 170: required attribute "alt" not specified
    …atic/themes/cityscape-paris/rll.gif"  />معرفی ۵ ویژگی جالب اما پنهان گلکسی اس ۳

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

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

  • Error Line 1169, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    </a><br>

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

  • Info Line 1169, Column 5: start tag was here
    </a><br>
  • Error Line 1177, Column 13: end tag for element "mt:Entries" which is not open
    </mt:Entries>

    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 1212, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 1212, Column 1: start tag was here
    <br>
  • Error Line 1214, Column 178: required attribute "alt" not specified
    … src="http://ariamobile.net/ads/sitosharj/sharj.gif"  width="468" height="60" >

    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 1214, Column 179: end tag for "img" omitted, but OMITTAG NO was specified
    … src="http://ariamobile.net/ads/sitosharj/sharj.gif"  width="468" height="60" >

    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 1214, Column 1: start tag was here
    <img style="border-style: dashed; border-width:0;color:CCE8FE; padding-bottom:5…
  • Error Line 1242, Column 387: required attribute "alt" not specified
    …riamobile.net/ads/rayankala/Poster0131.jpg" width="455" height="280" /></a></p>

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

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

  • Error Line 1247, Column 9: end tag for element "center" which is not open
    </center>

    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 1326, Column 76: required attribute "alt" not specified
    <img class="aligncenter" src="http://www.ariamobile.net/ads/b15/B15-1.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>.

  • Error Line 1326, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    <img class="aligncenter" src="http://www.ariamobile.net/ads/b15/B15-1.png" >

    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 1326, Column 1: start tag was here
    <img class="aligncenter" src="http://www.ariamobile.net/ads/b15/B15-1.png" >
  • Error Line 1328, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    </p><br>

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

  • Info Line 1328, Column 5: start tag was here
    </p><br>
  • Error Line 1330, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><center><a target="_blank" href="http://www.b15.ir/" rel="nofollow"><img  s…

    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 1330, Column 1: start tag was here
    <br><center><a target="_blank" href="http://www.b15.ir/" rel="nofollow"><img  s…
  • Error Line 1330, Column 129: required attribute "alt" not specified
    …"><img  src="http://www.ariamobile.net/ads/b15/B15-2.jpg" ></a><p></p></center>

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

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

  • Error Line 1330, Column 133: end tag for "img" omitted, but OMITTAG NO was specified
    …"><img  src="http://www.ariamobile.net/ads/b15/B15-2.jpg" ></a><p></p></center>

    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 1330, Column 73: start tag was here
    …f="http://www.b15.ir/" rel="nofollow"><img  src="http://www.ariamobile.net/ads…
  • Warning Line 1392, Column 23: character "<" is the first character of a delimiter but occurred as data
        for (var i = 0; i < ca.length; i++) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1423, Column 26: character "&" is the first character of a delimiter but occurred as data
        if (screen.width > 0 && screen.height > 0) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1423, Column 27: character "&" is the first character of a delimiter but occurred as data
        if (screen.width > 0 && screen.height > 0) {

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1479, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><div style="text-align: right;">شما در نقش مارین شارپشوتر، یکی از تک تیراندا…

    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 1480, Column 18: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p align="center"><a href="http://www.ariamobile.net/" target="_blank"><img src…

    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 1480, Column 176: required attribute "alt" not specified
    … border="0" height="205" width="410" /></a></p><p align="center"><b>iOS 4.0 or…

    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 1480, Column 202: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"205" width="410" /></a></p><p align="center"><b>iOS 4.0 or later</b><br /></p>

    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 1514, Column 10: ID "post" already defined
    <div id="post">

    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 1465, Column 10: ID "post" first defined here
    <div id="post">
  • Error Line 1515, Column 10: ID "posttitle" already defined
    <div id="posttitle">

    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 1466, Column 10: ID "posttitle" first defined here
    <div id="posttitle">
  • Error Line 1527, Column 10: ID "posttextbox" already defined
    <div id="posttextbox">

    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 1478, Column 10: ID "posttextbox" first defined here
    <div id="posttextbox">
  • Error Line 1539, Column 18: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p 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 1540, Column 127: required attribute "alt" not specified
    …;color:CCE8FE" src="http://dl.ariamobile.net/2013/02/Great_Big_War_Game.jpg" />

    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 1558, Column 10: ID "post-buttom-block" already defined
    <div id="post-buttom-block">

    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 1493, Column 10: ID "post-buttom-block" first defined here
    <div id="post-buttom-block">
  • Error Line 1579, Column 10: ID "post" already defined
    <div id="post">

    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 1465, Column 10: ID "post" first defined here
    <div id="post">
  • Error Line 1580, Column 10: ID "posttitle" already defined
    <div id="posttitle">

    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 1466, Column 10: ID "posttitle" first defined here
    <div id="posttitle">
  • Error Line 1592, Column 10: ID "posttextbox" already defined
    <div id="posttextbox">

    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 1478, Column 10: ID "posttextbox" first defined here
    <div id="posttextbox">
  • Error Line 1611, Column 18: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p 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 1612, Column 121: required attribute "alt" not specified
    …idth:0;color:CCE8FE" src="http://dl.ariamobile.net/2013/01/ExZeus_2-apk.jpg" />

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

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

  • Error Line 1630, Column 10: ID "post-buttom-block" already defined
    <div id="post-buttom-block">

    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 1493, Column 10: ID "post-buttom-block" first defined here
    <div id="post-buttom-block">
  • Error Line 1651, Column 10: ID "post" already defined
    <div id="post">

    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 1465, Column 10: ID "post" first defined here
    <div id="post">
  • Error Line 1652, Column 10: ID "posttitle" already defined
    <div id="posttitle">

    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 1466, Column 10: ID "posttitle" first defined here
    <div id="posttitle">
  • Error Line 1664, Column 10: ID "posttextbox" already defined
    <div id="posttextbox">

    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 1478, Column 10: ID "posttextbox" first defined here
    <div id="posttextbox">
  • Error Line 1669, Column 18: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p 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 1670, Column 126: required attribute "alt" not specified
    …0;color:CCE8FE" src="http://dl.ariamobile.net/2013/01/Zaxxon_Escape-apk.jpg" />

    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 1688, Column 10: ID "post-buttom-block" already defined
    <div id="post-buttom-block">

    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 1493, Column 10: ID "post-buttom-block" first defined here
    <div id="post-buttom-block">
  • Error Line 1709, Column 10: ID "post" already defined
    <div id="post">

    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 1465, Column 10: ID "post" first defined here
    <div id="post">
  • Error Line 1710, Column 10: ID "posttitle" already defined
    <div id="posttitle">

    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 1466, Column 10: ID "posttitle" first defined here
    <div id="posttitle">
  • Error Line 1722, Column 10: ID "posttextbox" already defined
    <div id="posttextbox">

    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 1478, Column 10: ID "posttextbox" first defined here
    <div id="posttextbox">
  • Error Line 1742, Column 18: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p 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 1743, Column 139: required attribute "alt" not specified
    …E" src="http://dl.ariamobile.net/2013/01/Monte_Gallery-Image_Viewer-apk.jpg" />

    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 1761, Column 10: ID "post-buttom-block" already defined
    <div id="post-buttom-block">

    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 1493, Column 10: ID "post-buttom-block" first defined here
    <div id="post-buttom-block">
  • Error Line 1782, Column 10: ID "post" already defined
    <div id="post">

    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 1465, Column 10: ID "post" first defined here
    <div id="post">
  • Error Line 1783, Column 10: ID "posttitle" already defined
    <div id="posttitle">

    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 1466, Column 10: ID "posttitle" first defined here
    <div id="posttitle">
  • Error Line 1795, Column 10: ID "posttextbox" already defined
    <div id="posttextbox">

    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 1478, Column 10: ID "posttextbox" first defined here
    <div id="posttextbox">
  • Error Line 1807, Column 18: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p 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 1808, Column 136: required attribute "alt" not specified
    …E8FE" src="http://dl.ariamobile.net/2013/01/PicSay_Pro-Photo_Editor-apk.jpg" />

    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 1826, Column 10: ID "post-buttom-block" already defined
    <div id="post-buttom-block">

    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 1493, Column 10: ID "post-buttom-block" first defined here
    <div id="post-buttom-block">
  • Error Line 1847, Column 10: ID "post" already defined
    <div id="post">

    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 1465, Column 10: ID "post" first defined here
    <div id="post">
  • Error Line 1848, Column 10: ID "posttitle" already defined
    <div id="posttitle">

    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 1466, Column 10: ID "posttitle" first defined here
    <div id="posttitle">
  • Error Line 1860, Column 10: ID "posttextbox" already defined
    <div id="posttextbox">

    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 1478, Column 10: ID "posttextbox" first defined here
    <div id="posttextbox">
  • Error Line 1875, Column 18: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p 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 1876, Column 127: required attribute "alt" not specified
    …;color:CCE8FE" src="http://dl.ariamobile.net/2013/01/Drag_Racing_3D-apk.jpg" />

    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 1894, Column 10: ID "post-buttom-block" already defined
    <div id="post-buttom-block">

    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 1493, Column 10: ID "post-buttom-block" first defined here
    <div id="post-buttom-block">
  • Error Line 1915, Column 10: ID "post" already defined
    <div id="post">

    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 1465, Column 10: ID "post" first defined here
    <div id="post">
  • Error Line 1916, Column 10: ID "posttitle" already defined
    <div id="posttitle">

    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 1466, Column 10: ID "posttitle" first defined here
    <div id="posttitle">
  • Error Line 1928, Column 10: ID "posttextbox" already defined
    <div id="posttextbox">

    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 1478, Column 10: ID "posttextbox" first defined here
    <div id="posttextbox">
  • Error Line 1953, Column 18: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p 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 1954, Column 132: required attribute "alt" not specified
    …r:CCE8FE" src="http://dl.ariamobile.net/2013/01/Mobile_Alarm_System-apk.jpg" />

    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 1972, Column 10: ID "post-buttom-block" already defined
    <div id="post-buttom-block">

    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 1493, Column 10: ID "post-buttom-block" first defined here
    <div id="post-buttom-block">
  • Error Line 1993, Column 10: ID "post" already defined
    <div id="post">

    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 1465, Column 10: ID "post" first defined here
    <div id="post">
  • Error Line 1994, Column 10: ID "posttitle" already defined
    <div id="posttitle">

    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 1466, Column 10: ID "posttitle" first defined here
    <div id="posttitle">
  • Error Line 2006, Column 10: ID "posttextbox" already defined
    <div id="posttextbox">

    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 1478, Column 10: ID "posttextbox" first defined here
    <div id="posttextbox">
  • Error Line 2013, Column 18: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p 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 2014, Column 127: required attribute "alt" not specified
    …;color:CCE8FE" src="http://dl.ariamobile.net/2013/01/Rescue_Roby_HD-apk.jpg" />

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

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

  • Error Line 2032, Column 10: ID "post-buttom-block" already defined
    <div id="post-buttom-block">

    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 1493, Column 10: ID "post-buttom-block" first defined here
    <div id="post-buttom-block">
  • Error Line 2053, Column 10: ID "post" already defined
    <div id="post">

    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 1465, Column 10: ID "post" first defined here
    <div id="post">
  • Error Line 2054, Column 10: ID "posttitle" already defined
    <div id="posttitle">

    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 1466, Column 10: ID "posttitle" first defined here
    <div id="posttitle">
  • Error Line 2066, Column 10: ID "posttextbox" already defined
    <div id="posttextbox">

    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 1478, Column 10: ID "posttextbox" first defined here
    <div id="posttextbox">
  • Error Line 2089, Column 18: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p 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 2090, Column 131: required attribute "alt" not specified
    …or:CCE8FE" src="http://dl.ariamobile.net/2013/01/NFL-Quarterback 13-apk.jpg" />

    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 2108, Column 10: ID "post-buttom-block" already defined
    <div id="post-buttom-block">

    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 1493, Column 10: ID "post-buttom-block" first defined here
    <div id="post-buttom-block">
  • Error Line 2181, Column 132: required attribute "type" not specified
    …r.ir/c.aspx?Code=903500&amp;t=counter"></script><noscript><a href="http://www.…

    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 2196, Column 71: end tag for element "b" which is not open
    	<a href="http://www.movabletype.com/">Movable Type Pro 4.21-en</a></b><br />

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

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

Visitor Analysis

Daily Visitor
  • 3.500 visits