1
nmshah
how to make xoops w3c compliant
  • 2007/9/7 16:42

  • nmshah

  • Just can't stay away

  • Posts: 556

  • Since: 2007/7/2 8


i just tried the w3c validator on my site. i was using the default theme. It showed some 39 error.

2
aph3x
Re: how to make xoops w3c compliant
  • 2007/9/7 16:59

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


default theme is valid w3c...valid since the 2.1.0
Everything I'm not made me everything I am
The Themes

3
Will_H
Re: how to make xoops w3c compliant
  • 2007/9/7 17:18

  • Will_H

  • Friend of XOOPS

  • Posts: 1786

  • Since: 2004/10/10


More times than not it is your content that is invalid... not the theme. Granted not all theme developers concern themselves with compliance, but most do.

Did you know that <a...><img></a> is not valid.... talk about harsh...

4
nmshah
Re: how to make xoops w3c compliant
  • 2007/9/7 17:22

  • nmshah

  • Just can't stay away

  • Posts: 556

  • Since: 2007/7/2 8


i m on 2.0.17
my default module is mastop publish, can this be the reason for errors

edited
my site url ishttp://makingdestiny.com

i have set default module as none. Rechecked with the validator, it still says 14 errors, these are:

Validation Output: 14 Errors

1. Error Line 46, Column 48: document type does not allow element "style" here.

<div class="blockContent"><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).
2. Error Line 127, Column 38: character ";" not allowed in attribute specification list.

for (var i=0; i<menuids7743.length; i++){


3. Error Line 127, Column 38: element "menuids7743.length" undefined.

for (var i=0; i<menuids7743.length; i++){



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).
4. Error Line 129, Column 37: character ";" not allowed in attribute specification list.

for (var t=0; t<ultags.length; t++){


5. Error Line 129, Column 37: element "ultags.length" undefined.

for (var t=0; t<ultags.length; t++){



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 169, Column 8: end tag for "ultags.length" omitted, but OMITTAG NO was specified.

</script>



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

for (var t=0; t<ultags.length; t++){

8. Error Line 169, Column 8: end tag for "menuids7743.length" omitted, but OMITTAG NO was specified.

</script>



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

for (var i=0; i<menuids7743.length; i++){

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

…ips' >Health, Goals, Honesty, People & Relationships</a></li>



This message may appear in several cases:
* You tried to include the "<" character in your page: you should escape it as "<"
* You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
* Another possibility is that you forgot to close quotes in a previous tag.
11. Error Line 127, Column 38: XML Parsing Error: error parsing attribute name.

for (var i=0; i<menuids7743.length; i++){


12. Error Line 127, Column 38: XML Parsing Error: attributes construct error.

for (var i=0; i<menuids7743.length; i++){


13. Error Line 127, Column 38: XML Parsing Error: Couldn't find end of Start Tag menuids7743.length line 127.

for (var i=0; i<menuids7743.length; i++){


14. Error Line 129, Column 37: XML Parsing Error: error parsing attribute name.

for (var t=0; t<ultags.length; t++){


15. Error Line 129, Column 37: XML Parsing Error: attributes construct error.

for (var t=0; t<ultags.length; t++){


16. Error Line 129, Column 37: XML Parsing Error: Couldn't find end of Start Tag ultags.length line 129.

for (var t=0; t<ultags.length; t++){


17. Error Line 182, Column > 80: XML Parsing Error: xmlParseEntityRef: no name.

…es/mastop_publish/?tac=Health%2C_Goals%2C_Honesty%2C_People_%26_Relationships…

5
skenow
Re: how to make xoops w3c compliant
  • 2007/9/7 17:31

  • skenow

  • Home away from home

  • Posts: 993

  • Since: 2004/11/17


Well, the default theme may be valid w3c, but there are some system templates that do not validate. A patch is provided here - SF patch 1712443

The templates had not changed in the 2.3.x branch and these do work with 2.0.17.

There is also some html generated in the code that has not been moved to templates, yet, and needs to be validated, too.

6
aph3x
Re: how to make xoops w3c compliant
  • 2007/9/7 17:34

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


Especially that you have 2.0.17 as theme was revised again :).
might be the module ..I'm not familiar with it so i can't say anything..however i can say that is like Biteronboard said and with the modules if not worse...there aren't any w3c compliant modules...yet
Everything I'm not made me everything I am
The Themes

7
nmshah
Re: how to make xoops w3c compliant
  • 2007/9/7 17:48

  • nmshah

  • Just can't stay away

  • Posts: 556

  • Since: 2007/7/2 8


so if the modules are not w3c compliant, any way to work around it.

8
nmshah
Re: how to make xoops w3c compliant
  • 2007/9/7 17:53

  • nmshah

  • Just can't stay away

  • Posts: 556

  • Since: 2007/7/2 8


the patch is for XOOPS 2.3.0

anything available for 2.0.17 or even 2.0.16.
and also shouldn,t these templates been modified in the 2.0.17 release.

9
nmshah
Re: how to make xoops w3c compliant
  • 2007/9/7 17:55

  • nmshah

  • Just can't stay away

  • Posts: 556

  • Since: 2007/7/2 8


so anything that can i do now?

10
skenow
Re: how to make xoops w3c compliant
  • 2007/9/7 18:00

  • skenow

  • Home away from home

  • Posts: 993

  • Since: 2004/11/17


Quote:

skenow wrote:

The templates had not changed in the 2.3.x branch and these do work with 2.0.17.


This does apply for 2.0.16/2.0.17

The 2.0.17 release focused on other things - not the templates. phppp has posted he will work on this next week.

To get around the module templates problems, you can rewrite them and override them so they do validate. I would suggest you submit any changes you make to the modules' authors, though, so they can add them to their next release.

Login

Who's Online

223 user(s) are online (138 user(s) are browsing Support Forums)


Members: 0


Guests: 223


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Mar 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits