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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsSkinsSkinsProblem with custom skin on child portal - order of css import is wrongProblem with custom skin on child portal - order of css import is wrong
Previous
 
Next
New Post
10/10/2014 3:40 PM
 

This is call for urgent help, please.

I am developing custom DNN skin. I developed a skin and it works perfect on my local DNN instalation (root portal).

But I have added new child portal and set my skin to it.

Now to the problem:

When I am logged in (as host) my skin on child portal works fine.

But when I logout my skin mess from some reason. And I have found what is the problem but have no idea why it happens and how to solve it.

Inside skin I have this lines of code:

<dnn:DnnCssInclude runat="server" FilePath="zurb/css/foundation.min.css" PathNameAlias="SkinPath" />

<dnn:DnnCssInclude runat="server" FilePath="/skin.css" PathNameAlias="SkinPath" />

When I am logged in skin.css is loaded after foundation.min.css but when I am logged out skin.css is loaded first and result of that is my styles that are in skin.css are pverwriten by other css files.

Can somebody explaint me why this happens and how can prevent this and always load  skin.css after all others?

 
New Post
10/10/2014 4:43 PM
 

First: 

You can specify the order of how the css loads. Example: 

< dnn:DnnCssInclude ID="DnnCssInclude1" runat="server" FilePath="~/htmlcut/css/styles.dev.css" Priority="20" />

< dnn:DnnCssInclude ID="DnnCssInclude2" runat="server" FilePath="css/styles.dev.css" PathNameAlias="SkinPath" Priority="30" />

< dnn:DnnCssInclude ID="DnnCssInclude3" runat="server" FilePath="css/src/vendor/jquery.sidr.dark.css" PathNameAlias="SkinPath" Priority="40" />

See: http://www.dnnsoftware.com/wiki/page/...

Second:

Check and make sure jquery is loading if you are logged out vs logged in. 

Hope that helps.

 
New Post
10/10/2014 4:56 PM
 
vladakg85 wrote:

This is call for urgent help, please.

I am developing custom DNN skin. I developed a skin and it works perfect on my local DNN instalation (root portal).

But I have added new child portal and set my skin to it.

Now to the problem:

When I am logged in (as host) my skin on child portal works fine.

But when I logout my skin mess from some reason. And I have found what is the problem but have no idea why it happens and how to solve it.

Inside skin I have this lines of code:


When I am logged in skin.css is loaded after foundation.min.css but when I am logged out skin.css is loaded first and result of that is my styles that are in skin.css are pverwriten by other css files.

Can somebody explaint me why this happens and how can prevent this and always load  skin.css after all others?

 Skin.css is loaded by default by DNN, there is no real reason to use an include like this.

I actually think you are loading it twice (once auto-loaded by DNN and once with the include).
I guess on the child portal the file is not found because the /Skin.css path references the path relative to the parent portal.

Remove the skin.css skin inclusion.

 
New Post
10/10/2014 4:58 PM
 

Erik :) You are god :D Thanks

Didn't have any idea about those priorities.

 
New Post
10/10/2014 5:18 PM
 
Not a god, but working on it.
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsSkinsSkinsProblem with custom skin on child portal - order of css import is wrongProblem with custom skin on child portal - order of css import is wrong


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