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, ...why doesnwhy doesn't file manager expose folders for CSS changes?
Previous
 
Next
New Post
2/16/2010 10:55 AM
 

something that's always confused me about DNN.....

there are layers of style sheets and yet the interface only exposes ONE stylesheet for editing. why is that? the stylesheet which is exposed only exposes a few of the elements needed to truely have control over the look and feel. and the other stylesheets are buried in folders which are not exposed by the admin or the host account's file manager. i've quite understood how the admin and host file managers determined the level of folders to expose. it would be great if it truely exposed ALL files and folders under the root. but instead....it's a small subset.

for example.....i don't see any way to alter the color of the menu items in the default setup. this is because the setting for the menu items is in a stylesheet which can not be accessed by the dnn interface.

why is this?

 
New Post
2/16/2010 1:01 PM
 

James,

It all has to do with how the CSS files within the DNN Framework stack.

*I can never get this right as I never use it in this way* (Someone will inevitably correct me)

  1. Default.CSS
  2. Skin.CSS
  3. Container.CSS
  4. Module.CSS
  5. Portal.CSS

Portal.CSS - the only one editable from the file manager, as you put it - is essentially the only one you need access to if you're wanting to edit CSS the way you do. The DNN Core team were rather clever in this regard, as when you think about multiple portals with multiple owners, you don't want some clown editing the module.CSS file of a common module for his portal only to mess up yours..! This is why things are the way they are...

With a solid knowledge of CSS and XHTML you should be able to overcome anything you want to in Portal.CSS.

Else, if you're serious about customizing DNN, access the files using an HTML / CSS editor application like Expression Web or Visual Studio. Either way, you're going to need to bear in mind how these things stack inherently.

Anyone elses thoughts..?


Shebang Websites - A product of Mogridge Design
Hey, we're partnered with UntangleMyWeb.com

 
New Post
2/16/2010 1:05 PM
 

AFAIK, correct order is

  1. Default.CSS
  2. Module.CSS
  3. Skin.CSS
  4. Container.CSS
  5. Portal.CSS

details can be found in Skinning guide.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/16/2010 1:15 PM
 

Like I said, I can never get it right... Thanks Sebastian.

Anyway, my point is that it's done that way for a reason....


Shebang Websites - A product of Mogridge Design
Hey, we're partnered with UntangleMyWeb.com

 
New Post
2/16/2010 1:51 PM
 

You can make all changes in portal.css simply by overwriting the CSS that's in the other CSS files.

Also since DNN is a multi portal system. Allowing an admin to edit the css of a skin might influence other portals that use that same skin.

That's what portal.css is for, it's portal specific, while a skin is not (always)

 

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...why doesnwhy doesn't file manager expose folders for CSS changes?


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