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...Skins, Themes, ...Skins, Themes, ...admin >> skins >> does not allow me to apply a skin to just the portaladmin >> skins >> does not allow me to apply a skin to just the portal
Previous
 
Next
New Post
8/21/2011 9:11 PM
 
admin >> skins >> does not allow me to apply a skin to just the portal. even if i check the box to apply only to the portal and deselect the box to apply to the admin area, the skin is still applied to both. same applies to the container.

i have read the superuser manual and am following the directions. should i be doing something differently? is this a bug?
 
New Post
8/22/2011 10:33 AM
 
it sounds like a bug (I saw another similar report also) - please log it at support.dotnetnuke.com

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/22/2011 1:12 PM
 
Cathal:

I am also experiencing the problem with a skin as it applies to the admin pages. Specifically, I am using 5.6.3 and the Maple skin. I have also read a lot of forum posts about this (old and new) and the whole thing is very confusing. Bug or not, there is a "opportunity for improvement" here related to the application of a skin to the portal and/or admin pages. Part of the confusion arises from the fact that even after you apply a skin to portal only (by removing the tick on the Admin checkbox), when you leave the skin management page and come back, the tick reappears by default on the Admin checkbox. In my opinion, the skin management page is not doing a good job of presenting the current state of affairs as far as what skin is currently applied to what (host/portal/admin).

In addition, and again IMHO, the so called "Admin" category is not well defined as in my experience with the Maple skin, if I go to Admin, User Accounts, everything looks fine, but when you edit one particular user all the controls on the page are centered instead of left justified. Apparently, for the application of the skin, Admin refers to pages that are in Edit mode (identified by having CTL in the URL) and not actually pages that represent an “Admin” function like UserAccounts.aspx or SiteSettings.aspx, the later look fine.

Granted, I may be running into a problem with the Maple skin, and I think I am, but if I try to "deselect" the skin or its container for Admin pages only it does not work the way I expect it to, it remains in effect.

By the way, I also saw an explanation of a change in the way skins are applied to the portal and Admin pages starting with DNN 5, that explanation did not help me. But maybe because of that change, the Skins management interface should have been updated.

Please let me know if I am misunderstanding the whole thing or if you think the problem is the skin.

Thanks.

Carlos

 
New Post
8/22/2011 6:35 PM
 
Carlos,
it's not an area im well versed in so I can't confirm what you're seeing, but I'd certainly recommend you add issues for any problems at support.dotnetnuke.com so we can look into them.

As for the "edit" issue -in early versions of dotnetnuke we had an indicator (IsAdmin) as to whether a control was admin or not (actually in really early versions if an item lived below the "admin" menu it was automatically admin) and if a control was loaded on an IsAdmin page or an item off the host menu then only the contentpane was displayed (this is why every skin must have a contentpane). The reasoning behind this was that admin functions were exactly that-something that had 1 simple function and were not a collection of related modules.

However with the 5.0 release, there is no such thing as an admin page anymore as pages under the admin menu can be granted access to for anyone. This does mean that using the edit variable allows us to see when an administrative task is underway and hence the skin changes - and this can be a bit odd when you have "old" admin pages operating as real pages but with admin functions - of course you can work around this by setting the same skin on both but its extra work. Oddly enough, with the 6.0 release as we dont redirect to new pages for edit but instead popup a window over the existing page this disconnect is much less evident.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/22/2011 10:10 PM
 
visited the support.dotnetnuke.com site and registered.  no clue on how to log an issue. dug around for while but couldn't find any way to do it.  will be happy to log an issue if someone could tell me how to do so.  also, i went to the "report" link on the support site and was trying to feel my way around.  i clicked on the "group by" dropdown and there are quite a few groups with the word F*CK in them.  not so sure i can take that support forum seriously.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...admin >> skins >> does not allow me to apply a skin to just the portaladmin >> skins >> does not allow me to apply a skin to just the portal


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