Rok założenia: 2008Kontakt
wszystko o serwisach WWW, głównie od strony technicznej (XHMTL, CSS, PHP, MySQL)
Poinformuj znajomych o tym wątku
Poinformuj znajomych na Facebook-u o tym wątku Poinformuj innych ludzi na Wykopie o tym wątku Poinformuj znajomych na Twitter-ze o tym wątku Poinformuj znajomych na Blip-ie o tym wątku Poinformuj znajomych na Buzz-ie o tym wątku Poinformuj znajomych na GG o tym wątku

Re: Walidacja W3C

Postprzez Subduer
napisane: 25 Mar 2010, o 08:21

  • Poinformuj znajomych na Facebook-u o tym wątku
  • Poinformuj innych ludzi na Wykopie o tym wątku
  • Poinformuj znajomych na Twitter-ze o tym wątku
  • Poinformuj znajomych na Blip-ie o tym wątku
  • Poinformuj znajomych na Buzz-ie o tym wątku
  • Poinformuj znajomych na GG o tym wątku
 
Właśnie, pomijając lenistwo i brak chęci współpracy z validatorem typu "bo po co?", bo do tego można się przekonać i skoro się robi, to można robić dobrze... to problemem są te edytory WYSIWYG w CMSach, sklepach, czy czasem skrypty, które się wykorzystuje, bo czasem nie ma sensu robić czegoś od zera, skoro ktoś coś wymyślił. Wtedy i błędy się pojawiają.

Ale nie zgodzę się z jedną rzeczą. :D
Fajne jest porównanie z ortografią, ale nie zgodzę się w 100%. Jak ktoś pisze z błędami ortograficznymi, rzuca się to od razu w oczy, jak ktoś pisze stronę z błędami walidacji, nie rzuca się to tak w oczy (no chyba, że robi totalne babole, ale to to samo co z "nie chcem ale muszem")... z pisaniem stron niewalidowanych można by lepiej porównać do mówienia z błędami ortogrficznymi (jeśli oczywiście byłoby to możliwe), bo na pierwszy rzut oka (ucha) nikt nie wie, że te błędy są obecne, a przekaz jest ten sam, wszyscy rozumieją i są zadowoleni, bez różnicy, że rozmówca myśli, że mówi "charcesz" a nie "harcerz".

No ale oczywiście to tylko moje zdanie i po Waszych postach powoli zaczynam się przekonywać do walidacji.

Awatar użytkownika
Subduer
 
Posty: 30
Rejestracja: 10 Lut 2010
Miejscowość: Jabłonna


PROBLEM Z WALIDACJĄ STRONY - POMOCY

Postprzez lukas
napisane: 28 Lip 2011, o 10:33

  • Poinformuj znajomych na Facebook-u o tym wątku
  • Poinformuj innych ludzi na Wykopie o tym wątku
  • Poinformuj znajomych na Twitter-ze o tym wątku
  • Poinformuj znajomych na Blip-ie o tym wątku
  • Poinformuj znajomych na Buzz-ie o tym wątku
  • Poinformuj znajomych na GG o tym wątku
 
Witam!

Chciałbym się dowiedzieć jak pozbyć się tych błędów na stronie - strona w wordpress, poniżej log z validatora:

POMOCY:)

Validation Output: 14 Errors

Error Line 221, Column 98: required attribute "type" not specified

…ect.facebook.net/en_US/all.js#xfbml=1"></script><fb:like-box href="http://www.…

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 221, Column 126: there is no attribute "href"

…s#xfbml=1"></script><fb:like-box href="http://www.facebook.com/pages/ALCOR-Bus…



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 221, Column 212: there is no attribute "width"

…rtner-Sp-z-o-o/212153468813018" width="164" colorscheme="dark" show_faces="tru…



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 221, Column 230: there is no attribute "colorscheme"

…153468813018" width="164" colorscheme="dark" show_faces="true" stream="false" …


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 221, Column 248: there is no attribute "show_faces"

…h="164" colorscheme="dark" show_faces="true" stream="false" header="true"></fb…


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 221, Column 262: there is no attribute "stream"

…cheme="dark" show_faces="true" stream="false" header="true"></fb:like-box></ce…


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 221, Column 277: there is no attribute "header"

…k" show_faces="true" stream="false" header="true"></fb:like-box></center></div>


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

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

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

…k" show_faces="true" stream="false" header="true"></fb:like-box></center></div>


You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Error Line 268, Column 193: end tag for element "span" which is not open

…-content/uploads/image/baner_01_czysty.png" width="153" /></a></span></p></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 268, Column 197: end tag for element "p" which is not open

…-content/uploads/image/baner_01_czysty.png" width="153" /></a></span></p></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 289, Column 7: element "right" undefined

<right><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2F…



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 289, Column 397: there is no attribute "allowTransparency"

…w:hidden; width:164px; height:21px;" allowTransparency="true"></iframe><right/>


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 289, Column 420: element "right" undefined

…w:hidden; width:164px; height:21px;" allowTransparency="true"></iframe><right/>


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 290, Column 10: end tag for "right" omitted, but OMITTAG NO was specified

</div>


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

Info Line 289, Column 1: start tag was here

<right><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2F…

lukas
 
Posty: 1
Rejestracja: 28 Lip 2011

walidacja

Postprzez Krzysztof Trynkiewicz
napisane: 29 Sie 2011, o 00:30

  • Poinformuj znajomych na Facebook-u o tym wątku
  • Poinformuj innych ludzi na Wykopie o tym wątku
  • Poinformuj znajomych na Twitter-ze o tym wątku
  • Poinformuj znajomych na Blip-ie o tym wątku
  • Poinformuj znajomych na Buzz-ie o tym wątku
  • Poinformuj znajomych na GG o tym wątku
 
Nie zwalidujesz raczej widgetu facebooka - to ich kod i nic na to nie poradzisz. Trudno, te 3-8 bledow na stronie bedziesz mial.
Ja walidacje traktuje przede wszystkim jako cos osobistego :P Wyznacznik robienia solidnej, dopracowanej roboty. Jak wspomnial ktos wyzej, walidacja sama wychodzi profesjonaliscie bez myslenia o tym, a jak jest jakis blad, tzn. ze zrobil literowke w znaczniku - a wtedy faktycznie trzeba to naprawic, bo sie rozne cuda moga dziac w roznych przegladarkach. Takze wg mnie olewanie walidacji jest bardzo zlym pomyslem.

Awatar użytkownika
Krzysztof Trynkiewicz
 
Posty: 461
Rejestracja: 28 Sie 2011


Poprzednia

Wróć do Tworzenie stron

Kto jest na forum

Użytkownicy przeglądający to forum: Brak zarejestrowanych użytkowników oraz 1 gość