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.0prevent control from using admin skinprevent control from using admin skin
Previous
 
Next
New Post
2/2/2007 9:43 AM
 
Is there a way to prevent a control from using the admin skin and force it to use the specified page skin?  I know it is a default behavior to have all controls in a module other than the default use the admin skin, but I need to find a way around it.
 
New Post
2/2/2007 11:57 AM
 

One way is to actually have your own control loading other controls. That's how quite a bit of our EngagePublish module functions, but loading other controls within a loader control, based on various querystring parameters.

Our loader control usually just has a placeholder control on it, and in the code we parse the QS and load the proper controls.


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
2/2/2007 6:55 PM
 

As long as you are using Module Controls idea (adding your controls to the ModuleControls table and calling them via NavigateUrl with ControlKey - when calling them or going to any plain old edit screen of some module, observe the url, you will see params ctl and mid being added, and DNN framework based on these loads an appropriate control of an appropriate module, and all of that in an admin skin) - no there isn't, but if you step out of the boundaries and just plain load your controls it works like a charm - and loads the portal skin correctly.

 

 


Thanks,
Vladan Strigo
NETMedia

My website: Vladan.Strigo.NET

Vladan.Strigo.NET: Projects
* Advanced VS2005 development approach - BlankModule
* DNN & Microsoft Ajax best practices guidance

Vladan.Strigo.NET: Resources
* Comprehensive list of DNN 4 Module development resources

 
New Post
2/5/2007 3:20 PM
 
thanks for the help.  It worked perfectly.
 
New Post
2/6/2007 5:11 AM
 

Np, glad I could help :)

 


Thanks,
Vladan Strigo
NETMedia

My website: Vladan.Strigo.NET

Vladan.Strigo.NET: Projects
* Advanced VS2005 development approach - BlankModule
* DNN & Microsoft Ajax best practices guidance

Vladan.Strigo.NET: Resources
* Comprehensive list of DNN 4 Module development resources

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0prevent control from using admin skinprevent control from using admin skin


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