Skocz do zawartości

Optymalizacja kody w3c

rasper1992

Przez rasper1992
w Strony przyjazne wyszukiwarkom

Rekomendowane odpowiedzi

rasper1992 Newbie

rasper1992

Opublikowano
Opublikowano

Witam, proszę o pomoc w anulowaniu błędów w kodowaniu strony.

NAJWAŻNIEJSZE <body> ?

</body>
  • You forgot to close a tag, or
  • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  1. Line 21, Column 315: document type does not allow element "TABLE" here 
    … ><table align="center" width="976" border="0" cellspacing="0" cellpadding="0">

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

  2. Line 27, Column 16: there is no attribute "BACKGROUND" 
    <td background="themes/portal/images/topa_01_02.png"  border="0" width="248" he…

    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.

  3. Line 27, Column 62: there is no attribute "BORDER" 
    …ound="themes/portal/images/topa_01_02.png"  border="0" width="248" height="26">

    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.

  4. Line 85, Column 24: document type does not allow element "DIV" here 
    <div style='float:left'>   <script type='text/javascript'>

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

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

  5. Line 96, 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).

  6. Line 546, Column 240: there is no attribute "CELLPADDING" 
    … class='panel' border='0' cellpadding='0' cellspacing='0'><center>Strefy Paker…

    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.

  7. Line 546, Column 256: there is no attribute "CELLSPACING" 
    …order='0' cellpadding='0' cellspacing='0'><center>Strefy Pakernia24</center></…

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

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

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

  8. Line 591, Column 6: end tag for "TABLE" omitted, but its declaration does not permit this 
    </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  9. Line 546, Column 85: start tag was here 
    …'0' width='100%'><tr><td width='100%'><table class='panel-border' cellSpacing=…
  10. Line 591, Column 6: end tag for "TABLE" omitted, but its declaration does not permit this 
    </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  11. Line 546, Column 1: start tag was here 
    <table border='0' cellpadding='0' cellspacing='0' width='100%'><tr><td width='1…
  12. Line 591, Column 6: end tag for "TABLE" omitted, but its declaration does not permit this 
    </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  13. Line 322, Column 1: start tag was here 
    <table width='100%' cellpadding='4' cellspacing='0' border='0'><tr><td valign='…
  14. error.png Line 593, Column 5: "TABLE" not finished but containing element ended 
    </td>
  15. Line 593, Column 5: end tag for "TABLE" omitted, but its declaration does not permit this 
    </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  16. Line 80, Column 1: start tag was here 
    <table width="976"   border="0" cellspacing="0" cellpadding="0" align="center">
  17. Line 596, Column 14: "TABLE" not finished but containing element ended 
    	</table></td></tr></table><table width='100%' cellspacing='0' cellpadding='0'>…
  18. Line 596, Column 14: end tag for "TABLE" omitted, but its declaration does not permit this 
    	</table></td></tr></table><table width='100%' cellspacing='0' cellpadding='0'>…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  19. Line 21, Column 171: start tag was here 
    …llspacing='0' cellpadding='0'><tr><td><table align='center' width='100%' cells…
  20. Line 756, Column 67: required attribute "TYPE" not specified 
    <script src='https://cookiealert.sruu.pl/CookieAlert-latest.min.js'></script>

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

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

  21. Line 757, Column 8: required attribute "TYPE" not specified 
    <script>

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

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

  22. Line 785, Column 8: required attribute "TYPE" not specified 
    <script>

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

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

Odnośnik do komentarza
Udostępnij na innych stronach
Aleksiejs Collaborator

Aleksiejs

Opublikowano
Opublikowano

Nie do końca wiem na co liczysz. Jeśli chcesz żeby ktoś za Ciebie poprawił błędy w kodzie to zleć to, jeśli chcesz sam to zrobić to google + to co wypluł walidator i można poprawiać ;)

Firia.pl - Blog pasjonatki wszystkiego co związane ze zdrowiem, odżywianiem oraz psychologią
Każdy czasem potrzebuje pięknych życzeń i wierszyków na najróżniejsze okazje - https://zyczeniowo.pl/ 

Odnośnik do komentarza
Udostępnij na innych stronach
rasper1992 Newbie

rasper1992

Opublikowano
  • Autor
Opublikowano

liczę tylko na podpowiedź do tego błędu, reszte gotowa.

NAJWAŻNIEJSZE <body> ?

</body>
  • You forgot to close a tag, or
  • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Odnośnik do komentarza
Udostępnij na innych stronach
Aleksiejs Collaborator

Aleksiejs

Opublikowano
Opublikowano

Nie zamknąłeś tagu body lub masz w kodzie coś co nie pozwala zwalidować kodu. Nie ma tu wróżek, bez kodu źródłowego nikt Ci nie pomoże.

Firia.pl - Blog pasjonatki wszystkiego co związane ze zdrowiem, odżywianiem oraz psychologią
Każdy czasem potrzebuje pięknych życzeń i wierszyków na najróżniejsze okazje - https://zyczeniowo.pl/ 

Odnośnik do komentarza
Udostępnij na innych stronach
Aleksiejs Collaborator

Aleksiejs

Opublikowano
Opublikowano

Co to za kod masakryczny?

Wywal wszystkie inline i daj style do pliku css

zamień wszystkie ' na "

Usuń tabelki i wykorzystaj divy

Firia.pl - Blog pasjonatki wszystkiego co związane ze zdrowiem, odżywianiem oraz psychologią
Każdy czasem potrzebuje pięknych życzeń i wierszyków na najróżniejsze okazje - https://zyczeniowo.pl/ 

Odnośnik do komentarza
Udostępnij na innych stronach

Zarchiwizowany

Ten temat przebywa obecnie w archiwum. Dodawanie nowych odpowiedzi zostało zablokowane.

Tematy

  • Ostatnio przeglądający   0 użytkowników

    • Brak zarejestrowanych użytkowników przeglądających tę stronę.
×
×
  • Dodaj nową pozycję...

Powiadomienie o plikach cookie

Umieściliśmy na Twoim urządzeniu pliki cookie, aby pomóc Ci usprawnić przeglądanie strony. Możesz dostosować ustawienia plików cookie, w przeciwnym wypadku zakładamy, że wyrażasz na to zgodę. Warunki użytkowania Polityka prywatności