Wordpress Themes - WP Forum at BFA
Click Here To DONATE! Support the theme development, get more attention and additional benefits based on your donation level. Your forum name will be highlighted.

Wordpress Themes - WP Forum at BFA » WordPress Themes » Atahualpa 3 Wordpress theme » New Versions, & Updating »

[SOLVED] W3C Validation 14 Errors 10 Warnings


Build custom WP THEMES, without
coding.
Click here for THEMEFRAME

From the author of Atahualpa, the #1 most
downloaded (700,000+) theme @ wordpress.org
  #1  
Old Feb 6, 2011, 12:41 PM
KatyDigg's Avatar
KatyDigg
 
318 posts · Jul 2009
[SOLVED] W3C Validation 14 Errors 10 Warnings

Previously, W3C Validation PASSED with WP 3.0.4 > Atahualpa 3.5.3

however, now...

have updated Atahualpa 3.5.3 with download and manual installation of Atahualpa 3.6.4

W3C Validation has Failed with 14 Errors, 10 Warnings.



PS. All plugins deactivated.
__________________
UniServer | WP 4.0 | ThemeFrame 1.2.6 | Montezuma 1.2.2 | ATA 3.7.18

Last edited by KatyDigg; Feb 7, 2011 at 06:28 AM. Reason: PS.
  #2  
Old Feb 7, 2011, 04:52 AM
juggledad's Avatar
juggledad
 
22,253 posts · Mar 2009
OSX 10.8.5 WP 3.8.x Atahualpa 3.7.x Safari 6.x Firefox 25 XP
what is the url?
__________________
"Tell me and I forget, teach me and I may remember, involve me and I learn." - Benjamin Franklin
Juggledad | Forum Moderator/Support
  #3  
Old Feb 7, 2011, 08:03 AM
juggledad's Avatar
juggledad
 
22,253 posts · Mar 2009
OSX 10.8.5 WP 3.8.x Atahualpa 3.7.x Safari 6.x Firefox 25 XP
I took a quick look at your site in the validator and it seems that the validator does not ignore comments. ie. if you have
HTML Code:
/* The pages widget gets "block" because it usually has only 
one link per <LI> and no text */
it flags the <li> as an error. Looks like the validator has some short comings....
__________________
"Tell me and I forget, teach me and I may remember, involve me and I learn." - Benjamin Franklin
Juggledad | Forum Moderator/Support
  #4  
Old Feb 7, 2011, 10:03 AM
KatyDigg's Avatar
KatyDigg
 
318 posts · Jul 2009
My "test" site has only one posting, and as I said previously, with ATA 3.5.3 it had passed W3C.

When I switch theme to
WP default theme and run W3C validation ... all clear and passes.

But then with ATA 3.6.4 the result is...

Validation Output: 14 Errors, 10 warnings.

1. Warning Line 111, Column 31: character "&" is the first character of a delimiter but occurred as data

/* reset "break-word" for pre & wp-syntax: */



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.

2. Warning Line 119, Column 31: character "&" is the first character of a delimiter but occurred as data

---------- WRAPPER, CONTAINER & LAYOUT ------------------------------



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.

3. Warning Line 546, Column 10: character "&" is the first character of a delimiter but occurred as data

in IE 6 & 7 */



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.

4. Error Line 664, Column 50: element "A" undefined

widgets get the left border and padding on the <A> instead of the <LI>.



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

5. Error Line 664, Column 70: element "LI" undefined

widgets get the left border and padding on the <A> instead of the <LI>.



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

6. Error Line 670, Column 58: element "LI" undefined

…move the left border and padding from the <LI>. The margin stays on the <LI>'s



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

7. Error Line 670, Column 88: element "LI" undefined

…move the left border and padding from the <LI>. The margin stays on the <LI>'s



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

8. Error Line 671, Column 18: element "A" undefined


because if the <A>'s of the cateories widget were set to display:inline (defaul…



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

9. Error Line 680, Column 47: element "A" undefined

/* Then, add left border and padding to the <A> */



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

10. Error Line 739, Column 17: element "LI" undefined

one link per <LI> and no text */



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

11. Warning Line 928, Column 48: character "&" is the first character of a delimiter but occurred as data

/*-------------------- ICONS in KICKER, BYLINE & FOOTER ---*/



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.

12. Warning Line 1210, Column 19: character "&" is the first character of a delimiter but occurred as data

---------- TABLES & CALENDAR ----------------------------------------



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.

13. Warning Line 1677, Column 19: character "&" is the first character of a delimiter but occurred as data

/* For accordion & tabs*/



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.

14. Warning Line 1786, Column 22: character "&" is the first character of a delimiter but occurred as data

height: auto; /* FF & Safari need auto */



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.
__________________
UniServer | WP 4.0 | ThemeFrame 1.2.6 | Montezuma 1.2.2 | ATA 3.7.18

Last edited by KatyDigg; Feb 7, 2011 at 10:07 AM.
  #5  
Old Feb 7, 2011, 10:04 AM
KatyDigg's Avatar
KatyDigg
 
318 posts · Jul 2009
15. Warning Line 2521, Column 24: character "&" is the first character of a delimiter but occurred as data

/* divs added for "IE6 & 2 menu styles" */



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.

16. Warning Line 2665, Column 56: character "&" is the first character of a delimiter but occurred as data

* HACKS : Suckerfish w/Form Field Support (for IE 5.5 & 6.x)



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.

17. Warning Line 2795, Column 28: character "&" is the first character of a delimiter but occurred as data

---------- HACKS: Clearfix & others ---------------------------------



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.

18. Error Line 2962, Column 9: end tag for "LI" omitted, but OMITTAG NO was specified

}</style>



You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
19. Info Line 739, Column 14: start tag was here

one link per <LI> and no text */

20. Error Line 2962, Column 9: end tag for "A" omitted, but OMITTAG NO was specified

}</style>



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

21. Info Line 680, Column 45: start tag was here

/* Then, add left border and padding to the <A> */

22. Error Line 2962, Column 9: end tag for "A" omitted, but OMITTAG NO was specified

}</style>



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

23. Info Line 671, Column 16: start tag was here

because if the <A>'s of the cateories widget were set to display:inline (defaulů

24. Error Line 2962, Column 9: end tag for "LI" omitted, but OMITTAG NO was specified

}</style>



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

25. Info Line 670, Column 85: start tag was here

ůmove the left border and padding from the <LI>. The margin stays on the <LI>'s

26. Error Line 2962, Column 9: end tag for "LI" omitted, but OMITTAG NO was specified

}</style>



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

27. Info Line 670, Column 55: start tag was here

ůmove the left border and padding from the <LI>. The margin stays on the <LI>'s

28. Error Line 2962, Column 9: end tag for "LI" omitted, but OMITTAG NO was specified

}</style>



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

29. Info Line 664, Column 67: start tag was here

widgets get the left border and padding on the <A> instead of the <LI>.

30. Error Line 2962, Column 9: end tag for "A" omitted, but OMITTAG NO was specified

}</style>



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

31. Info Line 664, Column 48: start tag was here

widgets get the left border and padding on the <A> instead of the <LI>.
__________________
UniServer | WP 4.0 | ThemeFrame 1.2.6 | Montezuma 1.2.2 | ATA 3.7.18
  #6  
Old Feb 7, 2011, 10:10 AM
KatyDigg's Avatar
KatyDigg
 
318 posts · Jul 2009
All of which, looks very much like this posting dated Jan 09, 2011

http://forum.bytesforall.com/showthread.php?t=12138
__________________
UniServer | WP 4.0 | ThemeFrame 1.2.6 | Montezuma 1.2.2 | ATA 3.7.18

Bookmarks

Tags
ata 3.6.4, w3c validation, wp 3.0.4, wp 3.0.5

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads
Thread Thread Starter Forum Replies Last Post
Atahualpa 3.6 - Validation Errors & Firefox will not show favicon hlanggo New Versions, & Updating 1 Jan 10, 2011 11:42 AM
W3C Validation Errors! pyoterguru Center area post/pages 1 Jan 5, 2011 07:15 AM
Ampersands Causing Validation Errors webgurl Header configuration & styling 0 Dec 7, 2010 09:00 PM
W3C Validation eschweiler1986 Atahualpa 3 Wordpress theme 3 Sep 27, 2009 12:45 PM
Help! My Atahualpa blog has awful W3C validation. Tomo9 Plugins & Atahualpa 0 Sep 10, 2009 01:19 PM


All times are GMT -6. The time now is 05:18 AM.


Powered by vBulletin® Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.