Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...XHTML 1.0 Strict validationXHTML 1.0 Strict validation
Previous
 
Next
New Post
5/30/2007 12:48 PM
 

the script issue is one of the fixes I'll be making, I'll have to investigate the clientAPICaps one to ensure theres no knock on effect - if theres not, i'll look to make that change also.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
5/30/2007 2:42 PM
 

Cathal, thanks for the great work.

Would it be useful to add XHTML compliance "problems" for the Core modules to gemini (or somewhere else)?

I guess that would be the next step in the process... and it's probably the team lead's responsibility...

But you might already have an overview of these...

 
New Post
5/30/2007 6:07 PM
 

Please feel free to add any module specific issues to the public issue tracker @ http://support.dotnetnuke.com/project/Project.aspx?PROJID=23 . Periodically the project leads view this tracker and get any valid issues moved to their forums.

I do the same with core issues, as well as add any others we decide to add to the core e.g. you can see a number of issues assigned to me @http://support.dotnetnuke.com/Issues.aspx?m=1&c=8&v=12&projid=2 that contain the word 'compliance' in their description.

FYI: I'm delivering a session at devconnections (along with Lee Sykes of dnncreative) about xhtml & accessibility, so i'll be looking to commit my changes soon so that we can work off a solid release for our presentation.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
5/31/2007 9:29 AM
 

Would be nice to have an xhtml compliant dotNetNuke.
A lot of out customers are requiring xhtml and currently we make changes to te source after each new version of dotNetNuke.
Perhaps this could be given a higher priority?
A common issue that breaks the design is the align="left" atribute in tables.

I think that some basic changes should be farely easy and have a low impact:
- change tags to lowercase
- remove align="left" attributes
- make sure tags are closed
- encode & in urls
- change span to div in "No Container.ascx"

 
New Post
6/3/2007 12:35 PM
 

Cathal, as always to you & the other heavy-lifters: Thanks! This is HUGE and very welcome.

I've not tried to create a nice CSS skin for almost a year - when I put one to two weeks into one unsuccessful effort, but I suspect my next efforts will be much happier.

- John

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...XHTML 1.0 Strict validationXHTML 1.0 Strict validation


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out