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.0Apply skin to all controls in a custom moduleApply skin to all controls in a custom module
Previous
 
Next
New Post
4/16/2009 5:17 AM
 

Hi All,

       I am having problem with applying skin to a module. I have a custom module which has 4 controls linked together. So for example, control 1 has a submit button when clicked, redirect to control 2, etc.. I created a new page and added my custom control and set the skin of a page. However, when I click the submit button on control 1, it redirects to control 2 but the skin become the default skin.

       How to make all the controls (pages) in a custom module to use the same skin ??? Need help please and also urgent :)

       Thanks in advance for all your time and help :)

 
New Post
4/20/2009 4:50 AM
 

Need help, can anybody advice how to achieve ? It is urgent. Thanks in advance.

 
New Post
4/20/2009 8:54 AM
Accepted Answer 

The default behavior of DNN is to display any module control other then the main view control (having a blank ControlKey) as the only module on the page using the admin skin. A quick but probably not acceptible fix is to use the same skin for both the default and admin skins for the page.

A better fix would be to look into alternatives to the default behavior that results when using the ControlKey as a parameter to NavigateUrl or EditUrl to redirect to your other controls. Techniques such as using only one control and panels or a MultiView control to show/hide the appropriate section of the control or dynamically loading child controls can be used. I generally use the latter method when I don't want to switch skins or need to display other modules on the same page.

Michael Washington has a tutorial on alternatives to NavigateURL: http://www.adefwebserver.com/DotNetNukeHELP/Misc/ModuleNavigationOptions.htm


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
4/21/2009 6:05 AM
 

Hi William Severance,

          Thanks for your reply and the link. I will try to change by using the MultiView control. Hope to be OK. Thanks :)

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Apply skin to all controls in a custom moduleApply skin to all controls in a custom module


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