Sadece Özel Haber, odatv, video, siyaset,politika,medya,politika haberleri,magazin,spor,gündem,tv ...

odatv.com
  • Domain Name
    odatv.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #14056
  • Page Size
    67.5 KB
  • Ip Address
    89.106.23.235
  • Heading
    H1: 0, H2: 7, H3: 0, H4: 14, H5: 0, H6: 0
  • Images
    23 GIF, 87 JPG, 16 PNG

Website Meta Analysis

  • Title
    Odatv.com Sadece Özel Haber, siyaset analiz ekonomi medya magazin kültür sanat video haber sitesi ODA TV
  • Meta Keyword
    haber,özel haber,odatv,video,gazete,istanbul,siyaset,politika,medya,politika haberleri,magazin,spor,gündem
  • Meta Description
    Sadece Özel Haber, odatv, video, siyaset,politika,medya,politika haberleri,magazin,spor,gündem,tv

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    89.106.23.235
  • Domain Age
    5 Years, 11 Months, 20 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 24 Feb 2013 06:10:29 GMT
  • server: Apache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • x-powered-by: PleskLin
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registration Service Provided By: WWW.ISIMTESCIL.NET
Contact: +90.2163299393

Domain Name: ODATV.COM

Registrant:
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

Creation Date: 07-Mar-2007
Expiration Date: 07-Mar-2013

Domain servers in listed order:
ns1.odatv.net
ns.odatv.net


Administrative Contact:
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:
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:
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

Status:LOCKED
Note: This Domain Name is currently Locked. In this status the domain
name cannot be transferred, hijacked, or modified. The Owner of this
domain name can easily change this status from their control panel.
This feature is provided as a security measure against fraudulent domain name hijacking.

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 FBS Inc..
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
ns.odatv.net
ns1.odatv.net


DNS Records

Answer records
odatv.com MX
preference: 10
exchange: mail.odatv.com
1800s
odatv.com TXT v=spf1 +a +mx -all 1800s
odatv.com A 89.106.23.235 1800s
odatv.com SOA
server: ns.odatv.com
email: atalikmurat@gmail.com
serial: 2012101728
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
1800s
odatv.com NS  ns.odatv.com 1800s

Authority records

Additional records
mail.odatv.com A 89.106.23.227 1800s
ns.odatv.com A 89.106.23.235 1800s

IP 89.106.23.235 Analysis

  • Country Code
    TR
  • Country Code3
    TUR
  • Country Name
    Turkey
  • City
    EU
  • Continent Code
    39° North
  • Latitude
    35.
  • Longitude
  • No whois ip data for 89.106.23.235

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 282 Errors
  • 35 Warnings
Ratio Text/Html
  • 0.7241034847190653
Message Error
  • Error Line 6, Column 45: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="robots" content="FOLLOW, INDEX"> 

    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 6, Column 1: start tag was here
    <meta name="robots" content="FOLLOW, INDEX"> 
  • Error Line 7, Column 41: there is no attribute "CONTENT"
    <meta http-equiv="Content-Type" CONTENT="text/html; charset=utf-8">

    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 7, Column 67: required attribute "content" not specified
    <meta http-equiv="Content-Type" CONTENT="text/html; charset=utf-8">

    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 7, Column 68: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Type" CONTENT="text/html; charset=utf-8">

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

  • Info Line 7, Column 1: start tag was here
    <meta http-equiv="Content-Type" CONTENT="text/html; charset=utf-8">
  • Error Line 12, Column 67: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="shortcut icon" type="image/x-icon" href="/favicon.ico">

    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 12, Column 1: start tag was here
    <link rel="shortcut icon" type="image/x-icon" href="/favicon.ico">
  • Error Line 16, Column 56: end tag for "meta" omitted, but OMITTAG NO was specified
     	<meta http-equiv="X-UA-Compatible" content="IE=edge">

    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 16, Column 3: start tag was here
     	<meta http-equiv="X-UA-Compatible" content="IE=edge">
  • Error Line 20, Column 62: end tag for "link" omitted, but OMITTAG NO was specified
        <link rel="apple-touch-icon" href="apple-touch-icon.png">

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

  • Info Line 20, Column 5: start tag was here
        <link rel="apple-touch-icon" href="apple-touch-icon.png">
  • Error Line 21, Column 40: there is no attribute "sizes"
    …   <link rel="apple-touch-icon" sizes="72x72" href="apple-touch-icon-72x72.png…

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

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

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

  • Error Line 21, Column 82: end tag for "link" omitted, but OMITTAG NO was specified
    …  <link rel="apple-touch-icon" sizes="72x72" href="apple-touch-icon-72x72.png">

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

  • Info Line 21, Column 5: start tag was here
        <link rel="apple-touch-icon" sizes="72x72" href="apple-touch-icon-72x72.png…
  • Error Line 22, Column 86: end tag for "link" omitted, but OMITTAG NO was specified
    …ink rel="apple-touch-icon" sizes="114x114" href="apple-touch-icon-114x114.png">

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

  • Info Line 22, Column 5: start tag was here
        <link rel="apple-touch-icon" sizes="114x114" href="apple-touch-icon-114x114…
  • Warning Line 52, Column 110: cannot generate system identifier for general entity "ciid"
    ….ashx?tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></…

    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 52, Column 110: general entity "ciid" not defined and no default entity
    ….ashx?tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></…

    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 52, Column 114: reference not terminated by REFC delimiter
    …x?tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"s…

    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 52, Column 114: reference to external entity in attribute value
    …x?tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"s…

    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 52, Column 114: reference to entity "ciid" for which no system identifier could be generated
    …x?tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"s…

    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 52, Column 109: entity was defined here
    …d.ashx?tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'><…
  • Warning Line 52, Column 116: cannot generate system identifier for general entity "rnd"
    …tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"scr…

    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 52, Column 116: general entity "rnd" not defined and no default entity
    …tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"scr…

    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 52, Column 119: reference not terminated by REFC delimiter
    …t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"script…

    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 52, Column 119: reference to external entity in attribute value
    …t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"script…

    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 52, Column 119: reference to entity "rnd" for which no system identifier could be generated
    …t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"script…

    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 52, Column 115: entity was defined here
    …?tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"sc…
  • Error Line 52, Column 147: required attribute "type" not specified
    …datv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"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 52, Column 147: document type does not allow element "script" here
    …datv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"script>");

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

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

  • Warning Line 52, Column 148: character "<" is the first character of a delimiter but occurred as data
    …datv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"script>");

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 57, Column 22: document type does not allow element "div" here
    <div class="headerv2">

    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 58, Column 129: there is no attribute "border"
    …limages/logo.png" alt="ODA TV" width="340" height="146" border="0" /></a></div>

    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 68, Column 28: there is no attribute "name"
                   	<form name="araform" id="araform" action="ara.php" method="get">

    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 74, Column 24: there is no attribute "language"
    						<SCRIPT language="JavaScript">

    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 74, Column 36: element "SCRIPT" undefined
    						<SCRIPT language="JavaScript">

    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 84, Column 67: there is no attribute "target"
    …ref="http://twitter.com/odatv" target="_blank"><img src="tplimages/twitter.png…

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

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

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

  • Error Line 89, Column 37: end tag for "br" omitted, but OMITTAG NO was specified
            <br class="clearfloat"></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 89, Column 9: start tag was here
            <br class="clearfloat"></div>
  • Error Line 101, Column 25: there is no attribute "align"
    			<div id="menu" align="center">

    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 107, Column 36: ID "nav-siyaset" already defined
    						<li class="no-border"><a id="nav-siyaset" class="nav-media no-border " hr…

    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 106, Column 36: ID "nav-siyaset" first defined here
    						<li class="no-border"><a id="nav-siyaset" class="nav-media no-border " hr…
  • Error Line 109, Column 36: ID "nav-siyaset" already defined
    						<li class="no-border"><a id="nav-siyaset"  class="nav-media no-border " h…

    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 106, Column 36: ID "nav-siyaset" first defined here
    						<li class="no-border"><a id="nav-siyaset" class="nav-media no-border " hr…
  • Error Line 111, Column 36: ID "nav-ekonomi" already defined
    						<li class="no-border"><a id="nav-ekonomi"  class="nav-media no-border " h…

    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 108, Column 36: ID "nav-ekonomi" first defined here
    						<li class="no-border"><a id="nav-ekonomi" class="nav-media no-border "  h…
  • Error Line 113, Column 36: ID "nav-siyaset" already defined
    						<li class="no-border"><a id="nav-siyaset"  class="nav-media no-border " h…

    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 106, Column 36: ID "nav-siyaset" first defined here
    						<li class="no-border"><a id="nav-siyaset" class="nav-media no-border " hr…
  • Error Line 114, Column 36: ID "nav-siyaset" already defined
    						<li class="no-border"><a id="nav-siyaset"  class="nav-media no-border " h…

    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 106, Column 36: ID "nav-siyaset" first defined here
    						<li class="no-border"><a id="nav-siyaset" class="nav-media no-border " hr…
  • Error Line 116, Column 36: ID "nav-spor" already defined
    						<li class="no-border"><a id="nav-spor"  class="nav-media no-border " href…

    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 110, Column 36: ID "nav-spor" first defined here
    						<li class="no-border"><a id="nav-spor"  class="nav-media no-border " href…
  • Error Line 124, Column 133: document type does not allow element "div" here
    …;padding-bottom:10px;padding-top:5px;"><center> <a target="_blank" href="http:…

    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 124, Column 141: element "center" undefined
    …-bottom:10px;padding-top:5px;"><center> <a target="_blank" href="http://www.ba…

    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 124, Column 285: end tag for "img" omitted, but OMITTAG NO was specified
    …" border="0" src="/staticimages/728x90_odatv_5.gif" alt=""></a> </center></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 124, Column 196: start tag was here
    …nk" href="http://www.bagimsiz.com.tr"><img width="728" height="90" border="0" …
  • Error Line 125, Column 32: document type does not allow element "div" here
    	<div class="column12container">

    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 176, Column 182: required attribute "alt" not specified
    …erStart(1)" src="tplimages/c1/1.gif" /></a><a href="n.php?n=bu-sozlerin-sahini…

    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 176, Column 364: required attribute "alt" not specified
    …erStart(2)" src="tplimages/c1/2.gif" /></a><a href="n.php?n=abd-istedi-turkiye…

    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 176, Column 542: required attribute "alt" not specified
    …erStart(3)" src="tplimages/c1/3.gif" /></a><a href="n.php?n=akp-ve-guleni-dest…

    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 176, Column 722: required attribute "alt" not specified
    …erStart(4)" src="tplimages/c1/4.gif" /></a><a href="n.php?n=kurdistani-turkiye…

    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 176, Column 893: required attribute "alt" not specified
    …erStart(5)" src="tplimages/c1/5.gif" /></a><a href="n.php?n=buyuk-bir-skandal-…

    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 176, Column 1086: required attribute "alt" not specified
    …erStart(6)" src="tplimages/c1/6.gif" /></a><a href="n.php?n=basbakan-erdogan-t…

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

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

  • Error Line 176, Column 1266: required attribute "alt" not specified
    …erStart(7)" src="tplimages/c1/7.gif" /></a><a href="n.php?n=kalici-isitme-kayb…

    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 176, Column 1440: required attribute "alt" not specified
    …erStart(8)" src="tplimages/c1/8.gif" /></a><a href="n.php?n=odatv-okuyuculari-…

    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 176, Column 1629: required attribute "alt" not specified
    …erStart(9)" src="tplimages/c1/9.gif" /></a><a href="n.php?n=imrali-muzakereler…

    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 176, Column 1814: required attribute "alt" not specified
    …sel(10)" onmouseout="timerStart(10)" src="tplimages/c1/10.gif" /></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 178, Column 120: end tag for element "A" which is not open
    …es/c1/tummanset.gif" width="84" height="32" border="0" alt="Tüm Manşetler"></A>

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

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

  • Error Line 178, Column 120: end tag for "img" omitted, but OMITTAG NO was specified
    …es/c1/tummanset.gif" width="84" height="32" border="0" alt="Tüm Manşetler"></A>

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

  • Info Line 178, Column 25: start tag was here
    					<a href="tops.php"><img src="tplimages/c1/tummanset.gif" width="84" height…
  • Error Line 179, Column 10: end tag for "a" 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 178, Column 6: start tag was here
    					<a href="tops.php"><img src="tplimages/c1/tummanset.gif" width="84" height…
  • Warning Line 194, Column 41: character "&" is the first character of a delimiter but occurred as data
    …			with (document) if (getElementById && ((obj=getElementById(changeID))!=null…

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 201, Column 34: character ";" not allowed in attribute specification list
    					for(i=1;i<maxHeaderlineCount;i++) {
  • Error Line 201, Column 34: element "maxHeaderlineCount" undefined
    					for(i=1;i<maxHeaderlineCount;i++) {

    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 219, Column 35: character ";" not allowed in attribute specification list
    						for(i=1;i<maxHeaderlineCount;i++){
  • Error Line 219, Column 35: element "maxHeaderlineCount" undefined
    						for(i=1;i<maxHeaderlineCount;i++){

    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 241, Column 12: end tag for "maxHeaderlineCount" omitted, but OMITTAG NO was specified
    			</script>

    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 219, Column 16: start tag was here
    						for(i=1;i<maxHeaderlineCount;i++){
  • Error Line 241, Column 12: end tag for "maxHeaderlineCount" omitted, but OMITTAG NO was specified
    			</script>

    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 201, Column 15: start tag was here
    					for(i=1;i<maxHeaderlineCount;i++) {
  • Error Line 276, Column 183: required attribute "alt" not specified
    …rStart2(1)" src="tplimages/c2/1.gif" /></a><a href="n.php?n=devran-donsun-sari…

    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 276, Column 359: required attribute "alt" not specified
    …rStart2(2)" src="tplimages/c2/2.gif" /></a><a href="n.php?n=oso-etilere-mi-yer…

    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 276, Column 525: required attribute "alt" not specified
    …rStart2(3)" src="tplimages/c2/3.gif" /></a><a href="n.php?n=hazreti-muhammed-1…

    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 276, Column 713: required attribute "alt" not specified
    …rStart2(4)" src="tplimages/c2/4.gif" /></a><a href="n.php?n=gangnam-stylein-tu…

    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 276, Column 897: required attribute "alt" not specified
    …usel2(5)" onmouseout="timerStart2(5)" src="tplimages/c2/5.gif" /></a>				</div>

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

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

  • Warning Line 291, Column 41: character "&" is the first character of a delimiter but occurred as data
    …			with (document) if (getElementById && ((obj=getElementById(changeID))!=null…

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 298, Column 35: character ";" not allowed in attribute specification list
    					for(i=1;i<maxHeaderlineCount2;i++) {
  • Error Line 298, Column 35: element "maxHeaderlineCount2" undefined
    					for(i=1;i<maxHeaderlineCount2;i++) {

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 316, Column 36: character ";" not allowed in attribute specification list
    						for(i=1;i<maxHeaderlineCount2;i++){
  • Error Line 316, Column 36: element "maxHeaderlineCount2" undefined
    						for(i=1;i<maxHeaderlineCount2;i++){

    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 338, Column 12: end tag for "maxHeaderlineCount2" omitted, but OMITTAG NO was specified
    			</script>

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

  • Info Line 316, Column 16: start tag was here
    						for(i=1;i<maxHeaderlineCount2;i++){
  • Error Line 338, Column 12: end tag for "maxHeaderlineCount2" omitted, but OMITTAG NO was specified
    			</script>

    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 298, Column 15: start tag was here
    					for(i=1;i<maxHeaderlineCount2;i++) {
  • Error Line 344, Column 190: required attribute "alt" not specified
    …2/" target="_blank"><img src="reklam/fitdesk.jpg" width="300" height="120"></a>

    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 344, Column 194: end tag for "img" omitted, but OMITTAG NO was specified
    …2/" target="_blank"><img src="reklam/fitdesk.jpg" width="300" height="120"></a>

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

  • Info Line 344, Column 136: start tag was here
    …55070/bannerType/22/" target="_blank"><img src="reklam/fitdesk.jpg" width="300…
  • Error Line 346, Column 152: required attribute "alt" not specified
    …1944/plan/338943/banner/352202/bannerType/22/" border='0' width="0" height="0">

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

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

  • Error Line 346, Column 153: end tag for "img" omitted, but OMITTAG NO was specified
    …1944/plan/338943/banner/352202/bannerType/22/" border='0' width="0" height="0">

    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 346, Column 5: start tag was here
    				<img src="http://delivery.reklamz.com/please/track/adClick/campaign/81944/p…
  • Error Line 354, Column 32: document type does not allow element "br" here
    	</div><br class="clearfloat" />

    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 356, Column 31: document type does not allow element "div" here
    	<div style="margin-left:25px"><div style="background-color: rgb(255,255,255); …

    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 356, Column 172: element "center" undefined
    …ght: 90px; margin-left: -16px"><center> <embed type="application/x-shockwave-f…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 356, Column 186: there is no attribute "type"
    …gin-left: -16px"><center> <embed type="application/x-shockwave-flash" pluginsp…

    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 356, Column 230: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" 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 356, Column 280: there is no attribute "src"
    …macromedia.com/go/getflashplayer" src="/staticimages/kirmizi-kedi27.swf" width…

    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 356, Column 321: there is no attribute "width"
    …taticimages/kirmizi-kedi27.swf" width="728" height="90" play="true" loop="true…

    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 356, Column 334: there is no attribute "height"
    …irmizi-kedi27.swf" width="728" height="90" play="true" loop="true" menu="true"…

    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 356, Column 344: there is no attribute "play"
    …i27.swf" width="728" height="90" play="true" loop="true" menu="true"></embed> …

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

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

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

  • Error Line 356, Column 356: there is no attribute "loop"
    …th="728" height="90" play="true" loop="true" menu="true"></embed> </center></d…

    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 356, Column 368: there is no attribute "menu"
    … height="90" play="true" loop="true" menu="true"></embed> </center></div></div>

    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 356, Column 374: element "embed" undefined
    … height="90" play="true" loop="true" menu="true"></embed> </center></div></div>

    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 358, Column 22: document type does not allow element "div" here
    	<div class="column1">

    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 364, Column 6: end tag for "img" omitted, but OMITTAG NO was specified
    "></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 362, Column 121: start tag was here
    …e-gelmiyor-diye-kestiler--2302131200"><img  width="128" src="images/2013_02/20…
  • Error Line 365, Column 123: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …se-gelmiyor-diye-kestiler--2302131200"><h2>PKK'nın kaçırdığı öğretmenin maaşını

    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 370, Column 262: end tag for "img" omitted, but OMITTAG NO was specified
    …n-2302131200_l.jpg" alt="Tüm suçlamaları derhal ve koşulsuz düşürün"></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 370, Column 100: start tag was here
    …erhal-ve-kosulsuz-dusurun-2302131200"><img  width="128" src="images/2013_02/20…
  • Error Line 371, Column 102: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …al-ve-kosulsuz-dusurun-2302131200"><h2>Tüm suçlamaları derhal ve koşulsuz düşü…

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

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

  • Error Line 374, Column 286: end tag for "img" omitted, but OMITTAG NO was specified
    …1200_l.jpg" alt="Benim duamı istemez ama Başbakan için dua edeceğim"></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 374, Column 108: start tag was here
    …asbakan-icin-dua-edecegim-2302131200"><img  width="128" src="images/2013_02/20…
  • Error Line 375, Column 110: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …akan-icin-dua-edecegim-2302131200"><h2>Benim duamı istemez ama Başbakan için d…

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

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

  • Error Line 378, Column 228: end tag for "img" omitted, but OMITTAG NO was specified
    …-davutogluna-2302131200_l.jpg" alt="İkinci cevap Ahmet Davutoğlu'na"></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 378, Column 89: start tag was here
    …i-cevap-ahmet-davutogluna-2302131200"><img  width="108" src="images/2013_02/20…
  • Error Line 379, Column 91: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …evap-ahmet-davutogluna-2302131200"><h4>İkinci cevap Ahmet Davutoğlu'na</h4></a…

    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 384, Column 240: end tag for "img" omitted, but OMITTAG NO was specified
    …li-haber-2302131200_l.jpg" alt="Almanya'daki Türklere müjdeli haber"></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 384, Column 93: start tag was here
    …ki-turklere-mujdeli-haber-2302131200"><img  width="108" src="images/2013_02/20…
  • Error Line 385, Column 95: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …turklere-mujdeli-haber-2302131200"><h4>Almanya'daki Türklere müjdeli haber</h4…

    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 390, Column 210: end tag for "img" omitted, but OMITTAG NO was specified
    …anda-darbeci-cikti-2302131200_l.jpg" alt="Kruvasan da darbeci çıktı"></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 390, Column 83: start tag was here
    …=kruvasanda-darbeci-cikti-2302131200"><img  width="108" src="images/2013_02/20…
  • Error Line 391, Column 85: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …p?n=kruvasanda-darbeci-cikti-2302131200"><h4>Kruvasan da darbeci çıktı</h4></a>

    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 398, Column 6: end tag for "img" omitted, but OMITTAG NO was specified
    "></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 396, Column 102: start tag was here
    …runun-cevabini-ogrenecek--2302131200"><img  width="108" src="images/2013_02/20…
  • Error Line 399, Column 104: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …php?n=mehmet-yilmaz-o-sorunun-cevabini-ogrenecek--2302131200"><h4>Mehmet Yılmaz

    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 406, Column 249: end tag for "img" omitted, but OMITTAG NO was specified
    …ir-mi-2302131200_l.jpg" alt="Türkiye'deki okullarda bu öğretilir mi"></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 406, Column 96: start tag was here
    …okullarda-bu-ogretilir-mi-2302131200"><img  width="108" src="images/2013_02/20…
  • Error Line 407, Column 98: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …llarda-bu-ogretilir-mi-2302131200"><h4>Türkiye'deki okullarda bu öğretilir mi<…

    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 415, Column 6: end tag for "img" omitted, but OMITTAG NO was specified
    "></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 412, Column 142: start tag was here
    …stirme-fantezisi-basladi--2302131200"><img  width="108" src="images/2013_02/20…
  • Error Line 416, Column 144: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …es-degistirme-fantezisi-basladi--2302131200"><h4>Harbiye'de bir daire kiralandı

    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 424, Column 216: end tag for "img" omitted, but OMITTAG NO was specified
    …yardimlari-kesin-2302131200_l.jpg" alt="Türkiye'ye yardımları kesin"></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 424, Column 85: start tag was here
    …urkiyeye-yardimlari-kesin-2302131200"><img  width="108" src="images/2013_02/20…
  • Error Line 425, Column 87: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …turkiyeye-yardimlari-kesin-2302131200"><h4>Türkiye'ye yardımları kesin</h4></a>

    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 433, Column 22: document type does not allow element "div" here
    	<div class="column2">

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

  • Warning Line 466, Column 112: reference not terminated by REFC delimiter
    …x?tt=t_odatv_site_genel_300x250_bt&rnd="+Math.random()%99999999+"'></"+"script…

    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 466, Column 112: reference to external entity in attribute value
    …x?tt=t_odatv_site_genel_300x250_bt&rnd="+Math.random()%99999999+"'></"+"script…

    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 466, Column 112: reference to entity "rnd" for which no system identifier could be generated
    …x?tt=t_odatv_site_genel_300x250_bt&rnd="+Math.random()%99999999+"'></"+"script…

    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 52, Column 115: entity was defined here
    …?tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"sc…
  • Error Line 466, Column 140: required attribute "type" not specified
    …t=t_odatv_site_genel_300x250_bt&rnd="+Math.random()%99999999+"'></"+"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 466, Column 140: document type does not allow element "script" here
    …t=t_odatv_site_genel_300x250_bt&rnd="+Math.random()%99999999+"'></"+"script>");

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

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

  • Warning Line 466, Column 141: character "<" is the first character of a delimiter but occurred as data
    …t=t_odatv_site_genel_300x250_bt&rnd="+Math.random()%99999999+"'></"+"script>");

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 468, Column 7: end tag for "script" omitted, but OMITTAG NO was specified
    	</div><!--end column2-->

    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 465, Column 7: start tag was here
    		    <script type="text/javascript">
  • Error Line 469, Column 7: end tag for element "div" which is not open
    	</div><!--end column12container-->

    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 473, Column 26: document type does not allow element "br" here
    	<br class="clearfloat" /><div class="bosluk2"></div>

    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 473, Column 47: document type does not allow element "div" here
    	<br class="clearfloat" /><div class="bosluk2"></div>

    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 477, Column 91: document type does not allow element "div" here
    …nd-color: rgb(255,255,255); width: 775px; height: 90px; margin: 10px;"><center>

    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 477, Column 99: element "center" undefined
    …nd-color: rgb(255,255,255); width: 775px; height: 90px; margin: 10px;"><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 479, Column 112: reference not terminated by REFC delimiter
    …x?tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"s…

    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 479, Column 112: reference to external entity in attribute value
    …x?tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"s…

    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 479, Column 112: reference to entity "ciid" for which no system identifier could be generated
    …x?tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"s…

    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 52, Column 109: entity was defined here
    …d.ashx?tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'><…
  • Warning Line 479, Column 117: reference not terminated by REFC delimiter
    …t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"script…

    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 479, Column 117: reference to external entity in attribute value
    …t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"script…

    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 479, Column 117: reference to entity "rnd" for which no system identifier could be generated
    …t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"script…

    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 52, Column 115: entity was defined here
    …?tt=t_odatv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"sc…
  • Error Line 479, Column 145: required attribute "type" not specified
    …datv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"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 479, Column 145: document type does not allow element "script" here
    …datv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"script>");

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

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

  • Warning Line 479, Column 146: character "<" is the first character of a delimiter but occurred as data
    …datv_site_genel_728x90_rp&ciid=&rnd="+Math.random()%99999999+"'></"+"script>");

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 483, Column 25: document type does not allow element "style" here
    		<style type="text/css">

    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 550, Column 28: document type does not allow element "div" here
    <div class="videohabercont">

    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 551, Column 32: there is no attribute "HREF"
    	<div class="vidtitco"><A HREF="vid.php"><img src="tplimages/videohabertit.png"…

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

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

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

  • Error Line 551, Column 41: element "A" undefined
    …div class="vidtitco"><A HREF="vid.php"><img src="tplimages/videohabertit.png" …

    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 558, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    				<div class="vidimgcon">

    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 560, Column 74: required attribute "alt" not specified
    						<img src="/tplimages/icons/play_large.png" width="40" height="40" />

    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 563, Column 94: required attribute "alt" not specified
    …http://www.odatv.com/images/2013_02/2013_02_23/vimg_8b803_v.jpg" width="136" />

    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 571, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    				<div class="vidimgcon">

    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 573, Column 74: required attribute "alt" not specified
    						<img src="/tplimages/icons/play_large.png" width="40" height="40" />

    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 576, Column 94: required attribute "alt" not specified
    …http://www.odatv.com/images/2013_02/2013_02_23/vimg_8b802_v.jpg" width="136" />

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

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

  • Error Line 584, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    				<div class="vidimgcon">

    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 586, Column 74: required attribute "alt" not specified
    						<img src="/tplimages/icons/play_large.png" width="40" height="40" />

    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 589, Column 94: required attribute "alt" not specified
    …http://www.odatv.com/images/2013_02/2013_02_23/vimg_8b801_v.jpg" width="136" />

    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 597, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    				<div class="vidimgcon">

    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 599, Column 74: required attribute "alt" not specified
    						<img src="/tplimages/icons/play_large.png" width="40" height="40" />

    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 602, Column 94: required attribute "alt" not specified
    …http://www.odatv.com/images/2013_02/2013_02_23/vimg_8b800_v.jpg" width="136" />

    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 610, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    				<div class="vidimgcon">

    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 612, Column 74: required attribute "alt" not specified
    						<img src="/tplimages/icons/play_large.png" width="40" height="40" />

    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 615, Column 94: required attribute "alt" not specified
    …http://www.odatv.com/images/2013_02/2013_02_23/vimg_8b7hh_v.jpg" width="136" />

    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 623, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    				<div class="vidimgcon">

    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 625, Column 74: required attribute "alt" not specified
    						<img src="/tplimages/icons/play_large.png" width="40" height="40" />

    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 628, Column 94: required attribute "alt" not specified
    …http://www.odatv.com/images/2013_02/2013_02_23/vimg_8b7hg_v.jpg" width="136" />

    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 636, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    				<div class="vidimgcon">

    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 638, Column 74: required attribute "alt" not specified
    						<img src="/tplimages/icons/play_large.png" width="40" height="40" />

    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 641, Column 94: required attribute "alt" not specified
    …http://www.odatv.com/images/2013_02/2013_02_23/vimg_8b7hf_v.jpg" width="136" />

    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 649, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    				<div class="vidimgcon">

    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 651, Column 74: required attribute "alt" not specified
    						<img src="/tplimages/icons/play_large.png" width="40" height="40" />

    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 654, Column 94: required attribute "alt" not specified
    …http://www.odatv.com/images/2013_02/2013_02_23/vimg_8b7he_v.jpg" width="136" />

    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 662, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    				<div class="vidimgcon">

    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 664, Column 74: required attribute "alt" not specified
    						<img src="/tplimages/icons/play_large.png" width="40" height="40" />

    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 667, Column 94: required attribute "alt" not specified
    …http://www.odatv.com/images/2013_02/2013_02_23/vimg_8b7hd_v.jpg" width="136" />

    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 675, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    				<div class="vidimgcon">

    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 677, Column 74: required attribute "alt" not specified
    						<img src="/tplimages/icons/play_large.png" width="40" height="40" />

    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 680, Column 94: required attribute "alt" not specified
    …http://www.odatv.com/images/2013_02/2013_02_23/vimg_8b7hc_v.jpg" width="136" />

    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 688, Column 18: document type does not allow element "div" here
    <div class="yuks"></div>		

    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 690, Column 91: document type does not allow element "div" here
    …h: 775px; height: 90px; margin: 10px;"><center><script type='text/javascript' …

    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 690, Column 99: element "center" undefined
    …; height: 90px; margin: 10px;"><center><script type='text/javascript' charset=…

    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 698, Column 11: end tag for element "center" which is not open
    	 </center></div><!--END REKS-->

    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 698, Column 17: end tag for element "div" which is not open
    	 </center></div><!--END REKS-->

    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 701, Column 22: document type does not allow element "div" here
    	<div class="bosluk2"></div>

    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 703, Column 26: document type does not allow element "br" here
    	<br class="clearfloat" />

    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 705, Column 32: document type does not allow element "div" here
    	<div class="column12container">

    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 717, Column 292: end tag for "img" omitted, but OMITTAG NO was specified
    …00_l.jpg" alt="BDP milletvekili şikayet etti gazeteci işten kovuldu"></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 717, Column 110: start tag was here
    …ti-gazeteci-isten-kovuldu-2202131200"><img  width="128" src="images/2013_02/20…
  • Error Line 718, Column 112: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …gazeteci-isten-kovuldu-2202131200"><h2>BDP milletvekili şikayet etti gazeteci …

    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 721, Column 305: end tag for "img" omitted, but OMITTAG NO was specified
    …jpg" alt="Hükümet Yargıtay ve Danıştay'ı Cemaat yüzünden kaldırıyor"></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 721, Column 114: start tag was here
    …emaat-yuzunden-kaldiriyor-2302131200"><img  width="128" src="images/2013_02/20…
  • Error Line 722, Column 116: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …at-yuzunden-kaldiriyor-2302131200"><h2>Hükümet Yargıtay ve Danıştay'ı Cemaat y…

    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 725, Column 262: end tag for "img" omitted, but OMITTAG NO was specified
    …i-2302131200_l.jpg" alt="Fethullah Gülen benimle helalleşmek istedi"></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 725, Column 100: start tag was here
    …enimle-helallesmek-istedi-2302131200"><img  width="128" src="images/2013_02/20…
  • Error Line 726, Column 102: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …mle-helallesmek-istedi-2302131200"><h2>Fethullah Gülen benimle helalleşmek ist…

    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 729, Column 326: end tag for "img" omitted, but OMITTAG NO was specified
    …lt="Balyoz davası gerekçeli kararında olmayan konuşmalar mı yazıldı"></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 729, Column 122: start tag was here
    …yan-konusmalar-mi-yazildi-2302131200"><img  width="108" src="images/2013_02/20…
  • Error Line 730, Column 124: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …-konusmalar-mi-yazildi-2302131200"><h4>Balyoz davası gerekçeli kararında olmay…

    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 735, Column 206: end tag for "img" omitted, but OMITTAG NO was specified
    …-artik-dedirten-saka-2302131200_l.jpg" alt="Yok artık dedirten şaka"></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 735, Column 82: start tag was here
    …n=yok-artik-dedirten-saka-2302131200"><img  width="108" src="images/2013_02/20…
  • Error Line 736, Column 84: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    ….php?n=yok-artik-dedirten-saka-2302131200"><h4>Yok artık dedirten şaka</h4></a>

    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 741, Column 254: end tag for "img" omitted, but OMITTAG NO was specified
    …iski-2302131200_l.jpg" alt="İmam Hatip müfredatındaki derin çelişki"></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 741, Column 98: start tag was here
    …redatindaki-derin-celiski-2302131200"><img  width="108" src="images/2013_02/20…
  • Error Line 742, Column 100: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …atindaki-derin-celiski-2302131200"><h4>İmam Hatip müfredatındaki derin çelişki…

    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 747, Column 279: end tag for "img" omitted, but OMITTAG NO was specified
    …1200_l.jpg" alt="Vali’nin ‘ilahi projesi’nin yolu mezardan geçiyor!"></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 747, Column 105: start tag was here
    …nin-yolu-mezardan-geciyor-2302131200"><img  width="108" src="images/2013_02/20…
  • Error Line 748, Column 107: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …-yolu-mezardan-geciyor-2302131200"><h4>Vali’nin ‘ilahi projesi’nin yolu mezard…

    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 753, Column 248: end tag for "img" omitted, but OMITTAG NO was specified
    …abilir-2302131200_l.jpg" alt="Çerkesler tembelliğe alışmış olabilir"></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 753, Column 96: start tag was here
    …mbellige-alismis-olabilir-2302131200"><img  width="108" src="images/2013_02/20…
  • Error Line 754, Column 98: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …llige-alismis-olabilir-2302131200"><h4>Çerkesler tembelliğe alışmış olabilir</…

    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 759, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    …ayiz-2202131200_l.jpg" alt="&quot;Ben ve ordumuz arkanızdayız&quot;"></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 759, Column 86: start tag was here
    …n-ve-ordumuz-arkanizdayiz-2202131200"><img  width="108" src="images/2013_02/20…
  • Error Line 760, Column 88: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …e-ordumuz-arkanizdayiz-2202131200"><h4>&quot;Ben ve ordumuz arkanızdayız&quot;…

    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 765, Column 201: end tag for "img" omitted, but OMITTAG NO was specified
    …haydi-aleviler-camiye-2302131200_l.jpg" alt="Haydi Aleviler! Camiye"></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 765, Column 80: start tag was here
    …p?n=haydi-aleviler-camiye-2302131200"><img  width="108" src="images/2013_02/20…
  • Error Line 766, Column 82: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …="n.php?n=haydi-aleviler-camiye-2302131200"><h4>Haydi Aleviler! Camiye</h4></a>

    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 782, Column 21: there is no attribute "language"
    			<script language="JavaScript">

    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 782, Column 33: required attribute "type" not specified
    			<script language="JavaScript">

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

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

  • Warning Line 785, Column 15: character "<" is the first character of a delimiter but occurred as data
    				for (i=1;i<=5;i++){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 792, Column 67: required attribute "alt" not specified
    			<img src="tplimages/encokokunanlar.jpg" width="296" height="25">

    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 792, Column 68: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="tplimages/encokokunanlar.jpg" width="296" height="25">

    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 792, Column 4: start tag was here
    			<img src="tplimages/encokokunanlar.jpg" width="296" height="25">
  • Error Line 799, Column 16: there is no attribute "width"
    					<td width="30" style='vertical-align:top; background-image:url(tplimages/b…

    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 799, Column 137: required attribute "alt" not specified
    …:url(tplimages/best_bg.gif)'><img src="tplimages/best1.jpg" width="30"  /></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 803, Column 129: there is no attribute "name"
    …er:none" class="encoktitle"><img name='k1' id='k1' class="encokk" src="images/…

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

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

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

  • Error Line 803, Column 267: required attribute "alt" not specified
    …2131200_l.jpg" width="75" height="55"/></a><a href="n.php?n=zaman-ne-ictiyse-a…

    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 809, Column 137: required attribute "alt" not specified
    …:url(tplimages/best_bg.gif)'><img src="tplimages/best2.jpg" width="30"  /></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 813, Column 269: required attribute "alt" not specified
    …2131200_l.jpg" width="75" height="55"/></a><a href="n.php?n=soner-yalcin-konus…

    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 819, Column 137: required attribute "alt" not specified
    …:url(tplimages/best_bg.gif)'><img src="tplimages/best3.jpg" width="30"  /></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 823, Column 267: required attribute "alt" not specified
    …2131200_l.jpg" width="75" height="55"/></a><a href="n.php?n=onder-aytac-oyle-b…

    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 829, Column 137: required attribute "alt" not specified
    …:url(tplimages/best_bg.gif)'><img src="tplimages/best4.jpg" width="30"  /></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 833, Column 225: required attribute "alt" not specified
    …2131200_l.jpg" width="75" height="55"/></a><a href="n.php?n=cemaat-savaslari-1…

    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 839, Column 137: required attribute "alt" not specified
    …:url(tplimages/best_bg.gif)'><img src="tplimages/best5.jpg" width="30"  /></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 843, Column 359: required attribute "alt" not specified
    …2131200_l.jpg" width="75" height="55"/></a><a href="n.php?n=harbiyede-bir-dair…

    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 856, Column 201: element "embed" undefined
    …niz.swf" width="300" height="250" play="true" loop="true" menu="true"></embed>	

    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 860, Column 44: required attribute "alt" not specified
    			<img src="tplimages/commentheader.jpg" />

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

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

  • Error Line 866, Column 437: required attribute "alt" not specified
    …pları ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 866, Column 448: there is no attribute "clear"
    …pları ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

    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 868, Column 409: required attribute "alt" not specified
    … bunu ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 870, Column 417: required attribute "alt" not specified
    …a cok ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 872, Column 418: required attribute "alt" not specified
    …kimse ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 874, Column 362: required attribute "alt" not specified
    …larla ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 876, Column 403: required attribute "alt" not specified
    …i bir ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 878, Column 397: required attribute "alt" not specified
    …urken ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 880, Column 421: required attribute "alt" not specified
    …ısını ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 882, Column 336: required attribute "alt" not specified
    …SIFIR ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 884, Column 412: required attribute "alt" not specified
    …'e oy ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 886, Column 327: required attribute "alt" not specified
    …ne mi ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 888, Column 402: required attribute "alt" not specified
    …adaki ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 890, Column 421: required attribute "alt" not specified
    …melek ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 892, Column 376: required attribute "alt" not specified
    …larin ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 894, Column 361: required attribute "alt" not specified
    …m iki ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 896, Column 368: required attribute "alt" not specified
    …n bir ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 898, Column 427: required attribute "alt" not specified
    …HE HE ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 900, Column 405: required attribute "alt" not specified
    … niye ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 902, Column 392: required attribute "alt" not specified
    …unlar ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 904, Column 422: required attribute "alt" not specified
    …ldir. ...</a><br/><img src="tplimages/separator2.jpg" /><br clear="all" /></li>

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

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

  • Error Line 919, Column 67: required attribute "alt" not specified
    		<img src="tplimages/space.gif" width="20" height="12" border="0">

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

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

  • Error Line 919, Column 68: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src="tplimages/space.gif" width="20" height="12" border="0">

    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 919, Column 3: start tag was here
    		<img src="tplimages/space.gif" width="20" height="12" border="0">
  • Error Line 928, Column 13: there is no attribute "src"
    <iframe src="http://www.facebook.com/plugins/likebox.php?href=http%3A%2F%2Fwww.…

    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 928, Column 101: cannot generate system identifier for general entity "width"
    …http%3A%2F%2Fwww.facebook.com%2Fodatv&width=300&connections=18&stream=false&he…

    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 928, Column 101: general entity "width" not defined and no default entity
    …http%3A%2F%2Fwww.facebook.com%2Fodatv&width=300&connections=18&stream=false&he…

    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 928, Column 106: reference not terminated by REFC delimiter
    …3A%2F%2Fwww.facebook.com%2Fodatv&width=300&connections=18&stream=false&header=…

    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 928, Column 106: reference to external entity in attribute value
    …3A%2F%2Fwww.facebook.com%2Fodatv&width=300&connections=18&stream=false&header=…

    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 928, Column 106: reference to entity "width" for which no system identifier could be generated
    …3A%2F%2Fwww.facebook.com%2Fodatv&width=300&connections=18&stream=false&header=…

    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 928, Column 100: entity was defined here
    …=http%3A%2F%2Fwww.facebook.com%2Fodatv&width=300&connections=18&stream=false&h…
  • Warning Line 928, Column 111: cannot generate system identifier for general entity "connections"
    …%2Fwww.facebook.com%2Fodatv&width=300&connections=18&stream=false&header=false…

    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 928, Column 111: general entity "connections" not defined and no default entity
    …%2Fwww.facebook.com%2Fodatv&width=300&connections=18&stream=false&header=false…

    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 928, Column 122: reference not terminated by REFC delimiter
    …book.com%2Fodatv&width=300&connections=18&stream=false&header=false&height=322…

    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 928, Column 122: reference to external entity in attribute value
    …book.com%2Fodatv&width=300&connections=18&stream=false&header=false&height=322…

    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 928, Column 122: reference to entity "connections" for which no system identifier could be generated
    …book.com%2Fodatv&width=300&connections=18&stream=false&header=false&height=322…

    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 928, Column 110: entity was defined here
    …F%2Fwww.facebook.com%2Fodatv&width=300&connections=18&stream=false&header=fals…
  • Warning Line 928, Column 126: cannot generate system identifier for general entity "stream"
    ….com%2Fodatv&width=300&connections=18&stream=false&header=false&height=322" sc…

    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 928, Column 126: general entity "stream" not defined and no default entity
    ….com%2Fodatv&width=300&connections=18&stream=false&header=false&height=322" sc…

    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 928, Column 132: reference not terminated by REFC delimiter
    …Fodatv&width=300&connections=18&stream=false&header=false&height=322" scrollin…

    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 928, Column 132: reference to external entity in attribute value
    …Fodatv&width=300&connections=18&stream=false&header=false&height=322" scrollin…

    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 928, Column 132: reference to entity "stream" for which no system identifier could be generated
    …Fodatv&width=300&connections=18&stream=false&header=false&height=322" scrollin…

    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 928, Column 125: entity was defined here
    …k.com%2Fodatv&width=300&connections=18&stream=false&header=false&height=322" s…
  • Warning Line 928, Column 139: cannot generate system identifier for general entity "header"
    …width=300&connections=18&stream=false&header=false&height=322" scrolling="no" …

    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 928, Column 139: general entity "header" not defined and no default entity
    …width=300&connections=18&stream=false&header=false&height=322" scrolling="no" …

    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 928, Column 145: reference not terminated by REFC delimiter
    …300&connections=18&stream=false&header=false&height=322" scrolling="no" frameb…

    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 928, Column 145: reference to external entity in attribute value
    …300&connections=18&stream=false&header=false&height=322" scrolling="no" frameb…

    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 928, Column 145: reference to entity "header" for which no system identifier could be generated
    …300&connections=18&stream=false&header=false&height=322" scrolling="no" frameb…

    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 928, Column 138: entity was defined here
    …&width=300&connections=18&stream=false&header=false&height=322" scrolling="no"…
  • Warning Line 928, Column 152: cannot generate system identifier for general entity "height"
    …nections=18&stream=false&header=false&height=322" scrolling="no" frameborder="…

    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 928, Column 152: general entity "height" not defined and no default entity
    …nections=18&stream=false&header=false&height=322" scrolling="no" frameborder="…

    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 928, Column 158: reference not terminated by REFC delimiter
    …ns=18&stream=false&header=false&height=322" scrolling="no" frameborder="0" sty…

    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 928, Column 158: reference to external entity in attribute value
    …ns=18&stream=false&header=false&height=322" scrolling="no" frameborder="0" sty…

    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 928, Column 158: reference to entity "height" for which no system identifier could be generated
    …ns=18&stream=false&header=false&height=322" scrolling="no" frameborder="0" sty…

    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 928, Column 151: entity was defined here
    …nnections=18&stream=false&header=false&height=322" scrolling="no" frameborder=…
  • Error Line 928, Column 174: there is no attribute "scrolling"
    …se&header=false&height=322" scrolling="no" frameborder="0" style="border:none;…

    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 928, Column 191: there is no attribute "frameborder"
    …eight=322" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

    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 928, Column 201: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:300…

    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 928, Column 278: there is no attribute "allowTransparency"
    …overflow:hidden; width:300px; height:322px;" allowTransparency="true"></iframe>

    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 928, Column 284: element "iframe" undefined
    …overflow:hidden; width:300px; height:322px;" allowTransparency="true"></iframe>

    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 930, Column 14: there is no attribute "href"
    <g:plus href="https://plus.google.com/113417973805133804085" size="badge"></g:p…

    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 930, Column 67: there is no attribute "size"
    …lus href="https://plus.google.com/113417973805133804085" size="badge"></g:plus>

    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 930, Column 74: element "g:plus" undefined
    …lus href="https://plus.google.com/113417973805133804085" size="badge"></g:plus>

    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 940, Column 25: document type does not allow element "div" here
    	<div class="clearfloat"></div>

    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 942, Column 25: document type does not allow element "div" here
    	<div class="clearfloat"></div>

    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 943, Column 24: document type does not allow element "div" here
    		<div id="footer_head"></div>

    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 944, Column 26: document type does not allow element "br" here
    	<br class="clearfloat" />

    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 945, Column 22: document type does not allow element "div" here
    	<div id="footer_sol"><a href="index.php"><img src="/tplimages/smalllogo.jpg" a…

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

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

  • Error Line 945, Column 93: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …href="index.php"><img src="/tplimages/smalllogo.jpg" alt="" border=0></a></div>
  • Error Line 945, Column 98: end tag for "img" omitted, but OMITTAG NO was specified
    …href="index.php"><img src="/tplimages/smalllogo.jpg" alt="" border=0></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 945, Column 43: start tag was here
    …v id="footer_sol"><a href="index.php"><img src="/tplimages/smalllogo.jpg" alt=…
  • Error Line 946, Column 22: document type does not allow element "div" here
    	<div id="footer_sag">

    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 948, Column 244: end tag for "br" omitted, but OMITTAG NO was specified
    …z Haber</a> | <a class="footer" href="c.php?c=medya">Medya Haberleri</a> | <br>

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

  • Info Line 948, Column 240: start tag was here
    …z Haber</a> | <a class="footer" href="c.php?c=medya">Medya Haberleri</a> | <br>
  • Error Line 949, Column 204: end tag for "br" omitted, but OMITTAG NO was specified
    …<a class="footer" href="c.php?c=kultur-sanat">Kültür-Sanat Haberleri</a> | <br>

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

  • Info Line 949, Column 200: start tag was here
    …<a class="footer" href="c.php?c=kultur-sanat">Kültür-Sanat Haberleri</a> | <br>
  • Error Line 952, Column 225: end tag for "br" omitted, but OMITTAG NO was specified
    …lto:duyguy@odatv.com" target="_blank">duyguy@odatv.com</a>&nbsp;</b></span><br>

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

  • Info Line 952, Column 221: start tag was here
    …lto:duyguy@odatv.com" target="_blank">duyguy@odatv.com</a>&nbsp;</b></span><br>
  • Error Line 964, Column 10: there is no attribute "align"
    <p align="center"><a target="_blank" href="rss.php"><img alt="" src="http://oda…

    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 964, Column 120: end tag for "img" omitted, but OMITTAG NO was specified
    …s.php"><img alt="" src="http://odatv.com/tplimages/rss.gif" border="0"></a></p>

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

  • Info Line 964, Column 53: start tag was here
    …er"><a target="_blank" href="rss.php"><img alt="" src="http://odatv.com/tplima…
  • Error Line 966, Column 24: document type does not allow element "div" here
    	<div id="footer_ensag">

    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 971, Column 20: document type does not allow element "div" here
    	<div id="pageskin">

    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 973, Column 80: end tag for "param" omitted, but OMITTAG NO was specified
    		<param value="http://www.odatv.com/staticimages/jonesbo(1).swf" name="movie">

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

  • Info Line 973, Column 3: start tag was here
    		<param value="http://www.odatv.com/staticimages/jonesbo(1).swf" name="movie">
  • Error Line 974, Column 38: end tag for "param" omitted, but OMITTAG NO was specified
    		<param value="high" name="quality"><embed width="200" height="200" type="appl…

    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 974, Column 3: start tag was here
    		<param value="high" name="quality"><embed width="200" height="200" type="appl…
  • Error Line 974, Column 173: there is no attribute "quality"
    …omedia.com/go/getflashplayer" quality="high" src="http://www.odatv.com/statici…

    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 974, Column 234: element "embed" undefined
    …hplayer" quality="high" src="http://www.odatv.com/staticimages/jonesbo(1).swf">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 975, Column 11: 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 974, Column 38: start tag was here
    		<param value="high" name="quality"><embed width="200" height="200" type="appl…
  • Error Line 977, Column 166: end tag for "img" omitted, but OMITTAG NO was specified
    …1278478"><img alt="" src="/staticimages/siyasetin-sefaleti-banner.gif"></a></p>

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

  • Info Line 977, Column 101: start tag was here
    …fault.asp?id=638727&amp;sa=131278478"><img alt="" src="/staticimages/siyasetin…
  • Error Line 979, Column 136: end tag for "img" omitted, but OMITTAG NO was specified
    …karaya-dvd-belgesel.aspx"><img alt="" src="/images/resimler/deeee.gif"></a></p>

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

  • Info Line 979, Column 88: start tag was here
    …m.tr/urun/ankaraya-dvd-belgesel.aspx"><img alt="" src="/images/resimler/deeee.…
  • Error Line 982, Column 78: end tag for "param" omitted, but OMITTAG NO was specified
    		<param value="http://www.odatv.com/staticimages/destek24.swf" name="movie">

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

  • Info Line 982, Column 3: start tag was here
    		<param value="http://www.odatv.com/staticimages/destek24.swf" name="movie">
  • Error Line 983, Column 38: end tag for "param" omitted, but OMITTAG NO was specified
    		<param value="high" name="quality"><embed width="200" height="200" type="appl…

    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 983, Column 3: start tag was here
    		<param value="high" name="quality"><embed width="200" height="200" type="appl…
  • Error Line 983, Column 232: element "embed" undefined
    …ashplayer" quality="high" src="http://www.odatv.com/staticimages/destek24.swf">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 984, Column 11: 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 983, Column 38: start tag was here
    		<param value="high" name="quality"><embed width="200" height="200" type="appl…
  • Error Line 987, Column 84: end tag for "param" omitted, but OMITTAG NO was specified
    …aram value="http://www.odatv.com/staticimages/kirmizi-kedi28.swf" name="movie">

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

  • Info Line 987, Column 3: start tag was here
    		<param value="http://www.odatv.com/staticimages/kirmizi-kedi28.swf" name="mov…
  • Error Line 988, Column 38: end tag for "param" omitted, but OMITTAG NO was specified
    		<param value="high" name="quality"><embed width="200" height="200" type="appl…

    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 988, Column 3: start tag was here
    		<param value="high" name="quality"><embed width="200" height="200" type="appl…
  • Error Line 988, Column 238: element "embed" undefined
    …yer" quality="high" src="http://www.odatv.com/staticimages/kirmizi-kedi28.swf">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 989, Column 11: 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 988, Column 38: start tag was here
    		<param value="high" name="quality"><embed width="200" height="200" type="appl…
  • Error Line 992, Column 81: end tag for "param" omitted, but OMITTAG NO was specified
    		<param value="http://www.odatv.com/staticimages/bilgi-01(7).swf" name="movie">

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

  • Info Line 992, Column 3: start tag was here
    		<param value="http://www.odatv.com/staticimages/bilgi-01(7).swf" name="movie">
  • Error Line 993, Column 38: end tag for "param" omitted, but OMITTAG NO was specified
    		<param value="high" name="quality"><embed width="200" height="200" type="appl…

    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 993, Column 3: start tag was here
    		<param value="high" name="quality"><embed width="200" height="200" type="appl…
  • Error Line 993, Column 235: element "embed" undefined
    …player" quality="high" src="http://www.odatv.com/staticimages/bilgi-01(7).swf">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 994, Column 11: 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 993, Column 38: start tag was here
    		<param value="high" name="quality"><embed width="200" height="200" type="appl…
  • Error Line 998, Column 14: there is no attribute "name"
    <iframe name="iframe" src="http://www.kaynakyayinlari.com/reklam/odatv/reklam.h…

    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 998, Column 91: there is no attribute "width"
    …i.com/reklam/odatv/reklam.html" width="200" height="400" marginwidth="1" margi…

    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 998, Column 104: there is no attribute "height"
    …odatv/reklam.html" width="200" height="400" marginwidth="1" marginheight="1" 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 998, Column 122: there is no attribute "marginwidth"
    … width="200" height="400" marginwidth="1" marginheight="1" scrolling="no" alig…

    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 998, Column 139: there is no attribute "marginheight"
    …ht="400" marginwidth="1" marginheight="1" scrolling="no" align="absmiddle" bor…

    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 998, Column 164: there is no attribute "align"
    …marginheight="1" scrolling="no" align="absmiddle" border="0" frameborder="0"><…

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

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

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

  • Error Line 998, Column 183: there is no attribute "border"
    …eight="1" scrolling="no" align="absmiddle" border="0" frameborder="0"></iframe>

    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 998, Column 202: element "iframe" undefined
    …eight="1" scrolling="no" align="absmiddle" border="0" frameborder="0"></iframe>

    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 1002, Column 134: end tag for "img" omitted, but OMITTAG NO was specified
    …"><img src="/staticimages/tarihci.gif" width="200" height="200" alt=""></a></p>

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

  • Info Line 1002, Column 62: start tag was here
    …ref="http://www.tarihcikitabevi.com/"><img src="/staticimages/tarihci.gif" wid…
  • Error Line 1004, Column 99: end tag for "img" omitted, but OMITTAG NO was specified
    …ef="http://bizimkitapci.com/"><img alt="" src="/staticimages/anim.gif"></a></p>

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

  • Info Line 1004, Column 55: start tag was here
    …lank" href="http://bizimkitapci.com/"><img alt="" src="/staticimages/anim.gif"…
  • Error Line 1028, Column 7: end tag for "script" omitted, but OMITTAG NO was specified
    </body>

    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 51, Column 5: start tag was here
        <script type="text/javascript">

Visitor Analysis

Daily Visitor
  • 13.300 visits
Daily Visitor