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, ...Is it possible to apply a separate skin when the user is logged in? Different from an Admin Skin.Is it possible to apply a separate skin when the user is logged in? Different from an Admin Skin.
Previous
 
Next
New Post
3/8/2006 5:17 PM
 

Hi gang,

It took me a while to realize this...a long while.  But I think I got it straight.  Please someone correct me if this is wrong.

I have always thought that an "Admin Skin" was a skin that gets applied when a user logs in.  This assumption is *wrong*.  An admin skin is the skin that gets applied when a user logs in and then views any page under the "Admin" Menu or clicks a control for a module such as "settings".  Correct?

Okay, so now that that's clear...I think...what I want is a different skin to get applied after a user logs in...let's say a user with admin privileges.  So, for example...

Admin user logs in....and sees the content panes with the dotted boxes around them with the settings, edit text controls, etc. for each module.

I want this page to look different.  Why?  Because the the controls and dotted lines often screw my design/skin up after logging in.  Especially across browsers.  Getting the same skin to not break, and keep the layout consistent from logged in state/not logged in state is an extreme pain.  Web developers already have to worry about the cross-browser stuff and now we have to try and get the design to work in two states.  Notice I said design, not code.  This is not a code challenge.  The challenge is to come up with a design to compensate for the new styling/elements that appear on the page when logged in.  Here are 3 simple examples of where a "different skin when the user is logged in" would come in handy.

  1. Different browsers interpret widths differently...as many of you know I'm sure.  So, if I have fixed width DIVs for example, the dotted border that gets applied to content panes after logging in sometimes can shove things around, especially if they're floating divs.
  2. I don't want any module controls on my site when a visitor to my site is browsing around.  So, I tried various things...messing with settings in skin.xml for ACTIONBUTTONS, messing with placement of the controls, above or below a module, messing with CSS (realized quickly that the same css gets applied, so a no go there).  I need to have the ACTIONBUTTONS tokens somewhere in my skin...otherwise once I'm logged in I can't change anything.  So, I put <div>[ACTIONS][ACTIONBUTTON:1][ACTIONBUTTON:2][ACTIONBUTTON:3][ACTIONBUTTON:4][ACTIONBUTTON:5]</div>  at the bottom of a container skin for example.  But....when visitors views the site....this bit of code is generated as <div>&nbsp;&nbsp;</div>...which puts an extra space in between my modules if I have multiple modules on a page, one on top of the other...annoying.  I tried <div>[ACTIONS]</div>....seems okay, I can deal with it...then I go into a page under the Host menu...such as "Skins"....and notice that the "upload skin" | "upload container" links are now missing....okay, so I need to have the ACTIONBUTTON tokens back in there...
  3. When logged in, I would like to have a different look and feel so the user is fully aware that they're logged in as an admin.  Right now, after I log in, I see those dotted borders around every content pane in say...DNN Blue....now I click a control on one of the modules...say..."edit text"....now if I have an admin skin applied I see a different skin at this point...say DNN Red.  This seems confusing.  It confused me, the developer [I imagine many other developers...but I am slow...so it may just be me...=)]....and it is confusing to my clients.  The point of having an admin skin is somewhat lost I believe in this scenario.

The basic problem for me is...that if I'm logged in as an admin....I want to see an "Admin Skin" from the point I log in and after...not just when I go to an item in the Admin menu.

Okay that's enough typing...hopefully there is a simple answer I am overlooking and I'm doing something wrong.  I'm using DNN 3.2.2

Peace!
-Tim

 
New Post
3/8/2006 5:28 PM
 

I don't have time to read all of this, but it sounds like you may be able to get what you need by clicking on the "Preview"  link/icon in the control panel.  That will turn of the extra styling stuff and remove the edit options from the modules.

Also, something I do is just keep to browser windows open, one logged in and the other not.

If you use the preview option, make sure to remember that it is in preview mode, or you may be scratching your head trying to figure out what happened to the edit capabilities.


DotNetNuke Modules from Snapsis.com
 
New Post
3/8/2006 5:35 PM
 
Hi John,

Thanks for your reply.  Apprecitate it.  But, that's not what I'm looking to do.  Read the post, or even just the title.  Perhaps you can spare a few mins later.

What I'm looking to do is apply a different skin from the point of being logged in. 

What I think you're suggesting is a technique to use while developing/creating a new skin.  I too, keep a separate browser window open and use the Preview function, very handy!

Thanks!
-Tim
 
New Post
3/8/2006 5:38 PM
 

The basic problem for me is...that if I'm logged in as an admin....I want to see an "Admin Skin" from the point I log in and after...not just when I go to an item in the Admin menu.

In a nutshell, let me think, I believe you want a role base skin to display containers.

I read this thread a couple of times and I do confess, I was a bit tired, so it's interpretation was harder to do.

What you want is a container that shows no actions when people are viewing the site, but actions available when administering it??? Is that correct, well that's my take.

You know if you have created a skin you apply it to the admin page as well.  The purpose of the admin skin is often it's a little wider in it's format to help design a skin that remains consistent for users and admnistrators.  Simpy apply the skin to the admin page and it won't change.

You can do that as well with the containers to create a seamless skin/container environment that doesn't visually throw you out, and I do understand how it can cause confusion.

I've got a couple of containers on my site you can download - one is called none.. it takes away all container actions except when logged in as administrator.

But what you need to remember is different container options is to help a user identify where are they are in the site in relevence to it's behaviour, eg.. admin mode - there was a time where we had alot of questions about people not being able to see things, because there was no identification between being logged in as administrator or being the user, and now, we don't have those sort of questions, it was changed to make it very visible where you are.

You know you can globally set functions for the containers - EG.. on one module, go in to the settings and make the changes you want, and then further down the page you can set that as default..  eg. no print, no syndicate, no container if you wish.. and then only on the ones you want change do you go in and action it.

Sometimes understanding these things in the purpose and sequence can seem a bit off beat, but believe me, once you grasp some of the very good key elements of design and flow when working in this space, it does make sense, and it also helps you know where to look for things that may not be as documented as well.  

I hope this gives you a little more insight - I have only interpreted as best as I can understand your question.  And that's in morning, before my cup of tea!! So, I hope this gives you some answers you're looking for.

Nina Meiers


Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
New Post
3/8/2006 6:01 PM
 

DotNetNuke Modules from Snapsis.com
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Is it possible to apply a separate skin when the user is logged in? Different from an Admin Skin.Is it possible to apply a separate skin when the user is logged in? Different from an 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