الموقع الرسمي لجريدة المنتخب المغربية ...

almountakhab.com
  • Domain Name
    almountakhab.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #27279
  • Page Size
    93.3 KB
  • Ip Address
    176.31.234.88
  • Heading
    H1: 0, H2: 5, H3: 26, H4: 4, H5: 3, H6: 0
  • Images
    14 GIF, 52 JPG, 8 PNG

Website Meta Analysis

  • Title
    جريدة المنتخب المغربية
  • Meta Keyword
    almountakhab,المنتخب,maroc championat,elbotola,botola,lions atlas,actualités sportif,sport maroc
  • Meta Description
    الموقع الرسمي لجريدة المنتخب المغربية

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    176.31.234.88
  • Domain Age
    13 Years, 0 Months, 17 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from almountakhab.com.

HTML Analysis

  • date: Tue, 30 Jul 2013 15:36:36 GMT
  • server: Apache
  • x-powered-by: PHP/5.3.16
  • p3p: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
  • cache-control: max-age=60, private, proxy-revalidate
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registration Service Provided By: NAJA7HOST.COM

Domain Name: ALMOUNTAKHAB.COM

Registration Date: 22-Jul-2000
Expiration Date: 22-Jul-2015

Status:ACTIVE


Name Servers:
ns1.almountakhab.com
ns2.almountakhab.com


Registrant Contact Details:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Administrative Contact Details:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Technical Contact Details:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Billing Contact Details:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

PRIVACYPROTECT.ORG is providing privacy protection services to this domain name to
protect the owner from spam and phishing attacks. PrivacyProtect.org is not
responsible for any of the activities associated with this domain name. If you wish
to report any abuse concerning the usage of this domain name, you may do so at
http://privacyprotect.org/contact. We have a stringent abuse policy and any
complaint will be actioned within a short period of time.

The data in this whois database is provided to you for information purposes
only, that is, to assist you in obtaining information about or related to a
domain name registration record. We make this information available "as is",
and do 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:
(1) enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or
(2) allow, enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic mail, or
by telephone.
The compilation, repackaging, dissemination or other use of this data is
expressly prohibited without prior written consent from us. The Registrar of
record is UK2 Group Ltd..
We reserve the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.

DNS Analysis


DNS servers
ns1.almountakhab.com [176.31.234.88]
ns2.almountakhab.com [176.31.234.88]


DNS Records

Answer records
almountakhab.com MX
preference: 0
exchange: almountakhab.com
14400s
almountakhab.com SOA
server: ns1.almountakhab.com
email: limad25@gmail.com
serial: 2012091801
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
almountakhab.com NS  ns2.almountakhab.com 86400s
almountakhab.com NS  ns1.almountakhab.com 86400s
almountakhab.com A 176.31.234.88 14400s

Authority records

Additional records
almountakhab.com A 176.31.234.88 14400s
ns1.almountakhab.com A 176.31.234.88 14400s
ns2.almountakhab.com A 176.31.234.88 14400s

IP 176.31.234.88 Analysis

  • Country Code
    FR
  • Country Code3
    FRA
  • Country Name
    France
  • City
    EU
  • Continent Code
    46° North
  • Latitude
    2.
  • Longitude
  • No whois ip data for 176.31.234.88

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 2 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.7625363790540399
Message Error
  • Error Line 77, Column 13: there is no attribute "target"
    		<a target="_blank" href="http://adserver.adtech.de/?adlink|3.0|1143|3642221|1…

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

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

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

  • Warning Line 77, Column 160: cannot generate system identifier for general entity "utm_medium"
    …ito.ma/fr/maroc?utm_source=TouchMedia&utm_medium=CPC&utm_campaign=almountakhab…

    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 77, Column 160: general entity "utm_medium" not defined and no default entity
    …ito.ma/fr/maroc?utm_source=TouchMedia&utm_medium=CPC&utm_campaign=almountakhab…

    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 77, Column 170: reference not terminated by REFC delimiter
    …a/fr/maroc?utm_source=TouchMedia&utm_medium=CPC&utm_campaign=almountakhab.com">

    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 77, Column 170: reference to external entity in attribute value
    …a/fr/maroc?utm_source=TouchMedia&utm_medium=CPC&utm_campaign=almountakhab.com">

    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 77, Column 170: reference to entity "utm_medium" for which no system identifier could be generated
    …a/fr/maroc?utm_source=TouchMedia&utm_medium=CPC&utm_campaign=almountakhab.com">

    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 77, Column 159: entity was defined here
    …vito.ma/fr/maroc?utm_source=TouchMedia&utm_medium=CPC&utm_campaign=almountakha…
  • Warning Line 77, Column 175: cannot generate system identifier for general entity "utm_campaign"
    …a/fr/maroc?utm_source=TouchMedia&utm_medium=CPC&utm_campaign=almountakhab.com">

    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 77, Column 175: general entity "utm_campaign" not defined and no default entity
    …a/fr/maroc?utm_source=TouchMedia&utm_medium=CPC&utm_campaign=almountakhab.com">

    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 77, Column 187: reference not terminated by REFC delimiter
    …a/fr/maroc?utm_source=TouchMedia&utm_medium=CPC&utm_campaign=almountakhab.com">

    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 77, Column 187: reference to external entity in attribute value
    …a/fr/maroc?utm_source=TouchMedia&utm_medium=CPC&utm_campaign=almountakhab.com">

    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 77, Column 187: reference to entity "utm_campaign" for which no system identifier could be generated
    …a/fr/maroc?utm_source=TouchMedia&utm_medium=CPC&utm_campaign=almountakhab.com">

    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 77, Column 174: entity was defined here
    …a/fr/maroc?utm_source=TouchMedia&utm_medium=CPC&utm_campaign=almountakhab.com">
  • Error Line 77, Column 205: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …a/fr/maroc?utm_source=TouchMedia&utm_medium=CPC&utm_campaign=almountakhab.com">

    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 78, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id="habillage"></div></a><div id="wrapper" class="container_16">

    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 84, Column 43: there is no attribute "align"
    …object height="175" width="472" align="right" id="logoalmountakhab" codebase="…

    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 89, Column 23: there is no attribute "height"
            <embed height="175" width="472" allowscriptaccess="samedomain" swliveco…

    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 89, Column 35: there is no attribute "width"
            <embed height="175" width="472" allowscriptaccess="samedomain" swliveco…

    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 89, Column 59: there is no attribute "allowscriptaccess"
    …t="175" width="472" allowscriptaccess="samedomain" swliveconnect="true" qualit…

    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 89, Column 86: there is no attribute "swliveconnect"
    …riptaccess="samedomain" swliveconnect="true" quality="high" bgcolor="#FFFFFF" …

    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 89, Column 101: there is no attribute "quality"
    …edomain" swliveconnect="true" quality="high" bgcolor="#FFFFFF" src="/img/logoa…

    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 89, Column 116: there is no attribute "bgcolor"
    …connect="true" quality="high" bgcolor="#FFFFFF" src="/img/logoalmountakhab.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 89, Column 130: there is no attribute "src"
    … quality="high" bgcolor="#FFFFFF" src="/img/logoalmountakhab.swf" name="logoal…

    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 89, Column 163: there is no attribute "name"
    … src="/img/logoalmountakhab.swf" name="logoalmountakhab" pluginspage="http://w…

    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 89, Column 194: there is no attribute "pluginspage"
    …" name="logoalmountakhab" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 89, Column 245: there is no attribute "type"
    …p://www.macromedia.com/go/getflashplayer" type="application/x-shockwave-flash">

    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 89, Column 276: element "embed" undefined
    …p://www.macromedia.com/go/getflashplayer" type="application/x-shockwave-flash">

    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 90, Column 19: element "noembed" undefined
              <noembed>

    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 92, Column 15: 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 89, Column 9: start tag was here
            <embed height="175" width="472" allowscriptaccess="samedomain" swliveco…
  • Error Line 98, Column 24: there is no attribute "direction"
    		  <marquee direction="right" scrollamount="3" onmouseover="this.scrollAmount=…

    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 98, Column 45: there is no attribute "scrollamount"
    …arquee direction="right" scrollamount="3" onmouseover="this.scrollAmount=0" on…

    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 98, Column 61: there is no attribute "onmouseover"
    …="right" scrollamount="3" onmouseover="this.scrollAmount=0" onmouseout="this.s…

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

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

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

  • Error Line 98, Column 94: there is no attribute "onmouseout"
    …lamount="3" onmouseover="this.scrollAmount=0" onmouseout="this.scrollAmount=3">

    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 98, Column 115: element "marquee" undefined
    …lamount="3" onmouseover="this.scrollAmount=0" onmouseout="this.scrollAmount=3">

    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 102, Column 19: element "center" undefined
    	</div>				<center> 

    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 118, Column 60: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …"submit" type="submit" value="البحث" /><input name="q" type="text" class="sear…

    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 118, Column 118: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …<input name="q" type="text" class="search_input" id="q" />        </form></div>

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

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

  • Error Line 128, Column 9: element "center" undefined
    	<center><img style = "cursor:pointer;" class="snapshot_image" src="/app/webroo…

    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 134, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 152, Column 77: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    					<div style="position:absolute; height:165px;width:217px;z-index:1000; ">

    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 154, Column 88: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …    style="z-index:100;position:absolute;top:0px;width:217px; height:165px;"  >

    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 166, Column 77: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    					<div style="position:absolute; height:165px;width:217px;z-index:1000; ">

    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 168, Column 88: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …    style="z-index:100;position:absolute;top:0px;width:217px; height:165px;"  >

    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 180, Column 77: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    					<div style="position:absolute; height:165px;width:217px;z-index:1000; ">

    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 182, Column 88: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …    style="z-index:100;position:absolute;top:0px;width:217px; height:165px;"  >

    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 194, Column 77: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    					<div style="position:absolute; height:165px;width:217px;z-index:1000; ">

    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 196, Column 88: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …    style="z-index:100;position:absolute;top:0px;width:217px; height:165px;"  >

    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 210, Column 8: element "center" undefined
    <center>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 211, Column 97: cannot generate system identifier for general entity "sport"
    …00" width="200" height="300" id="Cote&sport - PROGRAMME - 200 X 300" align="mi…

    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 211, Column 97: general entity "sport" not defined and no default entity
    …00" width="200" height="300" id="Cote&sport - PROGRAMME - 200 X 300" align="mi…

    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 211, Column 102: reference not terminated by REFC delimiter
    …idth="200" height="300" id="Cote&sport - PROGRAMME - 200 X 300" align="middle"…

    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 211, Column 102: reference to external entity in attribute value
    …idth="200" height="300" id="Cote&sport - PROGRAMME - 200 X 300" align="middle"…

    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 211, Column 102: reference to entity "sport" for which no system identifier could be generated
    …idth="200" height="300" id="Cote&sport - PROGRAMME - 200 X 300" align="middle"…

    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 211, Column 96: entity was defined here
    …000" width="200" height="300" id="Cote&sport - PROGRAMME - 200 X 300" align="m…
  • Error Line 211, Column 102: value of attribute "id" must be a single token
    …idth="200" height="300" id="Cote&sport - PROGRAMME - 200 X 300" align="middle"…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 211, Column 103: value of attribute "id" invalid: "-" cannot start a name
    …idth="200" height="300" id="Cote&sport - PROGRAMME - 200 X 300" align="middle">

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

  • Error Line 211, Column 115: value of attribute "id" invalid: "-" cannot start a name
    …idth="200" height="300" id="Cote&sport - PROGRAMME - 200 X 300" align="middle">

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

  • Error Line 211, Column 117: value of attribute "id" invalid: "2" cannot start a name
    …idth="200" height="300" id="Cote&sport - PROGRAMME - 200 X 300" align="middle">

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

  • Error Line 211, Column 123: value of attribute "id" invalid: "3" cannot start a name
    …idth="200" height="300" id="Cote&sport - PROGRAMME - 200 X 300" align="middle">

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

  • Error Line 290, Column 111: end tag for element "a" which is not open
    …s-international/slug:3cris">رونالدو يطيح بيونايتد ويقود ريال للربع</a></a></h2>

    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 297, Column 114: end tag for element "a" which is not open
    …nternational/slug:bosk47">بوسكيتس يعترف بان برشلونة يفتقد فيلانوفا</a></a></h2>

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

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

  • Error Line 304, Column 108: end tag for element "a" which is not open
    …news-international/slug:1marad">مارادونا مستعد للتفاوض مع مونبليي </a></a></h2>

    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 311, Column 94: end tag for element "a" which is not open
    …des/view/type:news-national/slug:g89">نادي الرؤساء الذي ولد ميتا  </a></a></h2>

    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 318, Column 103: end tag for element "a" which is not open
    …type:news-national/slug:1sallf">ياسين الصالحي: أشعر بتحسن مستواي  </a></a></h2>

    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 445, Column 8: element "center" undefined
    <center><img class="" id="nodes_last_photo" src="/app/webroot/files/image/galle…

    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 445, Column 132: required attribute "alt" not specified
    …files/image/gallery/1_jpg_51351c49_3d30_4391_9d89_7ac1b01fea58.jpg" /></center>

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

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

  • Error Line 469, Column 29: document type does not allow element "div" here
    $("<div class='message_ajax'></div>").insertBefore('#sondage_form');

    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 494, Column 104: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …[poll_id]" value="156" id="SondagePollResultPollId" /> <div class="formErrors">

    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 496, Column 115: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …agePollResultPollChoiceId_" value="" /><input type="radio" name="data[SondageP…

    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 496, Column 235: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …lResultPollChoiceId499" value="499"  /><label for="SondagePollResultPollChoice…

    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 496, Column 281: document type does not allow element "label" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …for="SondagePollResultPollChoiceId499">ريال مدريد</label><br /><input type="ra…

    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 496, Column 305: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …llChoiceId499">ريال مدريد</label><br /><input type="radio" name="data[SondageP…

    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 496, Column 425: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …lResultPollChoiceId500" value="500"  /><label for="SondagePollResultPollChoice…

    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 496, Column 471: document type does not allow element "label" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …  /><label for="SondagePollResultPollChoiceId500">مانشستر يونايتد</label><br />

    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 496, Column 500: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …  /><label for="SondagePollResultPollChoiceId500">مانشستر يونايتد</label><br />

    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 497, Column 8: element "center" undefined
    <center>

    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 498, Column 343: end tag for "input" omitted, but OMITTAG NO was specified
    …sizable=no, scrollbars=yes, status=no'); return false;" type="submit"></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 498, Column 58: start tag was here
    …" class="submit button" value="صوت" /><input class="submit" value="النتائج" st…
  • Warning Line 511, Column 155: unclosed start-tag requires SHORTTAG YES
    …mage/thumbs/Logo_DHJ_Det_jpg_4c6d48c7_dc3c_4e03_a045_6b3dd5fbba93.jpg"</a></td>

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

  • Error Line 511, Column 155: required attribute "alt" not specified
    …mage/thumbs/Logo_DHJ_Det_jpg_4c6d48c7_dc3c_4e03_a045_6b3dd5fbba93.jpg"</a></td>

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

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

  • Error Line 511, Column 158: end tag for "img" omitted, but OMITTAG NO was specified
    …mage/thumbs/Logo_DHJ_Det_jpg_4c6d48c7_dc3c_4e03_a045_6b3dd5fbba93.jpg"</a></td>

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

  • Info Line 511, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/17"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 513, Column 153: unclosed start-tag requires SHORTTAG YES
    …image/thumbs/morocco_ock_gif_4c18ba10_cd70_42e6_b845_01f47287acdc.gif"</a></td>

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

  • Error Line 513, Column 153: required attribute "alt" not specified
    …image/thumbs/morocco_ock_gif_4c18ba10_cd70_42e6_b845_01f47287acdc.gif"</a></td>

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

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

  • Error Line 513, Column 156: end tag for "img" omitted, but OMITTAG NO was specified
    …image/thumbs/morocco_ock_gif_4c18ba10_cd70_42e6_b845_01f47287acdc.gif"</a></td>

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

  • Info Line 513, Column 40: start tag was here
    …			<td><a href="/league/clubs/view/6"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 519, Column 162: unclosed start-tag requires SHORTTAG YES
    …umbs/naoufl_berkane_logo_jpg_4e6955a5_3138_4473_baf9_3368bca598bf.jpg"</a></td>

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

  • Error Line 519, Column 162: required attribute "alt" not specified
    …umbs/naoufl_berkane_logo_jpg_4e6955a5_3138_4473_baf9_3368bca598bf.jpg"</a></td>

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

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

  • Error Line 519, Column 165: end tag for "img" omitted, but OMITTAG NO was specified
    …umbs/naoufl_berkane_logo_jpg_4e6955a5_3138_4473_baf9_3368bca598bf.jpg"</a></td>

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

  • Info Line 519, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/39"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 521, Column 149: unclosed start-tag requires SHORTTAG YES
    …les/image/thumbs/Mas_fes_jpg_4c18bb86_7544_45c3_8108_01f47287acdc.jpg"</a></td>

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

  • Error Line 521, Column 149: required attribute "alt" not specified
    …les/image/thumbs/Mas_fes_jpg_4c18bb86_7544_45c3_8108_01f47287acdc.jpg"</a></td>

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

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

  • Error Line 521, Column 152: end tag for "img" omitted, but OMITTAG NO was specified
    …les/image/thumbs/Mas_fes_jpg_4c18bb86_7544_45c3_8108_01f47287acdc.jpg"</a></td>

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

  • Info Line 521, Column 40: start tag was here
    …			<td><a href="/league/clubs/view/9"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 527, Column 145: unclosed start-tag requires SHORTTAG YES
    …t/files/image/thumbs/waf_gif_4c18baaf_d914_411e_af3d_01f47287acdc.gif"</a></td>

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

  • Error Line 527, Column 145: required attribute "alt" not specified
    …t/files/image/thumbs/waf_gif_4c18baaf_d914_411e_af3d_01f47287acdc.gif"</a></td>

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

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

  • Error Line 527, Column 148: end tag for "img" omitted, but OMITTAG NO was specified
    …t/files/image/thumbs/waf_gif_4c18baaf_d914_411e_af3d_01f47287acdc.gif"</a></td>

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

  • Info Line 527, Column 40: start tag was here
    …			<td><a href="/league/clubs/view/7"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 529, Column 151: unclosed start-tag requires SHORTTAG YES
    …s/image/thumbs/maroc_ocs_gif_4c144c90_7be8_434b_b7dd_08447287acdc.gif"</a></td>

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

  • Error Line 529, Column 151: required attribute "alt" not specified
    …s/image/thumbs/maroc_ocs_gif_4c144c90_7be8_434b_b7dd_08447287acdc.gif"</a></td>

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

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

  • Error Line 529, Column 154: end tag for "img" omitted, but OMITTAG NO was specified
    …s/image/thumbs/maroc_ocs_gif_4c144c90_7be8_434b_b7dd_08447287acdc.gif"</a></td>

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

  • Info Line 529, Column 40: start tag was here
    …			<td><a href="/league/clubs/view/5"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 535, Column 157: unclosed start-tag requires SHORTTAG YES
    …ge/thumbs/Chabab_Hoceima_jpg_4c6d451d_5134_4489_b7f9_58ced5fbba93.jpg"</a></td>

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

  • Error Line 535, Column 157: required attribute "alt" not specified
    …ge/thumbs/Chabab_Hoceima_jpg_4c6d451d_5134_4489_b7f9_58ced5fbba93.jpg"</a></td>

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

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

  • Error Line 535, Column 160: end tag for "img" omitted, but OMITTAG NO was specified
    …ge/thumbs/Chabab_Hoceima_jpg_4c6d451d_5134_4489_b7f9_58ced5fbba93.jpg"</a></td>

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

  • Info Line 535, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/19"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 537, Column 145: unclosed start-tag requires SHORTTAG YES
    …t/files/image/thumbs/wac_jpg_4c144824_a4c4_4177_a344_08447287acdc.jpg"</a></td>

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

  • Error Line 537, Column 145: required attribute "alt" not specified
    …t/files/image/thumbs/wac_jpg_4c144824_a4c4_4177_a344_08447287acdc.jpg"</a></td>

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

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

  • Error Line 537, Column 148: end tag for "img" omitted, but OMITTAG NO was specified
    …t/files/image/thumbs/wac_jpg_4c144824_a4c4_4177_a344_08447287acdc.jpg"</a></td>

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

  • Info Line 537, Column 40: start tag was here
    …			<td><a href="/league/clubs/view/3"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 543, Column 146: unclosed start-tag requires SHORTTAG YES
    …t/files/image/thumbs/kac_jpg_4c18bc32_a5b8_440f_ac2a_01f47287acdc.jpg"</a></td>

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

  • Error Line 543, Column 146: required attribute "alt" not specified
    …t/files/image/thumbs/kac_jpg_4c18bc32_a5b8_440f_ac2a_01f47287acdc.jpg"</a></td>

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

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

  • Error Line 543, Column 149: end tag for "img" omitted, but OMITTAG NO was specified
    …t/files/image/thumbs/kac_jpg_4c18bc32_a5b8_440f_ac2a_01f47287acdc.jpg"</a></td>

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

  • Info Line 543, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/11"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 545, Column 151: unclosed start-tag requires SHORTTAG YES
    …es/image/thumbs/husa_big_jpg_4c18bd23_627c_4daa_ac7c_01f47287acdc.jpg"</a></td>

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

  • Error Line 545, Column 151: required attribute "alt" not specified
    …es/image/thumbs/husa_big_jpg_4c18bd23_627c_4daa_ac7c_01f47287acdc.jpg"</a></td>

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

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

  • Error Line 545, Column 154: end tag for "img" omitted, but OMITTAG NO was specified
    …es/image/thumbs/husa_big_jpg_4c18bd23_627c_4daa_ac7c_01f47287acdc.jpg"</a></td>

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

  • Info Line 545, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/14"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 551, Column 149: unclosed start-tag requires SHORTTAG YES
    …les/image/thumbs/rca_jpg_gif_4c144a9b_3688_4891_86c4_08447287acdc.gif"</a></td>

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

  • Error Line 551, Column 149: required attribute "alt" not specified
    …les/image/thumbs/rca_jpg_gif_4c144a9b_3688_4891_86c4_08447287acdc.gif"</a></td>

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

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

  • Error Line 551, Column 152: end tag for "img" omitted, but OMITTAG NO was specified
    …les/image/thumbs/rca_jpg_gif_4c144a9b_3688_4891_86c4_08447287acdc.gif"</a></td>

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

  • Info Line 551, Column 40: start tag was here
    …			<td><a href="/league/clubs/view/4"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 553, Column 158: unclosed start-tag requires SHORTTAG YES
    …e/thumbs/logo_maroc_codm_jpg_4cbb71fc_5f94_4491_af2a_0fb07287acdc.jpg"</a></td>

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

  • Error Line 553, Column 158: required attribute "alt" not specified
    …e/thumbs/logo_maroc_codm_jpg_4cbb71fc_5f94_4491_af2a_0fb07287acdc.jpg"</a></td>

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

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

  • Error Line 553, Column 161: end tag for "img" omitted, but OMITTAG NO was specified
    …e/thumbs/logo_maroc_codm_jpg_4cbb71fc_5f94_4491_af2a_0fb07287acdc.jpg"</a></td>

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

  • Info Line 553, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/26"><img class="thumb" src="/app/webroot/fil…
  • Error Line 715, Column 8: end tag for "p" omitted, but OMITTAG NO was specified
    		</div>

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

  • Info Line 713, Column 33: start tag was here
    		<div class="hide_me main_box"><p>
  • Warning Line 727, Column 154: unclosed start-tag requires SHORTTAG YES
    …image/thumbs/75516798hb5_jpg_4cbb88e1_b240_44fc_b1ec_0fb07287acdc.jpg"</a></td>

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

  • Error Line 727, Column 154: required attribute "alt" not specified
    …image/thumbs/75516798hb5_jpg_4cbb88e1_b240_44fc_b1ec_0fb07287acdc.jpg"</a></td>

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

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

  • Error Line 727, Column 157: end tag for "img" omitted, but OMITTAG NO was specified
    …image/thumbs/75516798hb5_jpg_4cbb88e1_b240_44fc_b1ec_0fb07287acdc.jpg"</a></td>

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

  • Info Line 727, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/33"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 729, Column 157: unclosed start-tag requires SHORTTAG YES
    …ge/thumbs/logo_maroc_ust_jpg_4cbb8e67_4454_4968_a941_0fb07287acdc.jpg"</a></td>

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

  • Error Line 729, Column 157: required attribute "alt" not specified
    …ge/thumbs/logo_maroc_ust_jpg_4cbb8e67_4454_4968_a941_0fb07287acdc.jpg"</a></td>

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

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

  • Error Line 729, Column 160: end tag for "img" omitted, but OMITTAG NO was specified
    …ge/thumbs/logo_maroc_ust_jpg_4cbb8e67_4454_4968_a941_0fb07287acdc.jpg"</a></td>

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

  • Info Line 729, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/36"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 735, Column 160: unclosed start-tag requires SHORTTAG YES
    …thumbs/logo_maroc_racing_jpg_4cbb888b_5134_4c7a_9ffc_0fb07287acdc.jpg"</a></td>

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

  • Error Line 735, Column 160: required attribute "alt" not specified
    …thumbs/logo_maroc_racing_jpg_4cbb888b_5134_4c7a_9ffc_0fb07287acdc.jpg"</a></td>

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

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

  • Error Line 735, Column 163: end tag for "img" omitted, but OMITTAG NO was specified
    …thumbs/logo_maroc_racing_jpg_4cbb888b_5134_4c7a_9ffc_0fb07287acdc.jpg"</a></td>

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

  • Info Line 735, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/32"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 737, Column 154: unclosed start-tag requires SHORTTAG YES
    …image/thumbs/ChababTadla_jpg_4c6d4b46_c454_45f8_9bba_7a6fd5fbba93.jpg"</a></td>

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

  • Error Line 737, Column 154: required attribute "alt" not specified
    …image/thumbs/ChababTadla_jpg_4c6d4b46_c454_45f8_9bba_7a6fd5fbba93.jpg"</a></td>

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

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

  • Error Line 737, Column 157: end tag for "img" omitted, but OMITTAG NO was specified
    …image/thumbs/ChababTadla_jpg_4c6d4b46_c454_45f8_9bba_7a6fd5fbba93.jpg"</a></td>

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

  • Info Line 737, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/20"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 743, Column 158: unclosed start-tag requires SHORTTAG YES
    …e/thumbs/logo_maroc_cayb_jpg_4cbb872d_ad90_4848_862a_0fb07287acdc.jpg"</a></td>

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

  • Error Line 743, Column 158: required attribute "alt" not specified
    …e/thumbs/logo_maroc_cayb_jpg_4cbb872d_ad90_4848_862a_0fb07287acdc.jpg"</a></td>

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

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

  • Error Line 743, Column 161: end tag for "img" omitted, but OMITTAG NO was specified
    …e/thumbs/logo_maroc_cayb_jpg_4cbb872d_ad90_4848_862a_0fb07287acdc.jpg"</a></td>

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

  • Info Line 743, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/28"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 745, Column 154: unclosed start-tag requires SHORTTAG YES
    …image/thumbs/ana_bar_325_gif_4cbb7137_966c_4efa_b392_0fb07287acdc.gif"</a></td>

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

  • Error Line 745, Column 154: required attribute "alt" not specified
    …image/thumbs/ana_bar_325_gif_4cbb7137_966c_4efa_b392_0fb07287acdc.gif"</a></td>

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

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

  • Error Line 745, Column 157: end tag for "img" omitted, but OMITTAG NO was specified
    …image/thumbs/ana_bar_325_gif_4cbb7137_966c_4efa_b392_0fb07287acdc.gif"</a></td>

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

  • Info Line 745, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/24"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 751, Column 148: unclosed start-tag requires SHORTTAG YES
    …files/image/thumbs/logoa_jpg_505f016f_9b08_47e4_9182_4b72b01fea58.jpg"</a></td>

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

  • Error Line 751, Column 148: required attribute "alt" not specified
    …files/image/thumbs/logoa_jpg_505f016f_9b08_47e4_9182_4b72b01fea58.jpg"</a></td>

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

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

  • Error Line 751, Column 151: end tag for "img" omitted, but OMITTAG NO was specified
    …files/image/thumbs/logoa_jpg_505f016f_9b08_47e4_9182_4b72b01fea58.jpg"</a></td>

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

  • Info Line 751, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/42"><img class="thumb" src="/app/webroot/fil…
  • Warning Line 753, Column 147: unclosed start-tag requires SHORTTAG YES
    …/files/image/thumbs/logo_png_4cbb869e_4590_4b15_abc7_0fb07287acdc.png"</a></td>

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

  • Error Line 753, Column 147: required attribute "alt" not specified
    …/files/image/thumbs/logo_png_4cbb869e_4590_4b15_abc7_0fb07287acdc.png"</a></td>

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

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

  • Error Line 753, Column 150: end tag for "img" omitted, but OMITTAG NO was specified
    …/files/image/thumbs/logo_png_4cbb869e_4590_4b15_abc7_0fb07287acdc.png"</a></td>

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

  • Info Line 753, Column 41: start tag was here
    …		<td><a href="/league/clubs/view/27"><img class="thumb" src="/app/webroot/fil…
  • Error Line 766, Column 10: ID "classement" already defined
    <div id="classement" class="hide_me main_box">

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

  • Info Line 566, Column 10: ID "classement" first defined here
    <div id="classement" class="hide_me main_box">
  • Error Line 914, Column 8: end tag for "p" omitted, but OMITTAG NO was specified
    		</div>

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

  • Info Line 912, Column 33: start tag was here
    		<div class="hide_me main_box"><p>
  • Error Line 921, Column 147: required attribute "alt" not specified
    …yaa"><img src="/img/kalimate.jpg" width="218" height="100"></a></div>    </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 921, Column 151: end tag for "img" omitted, but OMITTAG NO was specified
    …yaa"><img src="/img/kalimate.jpg" width="218" height="100"></a></div>    </div>

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

  • Info Line 921, Column 94: start tag was here
    …ref="/nodes/term/slug:kalimat-achyaa"><img src="/img/kalimate.jpg" width="218"…
  • Error Line 941, Column 125: required attribute "alt" not specified
    …lug:lion-dor"><img src="/img/asaad.jpg" width="288" height="190"></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>.

  • Error Line 941, Column 129: end tag for "img" omitted, but OMITTAG NO was specified
    …lug:lion-dor"><img src="/img/asaad.jpg" width="288" height="190"></a>    </div>

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

  • Info Line 941, Column 75: start tag was here
    …/nodes/view/type:pages/slug:lion-dor"><img src="/img/asaad.jpg" width="288" he…
  • Error Line 950, Column 66: end tag for element "a" which is not open
    <li id="milan"><a href="/nodes/term/slug:acmilan">أس ميلان</a></a></li>

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

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

  • Error Line 966, Column 14: ID "flashContent" already defined
    				<div id="flashContent">

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

  • Info Line 209, Column 10: ID "flashContent" first defined here
    <div id="flashContent">
  • Warning Line 967, Column 106: reference not terminated by REFC delimiter
    …idth="290" height="200" id="Cote&sport - MOUNTAKHAB - 400 X 150" align="middle…

    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 967, Column 106: reference to external entity in attribute value
    …idth="290" height="200" id="Cote&sport - MOUNTAKHAB - 400 X 150" align="middle…

    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 967, Column 106: reference to entity "sport" for which no system identifier could be generated
    …idth="290" height="200" id="Cote&sport - MOUNTAKHAB - 400 X 150" align="middle…

    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 211, Column 96: entity was defined here
    …000" width="200" height="300" id="Cote&sport - PROGRAMME - 200 X 300" align="m…
  • Error Line 967, Column 106: value of attribute "id" must be a single token
    …idth="290" height="200" id="Cote&sport - MOUNTAKHAB - 400 X 150" align="middle…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 967, Column 107: value of attribute "id" invalid: "-" cannot start a name
    …dth="290" height="200" id="Cote&sport - MOUNTAKHAB - 400 X 150" align="middle"…

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

  • Error Line 967, Column 120: value of attribute "id" invalid: "-" cannot start a name
    …dth="290" height="200" id="Cote&sport - MOUNTAKHAB - 400 X 150" align="middle">

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

  • Error Line 967, Column 122: value of attribute "id" invalid: "4" cannot start a name
    …dth="290" height="200" id="Cote&sport - MOUNTAKHAB - 400 X 150" align="middle">

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

  • Error Line 967, Column 128: value of attribute "id" invalid: "1" cannot start a name
    …dth="290" height="200" id="Cote&sport - MOUNTAKHAB - 400 X 150" align="middle">

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

  • Error Line 1001, Column 72: required attribute "type" not specified
    …div>			<script src="http://connect.facebook.net/ar_AR/all.js#xfbml=1"></script>

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

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

  • Error Line 1002, Column 18: there is no attribute "href"
    			<fb:like href="http://www.facebook.com/Almountakhabe" width="290"></fb:like>

    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 1002, Column 64: there is no attribute "width"
    			<fb:like href="http://www.facebook.com/Almountakhabe" width="290"></fb:like>

    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 1002, Column 69: element "fb:like" undefined
    			<fb:like href="http://www.facebook.com/Almountakhabe" width="290"></fb:like>

    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 1023, Column 11: element "center" undefined
    			<center> 

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

Visitor Analysis

Daily Visitor
  • 5.600 visits