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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsAnnouncementsAnnouncementsW3C compliantW3C compliant
Previous
 
Next
New Post
3/27/2009 9:27 AM
 

Any help on how to make the Announcements Module W3C compliant? The error message I've been getting is complaining about the &tabid instead of &tabid and I have no idea where to change that. It might not even be related directly to the Announcements module but to the way DNN is handling the link building.

Thanks!

Alessandra

 
New Post
3/27/2009 2:13 PM
 

what versions of dnn and the annoucement modules are you running? If you're running a version prior to  4.06.02  of announcements I recommend upgrading (The 4.06.02 version of announcements is marked as xhtml compliant (http://www.dotnetnuke.com/tabid/125/default.aspx) )

I seem to recall the & change was made quite a few versions of dotnetnuke back, what version are you running?

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
3/30/2009 5:55 AM
 

I am running DNN 04.09.00 and the Announcements module is version 04.01.00.

 
New Post
3/30/2009 9:18 AM
 

duh, i meant the 04.00.01 version (it requires 04.06.02 as a minimum dnn version). I'm not sure what's happening, as I thought that that version of dnn in combination with that version of the announcements module should be xhtml compliant (at least in the public face) e.g. take a look at http://www.dotnetnuke.com/tabid/125/default.aspx, if you view the source you'll see the linkclick requests all use the correct encodings. Please make sure you haven't simply posted static text.. If you still have problems please record the problems at the public issue tracker @ support.dotnetnuke.com so someone can take a look at it for a future release.

 


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
3/31/2009 5:54 AM
 

I thought so too, that why I was so surprised to find that out. The link you send above indeed has the LinkClick.aspx encoded, but this page doesn't have the Announcements module in it. If you see this page: http://www.dotnetnuke.com/News/Announcements/tabid/703/Default.aspx, you will see the LinkClick does not encode.


Warning Line 155, Column 672: cannot generate system identifier for general entity "tabid"

…w_submissiondetails.aspx%3fid%3d247&tabid=703&mid=1344" target="_self">read m

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".


Total pain. I know...

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsAnnouncementsAnnouncementsW3C compliantW3C compliant


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