Türkiyenin en hızlı güncellenen film izleme sitesidir. En yeni filmleri ilk siz izleyin. Online film izlemenin tadını çıkarın ...

direkizle.net
  • Domain Name
    direkizle.net
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #12012
  • Page Size
    44 KB
  • Ip Address
    5.153.19.31
  • Heading
    H1: 0, H2: 13, H3: 0, H4: 18, H5: 0, H6: 0
  • Images
    0 GIF, 14 JPG, 15 PNG

Website Meta Analysis

  • Title
    Direkizle.com - Film izle , Online Sinema , Film seyret
  • Meta Keyword
    Film izle,online sinema,film seyret,online izle,online film,online film izle,sinema izle,erotik film izle,dizi izle
  • Meta Description
    Türkiyenin en hızlı güncellenen film izleme sitesidir. En yeni filmleri ilk siz izleyin. Online film izlemenin tadını çıkarın

Technical Analysis

  • Webserver
    LiteSpeed
  • Ip Address
    5.153.19.31
  • Domain Age
    5 Years, 1 Months, 8 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-encoding: gzip
  • vary: Accept-Encoding
  • date: Sat, 09 Mar 2013 09:01:56 GMT
  • server: LiteSpeed
  • connection: close
  • x-powered-by: PHP/5.2.17
  • x-pingback: http://www.direkizle.com/xmlrpc.php
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domains By Proxy, LLC

Domain Name: DIREKIZLE.NET

Domain servers in listed order:
NS1.HASTAYIZ.COM
NS2.HASTAYIZ.COM

For complete domain details go to:
http://who.godaddy.com/whoischeck.aspx?domain=DIREKIZLE.NET

DNS Analysis


DNS servers
ns1.hastayiz.com
ns2.hastayiz.com

DNS Records

Answer records
direkizle.net MX
preference: 0
exchange: direkizle.net
14400s
direkizle.net SOA
server: ns1.hastayiz.com
email: root@direkizle.net
serial: 2012092502
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
direkizle.net NS  ns1.hastayiz.com 86400s
direkizle.net NS  ns2.hastayiz.com 86400s
direkizle.net A 5.153.19.31 14400s

Authority records

Additional records
direkizle.net A 5.153.19.31 14400s
ns1.hastayiz.com A 5.153.19.28 14400s
ns2.hastayiz.com A 5.153.19.28 14400s

IP 5.153.19.31 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 116 Errors
  • 99 Warnings
Ratio Text/Html
  • 0.7201003686103833
Message Error
  • Error Line 52, Column 16: there is no attribute "property"
    <meta property="og:site_name" content="Direkizle.net-  film izle , online sinem…

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

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

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

  • Error Line 158, Column 21: an attribute specification must start with a name or name token
    document.write('<scr'+'ipt src="http://d.serve-sys.com/w/1.0/jstag"><\/scr'+'ip…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 158, Column 21: element "scr" undefined
    document.write('<scr'+'ipt src="http://d.serve-sys.com/w/1.0/jstag"><\/scr'+'ip…

    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 158, Column 69: character "<" is the first character of a delimiter but occurred as data
    …ent.write('<scr'+'ipt src="http://d.serve-sys.com/w/1.0/jstag"><\/scr'+'ipt>');

    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 159, Column 9: end tag for "scr" 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 158, Column 17: start tag was here
    document.write('<scr'+'ipt src="http://d.serve-sys.com/w/1.0/jstag"><\/scr'+'ip…
  • Error Line 160, Column 10: document type does not allow element "noscript" here; assuming missing "object" start-tag
    <noscript><iframe id="505ca86a8e0c3" name="505ca86a8e0c3" src="http://d.serve-s…
  • Error Line 160, Column 23: value of attribute "id" invalid: "5" cannot start a name
    <noscript><iframe id="505ca86a8e0c3" name="505ca86a8e0c3" src="http://d.serve-s…

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

  • Warning Line 160, Column 109: cannot generate system identifier for general entity "cb"
    …d.serve-sys.com/w/1.0/afr?auid=219067&cb=INSERT_RANDOM_NUMBER_HERE" frameborde…

    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 160, Column 109: general entity "cb" not defined and no default entity
    …d.serve-sys.com/w/1.0/afr?auid=219067&cb=INSERT_RANDOM_NUMBER_HERE" frameborde…

    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 160, Column 111: reference not terminated by REFC delimiter
    …serve-sys.com/w/1.0/afr?auid=219067&cb=INSERT_RANDOM_NUMBER_HERE" frameborder=…

    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 160, Column 111: reference to external entity in attribute value
    …serve-sys.com/w/1.0/afr?auid=219067&cb=INSERT_RANDOM_NUMBER_HERE" frameborder=…

    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 160, Column 111: reference to entity "cb" for which no system identifier could be generated
    …serve-sys.com/w/1.0/afr?auid=219067&cb=INSERT_RANDOM_NUMBER_HERE" 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.

  • Info Line 160, Column 108: entity was defined here
    …/d.serve-sys.com/w/1.0/afr?auid=219067&cb=INSERT_RANDOM_NUMBER_HERE" framebord…
  • Warning Line 160, Column 255: reference not terminated by REFC delimiter
    …e-sys.com/w/1.0/rc?cs=505ca86a8e0c3&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    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 160, Column 255: reference to external entity in attribute value
    …e-sys.com/w/1.0/rc?cs=505ca86a8e0c3&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    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 160, Column 255: reference to entity "cb" for which no system identifier could be generated
    …e-sys.com/w/1.0/rc?cs=505ca86a8e0c3&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    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 160, Column 108: entity was defined here
    …/d.serve-sys.com/w/1.0/afr?auid=219067&cb=INSERT_RANDOM_NUMBER_HERE" framebord…
  • Warning Line 160, Column 338: cannot generate system identifier for general entity "cs"
    …/d.serve-sys.com/w/1.0/ai?auid=219067&cs=505ca86a8e0c3&cb=INSERT_RANDOM_NUMBER…

    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 160, Column 338: general entity "cs" not defined and no default entity
    …/d.serve-sys.com/w/1.0/ai?auid=219067&cs=505ca86a8e0c3&cb=INSERT_RANDOM_NUMBER…

    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 160, Column 340: reference not terminated by REFC delimiter
    ….serve-sys.com/w/1.0/ai?auid=219067&cs=505ca86a8e0c3&cb=INSERT_RANDOM_NUMBER_H…

    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 160, Column 340: reference to external entity in attribute value
    ….serve-sys.com/w/1.0/ai?auid=219067&cs=505ca86a8e0c3&cb=INSERT_RANDOM_NUMBER_H…

    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 160, Column 340: reference to entity "cs" for which no system identifier could be generated
    ….serve-sys.com/w/1.0/ai?auid=219067&cs=505ca86a8e0c3&cb=INSERT_RANDOM_NUMBER_H…

    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 160, Column 337: entity was defined here
    …//d.serve-sys.com/w/1.0/ai?auid=219067&cs=505ca86a8e0c3&cb=INSERT_RANDOM_NUMBE…
  • Warning Line 160, Column 357: reference not terminated by REFC delimiter
    …1.0/ai?auid=219067&cs=505ca86a8e0c3&cb=INSERT_RANDOM_NUMBER_HERE" border="0" a…

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

  • Warning Line 160, Column 357: reference to external entity in attribute value
    …1.0/ai?auid=219067&cs=505ca86a8e0c3&cb=INSERT_RANDOM_NUMBER_HERE" border="0" a…

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

  • Error Line 160, Column 357: reference to entity "cb" for which no system identifier could be generated
    …1.0/ai?auid=219067&cs=505ca86a8e0c3&cb=INSERT_RANDOM_NUMBER_HERE" border="0" a…

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

  • Info Line 160, Column 108: entity was defined here
    …/d.serve-sys.com/w/1.0/afr?auid=219067&cb=INSERT_RANDOM_NUMBER_HERE" framebord…
  • Error Line 160, Column 406: end tag for "img" omitted, but OMITTAG NO was specified
    …a8e0c3&cb=INSERT_RANDOM_NUMBER_HERE" border="0" alt=""></a></iframe></noscript>

    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 160, Column 284: start tag was here
    …a8e0c3&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="http://d.serve-sys.com/w/1.0/a…
  • Error Line 164, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

    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 160, Column 1: start tag was here
    <noscript><iframe id="505ca86a8e0c3" name="505ca86a8e0c3" src="http://d.serve-s…
  • Error Line 174, Column 21: an attribute specification must start with a name or name token
    document.write('<scr'+'ipt src="http://d.serve-sys.com/w/1.0/jstag"><\/scr'+'ip…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 174, Column 21: element "scr" undefined
    document.write('<scr'+'ipt src="http://d.serve-sys.com/w/1.0/jstag"><\/scr'+'ip…

    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 174, Column 69: character "<" is the first character of a delimiter but occurred as data
    …ent.write('<scr'+'ipt src="http://d.serve-sys.com/w/1.0/jstag"><\/scr'+'ipt>');

    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 175, Column 9: end tag for "scr" 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 174, Column 17: start tag was here
    document.write('<scr'+'ipt src="http://d.serve-sys.com/w/1.0/jstag"><\/scr'+'ip…
  • Error Line 176, Column 23: value of attribute "id" invalid: "4" cannot start a name
    <noscript><iframe id="4fc7441b3067d" name="4fc7441b3067d" src="http://d.serve-s…

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

  • Warning Line 176, Column 111: reference not terminated by REFC delimiter
    …serve-sys.com/w/1.0/afr?auid=219066&cb=INSERT_RANDOM_NUMBER_HERE" frameborder=…

    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 176, Column 111: reference to external entity in attribute value
    …serve-sys.com/w/1.0/afr?auid=219066&cb=INSERT_RANDOM_NUMBER_HERE" frameborder=…

    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 176, Column 111: reference to entity "cb" for which no system identifier could be generated
    …serve-sys.com/w/1.0/afr?auid=219066&cb=INSERT_RANDOM_NUMBER_HERE" 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.

  • Info Line 160, Column 108: entity was defined here
    …/d.serve-sys.com/w/1.0/afr?auid=219067&cb=INSERT_RANDOM_NUMBER_HERE" framebord…
  • Warning Line 176, Column 255: reference not terminated by REFC delimiter
    …e-sys.com/w/1.0/rc?cs=4fc7441b3067d&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    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 176, Column 255: reference to external entity in attribute value
    …e-sys.com/w/1.0/rc?cs=4fc7441b3067d&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    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 176, Column 255: reference to entity "cb" for which no system identifier could be generated
    …e-sys.com/w/1.0/rc?cs=4fc7441b3067d&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    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 160, Column 108: entity was defined here
    …/d.serve-sys.com/w/1.0/afr?auid=219067&cb=INSERT_RANDOM_NUMBER_HERE" framebord…
  • Warning Line 176, Column 340: reference not terminated by REFC delimiter
    ….serve-sys.com/w/1.0/ai?auid=219066&cs=4fc7441b3067d&cb=INSERT_RANDOM_NUMBER_H…

    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 176, Column 340: reference to external entity in attribute value
    ….serve-sys.com/w/1.0/ai?auid=219066&cs=4fc7441b3067d&cb=INSERT_RANDOM_NUMBER_H…

    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 176, Column 340: reference to entity "cs" for which no system identifier could be generated
    ….serve-sys.com/w/1.0/ai?auid=219066&cs=4fc7441b3067d&cb=INSERT_RANDOM_NUMBER_H…

    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 160, Column 337: entity was defined here
    …//d.serve-sys.com/w/1.0/ai?auid=219067&cs=505ca86a8e0c3&cb=INSERT_RANDOM_NUMBE…
  • Warning Line 176, Column 357: reference not terminated by REFC delimiter
    …1.0/ai?auid=219066&cs=4fc7441b3067d&cb=INSERT_RANDOM_NUMBER_HERE" border="0" a…

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

  • Warning Line 176, Column 357: reference to external entity in attribute value
    …1.0/ai?auid=219066&cs=4fc7441b3067d&cb=INSERT_RANDOM_NUMBER_HERE" border="0" a…

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

  • Error Line 176, Column 357: reference to entity "cb" for which no system identifier could be generated
    …1.0/ai?auid=219066&cs=4fc7441b3067d&cb=INSERT_RANDOM_NUMBER_HERE" border="0" a…

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

  • Info Line 160, Column 108: entity was defined here
    …/d.serve-sys.com/w/1.0/afr?auid=219067&cb=INSERT_RANDOM_NUMBER_HERE" framebord…
  • Error Line 176, Column 406: end tag for "img" omitted, but OMITTAG NO was specified
    …b3067d&cb=INSERT_RANDOM_NUMBER_HERE" border="0" alt=""></a></iframe></noscript>

    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 176, Column 284: start tag was here
    …b3067d&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="http://d.serve-sys.com/w/1.0/a…
  • Error Line 184, Column 13: there is no attribute "SRC"
    <IFRAME	SRC="http://display.clickpoint.com/adsrv/view.cp?PUB=61874&amp;SITE=0&a…

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

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

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

  • Error Line 185, Column 7: there is no attribute "WIDTH"
    WIDTH=120 HEIGHT=600 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">

    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 185, Column 7: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=120 HEIGHT=600 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 185, Column 18: there is no attribute "HEIGHT"
    WIDTH=120 HEIGHT=600 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">

    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 185, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=120 HEIGHT=600 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 185, Column 35: there is no attribute "MARGINHEIGHT"
    WIDTH=120 HEIGHT=600 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">

    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 185, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=120 HEIGHT=600 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 185, Column 49: there is no attribute "MARGINWIDTH"
    WIDTH=120 HEIGHT=600 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">

    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 185, Column 49: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=120 HEIGHT=600 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 185, Column 63: there is no attribute "FRAMEBORDER"
    WIDTH=120 HEIGHT=600 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">

    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 185, Column 63: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=120 HEIGHT=600 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 185, Column 75: there is no attribute "SCROLLING"
    WIDTH=120 HEIGHT=600 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">

    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 185, Column 79: element "IFRAME" undefined
    WIDTH=120 HEIGHT=600 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">

    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 186, Column 61: there is no attribute "SRC"
    …Script1.1" type="text/javascript" SRC="http://display.clickpoint.com/adsrv/vie…

    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 189, Column 9: there is no attribute "HREF"
    <A HREF="http://display.clickpoint.com/adsrv/jump.cp?PUB=61874&amp;SITE=0&amp;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 189, Column 120: element "A" undefined
    …srv/jump.cp?PUB=61874&amp;SITE=0&amp;SIZE=120x600&amp;SUB=direkizle_sol_kayan">

    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 190, Column 10: there is no attribute "SRC"
    <IMG SRC="http://display.clickpoint.com/adsrv/view.cp?PUB=61874&amp;SITE=0&amp;…

    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 190, Column 124: there is no attribute "border"
    …20x600&amp;SUB=&amp;BTYPE=img" border=0 width="120" height="600" alt="Clickpoi…

    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 190, Column 124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …20x600&amp;SUB=&amp;BTYPE=img" border=0 width="120" height="600" alt="Clickpoi…
  • Error Line 190, Column 132: there is no attribute "width"
    …mp;SUB=&amp;BTYPE=img" border=0 width="120" height="600" alt="Clickpoint adser…

    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 190, Column 145: there is no attribute "height"
    …B=&amp;BTYPE=img" border=0 width="120" height="600" alt="Clickpoint adserver"/>

    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 190, Column 155: there is no attribute "alt"
    …B=&amp;BTYPE=img" border=0 width="120" height="600" alt="Clickpoint adserver"/>

    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 190, Column 177: element "IMG" undefined
    …B=&amp;BTYPE=img" border=0 width="120" height="600" alt="Clickpoint adserver"/>

    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 211, Column 115: required attribute "alt" not specified
    …nofollow" target="_blank"><img src="http://direkizle.net/firsatimo2.jpg" /></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 219, Column 7: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=728 HEIGHT=90 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 219, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=728 HEIGHT=90 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 219, Column 34: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=728 HEIGHT=90 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 219, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=728 HEIGHT=90 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 219, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=728 HEIGHT=90 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 219, Column 78: element "IFRAME" undefined
    WIDTH=728 HEIGHT=90 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">

    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 223, Column 119: element "A" undefined
    …dsrv/jump.cp?PUB=61874&amp;SITE=0&amp;SIZE=728x90&amp;SUB=direkizle_alt_kisim">

    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 224, Column 123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …728x90&amp;SUB=&amp;BTYPE=img" border=0 width="728" height="90" alt="Clickpoin…
  • Error Line 224, Column 175: element "IMG" undefined
    …UB=&amp;BTYPE=img" border=0 width="728" height="90" alt="Clickpoint adserver"/>

    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 265, Column 291: there is no attribute "allowTransparency"
    …no" frameborder="0" allowTransparency="true" style="border:none; overflow:hidd…

    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 533, Column 5: end tag for element "br" which is not open
    </br></br></br></br></br>

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

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

  • Error Line 533, Column 10: end tag for element "br" which is not open
    </br></br></br></br></br>

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

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

  • Error Line 533, Column 15: end tag for element "br" which is not open
    </br></br></br></br></br>

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

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

  • Error Line 533, Column 20: end tag for element "br" which is not open
    </br></br></br></br></br>

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

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

  • Error Line 533, Column 25: end tag for element "br" which is not open
    </br></br></br></br></br>

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

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

  • Error Line 535, Column 5: end tag for element "br" which is not open
    </br></br>

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

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

  • Error Line 535, Column 10: end tag for element "br" which is not open
    </br></br>

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

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

  • Error Line 575, Column 73: end tag for "br" omitted, but OMITTAG NO was specified
    - Flash Player s&#252;r&#252;m&#252;n&#252;z&#252; g&#252;ncelleyin.<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 575, Column 69: start tag was here
    - Flash Player s&#252;r&#252;m&#252;n&#252;z&#252; g&#252;ncelleyin.<br>
  • Error Line 576, Column 114: end tag for "br" omitted, but OMITTAG NO was specified
    … firefox veya Google Chrome taray&#305;c&#305;s&#305;n&#305; kullan&#305;n.<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 576, Column 110: start tag was here
    … firefox veya Google Chrome taray&#305;c&#305;s&#305;n&#305; kullan&#305;n.<br>
  • Error Line 577, Column 147: end tag for "br" omitted, but OMITTAG NO was specified
    …&#305; de&#287;i&#351;tirerek deneyin.(4.2.2.1 ve 8.8.8.8 yapmay&#305;n..!)<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 577, Column 143: start tag was here
    …&#305; de&#287;i&#351;tirerek deneyin.(4.2.2.1 ve 8.8.8.8 yapmay&#305;n..!)<br>
  • Error Line 578, Column 74: end tag for "br" omitted, but OMITTAG NO was specified
    - Internet taray&#305;c&#305;n&#305;zda ge&#231;mi&#351;i temizleyin.<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 578, Column 70: start tag was here
    - Internet taray&#305;c&#305;n&#305;zda ge&#231;mi&#351;i temizleyin.<br>
  • Error Line 579, Column 95: end tag for "br" omitted, but OMITTAG NO was specified
    …set at&#305;n ve bilgisayar&#305;n&#305;z&#305; yeniden ba&#351;lat&#305;n.<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 579, Column 91: start tag was here
    …set at&#305;n ve bilgisayar&#305;n&#305;z&#305; yeniden ba&#351;lat&#305;n.<br>
  • Error Line 580, Column 129: end tag for "br" omitted, but OMITTAG NO was specified
    …madan yani http://direkizle.net &#351;eklinde giri&#351; yap&#305;n&#305;z.<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 580, Column 125: start tag was here
    …madan yani http://direkizle.net &#351;eklinde giri&#351; yap&#305;n&#305;z.<br>
  • Error Line 581, Column 104: end tag for "br" omitted, but OMITTAG NO was specified
    …1; doluyorsa, ayn&#305; anda bi&#351;ey indirmeyin,dinlemeyin ve izlemeyin.<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 581, Column 100: start tag was here
    …1; doluyorsa, ayn&#305; anda bi&#351;ey indirmeyin,dinlemeyin ve izlemeyin.<br>
  • Error Line 582, Column 115: end tag for "br" omitted, but OMITTAG NO was specified
    …ast&#305;ktan sonra 10 dakika dolmas&#305;n&#305; bekleyip oyle devam edin.<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 582, Column 111: start tag was here
    …ast&#305;ktan sonra 10 dakika dolmas&#305;n&#305; bekleyip oyle devam edin.<br>
  • Error Line 583, Column 83: end tag for "br" omitted, but OMITTAG NO was specified
    …uklenen filmler silinmis olabilir. Alternatif linkler varsa onlari deneyin.<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 583, Column 79: start tag was here
    …uklenen filmler silinmis olabilir. Alternatif linkler varsa onlari deneyin.<br>
  • Error Line 589, Column 106: required attribute "alt" not specified
    …ekizle.net/wp-content/themes/sorunsuztema/images/twitter.png" border="0" /></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 591, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 591, Column 1: start tag was here
    <br>
  • Error Line 592, Column 201: there is no attribute "VALUE"
    …<param name="AllowScriptAccess" VALUE="always"/><param name="AllowNetworking" …

    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 592, Column 347: cannot generate system identifier for general entity "a"
    …="flashvars" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=…

    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 592, Column 347: general entity "a" not defined and no default entity
    …="flashvars" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=…

    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 592, Column 348: reference not terminated by REFC delimiter
    …"flashvars" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=F…

    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 592, Column 348: reference to external entity in attribute value
    …"flashvars" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=F…

    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 592, Column 348: reference to entity "a" for which no system identifier could be generated
    …"flashvars" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=F…

    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 592, Column 346: entity was defined here
    …e="flashvars" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k…
  • Warning Line 592, Column 356: cannot generate system identifier for general entity "b"
    …rs" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=…

    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 592, Column 356: general entity "b" not defined and no default entity
    …rs" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=…

    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 592, Column 357: reference not terminated by REFC delimiter
    …s" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=9…

    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 592, Column 357: reference to external entity in attribute value
    …s" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=9…

    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 592, Column 357: reference to entity "b" for which no system identifier could be generated
    …s" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=9…

    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 592, Column 355: entity was defined here
    …ars" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l…
  • Warning Line 592, Column 362: cannot generate system identifier for general entity "c"
    …lue="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999…

    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 592, Column 362: general entity "c" not defined and no default entity
    …lue="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999…

    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 592, Column 363: reference not terminated by REFC delimiter
    …ue="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&…

    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 592, Column 363: reference to external entity in attribute value
    …ue="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&…

    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 592, Column 363: reference to entity "c" for which no system identifier could be generated
    …ue="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&…

    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 592, Column 361: entity was defined here
    …alue="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=99999…
  • Warning Line 592, Column 371: cannot generate system identifier for general entity "d"
    …1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=1…

    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 592, Column 371: general entity "d" not defined and no default entity
    …1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=1…

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

  • Warning Line 592, Column 372: reference not terminated by REFC delimiter
    …253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10…

    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 592, Column 372: reference to external entity in attribute value
    …253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10…

    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 592, Column 372: reference to entity "d" for which no system identifier could be generated
    …253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10…

    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 592, Column 370: entity was defined here
    …=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=…
  • Warning Line 592, Column 380: cannot generate system identifier for general entity "i"
    …0234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=…

    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 592, Column 380: general entity "i" not defined and no default entity
    …0234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&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.

  • Warning Line 592, Column 381: reference not terminated by REFC delimiter
    …234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1…

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

  • Warning Line 592, Column 381: reference to external entity in attribute value
    …234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1…

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

  • Error Line 592, Column 381: reference to entity "i" for which no system identifier could be generated
    …234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1…

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

  • Info Line 592, Column 379: entity was defined here
    …00234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s…
  • Warning Line 592, Column 385: cannot generate system identifier for general entity "k"
    …a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0…

    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 592, Column 385: general entity "k" not defined and no default entity
    …a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0…

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

  • Warning Line 592, Column 386: reference not terminated by REFC delimiter
    …=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&…

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

  • Warning Line 592, Column 386: reference to external entity in attribute value
    …=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&…

    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 592, Column 386: reference to entity "k" for which no system identifier could be generated
    …=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&…

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

  • Info Line 592, Column 384: entity was defined here
    …&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=…
  • Warning Line 592, Column 394: cannot generate system identifier for general entity "l"
    …b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"…

    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 592, Column 394: general entity "l" not defined and no default entity
    …b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"…

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

  • Warning Line 592, Column 395: reference not terminated by REFC delimiter
    …=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/…

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

  • Warning Line 592, Column 395: reference to external entity in attribute value
    …=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/…

    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 592, Column 395: reference to entity "l" for which no system identifier could be generated
    …=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/…

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

  • Info Line 592, Column 393: entity was defined here
    …&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0…
  • Warning Line 592, Column 403: cannot generate system identifier for general entity "o"
    …FFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed …

    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 592, Column 403: general entity "o" not defined and no default entity
    …FFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed …

    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 592, Column 404: reference not terminated by REFC delimiter
    …FFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed i…

    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 592, Column 404: reference to external entity in attribute value
    …FFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed i…

    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 592, Column 404: reference to entity "o" for which no system identifier could be generated
    …FFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed i…

    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 592, Column 402: entity was defined here
    …FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed…
  • Warning Line 592, Column 408: cannot generate system identifier for general entity "p"
    …&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="e…

    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 592, Column 408: general entity "p" not defined and no default entity
    …&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="e…

    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 592, Column 409: reference not terminated by REFC delimiter
    …d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="em…

    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 592, Column 409: reference to external entity in attribute value
    …d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="em…

    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 592, Column 409: reference to entity "p" for which no system identifier could be generated
    …d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="em…

    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 592, Column 407: entity was defined here
    …F&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="…
  • Warning Line 592, Column 413: cannot generate system identifier for general entity "r"
    …FFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_12…

    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 592, Column 413: general entity "r" not defined and no default entity
    …FFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_12…

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

  • Warning Line 592, Column 414: reference not terminated by REFC delimiter
    …FFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_125…

    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 592, Column 414: reference to external entity in attribute value
    …FFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_125…

    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 592, Column 414: reference to entity "r" for which no system identifier could be generated
    …FFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_125…

    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 592, Column 412: entity was defined here
    …FFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1…
  • Warning Line 592, Column 418: cannot generate system identifier for general entity "s"
    …i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308…

    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 592, Column 418: general entity "s" not defined and no default entity
    …i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308…

    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 592, Column 419: reference not terminated by REFC delimiter
    …=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_12533087…

    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 592, Column 419: reference to external entity in attribute value
    …=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_12533087…

    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 592, Column 419: reference to entity "s" for which no system identifier could be generated
    …=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_12533087…

    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 592, Column 417: entity was defined here
    …&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_125330…
  • Warning Line 592, Column 422: cannot generate system identifier for general entity "t"
    …&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_12533087002…

    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 592, Column 422: general entity "t" not defined and no default entity
    …&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_12533087002…

    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 592, Column 423: reference not terminated by REFC delimiter
    …k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_125330870023…

    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 592, Column 423: reference to external entity in attribute value
    …k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_125330870023…

    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 592, Column 423: reference to entity "t" for which no system identifier could be generated
    …k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_125330870023…

    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 592, Column 421: entity was defined here
    …8&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700…
  • Warning Line 592, Column 426: cannot generate system identifier for general entity "v"
    …FFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234" …

    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 592, Column 426: general entity "v" not defined and no default entity
    …FFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234" …

    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 592, Column 427: reference not terminated by REFC delimiter
    …FFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234" 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 592, Column 427: reference to external entity in attribute value
    …FFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234" 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 592, Column 427: reference to entity "v" for which no system identifier could be generated
    …FFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234" 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 592, Column 425: entity was defined here
    …FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234"…
  • Warning Line 592, Column 430: cannot generate system identifier for general entity "w"
    …F&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234" src=…

    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 592, Column 430: general entity "w" not defined and no default entity
    …F&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234" src=…

    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 592, Column 431: reference not terminated by REFC delimiter
    …&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234" src="…

    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 592, Column 431: reference to external entity in attribute value
    …&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234" src="…

    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 592, Column 431: reference to entity "w" for which no system identifier could be generated
    …&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234" src="…

    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 592, Column 429: entity was defined here
    …FF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234" src…
  • Error Line 592, Column 446: there is no attribute "id"
    …p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234" src="http://direkizl…

    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 592, Column 470: there is no attribute "src"
    …0"/><embed id="emb_1253308700234" src="http://direkizle.chatango.com/group" wi…

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

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

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

  • Error Line 592, Column 514: there is no attribute "width"
    …//direkizle.chatango.com/group" width="247" height="400" wmode="transparent" a…

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

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

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

  • Error Line 592, Column 527: there is no attribute "height"
    …hatango.com/group" width="247" height="400" wmode="transparent" allowScriptAcc…

    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 592, Column 539: there is no attribute "wmode"
    …group" width="247" height="400" wmode="transparent" allowScriptAccess="always"…

    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 592, Column 571: there is no attribute "allowScriptAccess"
    …wmode="transparent" allowScriptAccess="always" allowNetworking="all" type="app…

    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 592, Column 596: there is no attribute "allowNetworking"
    …ScriptAccess="always" allowNetworking="all" type="application/x-shockwave-flas…

    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 592, Column 607: there is no attribute "type"
    …s="always" allowNetworking="all" type="application/x-shockwave-flash" allowFul…

    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 592, Column 655: there is no attribute "allowFullScreen"
    …on/x-shockwave-flash" allowFullScreen="true" flashvars="cid=1253308700234&a=00…

    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 592, Column 672: there is no attribute "flashvars"
    …ash" allowFullScreen="true" flashvars="cid=1253308700234&a=00A7FF&b=100&c=FFFF…

    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 592, Column 692: reference not terminated by REFC delimiter
    …="true" flashvars="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=F…

    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 592, Column 692: reference to external entity in attribute value
    …="true" flashvars="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=F…

    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 592, Column 692: reference to entity "a" for which no system identifier could be generated
    …="true" flashvars="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=F…

    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 592, Column 346: entity was defined here
    …e="flashvars" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k…
  • Warning Line 592, Column 701: reference not terminated by REFC delimiter
    …lashvars="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=9…

    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 592, Column 701: reference to external entity in attribute value
    …lashvars="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=9…

    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 592, Column 701: reference to entity "b" for which no system identifier could be generated
    …lashvars="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=9…

    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 592, Column 355: entity was defined here
    …ars" value="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l…
  • Warning Line 592, Column 707: reference not terminated by REFC delimiter
    …rs="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&…

    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 592, Column 707: reference to external entity in attribute value
    …rs="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&…

    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 592, Column 707: reference to entity "c" for which no system identifier could be generated
    …rs="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&…

    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 592, Column 361: entity was defined here
    …alue="cid=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=99999…
  • Warning Line 592, Column 716: reference not terminated by REFC delimiter
    …253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10…

    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 592, Column 716: reference to external entity in attribute value
    …253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10…

    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 592, Column 716: reference to entity "d" for which no system identifier could be generated
    …253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10…

    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 592, Column 370: entity was defined here
    …=1253308700234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=…
  • Warning Line 592, Column 725: reference not terminated by REFC delimiter
    …234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1…

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

  • Warning Line 592, Column 725: reference to external entity in attribute value
    …234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1…

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

  • Error Line 592, Column 725: reference to entity "i" for which no system identifier could be generated
    …234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1…

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

  • Info Line 592, Column 379: entity was defined here
    …00234&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s…
  • Warning Line 592, Column 730: reference not terminated by REFC delimiter
    …=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&…

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

  • Warning Line 592, Column 730: reference to external entity in attribute value
    …=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&…

    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 592, Column 730: reference to entity "k" for which no system identifier could be generated
    …=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&…

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

  • Info Line 592, Column 384: entity was defined here
    …&a=00A7FF&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=…
  • Warning Line 592, Column 739: reference not terminated by REFC delimiter
    …=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0">…

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

  • Warning Line 592, Column 739: reference to external entity in attribute value
    …=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0">…

    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 592, Column 739: reference to entity "l" for which no system identifier could be generated
    …=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0">…

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

  • Info Line 592, Column 393: entity was defined here
    …&b=100&c=FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0…
  • Warning Line 592, Column 748: reference not terminated by REFC delimiter
    …FFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed><…

    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 592, Column 748: reference to external entity in attribute value
    …FFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed><…

    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 592, Column 748: reference to entity "o" for which no system identifier could be generated
    …FFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed><…

    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 592, Column 402: entity was defined here
    …FFFFFF&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed…
  • Warning Line 592, Column 753: reference not terminated by REFC delimiter
    …d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></obje…

    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 592, Column 753: reference to external entity in attribute value
    …d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></obje…

    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 592, Column 753: reference to entity "p" for which no system identifier could be generated
    …d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></obje…

    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 592, Column 407: entity was defined here
    …F&d=FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="…
  • Warning Line 592, Column 758: reference not terminated by REFC delimiter
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 758: reference to external entity in attribute value
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 758: reference to entity "r" for which no system identifier could be generated
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 412: entity was defined here
    …FFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1…
  • Warning Line 592, Column 763: reference not terminated by REFC delimiter
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 763: reference to external entity in attribute value
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 763: reference to entity "s" for which no system identifier could be generated
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 417: entity was defined here
    …&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_125330…
  • Warning Line 592, Column 767: reference not terminated by REFC delimiter
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 767: reference to external entity in attribute value
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 767: reference to entity "t" for which no system identifier could be generated
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 421: entity was defined here
    …8&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700…
  • Warning Line 592, Column 771: reference not terminated by REFC delimiter
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 771: reference to external entity in attribute value
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 771: reference to entity "v" for which no system identifier could be generated
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 425: entity was defined here
    …FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234"…
  • Warning Line 592, Column 775: reference not terminated by REFC delimiter
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 775: reference to external entity in attribute value
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 775: reference to entity "w" for which no system identifier could be generated
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

    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 592, Column 429: entity was defined here
    …FF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"/><embed id="emb_1253308700234" src…
  • Error Line 592, Column 778: element "embed" undefined
    …FFFFFF&i=88&k=FFFFFF&l=999999&o=70&p=10&r=80&s=1&t=0&v=0&w=0"></embed></object>

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

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

  • Info Line 593, Column 1: start tag was here
    <br>
  • Error Line 595, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 595, Column 1: start tag was here
    <br>
  • Error Line 598, Column 159: required attribute "alt" not specified
    …kizle.net/wp-content/themes/sorunsuztema/images/facebook.png" border="0" /></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 600, Column 128: required attribute "alt" not specified
    …ofollow" target="_blank"><img src="http://direkizle.net/facebook111.jpg" /></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 615, Column 7: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=728 HEIGHT=90 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 615, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=728 HEIGHT=90 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 615, Column 34: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=728 HEIGHT=90 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 615, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=728 HEIGHT=90 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 615, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    WIDTH=728 HEIGHT=90 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">
  • Error Line 615, Column 78: element "IFRAME" undefined
    WIDTH=728 HEIGHT=90 MARGINHEIGHT=0 MARGINWIDTH=0 FRAMEBORDER=0 SCROLLING="no">

    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 619, Column 119: element "A" undefined
    …dsrv/jump.cp?PUB=61874&amp;SITE=0&amp;SIZE=728x90&amp;SUB=direkizle_alt_kisim">

    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 620, Column 123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …728x90&amp;SUB=&amp;BTYPE=img" border=0 width="728" height="90" alt="Clickpoin…
  • Error Line 620, Column 175: element "IMG" undefined
    …UB=&amp;BTYPE=img" border=0 width="728" height="90" alt="Clickpoint adserver"/>

    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 644, Column 7: end tag for "div" 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 195, Column 1: start tag was here
    <div id="wrap">

Visitor Analysis

Daily Visitor
  • 10.500 visits
Daily Visitor