XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. Xoops Development / 
  3. Roadmap 
  4.  / Make it XHTML 1.0 compliant please!
Register
1
MosesTycoon
Make it XHTML 1.0 compliant please!

I haven't got the time to browse alle entries here @ Roadmap forum, but if this was mentioned somewhere else, just forget it

Is there a possibility to make XOOPS XHTML 1.0 compliant? At the moment my portal (xoops 2.0.5) *generates* more than 200 errors and warnings...
2
robekras
Re: Make it XHTML 1.0 compliant please!

  • 2003/11/9 18:05

  • robekras

  • Documentation Writer

  • Posts: 187

  • Since: 2002/12/10


To be more helpfully here are some lines for one of the
causes of the non-compliance to XHTML (which is the single & instead of &)

in modules/newbb/include/notification.inc.php line 56
in modules/newbb/delete.php line 52, 57, 74
in modules/newbb/edit.php line 64, 83, 101
in modules/newbb/post.php line 126, 142, 182
in modules/newbb/reply.php line 43, 47, 71, 91

Hope this is helpful for one of the developers.
3
onokazu
Re: Make it XHTML 1.0 compliant please!

  • 2003/11/9 18:16

  • onokazu

  • XOOPS Founder

  • Posts: 617

  • Since: 2001/12/13


Which theme are you using? XOOPS is almost completely xhtml 1.0 transitional compliant when using the default theme. There are, however, some pages that aren't, especially in the modules.
4
robekras
Re: Make it XHTML 1.0 compliant please!

  • 2003/11/9 20:19

  • robekras

  • Documentation Writer

  • Posts: 187

  • Since: 2002/12/10


There is also an non-compliant output when a XoopsFormHidden
is used.
A XoopsFormHidden within a XoopsForm is outputted without
the environment.

It's true for both the template output and the direct output.
(See class/xoopsform/themeform.php function render () : line 102)
But with a surrounding the output (see the
5
gstarrett
Re: Make it XHTML 1.0 compliant please!

  • 2003/11/9 21:22

  • gstarrett

  • Friend of XOOPS

  • Posts: 174

  • Since: 2002/3/12


Quote:

robekras wrote:
There is also an non-compliant output when a XoopsFormHidden
is used.
A XoopsFormHidden within a XoopsForm is outputted without
the environment.


Perhaps getting rid of the tables-for-layout of XoopsForm would work... Not that it's always a bad thing, just has it's limitations.
6
MosesTycoon
Re: Make it XHTML 1.0 compliant please!

Quote:
Which theme are you using? XOOPS is almost completely xhtml 1.0 transitional compliant when using the default theme. There are, however, some pages that aren't, especially in the modules.


Well my theme is not very representative, as it is a (very) hacked version of x2t. (See it at localfoo.info), so the 200 errors and warnings are partially my fault. I have also some special modules integrated (ipb, mantis, etc.). So as mentioned above...

But if you follow this link to the validator you will find out, that http://www.xoops.org as well gets something around 100 errors and warnings...

Cheers Chris
7
MosesTycoon
Re: Make it XHTML 1.0 compliant please!

Mainly these are opened, but non-closed tags...
8
sunsnapper
Re: Make it XHTML 1.0 compliant please!

Well, this makes me feel a little better about the 9 errors I get. I think most of my errors are being caused by the fact that I'm beginning a form before I'm supposed to get IE 5.5 to render the search box in the right place.

Given that it's an intentional error, I guess I'll let these nine errors live until I move to a table-free layout.

validation link

http://www.brilliantenergy.com/
9
mvandam
Re: Make it XHTML 1.0 compliant please!

  • 2003/11/13 7:50

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Quote:

There is also an non-compliant output when a XoopsFormHidden
is used.
A XoopsFormHidden within a XoopsForm is outputted without
the environment.

I don't think input elements (e.g. hidden) are required to be inside anything (other than the form) in XHTML 1.0 transitional. This is what XOOPS strives to support right now. In stricter XHTML all form inputs are required to be within a block-level element (but not necessarily a table row, it could simply be a 'div').

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

161 user(s) are online (111 user(s) are browsing Support Forums)

Members: 0

Guests: 161

more...

Donat-O-Meter

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

Latest GitHub Commits