Your Account and html 401

Worker Joined: Nov 22, 2004 Posts: 208 Location: Italy

Ok , i dont know why, but i can't have the your account module validate HTML 4.01
I'm using ravennuke 2.02 but even with fisubice theme I get 11 errors and 64 warnings. (warnings are from sommaire parametrable)
The errors are:
Unexpected </form>
Unexpected </font>
Missing </font>
repeated several times

Funny, this site says 0 erros and 3 warnings.
All the rest of my site is just fine.
Is "Your Account" on this site different from the one in the distribution?
Guido

Regular Joined: Jun 02, 2004 Posts: 88

After blazing thru all the original 7.6 code, I found a lot of what you are seeing. Generally if you get those errors, there is not a starting tag to correspond with those ending tags. Missing would imply that there is not a corresponding ending tag to the start tag.

Some of the issue may also be with what order the closing tags are placed in the code. The closing tags must be placed in exact reverse order of the opening tags.... mirror image so to speak.

....not sure if the above is your problem, but I did find all of that in the nuke code.

Posted: Thu Apr 13, 2006 1:18 pm

Yes, the your account code is rather messed up..
Most of the errors were on the navbar.php (there was a orphan </form> some random <center> and some missing closing tags)
but the most common problem (not only into Your account, but everywhere) is with <font class="content"> this tag is invalid before <tables>, inside paragraphs etc.
If you use the Wysiwyg editor, every piece of content you write, will make the page 401 invalid just because of the <font>.
Another problem very common is with <form>: I found <table><form blah blah><tr><td>input= blah blah</td></tr></form></table> that will Never validate Rolling Eyes

Too bad the problem is deep inside of php-nuke, so every upgrade is a pain in da butt.... (hours of file compare to fix it all)
Wonder when that FB guy, will start to listen.....

Guido

Posted: Fri Apr 14, 2006 9:48 am

Quote:

Wonder when that FB guy, will start to listen.....

Do not hold your breath...

We are on our own. Others have corrected the code (64bitguy), but have not released it, and others have tried as well. You are correct, it makes every new patch that much more difficult to deal with.

No solutions, just answers... Laughing

Posted: Fri Apr 14, 2006 12:14 pm

Well, my "new" yummyfood.net will be 401 valid every where (except all the admin area)
I'm still testing it on my local machine, but it's going pretty good.
I'm waiting the latest rn76 to go live.
what did i do?
messed up with my main theme (sunset)
(deleted <font class="content"> in several places so it doesnt conflict with the HTML editor.
moved almost everything on the style.css (I merged style.css and forums.css)
Deleted everything related to css from the overallheader.tpl: now I do not have the double <head> anymore when displaying forums
changed news/index.php
changed news/comment.php (there where a </form> too much)
changed your_account/index.php and navbar.php (again unfinished tags or redundant tags>
changed encyclopedia/index.php (wrong nesting as usual)
in mainfile.php i changed <font class="content> to class="title" for modules titles (that's only cosmetic stuff but it looks better imho)
changed footer.php (dropped font class="footmsg"> so i can use <div> and
<table>. Created CSS elements for footer.
changed weblinks redirect from 302 moved temporarily to 301 moved permanently
For better SEO I still need to fix encyclopedia to go to a custom 404.php page when an encyclopedia or a term has been removed.
Same for inactive modules. (instead of "sorry this module isn't active" goto 404.php)
The problem is: my php skills are close to zero... Very Happy

Guido

Posted: Fri Apr 14, 2006 12:28 pm

Well, it sounds like your skills are better than you think. Wink

Not sure yet whether we are going to focus on W3C compliance with RN76 2.10.00 release... I think it to be a good idea, but with it comes alot of on-going work. Keep an eye on the RavenNuke76 Announcements and maybe it will be "in scope".

Posted: Fri Apr 14, 2006 12:51 pm

Hell! my goal is to have a better ranking than foodnetwork with 1/1,000,000 of their budget LOL! so i'm trying everything Very Happy

If you want, i can send my files, so you can diff and see what's wrong (beside my coding).
Guido

Posted: Fri Apr 14, 2006 2:10 pm

No need... I've seen the W3C validation results... UGLY! Laughing

registered · Worker Joined: Jan 07, 2005 Posts: 163

think everyone needs to come up with a standard theme css and template so that we can convert all themes to it rather than just make "our" theme compliant, we also need theme designers to follow this standardized set. As Raven said before its a challenge but if we could make a default css and then recoded the themes, we could offer the entire package. Smile

Posted: Fri Apr 14, 2006 4:49 pm

daemon, not quite. Themes are relatively "easy" to make W3C compliant. The problem is that the core nuke code that also renders HTML (through "echo" and "print" statements) in many cases is not compliant. In addition, nuke does nothing to ensure the news articles and other submissions from others is compliant. So, you can have a compliant theme, such as the fisubice theme distributed with RavenNuke76, but your nuke site may not be.

Posted: Sat Apr 29, 2006 1:46 am

If you give your users a very basic toolbar for the FCK editor bold ,italic, list, url, and couple of font sizes, 99% of posts will be 4.01.
Some problems may come with special characters but not so much..
of course you need to get rid of <font class=content> in your theme.
Guido

Posted: Sun Apr 30, 2006 9:18 am

guidyy, excellent advice! Thank you.