Page 2 of 4
xhtml!
Posted: Mon 23. Feb 2004, 17:24
by ionrock
Please post a patch as soon as possible for making phpwcms xhtml compliant. This would be really great. Thanks to those working on it and three cheers for making the best cms standards compliant
Posted: Tue 24. Feb 2004, 23:39
by meneceo
http://www.mastermelzo.it/
I am building this small site with phpWCMS. The output is valid Xhtml 1 (transitional), I sent the files to Olivier: I think he is checking if all is okay.
@Olivier
Please note that in the files I sent to you there are some "bad" tags yet... I forgot that in xhml you can't write onClick or onMouseOver, but you have to write onclick and onmouseover. The background image (if set) should also be inserted in a style="background-image: url(blahblah)" parameter (just extend the "hack" I put in front.func.inc.php).
If you want, I can obviously send the corrected pack to you...
Posted: Wed 25. Feb 2004, 00:05
by Oliver Georgi
@meneceo
Nice work. I'm glad to see results with phpwcms
You can send patched files again via email. I will release it on weekend.
Regards
Oliver
Posted: Wed 25. Feb 2004, 00:47
by gent
sounds very nice, so i dont try to do the same work with HTML4.
i just wait for the next release ...
thanks again for the very nice work here.
Posted: Wed 25. Feb 2004, 01:05
by Fulvio Romanin
wow
a new release this weekend too
wonder which other improvement there will be.... (wink wink nudge nudge)
Posted: Wed 25. Feb 2004, 01:34
by Oliver Georgi
me too
Posted: Wed 25. Feb 2004, 03:37
by Fulvio Romanin
Posted: Tue 6. Apr 2004, 14:37
by gent
any news about XHTML ?
the last release-update use a " HTML 4.01 Transitional"-doctype
Posted: Tue 6. Apr 2004, 14:49
by frold
When inserting images via spaw images miss the ALT="" tag howto fix it? anyone who knew that?
Posted: Tue 6. Apr 2004, 15:00
by Jérôme
Normally, the ALT-Tag is not intended just to be empty, but to provide people that have graphics turned off in their browser or who can't see (blind people, ever heard of barrier-free web sites?) with information about what the picture shows.
That's why I think that this is a task for the developers of SPAW to include the function to add suggestive ALT-attributes to images.
But I think you are not so much interested in such philosophical questions than in an answer to your question
.
I have not tested it, but I think the solution can be found in include/inc_ext/spaw/dialogs/img.php
Search after the function
okClick with the line
Code: Select all
iProps.alt = (img_prop.calt.value)?(img_prop.calt.value):'';
As I said, I haven't looked deeply in the code, but this line seems to do what is asked by you. Why it doesn't work: I don't know.
Anyway I think the solution can be found in this file somewhere...
Posted: Tue 6. Apr 2004, 15:43
by Jan212
i've validate the whole null212.de site - what a f**cking work. every spacer has no alt tag defined, the body topmargins aren't excisting in correct html and so on.
my only advice i could give to you is to go through every line which is declared form the validator.w3c.org
if you'll need to know where some things are, post with a detailled explanation, i'll perhaps know the answer
Posted: Tue 6. Apr 2004, 15:46
by frold
well I do not know what release you are using but there was no problem in getting my site validated...I had some problem with my template getting valid but it had nothing to do with phpwcms frontend which is w3c html 4.01 valid...
Posted: Tue 6. Apr 2004, 15:48
by gent
u have to disable the topmargins at the admin-layout-section , and have to add the "margin"-tag to your body-section at the css. this will work.
if i understand it right , then the phpwcms want to be switched from HTML to XHTML. so, if there is not set the Doctype the validator will report every <br /> as a bad tag.
Posted: Tue 6. Apr 2004, 15:50
by frold
gent wrote:u have to disable the topmargins at the admin-layout-section , and have to add the "margin"-tag to your body-section at the css. this will work.
That killed alot if my errors
Posted: Tue 6. Apr 2004, 15:53
by Jérôme
As far as I know, the upcoming version is to be W3C-valid, but not XHTML and W3C-valid, or am I wrong?
