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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Site level skin -- not host levelSite level skin -- not host level
Previous
 
Next
New Post
11/10/2010 2:04 PM
 
In older versions of DNN, I know that you, as an admin, could upload a skin to the site and it would only be available on that portal.  I have a portal with several subportals and each subportal will have it's own skin.  I want the admin for each subportal to only be able to use the skin assigned to them and not have the entire list available.  When I upload a skin, however, I can only do so when logged in as host and sets the default access level to host level rather than site.

Is there a way to make sure the subportal skins are only available at the site level and not the host level?  I used to do this by uploading the skin through admin>skins, but with DNN 5 it doesn't appear that you can do that anymore.  Is there a workaround?

Thanks so much!
Kristine
 
New Post
11/10/2010 2:07 PM
 
As a HOST go to the Admin/Extensions page and upload the skin from there, INSTEAD of the Host/Extensions page, that will make the skin a site level skin.

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
11/10/2010 2:30 PM
 
Wow, now don't I feel dumb. :) Thanks for the advice! Is there a way to change a skin that is already set at host level? I guess I could just change the db....
 
New Post
11/10/2010 2:59 PM
 
Actually I am not sure changing it in the DB would do anything, you would also need to move it in the file system from /portals/_default/skins to /portals/#/skins (where # is the correct portal id)

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
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Site level skin -- not host levelSite level skin -- not host level


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