Products

Solutions

Resources

Partners

Community

About

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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsLinksLinksAccessiblity Compliance IssuesAccessiblity Compliance Issues
Previous
 
Next
New Post
5/6/2008 1:27 PM
 

I am running the Adammer ADA Compliant skin on my sites to fill any State and Federal mandates.  In validating one of the external sites I came across issues causing a fail.  Adammer gave me the following information.

2) Error: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified

This is caused by the poorly written Links module. The code should read <|td nowrap="nowrap"|> not <|td nowrap|>. The skin cannot change poorly written module code. Either way nowrap is depreciated and should be accomplished with a CSS style attribute like style="white-space:nowrap;". We recommend that you use the HTML/Text module instead of the Links module. 

Having my users edit/add links through the html/text module rather then the links module is not in the game plan.  I can see information being deleted etc...  Can this be corrected?  Or does anyone know of a third party links module which would pass validation?  Thanks. 
 

 
New Post
6/6/2008 8:37 AM
 

Hi LeAnne and the Link team

I use xhtml a lot and there are now under 50 errors which are not generated by skins or containers. DotNetNuke is going in the right direction.

Here is a fast and simple workaround for the above error from the link module. The Link team can do this a lot smarter, i'm sure.

In the \DesktopModules\Links\Links.ascx file, change the following line:

<td <%# NoWrap %>>

to:

<td style=" white-space: <%# NoWrap %>;">

From now on you will only have css warnings if you have choosen 'Wrap' in the Links Settings (It gives "whitespace: ;" in the html code) which is better than errors :-)

 


Niels-Jørgen Hvidberg http://newcomtech.dk http://njhvidberg.dk
 
New Post
6/6/2008 9:16 AM
 

version 4.0.0 of the module will solve this (version has been submitted to the release tracker).

also: DNN 5.0 will be almost completely xhtml compliant


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
6/12/2008 11:09 AM
 

Eric - We have not been able to find many resources on getting DNN compliant - we're using ver. 4.8.3.  do you know of any good resources?  We've are editing a decent amount of the core coding to attempt to make the existing version compliant.

Tim

 
New Post
6/12/2008 12:07 PM
 

one of the things you could do is to check out the DNN 5.0 roadmap, and see what issues have been fixed that have to do with Compliancy: http://support.dotnetnuke.com/project/RoadMap.aspx?PROJID=2

I would very much like to discourage you to make changes to the core, as you will loose all those changes with an upgrade (eg. dnn 4.8.4 was just released, with a few security fixes....)

One of the things i did before was to use a third party http handler that could fix dnn output before it was send to the client. Check out Snapsis Pageblaster, that has a functionality to make the output xhtml compliant...


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsLinksLinksAccessiblity Compliance IssuesAccessiblity Compliance Issues


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