Default About Us Advertise Careers Contact Us Sign Up Login الرئيسة النشرات برامج رياضة أنت المراسل Beirut 11.09.2013 GMT + 3 أهم الاخبار صور - تشييع مي جنبلاط في المختارةووريت والدة رئيس جبهة ...

aljadeed.tv
  • Domain Name
    aljadeed.tv
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #20898
  • Page Size
    205.5 KB
  • Ip Address
    141.101.112.107
  • Heading
    H1: 5, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 41 JPG, 24 PNG

Website Meta Analysis

  • Title
    Al Jadeed Official Website | الرئيسية
  • Meta Keyword
  • Meta Description
    Default About Us Advertise Careers Contact Us Sign Up Login الرئيسة النشرات برامج رياضة أنت المراسل Beirut 11.09.2013 GMT + 3 أهم الاخبار صور - تشييع مي جنبلاط في المختارةووريت والدة رئيس جبهة النضال الوطني النائب وليد جنبلاط السيدة مي إرسلان ...

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    141.101.112.107
  • Domain Age
    5 Years, 7 Months, 12 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from aljadeed.tv.

HTML Analysis

  • server: cloudflare-nginx
  • date: Wed, 11 Sep 2013 12:07:59 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • cache-control: public, max-age=56
  • expires: Wed, 11 Sep 2013 12:09:05 GMT
  • last-modified: Wed, 11 Sep 2013 12:06:05 GMT
  • vary: Accept-Encoding
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • cf-ray: ac43da1bfa9059d
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
New TV
Musaitbeh
Beirut, Beirut 20727508
LB

Domain name: ALJADEED.TV


Administrative Contact:
Jaber, Peter email
Musaitbeh
Beirut, Beirut 20727508
LB
+961.1577511
Technical Contact:
Admin, DNS email
Nassar Center
5th Floor
Charles El-Helou Avenue, Rmeil
Beirut, 20727508
LB
+961 1 577511 Fax: +961 1 577533



Registration Service Provider:
TerraNet s.a.l., email
+961 1 577511
This company may be contacted for domain login/passwords,
DNS/Nameserver changes, and general domain support questions.


Registrar of Record: TUCOWS, INC.
Record last updated on 05-Jun-2012.
Record expires on 29-Jan-2013.
Record created on 29-Jan-2008.

Registrar Domain Name Help Center:
http://tucowsdomains.com

Domain servers in listed order:
DORA.NS.CLOUDFLARE.COM
SETH.NS.CLOUDFLARE.COM


Domain status: ok

The Data in the Tucows Registrar WHOIS database is provided to you by Tucows
for information purposes only, and may be used to assist you in obtaining
information about or related to a domain name's registration record.

Tucows makes this information available "as is," and does not guarantee its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
a) allow, enable, or otherwise support the transmission by e-mail,
telephone, or facsimile of mass, unsolicited, commercial advertising or
solicitations to entities other than the data recipient's own existing
customers; or (b) enable high volume, automated, electronic processes that
send queries or data to the systems of any Registry Operator or
ICANN-Accredited registrar, except as reasonably necessary to register
domain names or modify existing registrations.

The compilation, repackaging, dissemination or other use of this Data is
expressly prohibited without the prior written consent of Tucows.

Tucows reserves the right to terminate your access to the Tucows WHOIS
database in its sole discretion, including without limitation, for excessive
querying of the WHOIS database or for failure to otherwise abide by this
policy.

Tucows reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by these terms.

NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY. LACK OF A DOMAIN
RECORD DOES NOT SIGNIFY DOMAIN AVAILABILITY.


DNS Analysis


DNS servers
seth.ns.cloudflare.com [173.245.59.142]
dora.ns.cloudflare.com [173.245.58.108]


DNS Records

Answer records
aljadeed.tv A 66.135.34.152 300s
aljadeed.tv NS  dora.ns.cloudflare.com 86400s
aljadeed.tv NS  seth.ns.cloudflare.com 86400s
aljadeed.tv TXT google-site-verification=HoB6bYX0FM4npgpBSjcvG70bGO5vSfctcPCEIjttHoM 600s
aljadeed.tv SOA
server: dora.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2013010207
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s
aljadeed.tv MX
preference: 10
exchange: mail.aljadeed.tv
300s

Authority records

Additional records
mail.aljadeed.tv A 212.98.141.230 300s

IP 141.101.112.107 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 167 Errors
  • 236 Warnings
Ratio Text/Html
  • 0.7666327723346226
Message Error
  • Error Line 6, Column 24: there is no attribute "property"
    </title><meta property="og:image" content="http://apps.aljadeed.tv/test/fb.png"…

    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 24, Column 7: document type does not allow element "title" here
    <title>Default</title></head>

    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 189, Column 52: an attribute value must be a literal unless it contains only name characters
    						<img alt='Logo' height='113' width='148' src=/images/logo2.png>

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

  • Error Line 189, Column 70: end tag for "img" omitted, but OMITTAG NO was specified
    						<img alt='Logo' height='113' width='148' src=/images/logo2.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 189, Column 7: start tag was here
    						<img alt='Logo' height='113' width='148' src=/images/logo2.png>
  • Error Line 240, Column 31: required attribute "type" not specified
    	<script language="JavaScript">

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

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

  • Warning Line 302, Column 25: multiple comments in comment declaration
                    <!------------AddBanner1-------------------->
  • Warning Line 302, Column 29: multiple comments in comment declaration
                    <!------------AddBanner1-------------------->
  • Error Line 302, Column 31: invalid comment declaration: found name start character outside comment but inside comment declaration
                    <!------------AddBanner1-------------------->
  • Info Line 302, Column 17: comment declaration started here
                    <!------------AddBanner1-------------------->
  • Error Line 308, Column 60: end tag for "param" omitted, but OMITTAG NO was specified
            <param value="sameDomain" name="allowScriptAccess">

    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 9: start tag was here
            <param value="sameDomain" name="allowScriptAccess">
  • Error Line 309, Column 53: end tag for "param" omitted, but OMITTAG NO was specified
            <param value="false" name="allowFullScreen">

    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 309, Column 9: start tag was here
            <param value="false" name="allowFullScreen">
  • Error Line 310, Column 49: end tag for "param" omitted, but OMITTAG NO was specified
            <param value="transparent" name="WMODE">

    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 310, Column 9: start tag was here
            <param value="transparent" name="WMODE">
  • Error Line 312, Column 54: end tag for "param" omitted, but OMITTAG NO was specified
    	    <param value="/flash/aljadeed.swf" name="movie">

    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 6: start tag was here
    	    <param value="/flash/aljadeed.swf" name="movie">
  • Error Line 313, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
            <param value="High" name="quality">

    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 313, Column 9: start tag was here
            <param value="High" name="quality">
  • Error Line 314, Column 47: end tag for "param" omitted, but OMITTAG NO was specified
            <param value="#000000" name="bgcolor">

    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 314, Column 9: start tag was here
            <param value="#000000" name="bgcolor">
  • Error Line 315, Column 23: there is no attribute "height"
            <embed height="93" width="922" align="middle" pluginspage="http://www.a…

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

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

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

  • Error Line 315, Column 34: there is no attribute "width"
            <embed height="93" width="922" align="middle" pluginspage="http://www.a…

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

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

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

  • Error Line 315, Column 46: there is no attribute "align"
    … <embed height="93" width="922" align="middle" pluginspage="http://www.adobe.c…

    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 315, Column 67: there is no attribute "pluginspage"
    …width="922" align="middle" pluginspage="http://www.adobe.com/go/getflashplayer"

    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 316, Column 18: there is no attribute "type"
                type="application/x-shockwave-flash" allowfullscreen="false" allows…

    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 316, Column 66: there is no attribute "allowfullscreen"
    …ation/x-shockwave-flash" allowfullscreen="false" allowscriptaccess="sameDomain"

    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 316, Column 92: there is no attribute "allowscriptaccess"
    …ation/x-shockwave-flash" allowfullscreen="false" allowscriptaccess="sameDomain"

    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 317, Column 18: there is no attribute "name"
                name="bob2" bgcolor="transparent" quality="High" wmode="transparent…

    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 317, Column 33: there is no attribute "bgcolor"
                name="bob2" bgcolor="transparent" quality="High" wmode="transparent…

    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 317, Column 55: there is no attribute "quality"
    …="bob2" bgcolor="transparent" quality="High" wmode="transparent" src="/flash/a…

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

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

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

  • Error Line 317, Column 68: there is no attribute "wmode"
    …lor="transparent" quality="High" wmode="transparent" src="/flash/aljadeed.swf">

    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 317, Column 86: there is no attribute "src"
    …lor="transparent" quality="High" wmode="transparent" src="/flash/aljadeed.swf">

    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 317, Column 107: element "embed" undefined
    …lor="transparent" quality="High" wmode="transparent" src="/flash/aljadeed.swf">

    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 319, Column 13: end tag for "embed" omitted, but OMITTAG NO was specified
        </object>

    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 315, Column 9: start tag was here
            <embed height="93" width="922" align="middle" pluginspage="http://www.a…
  • Error Line 352, Column 302: required attribute "dir" not specified
    …ة</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 352, Column 615: required attribute "dir" not specified
    ….</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 352, Column 925: required attribute "dir" not specified
    …ن</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 352, Column 1232: required attribute "dir" not specified
    …ن</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 352, Column 1542: required attribute "dir" not specified
    …ر</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 352, Column 1854: required attribute "dir" not specified
    …ي</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 352, Column 2167: required attribute "dir" not specified
    ….</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 352, Column 2480: required attribute "dir" not specified
    …ن</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 352, Column 2783: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 352, Column 3097: required attribute "dir" not specified
    … الدولية لإطلاق سراح عبد الله</a></span><bdo class="videogalhoder"></bdo></div>

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

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

  • Error Line 400, Column 15: end tag for "ul" which is not finished
    										</ul>

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

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

  • Warning Line 411, Column 35: multiple comments in comment declaration
                           		 <!------------AddBanner-------------------->
  • Warning Line 411, Column 39: multiple comments in comment declaration
                           		 <!------------AddBanner-------------------->
  • Error Line 411, Column 41: invalid comment declaration: found name start character outside comment but inside comment declaration
                           		 <!------------AddBanner-------------------->
  • Info Line 411, Column 27: comment declaration started here
                           		 <!------------AddBanner-------------------->
  • Error Line 421, Column 164: required attribute "alt" not specified
    …loads/284914818_Image.jpg" style="height:85px;width:670px;border-width:0px;" />

    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 457, Column 80: there is no attribute "allowfullscreen"
    …showrelative'><iframe allowfullscreen='' frameborder='0' height='335' src='htt…

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

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

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

  • Warning Line 457, Column 176: cannot generate system identifier for general entity "showinfo"
    …m/embed/K6K3UXEljMY?wmode=transparent&showinfo=0' width='512'></iframe></div><…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 457, Column 176: general entity "showinfo" not defined and no default entity
    …m/embed/K6K3UXEljMY?wmode=transparent&showinfo=0' width='512'></iframe></div><…

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

  • Warning Line 457, Column 184: reference not terminated by REFC delimiter
    …K6K3UXEljMY?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

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

  • Warning Line 457, Column 184: reference to external entity in attribute value
    …K6K3UXEljMY?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 457, Column 184: reference to entity "showinfo" for which no system identifier could be generated
    …K6K3UXEljMY?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

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

  • Info Line 457, Column 175: entity was defined here
    …om/embed/K6K3UXEljMY?wmode=transparent&showinfo=0' width='512'></iframe></div>…
  • Warning Line 457, Column 463: cannot generate system identifier for general entity "t"
    …eed.tv/videoplayerarchive.html?id=600&t=عين الحلوة,'sharer','toolbar=0,status=…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 457, Column 463: general entity "t" not defined and no default entity
    …eed.tv/videoplayerarchive.html?id=600&t=عين الحلوة,'sharer','toolbar=0,status=…

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

  • Warning Line 457, Column 464: reference not terminated by REFC delimiter
    …ed.tv/videoplayerarchive.html?id=600&t=عين الحلوة,'sharer','toolbar=0,status=0…

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

  • Error Line 457, Column 464: reference to entity "t" for which no system identifier could be generated
    …ed.tv/videoplayerarchive.html?id=600&t=عين الحلوة,'sharer','toolbar=0,status=0…

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

  • Info Line 457, Column 462: entity was defined here
    …deed.tv/videoplayerarchive.html?id=600&t=عين الحلوة,'sharer','toolbar=0,status…
  • Warning Line 457, Column 1168: reference not terminated by REFC delimiter
    …nvJ_2rywkQA?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

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

  • Warning Line 457, Column 1168: reference to external entity in attribute value
    …nvJ_2rywkQA?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 457, Column 1168: reference to entity "showinfo" for which no system identifier could be generated
    …nvJ_2rywkQA?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

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

  • Info Line 457, Column 175: entity was defined here
    …om/embed/K6K3UXEljMY?wmode=transparent&showinfo=0' width='512'></iframe></div>…
  • Warning Line 457, Column 1448: reference not terminated by REFC delimiter
    …ed.tv/videoplayerarchive.html?id=599&t=مواجهات بالقاهرة,'sharer','toolbar=0,st…

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

  • Error Line 457, Column 1448: reference to entity "t" for which no system identifier could be generated
    …ed.tv/videoplayerarchive.html?id=599&t=مواجهات بالقاهرة,'sharer','toolbar=0,st…

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

  • Info Line 457, Column 462: entity was defined here
    …deed.tv/videoplayerarchive.html?id=600&t=عين الحلوة,'sharer','toolbar=0,status…
  • Warning Line 457, Column 2149: reference not terminated by REFC delimiter
    …7mJDTIgPtLo?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

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

  • Warning Line 457, Column 2149: reference to external entity in attribute value
    …7mJDTIgPtLo?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 457, Column 2149: reference to entity "showinfo" for which no system identifier could be generated
    …7mJDTIgPtLo?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

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

  • Info Line 457, Column 175: entity was defined here
    …om/embed/K6K3UXEljMY?wmode=transparent&showinfo=0' width='512'></iframe></div>…
  • Warning Line 457, Column 2429: reference not terminated by REFC delimiter
    …ed.tv/videoplayerarchive.html?id=598&t=الأسير بفاريّا,'sharer','toolbar=0,stat…

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

  • Error Line 457, Column 2429: reference to entity "t" for which no system identifier could be generated
    …ed.tv/videoplayerarchive.html?id=598&t=الأسير بفاريّا,'sharer','toolbar=0,stat…

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

  • Info Line 457, Column 462: entity was defined here
    …deed.tv/videoplayerarchive.html?id=600&t=عين الحلوة,'sharer','toolbar=0,status…
  • Warning Line 457, Column 3102: reference not terminated by REFC delimiter
    …23aIp93_xzM?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

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

  • Warning Line 457, Column 3102: reference to external entity in attribute value
    …23aIp93_xzM?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 457, Column 3102: reference to entity "showinfo" for which no system identifier could be generated
    …23aIp93_xzM?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

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

  • Info Line 457, Column 175: entity was defined here
    …om/embed/K6K3UXEljMY?wmode=transparent&showinfo=0' width='512'></iframe></div>…
  • Warning Line 457, Column 3382: reference not terminated by REFC delimiter
    …ed.tv/videoplayerarchive.html?id=597&t=نجاة طفلة,'sharer','toolbar=0,status=0,…

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

  • Error Line 457, Column 3382: reference to entity "t" for which no system identifier could be generated
    …ed.tv/videoplayerarchive.html?id=597&t=نجاة طفلة,'sharer','toolbar=0,status=0,…

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

  • Info Line 457, Column 462: entity was defined here
    …deed.tv/videoplayerarchive.html?id=600&t=عين الحلوة,'sharer','toolbar=0,status…
  • Warning Line 457, Column 4084: reference not terminated by REFC delimiter
    …4KlsBBg_G4o?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

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

  • Warning Line 457, Column 4084: reference to external entity in attribute value
    …4KlsBBg_G4o?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 457, Column 4084: reference to entity "showinfo" for which no system identifier could be generated
    …4KlsBBg_G4o?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

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

  • Info Line 457, Column 175: entity was defined here
    …om/embed/K6K3UXEljMY?wmode=transparent&showinfo=0' width='512'></iframe></div>…
  • Warning Line 457, Column 4364: reference not terminated by REFC delimiter
    …ed.tv/videoplayerarchive.html?id=596&t=الأسد بالمسجد,'sharer','toolbar=0,statu…

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

  • Error Line 457, Column 4364: reference to entity "t" for which no system identifier could be generated
    …ed.tv/videoplayerarchive.html?id=596&t=الأسد بالمسجد,'sharer','toolbar=0,statu…

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

  • Info Line 457, Column 462: entity was defined here
    …deed.tv/videoplayerarchive.html?id=600&t=عين الحلوة,'sharer','toolbar=0,status…
  • Warning Line 457, Column 5043: reference not terminated by REFC delimiter
    …9-qyFf5MN7E?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

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

  • Warning Line 457, Column 5043: reference to external entity in attribute value
    …9-qyFf5MN7E?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 457, Column 5043: reference to entity "showinfo" for which no system identifier could be generated
    …9-qyFf5MN7E?wmode=transparent&showinfo=0' width='512'></iframe></div><div clas…

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

  • Info Line 457, Column 175: entity was defined here
    …om/embed/K6K3UXEljMY?wmode=transparent&showinfo=0' width='512'></iframe></div>…
  • Warning Line 457, Column 5323: reference not terminated by REFC delimiter
    …ed.tv/videoplayerarchive.html?id=595&t=الأسير الى فاريا,'sharer','toolbar=0,st…

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

  • Error Line 457, Column 5323: reference to entity "t" for which no system identifier could be generated
    …ed.tv/videoplayerarchive.html?id=595&t=الأسير الى فاريا,'sharer','toolbar=0,st…

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

  • Info Line 457, Column 462: entity was defined here
    …deed.tv/videoplayerarchive.html?id=600&t=عين الحلوة,'sharer','toolbar=0,status…
  • Error Line 464, Column 107: end tag for "img" omitted, but OMITTAG NO was specified
    …img.youtube.com/vi/K6K3UXEljMY/0.jpg'><span>عين الحلوة</span><bdo></bdo></a></…

    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 464, Column 20: start tag was here
    			<li><a href='#'><img alt='' height='103' width='125' src='http://img.youtube…
  • Error Line 464, Column 134: required attribute "dir" not specified
    …jMY/0.jpg'><span>عين الحلوة</span><bdo></bdo></a></li><li><a href='#'><img alt…

    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 464, Column 253: end tag for "img" omitted, but OMITTAG NO was specified
    …img.youtube.com/vi/nvJ_2rywkQA/0.jpg'><span>مواجهات بالقاهر</span><bdo></bdo><…

    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 464, Column 166: start tag was here
    …n><bdo></bdo></a></li><li><a href='#'><img alt='' height='103' width='125' src…
  • Error Line 464, Column 285: required attribute "dir" not specified
    ….jpg'><span>مواجهات بالقاهر</span><bdo></bdo></a></li><li><a href='#'><img alt…

    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 464, Column 404: end tag for "img" omitted, but OMITTAG NO was specified
    …img.youtube.com/vi/7mJDTIgPtLo/0.jpg'><span>الأسير بفاريّا</span><bdo></bdo></…

    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 464, Column 317: start tag was here
    …n><bdo></bdo></a></li><li><a href='#'><img alt='' height='103' width='125' src…
  • Error Line 464, Column 435: required attribute "dir" not specified
    …0.jpg'><span>الأسير بفاريّا</span><bdo></bdo></a></li><li><a href='#'><img alt…

    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 464, Column 554: end tag for "img" omitted, but OMITTAG NO was specified
    …img.youtube.com/vi/23aIp93_xzM/0.jpg'><span>نجاة طفلة</span><bdo></bdo></a></l…

    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 464, Column 467: start tag was here
    …n><bdo></bdo></a></li><li><a href='#'><img alt='' height='103' width='125' src…
  • Error Line 464, Column 580: required attribute "dir" not specified
    …_xzM/0.jpg'><span>نجاة طفلة</span><bdo></bdo></a></li><li><a href='#'><img alt…

    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 464, Column 699: end tag for "img" omitted, but OMITTAG NO was specified
    …img.youtube.com/vi/4KlsBBg_G4o/0.jpg'><span>الأسد بالمسجد</span><bdo></bdo></a…

    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 464, Column 612: start tag was here
    …n><bdo></bdo></a></li><li><a href='#'><img alt='' height='103' width='125' src…
  • Error Line 464, Column 729: required attribute "dir" not specified
    …/0.jpg'><span>الأسد بالمسجد</span><bdo></bdo></a></li><li><a href='#'><img alt…

    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 464, Column 848: end tag for "img" omitted, but OMITTAG NO was specified
    …img.youtube.com/vi/9-qyFf5MN7E/0.jpg'><span>الأسير الى فاري</span><bdo></bdo><…

    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 464, Column 761: start tag was here
    …n><bdo></bdo></a></li><li><a href='#'><img alt='' height='103' width='125' src…
  • Error Line 464, Column 880: required attribute "dir" not specified
    …tube.com/vi/9-qyFf5MN7E/0.jpg'><span>الأسير الى فاري</span><bdo></bdo></a></li>

    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 494, Column 333: required attribute "dir" not specified
    …ً</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 494, Column 641: required attribute "dir" not specified
    …ا</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 494, Column 947: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 494, Column 1270: required attribute "dir" not specified
    …د</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 494, Column 1595: required attribute "dir" not specified
    …ي</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 494, Column 1891: required attribute "dir" not specified
    …ه</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 494, Column 2207: required attribute "dir" not specified
    …ن</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 494, Column 2513: required attribute "dir" not specified
    …ا</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 494, Column 2813: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 494, Column 3135: required attribute "dir" not specified
    …افرة بقضية المخطوفين في اعزاز</a></span><bdo class="videogalhoder"></bdo></div>

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

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

  • Error Line 521, Column 365: required attribute "dir" not specified
    …ة</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 521, Column 686: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 521, Column 1007: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 521, Column 1313: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 521, Column 1631: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 521, Column 1936: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 521, Column 2251: required attribute "dir" not specified
    …ي</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 521, Column 2568: required attribute "dir" not specified
    …ي</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 521, Column 2883: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 521, Column 3196: required attribute "dir" not specified
    … الحالي لن يستمر الا بالتوافق</a></span><bdo class="videogalhoder"></bdo></div>

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

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

  • Error Line 543, Column 341: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 543, Column 649: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 543, Column 970: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 543, Column 1278: required attribute "dir" not specified
    …ي</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 543, Column 1598: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 543, Column 1911: required attribute "dir" not specified
    …ي</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 543, Column 2223: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 543, Column 2530: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 543, Column 2836: required attribute "dir" not specified
    …ر</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 543, Column 3148: required attribute "dir" not specified
    …ون جسرا استراتيجيا قرب النيجر</a></span><bdo class="videogalhoder"></bdo></div>

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

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

  • Error Line 564, Column 340: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 564, Column 635: required attribute "dir" not specified
    …ا</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 564, Column 945: required attribute "dir" not specified
    …ض</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 564, Column 1255: required attribute "dir" not specified
    …ض</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 564, Column 1562: required attribute "dir" not specified
    …ة</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 564, Column 1863: required attribute "dir" not specified
    …ن</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 564, Column 2173: required attribute "dir" not specified
    …1</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 564, Column 2476: required attribute "dir" not specified
    …ة</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 564, Column 2791: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 564, Column 3101: required attribute "dir" not specified
    … النفط يتذبذب تبعا لعوامل عدة</a></span><bdo class="videogalhoder"></bdo></div>

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

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

  • Error Line 584, Column 335: required attribute "dir" not specified
    …ه</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 584, Column 648: required attribute "dir" not specified
    …ز</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 584, Column 965: required attribute "dir" not specified
    …ي</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 584, Column 1261: required attribute "dir" not specified
    …ا</a></span><bdo class="videogalhoder"><a target='_blank' href="/MenuAr/news/D…

    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 584, Column 1729: required attribute "dir" not specified
    …ة</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 584, Column 2038: required attribute "dir" not specified
    …ت</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 584, Column 2342: required attribute "dir" not specified
    …ك</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 584, Column 2654: required attribute "dir" not specified
    …ا</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 584, Column 2965: required attribute "dir" not specified
    …ة</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 584, Column 3266: required attribute "dir" not specified
    …واطن في سيارة اجرة في سعدنايل</a></span><bdo class="videogalhoder"></bdo></div>

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

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

  • Error Line 604, Column 320: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 604, Column 620: required attribute "dir" not specified
    …ر</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 604, Column 945: required attribute "dir" not specified
    …ع</a></span><bdo class="videogalhoder"><a target='_blank'  href="/MenuAr/news/…

    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 604, Column 1399: required attribute "dir" not specified
    …ن</a></span><bdo class="videogalhoder"><a target='_blank'  href="/MenuAr/news/…

    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 604, Column 1850: required attribute "dir" not specified
    …ة</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 604, Column 2161: required attribute "dir" not specified
    …ر</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 604, Column 2483: required attribute "dir" not specified
    …"</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 604, Column 2769: required attribute "dir" not specified
    …ة</a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 604, Column 3073: required attribute "dir" not specified
    … </a></span><bdo class="videogalhoder"></bdo></div><div class="newsdiv newsdiv…

    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 604, Column 3393: required attribute "dir" not specified
    …ناً يوم الأربعاء من كل إسبوع </a></span><bdo class="videogalhoder"></bdo></div>

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

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

  • Warning Line 660, Column 19: multiple comments in comment declaration
    										<!-----------------------------most commmon------------------->
  • Warning Line 660, Column 23: multiple comments in comment declaration
    										<!-----------------------------most commmon------------------->
  • Warning Line 660, Column 27: multiple comments in comment declaration
    										<!-----------------------------most commmon------------------->
  • Warning Line 660, Column 31: multiple comments in comment declaration
    										<!-----------------------------most commmon------------------->
  • Warning Line 660, Column 35: multiple comments in comment declaration
    										<!-----------------------------most commmon------------------->
  • Warning Line 660, Column 39: multiple comments in comment declaration
    										<!-----------------------------most commmon------------------->
  • Error Line 660, Column 41: invalid comment declaration: found name character outside comment but inside comment declaration
    										<!-----------------------------most commmon------------------->
  • Info Line 660, Column 11: comment declaration started here
    										<!-----------------------------most commmon------------------->
  • Warning Line 701, Column 49: multiple comments in comment declaration
    …                              <!--------------------------end most common-----…
  • Warning Line 701, Column 53: multiple comments in comment declaration
    …                          <!--------------------------end most common---------…
  • Warning Line 701, Column 57: multiple comments in comment declaration
    …                      <!--------------------------end most common-------------…
  • Warning Line 701, Column 61: multiple comments in comment declaration
    …                  <!--------------------------end most common-----------------…
  • Warning Line 701, Column 65: multiple comments in comment declaration
    …                <!--------------------------end most common------------------->
  • Warning Line 701, Column 84: multiple comments in comment declaration
    …                <!--------------------------end most common------------------->
  • Warning Line 701, Column 88: multiple comments in comment declaration
    …                <!--------------------------end most common------------------->
  • Warning Line 701, Column 92: multiple comments in comment declaration
    …                <!--------------------------end most common------------------->
  • Warning Line 701, Column 96: multiple comments in comment declaration
    …                <!--------------------------end most common------------------->
  • Warning Line 701, Column 100: multiple comments in comment declaration
    …                <!--------------------------end most common------------------->
  • Error Line 701, Column 102: invalid comment declaration: found name character outside comment but inside comment declaration
    …                <!--------------------------end most common------------------->
  • Info Line 701, Column 41: comment declaration started here
    <!--------------------------end most com…
  • Error Line 721, Column 167: required attribute "alt" not specified
    …loads/999615260_Image.jpg" style="height:85px;width:670px;border-width:0px;" />

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

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

  • Warning Line 736, Column 34: multiple comments in comment declaration
                             <!------------AddBanner-------------------->
  • Warning Line 736, Column 38: multiple comments in comment declaration
                             <!------------AddBanner-------------------->
  • Error Line 736, Column 40: invalid comment declaration: found name start character outside comment but inside comment declaration
                             <!------------AddBanner-------------------->
  • Info Line 736, Column 26: comment declaration started here
                             <!------------AddBanner-------------------->
  • Error Line 742, Column 164: required attribute "alt" not specified
    …loads/860417342_Image.jpg" style="height:85px;width:670px;border-width:0px;" />

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

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

  • Warning Line 759, Column 41: multiple comments in comment declaration
    …                              <!-----------------------Local sport------------…
  • Warning Line 759, Column 45: multiple comments in comment declaration
    …                          <!-----------------------Local sport----------------…
  • Warning Line 759, Column 49: multiple comments in comment declaration
    …                      <!-----------------------Local sport--------------------…
  • Warning Line 759, Column 53: multiple comments in comment declaration
    …                  <!-----------------------Local sport------------------------…
  • Warning Line 759, Column 69: multiple comments in comment declaration
    …           <!-----------------------Local sport------------------------------->
  • Warning Line 759, Column 73: multiple comments in comment declaration
    …           <!-----------------------Local sport------------------------------->
  • Warning Line 759, Column 77: multiple comments in comment declaration
    …           <!-----------------------Local sport------------------------------->
  • Warning Line 759, Column 81: multiple comments in comment declaration
    …           <!-----------------------Local sport------------------------------->
  • Warning Line 759, Column 85: multiple comments in comment declaration
    …           <!-----------------------Local sport------------------------------->
  • Warning Line 759, Column 89: multiple comments in comment declaration
    …           <!-----------------------Local sport------------------------------->
  • Warning Line 759, Column 93: multiple comments in comment declaration
    …           <!-----------------------Local sport------------------------------->
  • Warning Line 759, Column 97: multiple comments in comment declaration
    …           <!-----------------------Local sport------------------------------->
  • Error Line 759, Column 99: invalid comment declaration: found name character outside comment but inside comment declaration
    …           <!-----------------------Local sport------------------------------->
  • Info Line 759, Column 33: comment declaration started here
                                    <!-----------------------Local sport-----------…
  • Error Line 760, Column 402: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …xtaligner"><div style='direction:rtl;'><a target='_blank' href='/MenuAr/news/D…

    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 760, Column 1247: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …xtaligner"><div style='direction:rtl;'><a target='_blank' href='/MenuAr/news/D…

    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 762, Column 427: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …xtaligner"><div style='direction:rtl;'><a target='_blank' href='/MenuAr/news/D…

    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 762, Column 1258: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …xtaligner"><div style='direction:rtl;'><a target='_blank' href='/MenuAr/news/D…

    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 764, Column 423: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …xtaligner"><div style='direction:rtl;'><a target='_blank' href='/MenuAr/news/D…

    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 764, Column 1228: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …xtaligner"><div style='direction:rtl;'><a target='_blank' href='/MenuAr/news/D…

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

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

  • Warning Line 773, Column 38: multiple comments in comment declaration
                                 <!------------AddBanner-------------------->
  • Warning Line 773, Column 42: multiple comments in comment declaration
                                 <!------------AddBanner-------------------->
  • Error Line 773, Column 44: invalid comment declaration: found name start character outside comment but inside comment declaration
                                 <!------------AddBanner-------------------->
  • Info Line 773, Column 30: comment declaration started here
                                 <!------------AddBanner-------------------->
  • Warning Line 787, Column 60: cannot generate system identifier for general entity "typeId"
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 787, Column 60: general entity "typeId" not defined and no default entity
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 

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

  • Warning Line 787, Column 66: reference not terminated by REFC delimiter
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 

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

  • Warning Line 787, Column 66: reference to external entity in attribute value
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 787, Column 66: reference to entity "typeId" for which no system identifier could be generated
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 

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

  • Info Line 787, Column 59: entity was defined here
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 
  • Warning Line 798, Column 125: reference not terminated by REFC delimiter
    …/Galleryfront.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Le…

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

  • Warning Line 798, Column 125: reference to external entity in attribute value
    …/Galleryfront.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Le…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 125: reference to entity "typeId" for which no system identifier could be generated
    …/Galleryfront.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Le…

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

  • Info Line 787, Column 59: entity was defined here
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 
  • Warning Line 798, Column 128: cannot generate system identifier for general entity "PublicId"
    …lleryfront.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Leban…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 798, Column 128: general entity "PublicId" not defined and no default entity
    …lleryfront.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Leban…

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

  • Warning Line 798, Column 136: reference not terminated by REFC delimiter
    …nt.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Lebanon Web A…

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

  • Warning Line 798, Column 136: reference to external entity in attribute value
    …nt.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Lebanon Web A…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 136: reference to entity "PublicId" for which no system identifier could be generated
    …nt.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Lebanon Web A…

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

  • Info Line 798, Column 127: entity was defined here
    …alleryfront.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Leba…
  • Warning Line 798, Column 423: reference not terminated by REFC delimiter
    …/Galleryfront.html?AlbumId=1824&typeId=4&PublicId=1">توزيع جوائز  Lebanon Web …

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

  • Warning Line 798, Column 423: reference to external entity in attribute value
    …/Galleryfront.html?AlbumId=1824&typeId=4&PublicId=1">توزيع جوائز  Lebanon Web …

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 423: reference to entity "typeId" for which no system identifier could be generated
    …/Galleryfront.html?AlbumId=1824&typeId=4&PublicId=1">توزيع جوائز  Lebanon Web …

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

  • Info Line 787, Column 59: entity was defined here
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 
  • Warning Line 798, Column 434: reference not terminated by REFC delimiter
    …nt.html?AlbumId=1824&typeId=4&PublicId=1">توزيع جوائز  Lebanon Web Award</a></…

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

  • Warning Line 798, Column 434: reference to external entity in attribute value
    …nt.html?AlbumId=1824&typeId=4&PublicId=1">توزيع جوائز  Lebanon Web Award</a></…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 434: reference to entity "PublicId" for which no system identifier could be generated
    …nt.html?AlbumId=1824&typeId=4&PublicId=1">توزيع جوائز  Lebanon Web Award</a></…

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

  • Info Line 798, Column 127: entity was defined here
    …alleryfront.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Leba…
  • Warning Line 798, Column 608: reference not terminated by REFC delimiter
    …/Galleryfront.html?AlbumId=1590&typeId=4&PublicId=1"><img alt="إحتفال Renault"…

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

  • Warning Line 798, Column 608: reference to external entity in attribute value
    …/Galleryfront.html?AlbumId=1590&typeId=4&PublicId=1"><img alt="إحتفال Renault"…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 608: reference to entity "typeId" for which no system identifier could be generated
    …/Galleryfront.html?AlbumId=1590&typeId=4&PublicId=1"><img alt="إحتفال Renault"…

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

  • Info Line 787, Column 59: entity was defined here
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 
  • Warning Line 798, Column 619: reference not terminated by REFC delimiter
    …nt.html?AlbumId=1590&typeId=4&PublicId=1"><img alt="إحتفال Renault" height="12…

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

  • Warning Line 798, Column 619: reference to external entity in attribute value
    …nt.html?AlbumId=1590&typeId=4&PublicId=1"><img alt="إحتفال Renault" height="12…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 619: reference to entity "PublicId" for which no system identifier could be generated
    …nt.html?AlbumId=1590&typeId=4&PublicId=1"><img alt="إحتفال Renault" height="12…

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

  • Info Line 798, Column 127: entity was defined here
    …alleryfront.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Leba…
  • Warning Line 798, Column 890: reference not terminated by REFC delimiter
    …/Galleryfront.html?AlbumId=1590&typeId=4&PublicId=1">إحتفال Renault</a></div><…

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

  • Warning Line 798, Column 890: reference to external entity in attribute value
    …/Galleryfront.html?AlbumId=1590&typeId=4&PublicId=1">إحتفال Renault</a></div><…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 890: reference to entity "typeId" for which no system identifier could be generated
    …/Galleryfront.html?AlbumId=1590&typeId=4&PublicId=1">إحتفال Renault</a></div><…

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

  • Info Line 787, Column 59: entity was defined here
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 
  • Warning Line 798, Column 901: reference not terminated by REFC delimiter
    …nt.html?AlbumId=1590&typeId=4&PublicId=1">إحتفال Renault</a></div></div><div c…

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

  • Warning Line 798, Column 901: reference to external entity in attribute value
    …nt.html?AlbumId=1590&typeId=4&PublicId=1">إحتفال Renault</a></div></div><div c…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 901: reference to entity "PublicId" for which no system identifier could be generated
    …nt.html?AlbumId=1590&typeId=4&PublicId=1">إحتفال Renault</a></div></div><div c…

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

  • Info Line 798, Column 127: entity was defined here
    …alleryfront.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Leba…
  • Warning Line 798, Column 1059: reference not terminated by REFC delimiter
    …/Galleryfront.html?AlbumId=1458&typeId=4&PublicId=1"><img alt="تكريم ملكة جمال…

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

  • Warning Line 798, Column 1059: reference to external entity in attribute value
    …/Galleryfront.html?AlbumId=1458&typeId=4&PublicId=1"><img alt="تكريم ملكة جمال…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 1059: reference to entity "typeId" for which no system identifier could be generated
    …/Galleryfront.html?AlbumId=1458&typeId=4&PublicId=1"><img alt="تكريم ملكة جمال…

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

  • Info Line 787, Column 59: entity was defined here
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 
  • Warning Line 798, Column 1070: reference not terminated by REFC delimiter
    …nt.html?AlbumId=1458&typeId=4&PublicId=1"><img alt="تكريم ملكة جمال لبنان رينا…

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

  • Warning Line 798, Column 1070: reference to external entity in attribute value
    …nt.html?AlbumId=1458&typeId=4&PublicId=1"><img alt="تكريم ملكة جمال لبنان رينا…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 1070: reference to entity "PublicId" for which no system identifier could be generated
    …nt.html?AlbumId=1458&typeId=4&PublicId=1"><img alt="تكريم ملكة جمال لبنان رينا…

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

  • Info Line 798, Column 127: entity was defined here
    …alleryfront.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Leba…
  • Warning Line 798, Column 1361: reference not terminated by REFC delimiter
    …/Galleryfront.html?AlbumId=1458&typeId=4&PublicId=1">تكريم ملكة جمال لبنان رين…

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

  • Warning Line 798, Column 1361: reference to external entity in attribute value
    …/Galleryfront.html?AlbumId=1458&typeId=4&PublicId=1">تكريم ملكة جمال لبنان رين…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 1361: reference to entity "typeId" for which no system identifier could be generated
    …/Galleryfront.html?AlbumId=1458&typeId=4&PublicId=1">تكريم ملكة جمال لبنان رين…

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

  • Info Line 787, Column 59: entity was defined here
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 
  • Warning Line 798, Column 1372: reference not terminated by REFC delimiter
    …nt.html?AlbumId=1458&typeId=4&PublicId=1">تكريم ملكة جمال لبنان رينا شيباني </…

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

  • Warning Line 798, Column 1372: reference to external entity in attribute value
    …nt.html?AlbumId=1458&typeId=4&PublicId=1">تكريم ملكة جمال لبنان رينا شيباني </…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 1372: reference to entity "PublicId" for which no system identifier could be generated
    …nt.html?AlbumId=1458&typeId=4&PublicId=1">تكريم ملكة جمال لبنان رينا شيباني </…

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

  • Info Line 798, Column 127: entity was defined here
    …alleryfront.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Leba…
  • Warning Line 798, Column 1550: reference not terminated by REFC delimiter
    …/Galleryfront.html?AlbumId=1413&typeId=4&PublicId=1"><img alt="تكريم سعد رمضان…

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

  • Warning Line 798, Column 1550: reference to external entity in attribute value
    …/Galleryfront.html?AlbumId=1413&typeId=4&PublicId=1"><img alt="تكريم سعد رمضان…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 1550: reference to entity "typeId" for which no system identifier could be generated
    …/Galleryfront.html?AlbumId=1413&typeId=4&PublicId=1"><img alt="تكريم سعد رمضان…

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

  • Info Line 787, Column 59: entity was defined here
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 
  • Warning Line 798, Column 1561: reference not terminated by REFC delimiter
    …nt.html?AlbumId=1413&typeId=4&PublicId=1"><img alt="تكريم سعد رمضان في طرابلس"…

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

  • Warning Line 798, Column 1561: reference to external entity in attribute value
    …nt.html?AlbumId=1413&typeId=4&PublicId=1"><img alt="تكريم سعد رمضان في طرابلس"…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 1561: reference to entity "PublicId" for which no system identifier could be generated
    …nt.html?AlbumId=1413&typeId=4&PublicId=1"><img alt="تكريم سعد رمضان في طرابلس"…

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

  • Info Line 798, Column 127: entity was defined here
    …alleryfront.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Leba…
  • Warning Line 798, Column 1843: reference not terminated by REFC delimiter
    …/Galleryfront.html?AlbumId=1413&typeId=4&PublicId=1">تكريم سعد رمضان في طرابلس…

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

  • Warning Line 798, Column 1843: reference to external entity in attribute value
    …/Galleryfront.html?AlbumId=1413&typeId=4&PublicId=1">تكريم سعد رمضان في طرابلس…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 1843: reference to entity "typeId" for which no system identifier could be generated
    …/Galleryfront.html?AlbumId=1413&typeId=4&PublicId=1">تكريم سعد رمضان في طرابلس…

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

  • Info Line 787, Column 59: entity was defined here
    <a target="_blank" href="/Mojtama3archive.html?AlbumId=922&typeId=4"> 
  • Warning Line 798, Column 1854: reference not terminated by REFC delimiter
    …nt.html?AlbumId=1413&typeId=4&PublicId=1">تكريم سعد رمضان في طرابلس</a></div><…

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

  • Warning Line 798, Column 1854: reference to external entity in attribute value
    …nt.html?AlbumId=1413&typeId=4&PublicId=1">تكريم سعد رمضان في طرابلس</a></div><…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 798, Column 1854: reference to entity "PublicId" for which no system identifier could be generated
    …nt.html?AlbumId=1413&typeId=4&PublicId=1">تكريم سعد رمضان في طرابلس</a></div><…

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

  • Info Line 798, Column 127: entity was defined here
    …alleryfront.html?AlbumId=1824&typeId=4&PublicId=1"><img alt="توزيع جوائز  Leba…
  • Warning Line 843, Column 37: multiple comments in comment declaration
                                <!------------------watch tonight -----------------…
  • Warning Line 843, Column 41: multiple comments in comment declaration
    …                          <!------------------watch tonight ------------------…
  • Warning Line 843, Column 45: multiple comments in comment declaration
    …                       <!------------------watch tonight --------------------->
  • Warning Line 843, Column 63: multiple comments in comment declaration
    …                       <!------------------watch tonight --------------------->
  • Warning Line 843, Column 67: multiple comments in comment declaration
    …                       <!------------------watch tonight --------------------->
  • Warning Line 843, Column 71: multiple comments in comment declaration
    …                       <!------------------watch tonight --------------------->
  • Warning Line 843, Column 75: multiple comments in comment declaration
    …                       <!------------------watch tonight --------------------->
  • Warning Line 843, Column 79: multiple comments in comment declaration
    …                       <!------------------watch tonight --------------------->
  • Warning Line 872, Column 31: multiple comments in comment declaration
                                <!------------------end watch tonight--------------…
  • Warning Line 872, Column 35: multiple comments in comment declaration
                                <!------------------end watch tonight--------------…
  • Warning Line 872, Column 39: multiple comments in comment declaration
                                <!------------------end watch tonight--------------…
  • Warning Line 872, Column 43: multiple comments in comment declaration
    …                        <!------------------end watch tonight-----------------…
  • Warning Line 872, Column 47: multiple comments in comment declaration
    …                    <!------------------end watch tonight---------------------…
  • Error Line 872, Column 49: invalid comment declaration: found name start character outside comment but inside comment declaration
    …                    <!------------------end watch tonight--------------------->
  • Info Line 843, Column 29: comment declaration started here
                                <!------------------watch tonight -----------------…
  • Error Line 878, Column 62: there is no attribute "SCROLLING"
    …0_MainContentPlaceHolder_s" SCROLLING="NO" style="border:0;overflow:hidden" wi…

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

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

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

  • Warning Line 889, Column 33: multiple comments in comment declaration
                            <!-------------------------------------------------->
  • Warning Line 889, Column 37: multiple comments in comment declaration
                            <!-------------------------------------------------->
  • Warning Line 889, Column 41: multiple comments in comment declaration
                            <!-------------------------------------------------->
  • Warning Line 889, Column 45: multiple comments in comment declaration
                            <!-------------------------------------------------->
  • Warning Line 889, Column 49: multiple comments in comment declaration
                            <!-------------------------------------------------->
  • Warning Line 889, Column 53: multiple comments in comment declaration
                            <!-------------------------------------------------->
  • Warning Line 889, Column 57: multiple comments in comment declaration
                            <!-------------------------------------------------->
  • Warning Line 889, Column 61: multiple comments in comment declaration
                            <!-------------------------------------------------->
  • Warning Line 889, Column 65: multiple comments in comment declaration
                            <!-------------------------------------------------->
  • Warning Line 889, Column 69: multiple comments in comment declaration
                            <!-------------------------------------------------->
  • Warning Line 889, Column 73: multiple comments in comment declaration
                            <!-------------------------------------------------->
  • Warning Line 891, Column 27: multiple comments in comment declaration
                            <!-----------------------------------------------------…
  • Warning Line 891, Column 31: multiple comments in comment declaration
                            <!-----------------------------------------------------…
  • Warning Line 891, Column 35: multiple comments in comment declaration
                            <!-----------------------------------------------------…
  • Warning Line 891, Column 39: multiple comments in comment declaration
                            <!-----------------------------------------------------…
  • Warning Line 891, Column 43: multiple comments in comment declaration
    …                      <!------------------------------------------------------>
  • Warning Line 891, Column 47: multiple comments in comment declaration
    …                      <!------------------------------------------------------>
  • Warning Line 891, Column 51: multiple comments in comment declaration
    …                      <!------------------------------------------------------>
  • Warning Line 891, Column 55: multiple comments in comment declaration
    …                      <!------------------------------------------------------>
  • Warning Line 891, Column 59: multiple comments in comment declaration
    …                      <!------------------------------------------------------>
  • Warning Line 891, Column 63: multiple comments in comment declaration
    …                      <!------------------------------------------------------>
  • Warning Line 891, Column 67: multiple comments in comment declaration
    …                      <!------------------------------------------------------>
  • Warning Line 891, Column 71: multiple comments in comment declaration
    …                      <!------------------------------------------------------>
  • Warning Line 891, Column 75: multiple comments in comment declaration
    …                      <!------------------------------------------------------>
  • Warning Line 891, Column 79: multiple comments in comment declaration
    …                      <!------------------------------------------------------>
  • Error Line 980, Column 93: required attribute "alt" not specified
    …der:0px;" height="106" width="232" src="/images/Presssecret4.jpg"  /></a></div>

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

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

  • Warning Line 1013, Column 37: multiple comments in comment declaration
                                <!------------------------انت المراسل--------------…
  • Warning Line 1013, Column 41: multiple comments in comment declaration
    …                          <!------------------------انت المراسل---------------…
  • Warning Line 1013, Column 45: multiple comments in comment declaration
    …                      <!------------------------انت المراسل-------------------…
  • Warning Line 1013, Column 49: multiple comments in comment declaration
    …                  <!------------------------انت المراسل-----------------------…
  • Warning Line 1013, Column 53: multiple comments in comment declaration
    …              <!------------------------انت المراسل---------------------------…
  • Error Line 1013, Column 55: invalid comment declaration: found name start character outside comment but inside comment declaration
    …            <!------------------------انت المراسل-----------------------------…
  • Info Line 1013, Column 29: comment declaration started here
                                <!------------------------انت المراسل--------------…
  • Warning Line 1043, Column 37: multiple comments in comment declaration
                                <!------------------------انت المراسل--------------…
  • Warning Line 1043, Column 41: multiple comments in comment declaration
    …                          <!------------------------انت المراسل---------------…
  • Warning Line 1043, Column 45: multiple comments in comment declaration
    …                      <!------------------------انت المراسل-------------------…
  • Warning Line 1043, Column 49: multiple comments in comment declaration
    …                  <!------------------------انت المراسل-----------------------…
  • Warning Line 1043, Column 53: multiple comments in comment declaration
    …              <!------------------------انت المراسل---------------------------…
  • Error Line 1043, Column 55: invalid comment declaration: found name start character outside comment but inside comment declaration
    …            <!------------------------انت المراسل-----------------------------…
  • Info Line 1043, Column 29: comment declaration started here
                                <!------------------------انت المراسل--------------…
  • Warning Line 1122, Column 37: multiple comments in comment declaration
                                <!------------------watch tonight -----------------…
  • Warning Line 1122, Column 41: multiple comments in comment declaration
    …                          <!------------------watch tonight ------------------…
  • Warning Line 1122, Column 45: multiple comments in comment declaration
    …                       <!------------------watch tonight --------------------->
  • Warning Line 1122, Column 63: multiple comments in comment declaration
    …                       <!------------------watch tonight --------------------->
  • Warning Line 1122, Column 67: multiple comments in comment declaration
    …                       <!------------------watch tonight --------------------->
  • Warning Line 1122, Column 71: multiple comments in comment declaration
    …                       <!------------------watch tonight --------------------->
  • Warning Line 1122, Column 75: multiple comments in comment declaration
    …                       <!------------------watch tonight --------------------->
  • Warning Line 1122, Column 79: multiple comments in comment declaration
    …                       <!------------------watch tonight --------------------->
  • Warning Line 1148, Column 31: multiple comments in comment declaration
                                <!------------------end watch tonight--------------…
  • Warning Line 1148, Column 35: multiple comments in comment declaration
                                <!------------------end watch tonight--------------…
  • Warning Line 1148, Column 39: multiple comments in comment declaration
                                <!------------------end watch tonight--------------…
  • Warning Line 1148, Column 43: multiple comments in comment declaration
    …                        <!------------------end watch tonight-----------------…
  • Warning Line 1148, Column 47: multiple comments in comment declaration
    …                    <!------------------end watch tonight---------------------…
  • Error Line 1148, Column 49: invalid comment declaration: found name start character outside comment but inside comment declaration
    …                    <!------------------end watch tonight--------------------->
  • Info Line 1122, Column 29: comment declaration started here
                                <!------------------watch tonight -----------------…
  • Warning Line 1153, Column 34: multiple comments in comment declaration
                             <!------------AddBanner4-------------------->
  • Warning Line 1153, Column 38: multiple comments in comment declaration
                             <!------------AddBanner4-------------------->
  • Error Line 1153, Column 40: invalid comment declaration: found name start character outside comment but inside comment declaration
                             <!------------AddBanner4-------------------->
  • Info Line 1153, Column 26: comment declaration started here
                             <!------------AddBanner4-------------------->
  • Warning Line 1209, Column 114: reference not terminated by REFC delimiter
    …u='http://www.aljadeed.tv/Polls.html&t=هل توافق(ين) على الانتخاب بحسب قانون ال…

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

  • Error Line 1209, Column 114: reference to entity "t" for which no system identifier could be generated
    …u='http://www.aljadeed.tv/Polls.html&t=هل توافق(ين) على الانتخاب بحسب قانون ال…

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

  • Info Line 457, Column 462: entity was defined here
    …deed.tv/videoplayerarchive.html?id=600&t=عين الحلوة,'sharer','toolbar=0,status…
  • Warning Line 1221, Column 37: multiple comments in comment declaration
                                <!--------------Polls---------------->
  • Warning Line 1221, Column 41: multiple comments in comment declaration
                                <!--------------Polls---------------->
  • Warning Line 1221, Column 50: multiple comments in comment declaration
                                <!--------------Polls---------------->
  • Warning Line 1221, Column 54: multiple comments in comment declaration
                                <!--------------Polls---------------->
  • Warning Line 1221, Column 58: multiple comments in comment declaration
                                <!--------------Polls---------------->
  • Warning Line 1221, Column 62: multiple comments in comment declaration
                                <!--------------Polls---------------->
  • Warning Line 1262, Column 11: multiple comments in comment declaration
    							 <!------------AddBanner4-------------------->
  • Warning Line 1262, Column 15: multiple comments in comment declaration
    							 <!------------AddBanner4-------------------->
  • Warning Line 1262, Column 19: multiple comments in comment declaration
    							 <!------------AddBanner4-------------------->
  • Warning Line 1262, Column 33: multiple comments in comment declaration
    							 <!------------AddBanner4-------------------->
  • Warning Line 1262, Column 37: multiple comments in comment declaration
    							 <!------------AddBanner4-------------------->
  • Warning Line 1262, Column 41: multiple comments in comment declaration
    							 <!------------AddBanner4-------------------->
  • Warning Line 1262, Column 45: multiple comments in comment declaration
    							 <!------------AddBanner4-------------------->
  • Warning Line 1262, Column 49: multiple comments in comment declaration
    							 <!------------AddBanner4-------------------->
  • Warning Line 1282, Column 24: multiple comments in comment declaration
                         <!------------AddBanner4-------------------->
  • Warning Line 1282, Column 28: multiple comments in comment declaration
                         <!------------AddBanner4-------------------->
  • Warning Line 1282, Column 32: multiple comments in comment declaration
                         <!------------AddBanner4-------------------->
  • Warning Line 1282, Column 46: multiple comments in comment declaration
                         <!------------AddBanner4-------------------->
  • Warning Line 1282, Column 50: multiple comments in comment declaration
                         <!------------AddBanner4-------------------->
  • Warning Line 1282, Column 54: multiple comments in comment declaration
                         <!------------AddBanner4-------------------->
  • Warning Line 1282, Column 58: multiple comments in comment declaration
                         <!------------AddBanner4-------------------->
  • Warning Line 1282, Column 62: multiple comments in comment declaration
                         <!------------AddBanner4-------------------->
  • Warning Line 1286, Column 28: multiple comments in comment declaration
                             <!------------AddBanner4-------------------->
  • Warning Line 1286, Column 32: multiple comments in comment declaration
                             <!------------AddBanner4-------------------->
  • Warning Line 1286, Column 36: multiple comments in comment declaration
                             <!------------AddBanner4-------------------->
  • Warning Line 1286, Column 50: multiple comments in comment declaration
                             <!------------AddBanner4-------------------->
  • Warning Line 1286, Column 54: multiple comments in comment declaration
                             <!------------AddBanner4-------------------->
  • Warning Line 1286, Column 58: multiple comments in comment declaration
                             <!------------AddBanner4-------------------->
  • Warning Line 1286, Column 62: multiple comments in comment declaration
                             <!------------AddBanner4-------------------->
  • Warning Line 1286, Column 66: multiple comments in comment declaration
                             <!------------AddBanner4-------------------->
  • Warning Line 1298, Column 34: multiple comments in comment declaration
    <script type='text/javascript'><!--	//<![CDATA[
  • Warning Line 1298, Column 36: S separator in comment declaration
    <script type='text/javascript'><!--	//<![CDATA[

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1298, Column 37: invalid comment declaration: found character "/" outside comment but inside comment declaration
    <script type='text/javascript'><!--	//<![CDATA[

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1221, Column 29: comment declaration started here
                                <!--------------Polls---------------->
  • Error Line 1312, Column 17: end tag for element "script" which is not open
    //]]>--></script><noscript><a href='http://d1.openx.org/ck.php?n=ab3d70c5&amp;c…

    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 1358, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
            </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 263, Column 4: start tag was here
    			<div class="sitemainmiddle" style="position:relative">
  • Error Line 1358, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
            </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 262, Column 3: start tag was here
    		<div id="secmainwrapper">
  • Warning Line 1367, Column 55: character "<" is the first character of a delimiter but occurred as data
    			                                          if (year < 1900) {

    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 1422, Column 33: multiple comments in comment declaration
                            <!---------------------Register------------------------…
  • Warning Line 1422, Column 37: multiple comments in comment declaration
                            <!---------------------Register------------------------…
  • Warning Line 1422, Column 41: multiple comments in comment declaration
    …                      <!---------------------Register-------------------------…
  • Warning Line 1422, Column 45: multiple comments in comment declaration
    …                     <!---------------------Register-------------------------->
  • Error Line 1422, Column 47: invalid comment declaration: found name character outside comment but inside comment declaration
    …                     <!---------------------Register-------------------------->
  • Info Line 1422, Column 25: comment declaration started here
                            <!---------------------Register------------------------…
  • Warning Line 1587, Column 33: multiple comments in comment declaration
                            <!---------------------end Register--------------------…
  • Warning Line 1587, Column 37: multiple comments in comment declaration
                            <!---------------------end Register--------------------…
  • Warning Line 1587, Column 41: multiple comments in comment declaration
    …                      <!---------------------end Register---------------------…
  • Warning Line 1587, Column 45: multiple comments in comment declaration
    …                  <!---------------------end Register-------------------------…
  • Error Line 1587, Column 47: invalid comment declaration: found name character outside comment but inside comment declaration
    …                 <!---------------------end Register-------------------------->
  • Info Line 1587, Column 25: comment declaration started here
                            <!---------------------end Register--------------------…
  • Warning Line 1606, Column 33: multiple comments in comment declaration
                            <!---------------------login-------------------------->
  • Warning Line 1606, Column 37: multiple comments in comment declaration
                            <!---------------------login-------------------------->
  • Warning Line 1606, Column 41: multiple comments in comment declaration
                            <!---------------------login-------------------------->
  • Warning Line 1606, Column 45: multiple comments in comment declaration
                            <!---------------------login-------------------------->
  • Error Line 1606, Column 47: invalid comment declaration: found name character outside comment but inside comment declaration
                            <!---------------------login-------------------------->
  • Info Line 1606, Column 25: comment declaration started here
                            <!---------------------login-------------------------->
  • Warning Line 1683, Column 33: multiple comments in comment declaration
                            <!---------------------end login-----------------------…
  • Warning Line 1683, Column 37: multiple comments in comment declaration
                            <!---------------------end login-----------------------…
  • Warning Line 1683, Column 41: multiple comments in comment declaration
    …                      <!---------------------end login------------------------…
  • Warning Line 1683, Column 45: multiple comments in comment declaration
    …                    <!---------------------end login-------------------------->
  • Error Line 1683, Column 47: invalid comment declaration: found name character outside comment but inside comment declaration
    …                    <!---------------------end login-------------------------->
  • Info Line 1683, Column 25: comment declaration started here
                            <!---------------------end login-----------------------…
  • Warning Line 1695, Column 13: multiple comments in comment declaration
        <!---------------------GetScore------------------------->
  • Warning Line 1695, Column 17: multiple comments in comment declaration
        <!---------------------GetScore------------------------->
  • Warning Line 1695, Column 21: multiple comments in comment declaration
        <!---------------------GetScore------------------------->
  • Warning Line 1695, Column 25: multiple comments in comment declaration
        <!---------------------GetScore------------------------->
  • Error Line 1695, Column 27: invalid comment declaration: found name character outside comment but inside comment declaration
        <!---------------------GetScore------------------------->
  • Info Line 1695, Column 5: comment declaration started here
        <!---------------------GetScore------------------------->
  • Error Line 1706, Column 34: required attribute "type" not specified
        <script language="javascript">

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

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

  • Warning Line 1762, Column 13: multiple comments in comment declaration
        <!---------------------end GetScore-------------------------->
  • Warning Line 1762, Column 17: multiple comments in comment declaration
        <!---------------------end GetScore-------------------------->
  • Warning Line 1762, Column 21: multiple comments in comment declaration
        <!---------------------end GetScore-------------------------->
  • Warning Line 1762, Column 25: multiple comments in comment declaration
        <!---------------------end GetScore-------------------------->
  • Error Line 1762, Column 27: invalid comment declaration: found name character outside comment but inside comment declaration
        <!---------------------end GetScore-------------------------->
  • Info Line 1762, Column 5: comment declaration started here
        <!---------------------end GetScore-------------------------->

Visitor Analysis

Daily Visitor
  • 8.633 visits