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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Removing global qualifiers to asp.net controls within modules?Removing global qualifiers to asp.net controls within modules?
Previous
 
Next
New Post
6/17/2009 9:23 AM
 

I'm trying to sort out some accessibility (WCAG 2) issues within our DNN project. At the moment I’ve got stuck on a really common one that is being caused by the way dotnetnuke generates pages. Basically, where you have to have a “for” tag in a label, the Id of the item that the label is tagged to is being changed by DNN. It seems to be turning the name into a global qualifier name, for example txtInactive becomes dnn_ctr566_ViewCmis_committeedetails_txtInactive.

Within the desktop module files, the original ID is maintained, so I presume the extended qualifier is generated when the module is loaded into DNN itself. 

I can’t use the long version in visual studio as it won’t be able to find the item with that id and therefore won’t build – if i use the long version it will just create a doubly long version, and the problem persists.

If anybody has any suggestions on where I would need to look to change the way this is done I would be very greatful!

Thanks

 
New Post
6/21/2009 6:35 PM
 

it's actually asp.net that changes the id's not dotnetnuke.(if you want further info on this search for asp.net naming containers e.g. http://aspadvice.com/blogs/joteke/archive/2007/02/25/Understanding-the-naming-container-hierarchy-of-ASP.NET-databound-controls.aspx). I'm assuming you're trying to access server controls via javascript? If so the easiest way is to typically generate the javascript server side, or else inline e.g.

txtEmail=document.getElementById('<%=txtEmail.ClientID%>'); 

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Removing global qualifiers to asp.net controls within modules?Removing global qualifiers to asp.net controls within modules?


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