I have a site under development with 2 skins - a fixed width for the portal skin and a full-width skin for the admin skin.

I have found that some pages that I think are "portal" pages insist on loading the admin skin.  This happens when a module appears on the page with a key of "Drill" and a type of "View". 

I would have thought that the type "View" would make it load the portal skin.

Thanks in advance!

John B

 

I have come across this problem in DNN C. and never found out why it was occurring. On DNN C. it is random where it will display the correct skin and then another time it will display the admin skin. The only solution I found was to specify the skin in the actual page settings.

If it is just one module that is causing the problem on a page, it's an easy workaround.

Let us know how you get on, I would be interested in any further info you come across, thanks,

Lee

Hi Lee,

I found this comment in a DNN forum post which explains MY problem, and may explain yours:

Whenever you call a control from a querystring in the URL, DNN loads the page using your admin skin. If you want DNN to work with the curretn screen, load the control programatically. The Forum module works like that.

The thread then goes on to explain how to load a control programatically, which I am going to try - looks useful!

See:

http://www.dotnetnuke.com/DotNetNuk...fault.aspx

John B

BTW Lee, what do you mean by "DNN C"?

Hi John,

Thanks for the info I will take a look. 

By DNN C. I mean DNN Creative ;-)