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 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 is http://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.

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

477 user(s) are online (100 user(s) are browsing Support Forums)


Members: 0


Guests: 477


more...

Donat-O-Meter

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

Latest GitHub Commits