MyBBDepo - Türkiyenin MyBB Deposu Forumuna Hoşgeldiniz
Eğer sitemize yaptığınız ilk ziyaretiniz ise, lütfen öncelikle Forum Kurallarını okuyunuz. Forumumuzda bilgi alışverişinde bulunabilmeniz için Kayıt olmalısınız. Üye olmayanlar forumumuzdan yararlanamazlar.
Eğer zaten kayıtlı kullanıcı iseniz, lütfen kullanıcı adınız ve şifreniz ile, Giriş yapınız. (Sitemize üyelik ücretsizdir).
fatihcray09 avatar
Konuyu Oyla:
  • Derecelendirme: 0/5 - 0 oy
  • 1
  • 2
  • 3
  • 4
  • 5

Derecelendirme: 0/5 - 0 oy

w3c Optimize Hataları


Sponsor Reklam
media venus

Çevrimdışı fatihcray09
 Tarih: 15-07-2014, Saat:06:31
#1
Arkadaşlar tam 49 tane hata belirlemiş bunları nasıl düzelteceğim
Direk Link



Validation Output: 49 Errors

Error Line 120, Column 3: "DOCTYPE" declaration not allowed in instance
<!DOCTYPE HTML><style type="text/css">div.fixued-position{position:fixed;text-a…

Error Line 120, Column 38: document type does not allow element "style" here
<!DOCTYPE HTML><style type="text/css">div.fixued-position{position:fixed;text-a…

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

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

Error Line 120, Column 170: document type does not allow element "style" here
…ht:0px;}</style><style type="text/css">div.fixued-position{_position:absolute;…

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

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

Error Line 120, Column 755: required attribute "alt" not specified
…LXe8/s1600/sitenizeeklemekicinkoddostunuziyaretedin1.png" border="0"></a></div>

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

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

Error Line 120, Column 759: end tag for "img" omitted, but OMITTAG NO was specified
…LXe8/s1600/sitenizeeklemekicinkoddostunuziyaretedin1.png" border="0"></a></div>

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

Info Line 120, Column 536: start tag was here
…://yulgang2tr.org" title="Yulgan2 TR"><img style="margin:0px;padding:0px;borde…
Error Line 169, Column 160: required attribute "alt" not specified
…ttp://yulgang2tr.org/images/facebookilebaglan.png" width="186" height="25"></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 169, Column 164: end tag for "img" omitted, but OMITTAG NO was specified
…ttp://yulgang2tr.org/images/facebookilebaglan.png" width="186" height="25"></a>

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

Info Line 169, Column 64: start tag was here
…r.org/myfbconnect.php?action=fblogin"><img border="0" src="http://yulgang2tr.o…
Error Line 170, Column 32: end tag for "div" omitted, but OMITTAG NO was specified
<!-- AddThis Button END --></td>

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

Info Line 168, Column 1: start tag was here
<div class="addthis_toolbox addthis_default_style ">
Error Line 170, Column 32: end tag for "div" omitted, but OMITTAG NO was specified
<!-- AddThis Button END --></td>

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

Info Line 167, Column 1: start tag was here
<div style="float: right; vertical-align: middle;">
Error Line 197, Column 123: "allowfullscreen" is not a member of a group specified for any attribute
…w.youtube.com/embed/mSq0cyOXmiQ" frameborder="0" allowfullscreen></iframe></th>

Error Line 198, Column 123: "allowfullscreen" is not a member of a group specified for any attribute
…w.youtube.com/embed/q8foxovjKao" frameborder="0" allowfullscreen></iframe></th>

Error Line 202, Column 28: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
padding: 8px;"><font color=black><span style="text-shadow: 0px 0px 8px ;"><stro…

Error Line 214, Column 74: required attribute "alt" not specified
…<a href="/index.php" title="Anasayfa"><img src="images/nav_home.png"/></a></li>

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

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

Error Line 254, Column 77: end tag for "input" omitted, but OMITTAG NO was specified
<input type="button" value="Yenile" class="button" onclick="fcb_refresh();">

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 254, Column 1: start tag was here
<input type="button" value="Yenile" class="button" onclick="fcb_refresh();">
Error Line 255, Column 76: end tag for "input" omitted, but OMITTAG NO was specified
<input type="button" value="Arşiv" class="button" onclick="archivepage();">

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 255, Column 1: start tag was here
<input type="button" value="Arşiv" class="button" onclick="archivepage();">
Warning Line 432, Column 79: cannot generate system identifier for general entity "key"
…tr.org/chatbox/index.php?do=postshout&key=' + chatboxkey + '&userid=' + huid +…

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 (Göz kırpma. 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 (Göz kırpma. 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 432, Column 79: general entity "key" not defined and no default entity
…tr.org/chatbox/index.php?do=postshout&key=' + chatboxkey + '&userid=' + huid +…

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 432, Column 82: reference not terminated by REFC delimiter
…org/chatbox/index.php?do=postshout&key=' + chatboxkey + '&userid=' + huid + '&…

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

Error Line 432, Column 82: reference to entity "key" for which no system identifier could be generated
…org/chatbox/index.php?do=postshout&key=' + chatboxkey + '&userid=' + huid + '&…

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 432, Column 78: entity was defined here
…2tr.org/chatbox/index.php?do=postshout&key=' + chatboxkey + '&userid=' + huid …
Warning Line 432, Column 102: cannot generate system identifier for general entity "userid"
…p?do=postshout&key=' + chatboxkey + '&userid=' + huid + '&groupid=' + hgroupid…

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 (Göz kırpma. 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 (Göz kırpma. 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 432, Column 102: general entity "userid" not defined and no default entity
…p?do=postshout&key=' + chatboxkey + '&userid=' + huid + '&groupid=' + hgroupid…

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 432, Column 108: reference not terminated by REFC delimiter
…ostshout&key=' + chatboxkey + '&userid=' + huid + '&groupid=' + hgroupid + '&u…

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

Error Line 432, Column 108: reference to entity "userid" for which no system identifier could be generated
…ostshout&key=' + chatboxkey + '&userid=' + huid + '&groupid=' + hgroupid + '&u…

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 432, Column 101: entity was defined here
…hp?do=postshout&key=' + chatboxkey + '&userid=' + huid + '&groupid=' + hgroupi…
Warning Line 432, Column 122: cannot generate system identifier for general entity "groupid"
… + chatboxkey + '&userid=' + huid + '&groupid=' + hgroupid + '&username=' + hu…

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 (Göz kırpma. 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 (Göz kırpma. 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 432, Column 122: general entity "groupid" not defined and no default entity
… + chatboxkey + '&userid=' + huid + '&groupid=' + hgroupid + '&username=' + hu…

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 432, Column 129: reference not terminated by REFC delimiter
…boxkey + '&userid=' + huid + '&groupid=' + hgroupid + '&username=' + huser + '…

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

Error Line 432, Column 129: reference to entity "groupid" for which no system identifier could be generated
…boxkey + '&userid=' + huid + '&groupid=' + hgroupid + '&username=' + huser + '…

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 432, Column 121: entity was defined here
…' + chatboxkey + '&userid=' + huid + '&groupid=' + hgroupid + '&username=' + h…
Warning Line 432, Column 147: cannot generate system identifier for general entity "username"
…' + huid + '&groupid=' + hgroupid + '&username=' + huser + '&message=' + encod…

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 (Göz kırpma. 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 (Göz kırpma. 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 432, Column 147: general entity "username" not defined and no default entity
…' + huid + '&groupid=' + hgroupid + '&username=' + huser + '&message=' + encod…

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 432, Column 155: reference not terminated by REFC delimiter
… + '&groupid=' + hgroupid + '&username=' + huser + '&message=' + encodeURIComp…

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

Error Line 432, Column 155: reference to entity "username" for which no system identifier could be generated
… + '&groupid=' + hgroupid + '&username=' + huser + '&message=' + encodeURIComp…

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 432, Column 146: entity was defined here
…=' + huid + '&groupid=' + hgroupid + '&username=' + huser + '&message=' + enco…
Warning Line 432, Column 170: cannot generate system identifier for general entity "message"
…+ hgroupid + '&username=' + huser + '&message=' + encodeURIComponent(hmess) + …

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 (Göz kırpma. 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 (Göz kırpma. 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 432, Column 170: general entity "message" not defined and no default entity
…+ hgroupid + '&username=' + huser + '&message=' + encodeURIComponent(hmess) + …

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 432, Column 177: reference not terminated by REFC delimiter
…pid + '&username=' + huser + '&message=' + encodeURIComponent(hmess) + '&color…

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

Error Line 432, Column 177: reference to entity "message" for which no system identifier could be generated
…pid + '&username=' + huser + '&message=' + encodeURIComponent(hmess) + '&color…

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 432, Column 169: entity was defined here
… + hgroupid + '&username=' + huser + '&message=' + encodeURIComponent(hmess) +…
Warning Line 432, Column 212: cannot generate system identifier for general entity "color"
…age=' + encodeURIComponent(hmess) + '&color=' + hcolor + '&font=' + hfont + '&…

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 (Göz kırpma. 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 (Göz kırpma. 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 432, Column 212: general entity "color" not defined and no default entity
…age=' + encodeURIComponent(hmess) + '&color=' + hcolor + '&font=' + hfont + '&…

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 432, Column 217: reference not terminated by REFC delimiter
… + encodeURIComponent(hmess) + '&color=' + hcolor + '&font=' + hfont + '&bold=…

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

Error Line 432, Column 217: reference to entity "color" for which no system identifier could be generated
… + encodeURIComponent(hmess) + '&color=' + hcolor + '&font=' + hfont + '&bold=…

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 432, Column 211: entity was defined here
…sage=' + encodeURIComponent(hmess) + '&color=' + hcolor + '&font=' + hfont + '…
Warning Line 432, Column 233: cannot generate system identifier for general entity "font"
…onent(hmess) + '&color=' + hcolor + '&font=' + hfont + '&bold=' + hbold + '&it…

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 (Göz kırpma. 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 (Göz kırpma. 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 432, Column 233: general entity "font" not defined and no default entity
…onent(hmess) + '&color=' + hcolor + '&font=' + hfont + '&bold=' + hbold + '&it…

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 432, Column 237: reference not terminated by REFC delimiter
…t(hmess) + '&color=' + hcolor + '&font=' + hfont + '&bold=' + hbold + '&italic…

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

Error Line 432, Column 237: reference to entity "font" for which no system identifier could be generated
…t(hmess) + '&color=' + hcolor + '&font=' + hfont + '&bold=' + hbold + '&italic…

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 432, Column 232: entity was defined here
…ponent(hmess) + '&color=' + hcolor + '&font=' + hfont + '&bold=' + hbold + '&i…
Warning Line 432, Column 252: cannot generate system identifier for general entity "bold"
…lor=' + hcolor + '&font=' + hfont + '&bold=' + hbold + '&italic=' + hitalic + …

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 (Göz kırpma. 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 (Göz kırpma. 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 432, Column 252: general entity "bold" not defined and no default entity
…lor=' + hcolor + '&font=' + hfont + '&bold=' + hbold + '&italic=' + hitalic + …

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 432, Column 256: reference not terminated by REFC delimiter
…' + hcolor + '&font=' + hfont + '&bold=' + hbold + '&italic=' + hitalic + '&un…

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

Error Line 432, Column 256: reference to entity "bold" for which no system identifier could be generated
…' + hcolor + '&font=' + hfont + '&bold=' + hbold + '&italic=' + hitalic + '&un…

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 432, Column 251: entity was defined here
…olor=' + hcolor + '&font=' + hfont + '&bold=' + hbold + '&italic=' + hitalic +…
Warning Line 432, Column 271: cannot generate system identifier for general entity "italic"
…font=' + hfont + '&bold=' + hbold + '&italic=' + hitalic + '&underline=' + hun…

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 (Göz kırpma. 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 (Göz kırpma. 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 432, Column 271: general entity "italic" not defined and no default entity
…font=' + hfont + '&bold=' + hbold + '&italic=' + hitalic + '&underline=' + hun…

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 432, Column 277: reference not terminated by REFC delimiter
… + hfont + '&bold=' + hbold + '&italic=' + hitalic + '&underline=' + hunderlin…

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

Error Line 432, Column 277: reference to entity "italic" for which no system identifier could be generated
… + hfont + '&bold=' + hbold + '&italic=' + hitalic + '&underline=' + hunderlin…

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 432, Column 270: entity was defined here
…&font=' + hfont + '&bold=' + hbold + '&italic=' + hitalic + '&underline=' + hu…
Warning Line 432, Column 294: cannot generate system identifier for general entity "underline"
…+ hfont + '&bold=' + hbold + '&italic=' + hitalic + '&underline=' + hunderline;

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 (Göz kırpma. 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 (Göz kırpma. 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 432, Column 294: general entity "underline" not defined and no default entity
…+ hfont + '&bold=' + hbold + '&italic=' + hitalic + '&underline=' + hunderline;

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 432, Column 303: reference not terminated by REFC delimiter
…+ hfont + '&bold=' + hbold + '&italic=' + hitalic + '&underline=' + hunderline;

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

Error Line 432, Column 303: reference to entity "underline" for which no system identifier could be generated
…+ hfont + '&bold=' + hbold + '&italic=' + hitalic + '&underline=' + hunderline;

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 432, Column 293: entity was defined here
…+ hfont + '&bold=' + hbold + '&italic=' + hitalic + '&underline=' + hunderline;
Warning Line 451, Column 31: character "&" is the first character of a delimiter but occurred as data
if (request.readyState == 4 && request.status == 200)

This message may appear in several cases:

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

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 1106, Column 253: required attribute "alt" not specified
…g2tr.org/images/w.png" title="W3C Bot">, <img src="http://yulgang2tr.org/image…

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 1106, Column 254: end tag for "img" omitted, but OMITTAG NO was specified
…2tr.org/images/w.png" title="W3C Bot">, <img src="http://yulgang2tr.org/images…

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 1106, Column 192: start tag was here
…iyaretçi</b></a>] Bulunmaktadır.<br /><img src="http://yulgang2tr.org/images/w…
Error Line 1106, Column 317: required attribute "alt" not specified
…g2tr.org/images/w.png" title="W3C Bot">, <img src="http://yulgang2tr.org/image…

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 1106, Column 318: end tag for "img" omitted, but OMITTAG NO was specified
…2tr.org/images/w.png" title="W3C Bot">, <img src="http://yulgang2tr.org/images…

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 1106, Column 256: start tag was here
…r.org/images/w.png" title="W3C Bot">, <img src="http://yulgang2tr.org/images/w…
Error Line 1106, Column 385: required attribute "alt" not specified
….org/images/yx.png" title="Yandex Bot">, <img src="http://yulgang2tr.org/image…

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 1106, Column 386: end tag for "img" omitted, but OMITTAG NO was specified
…org/images/yx.png" title="Yandex Bot">, <img src="http://yulgang2tr.org/images…

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 1106, Column 320: start tag was here
…r.org/images/w.png" title="W3C Bot">, <img src="http://yulgang2tr.org/images/y…
Error Line 1106, Column 453: required attribute "alt" not specified
….org/images/yx.png" title="Yandex Bot">, <a href="http://yulgang2tr.org/uye-fa…

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 1106, Column 454: end tag for "img" omitted, but OMITTAG NO was specified
…org/images/yx.png" title="Yandex Bot">, <a href="http://yulgang2tr.org/uye-fat…

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 1106, Column 388: start tag was here
…g/images/yx.png" title="Yandex Bot">, <img src="http://yulgang2tr.org/images/y…
Error Line 1151, Column 327: there is no attribute "alt"
…href="http://www.ping-fast.com/" alt="ping fast my blog, website, or RSS fee…

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 1153, Column 62: required attribute "type" not specified
…mca.com/Badges/DMCABadgeHelper.min.js"></script><a href="http://www.dmca.com/P…

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

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

Error Line 1188, Column 9: end tag for element "div" which is not open
</div>

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 1207, Column 8: end tag for element "div" which is not open
</div>

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 1215, Column 25: document type does not allow element "div" here
<div id='social-sidebar'>

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

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

Error Line 1234, Column 23: document type does not allow element "style" here
<style type='text/css'>

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

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

Çevrimdışı usameavci
 Tarih: 15-07-2014, Saat:06:36
#2
Burada 49 hatayı tek tek açıklayacak biri çıkacağını sanmıyorum. Üşenmeyip google translate ile cümleleri çevirtebilirsiniz. Bu işten anlıyorsanız zaten çözersiniz. Anlamıyorsanızda hiç bulaşmayın, bilen birilerine yaptırın derim Melek - Masum
Bunu Beğenenler:

Çevrimdışı fatihcray09
 Tarih: 15-07-2014, Saat:07:51
#3
Açık Ağızlı Gülümseme anladım
Bunu Beğenenler:

 


Konu ile Alakalı Benzer Konular
Konular Yazar Yorumlar Okunma Son Yorum
  [MCTR - 1.8] MyBB Bana verdiği hataları yardımcı olun Brky 4 711 27-04-2015, Saat:21:42
Son Yorum: EmreKarakaya
  MyBB 1.8 Tema Resim Hataları SiberLeon 3 657 08-09-2014, Saat:01:30
Son Yorum: SiberLeon
  w3c Optimize Hakkında StaRFoX 2 460 14-07-2014, Saat:20:50
Son Yorum: StaRFoX
Hata [MD] Forum Hataları Nefes__ 1 836 03-08-2012, Saat:00:34
Son Yorum: Hakan Cengiz



Konuyu Okuyanlar: 1 Ziyaretçi