confused about compliance

kevinkap · Involved Joined: Apr 22, 2006 Posts: 350

Ok, I have had my theme made compliant and checked on a clean install of rn2.1. However when I upload it to my site it is not compliant. some errors are actually spelling errors but some are coding. The url is maysvillesports.com. Can someone please explain to me what is wrong?

Thanks.

jakec · Posted: Wed Apr 11, 2007 5:10 am

It is possible that some of the third party modules that you use on your site are introducing compliance errors.

What third party modules are you using?

montego · Posted: Wed Apr 11, 2007 6:38 am

Yes, jakec is right, but let me expound upon that as I just went through this effort on my own site (almost done) and this is what I found:

1) Non-compliant blocks
2) Non-compliant modules
3) Non-compliant data!

What is up with this last one? Well, prior to RN 2.10 and the new FCKEditor that is in there, many news articles and other potential content was added with HTML that was not forced to be compliant. For example, how many times have you seen people use a <br> tag instead of <br />, or open a <li> tag, but not close it.

What I finally did, was go Topic by topic (news) and found which articles were not compliant and simply clicked on "Edit" and then just re-saved them using the FCKEditor. The editor will correct ALL of these I have found.

Of course, that is if you wish your site to be compliant.

Now, I will also say that the BBtoNuke integration is NOT compliant in RN, nor any other nuke (that has been released anyways), so I'll be tackling that one LAST. That involves Forums, Private Messages and Members List modules.

kevinkap · Involved Joined: Apr 22, 2006 Posts: 350

well you can see it here.

Only registered users can see links on this board!
Get registered or login to the forums!

now some of it is the tags used in the stories, some have to do with gcalendar but some are stories archive, links m met authors and such

Gremmie · Posted: Wed Apr 11, 2007 3:04 pm

GCalendar is XHTML 1.0 transitional compliant. It is not adding that "&PHPSESSID=..." to the links.

That looks like some PHP session stuff.... Confused

Gremmie · Posted: Wed Apr 11, 2007 3:14 pm

It looks like something is tacking on those &PHPSESSID things, which are causing most of your problems. You also have some non-compliant data.

montego · Posted: Fri Apr 13, 2007 6:51 am

Do a search here on "PHPSESSID" and I think you will find an answer to this. It is an environment setting (host) somewhere on how PHP handles sessions. It should be using cookies and not the URL string.