Wordpress Themes - WP Forum at BFA
There will be no more development for Atahualpa (or any other theme), and no support. Also no new registrations. I turned off the donation system. I may turn the forum to read only if it gets abused for spam. Unfortunately I have no time for the forum or the themes. Thanks a lot to the people who helped in all these years, especially Larry and of course: Paul. Take care and stay healthy -- Flynn, Atahualpa developer, Sep 2021

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

Need validation help - 53 errors and 9 warnings


  #1  
Old May 2, 2011, 03:59 PM
jlindseyjr
 
5 posts · May 2011
Hello, this is all new to me and I don't know anything about what these errors and warnings mean.
I'm using Atahualpa 3.6.4 and WP 3.1 I don't even know what to look for.
I guess I should put this in several posts because it's long.
Could someone offer some advice?

edited to add: url is http://freemlmtraining4u.com

Thanks
John

I git rid of the youtube vids, the facebook like plugin and the fb and twitter share plugin, and I'm down to 14 errors and 9 warnings, which I'm assuming are all theme related.

Validation Output: 14 Errors

Line 136, 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.
Line 144, 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.
Line 571, 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.
Line 689, 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).
Line 689, 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).
Line 695, 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).
Line 695, 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).
Line 696, 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).
Line 705, 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).
Line 764, 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).
Line 945, 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.
Line 1194, 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.
Line 1660, 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.
Line 2493, 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.
Line 2637, 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.
Line 2767, 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.
Line 2806, Column 70: end tag for "LI" omitted, but OMITTAG NO was specified
h6 { font-size: 1.15em; margin: 1.67em 0; font-weight: bold; }</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 ">".

Last edited by jlindseyjr; May 2, 2011 at 05:00 PM. Reason: remove corrected errors
  #2  
Old May 2, 2011, 04:01 PM
jlindseyjr
 
5 posts · May 2011
Line 764, Column 14: start tag was here
one link per <LI> and no text */
Line 2806, Column 70: end tag for "A" omitted, but OMITTAG NO was specified
h6 { font-size: 1.15em; margin: 1.67em 0; font-weight: bold; }</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 ">".

Line 705, Column 45: start tag was here
/* Then, add left border and padding to the <A> */
Line 2806, Column 70: end tag for "A" omitted, but OMITTAG NO was specified
h6 { font-size: 1.15em; margin: 1.67em 0; font-weight: bold; }</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 ">".

Line 696, Column 16: start tag was here
because if the <A>'s of the cateories widget were set to display:inline (defaul…
Line 2806, Column 70: end tag for "LI" omitted, but OMITTAG NO was specified
h6 { font-size: 1.15em; margin: 1.67em 0; font-weight: bold; }</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 ">".

Line 695, Column 85: start tag was here
…move the left border and padding from the <LI>. The margin stays on the <LI>'s
Line 2806, Column 70: end tag for "LI" omitted, but OMITTAG NO was specified
h6 { font-size: 1.15em; margin: 1.67em 0; font-weight: bold; }</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 ">".

Line 695, Column 55: start tag was here
…move the left border and padding from the <LI>. The margin stays on the <LI>'s
Line 2806, Column 70: end tag for "LI" omitted, but OMITTAG NO was specified
h6 { font-size: 1.15em; margin: 1.67em 0; font-weight: bold; }</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 ">".

Line 689, Column 67: start tag was here
widgets get the left border and padding on the <A> instead of the <LI>.
Line 2806, Column 70: end tag for "A" omitted, but OMITTAG NO was specified
h6 { font-size: 1.15em; margin: 1.67em 0; font-weight: bold; }</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 ">".

Line 689, Column 48: start tag was here
widgets get the left border and padding on the <A> instead of the <LI>.

Last edited by jlindseyjr; May 2, 2011 at 05:01 PM.
  #3  
Old May 2, 2011, 04:02 PM
jlindseyjr
 
5 posts · May 2011
cont'd...

removed facebook like plugin

Last edited by jlindseyjr; May 2, 2011 at 04:56 PM.
  #4  
Old May 2, 2011, 04:03 PM
jlindseyjr
 
5 posts · May 2011
cont'd...

Getting rid of the youtube vids took care of these.

Last edited by jlindseyjr; May 2, 2011 at 04:11 PM.
  #5  
Old May 2, 2011, 04:04 PM
jlindseyjr
 
5 posts · May 2011
cont'd

Getting rid of the youtube vids took care of these.

Last edited by jlindseyjr; May 2, 2011 at 04:12 PM.

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] W3C Validation 14 Errors 10 Warnings KatyDigg New Versions, & Updating 14 Feb 8, 2011 06:55 AM
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
Errors in loading the template appear to occur with header - errors below Gfeiste Header configuration & styling 3 Aug 9, 2009 10:45 AM


All times are GMT -6. The time now is 11:06 AM.


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