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.0navigateURL changes skin to admin skinnavigateURL changes skin to admin skin
Previous
 
Next
New Post
11/18/2008 10:29 AM
 

I'm developing a module with a number of different internal paths. 

Using NavigateURL(tabid,"UserControl","mid=" + moduleid.Tostring, "PRID" + projectID.ToString) work to a point as in the page navigates a user with only view privileges can work through the flow (about 6 usercontrols) so thats not a problem. The crux of the issue which is a total annoyance we use a separate admin skin to the public facing skin. However linking, in the manner described above, for some reason cause dnn to use the admin skin, even though the controls are defined as view (not edit or admin) within the module deffinition.

I realise I could create a containing page to route all the controls through but that really is a total pain.

Any Ideas on how to remedy this would be apreciated.

John


John Nicholson
 
New Post
11/18/2008 10:38 AM
Accepted Answer 

When you include "mid" on the querystring, it triggers module isolation (that is, it makes your module take up the entire page and removes other module).  Module isolation always uses the admin skin (though, starting in DNN 5.0, there is no longer an admin skin, so this won't be an issue going forward).

The only workaround is to avoid module isolation in your navigation.  You can look at Michael Washington's Module Navigation tutorial to see some of your other options.

Hope that helps,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
11/18/2008 11:38 AM
 

One may also use the "skinsrc" skin preview querystring value to explicitly specify a skin, even with a mid directive.  As Brian outlined, this would be a bit of a hack, since this sort of behavior is not an issue in 5.0.

Brandon

 


Brandon Haynes
BrandonHaynes.org
 
New Post
11/20/2008 10:58 AM
 

Thanks for that guys as this is still in a beta I may simply delp[oy to 5 only as this is a single install module.

John


John Nicholson
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0navigateURL changes skin to admin skinnavigateURL changes skin to 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