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, ...Adding CSS to Shared Header (and Footer) ASCXAdding CSS to Shared Header (and Footer) ASCX
Previous
 
Next
New Post
4/19/2011 12:29 PM
 
Gerard,

Glad the 40Fingers worked! I have made this something that I add to my DNN install as soon as I create it. Love this skin object!


Ralph Williams, Jr.
UX Designer / Front-End Web Developer
www.RalphWilliams.com
Ralph Williams Consulting
Twitter: twitter.com/ralphwilliams

Professional DNN7: Open Source .NET CMS Platform
 
New Post
4/22/2011 8:53 AM
 
There seems to be a problem, I'm afraid.

I've got the SharedHeader.ascx in de skin directory "\Portals\_default\Skins\MyFirstSkin\" and using it in the HomePage1.ascx skin in that same directory. I also use the SharedHeader.ascx in the HomePage2.ascx skin in "\Portals\_default\Skins\MySecondSkin\". Everything is included except for the css styles / SharedHeader.css file. Even if I change its reference in SharedHeader.ascx, like:
<fortyfingers:STYLEHELPER ID="STYLEHELPER1" AddCssFile="~/Portals/_default/Skins/MyFirstSkin/SharedHeader.css" runat="server" />

Any clues how I can solve this?
 
New Post
4/22/2011 9:44 AM
 
If I use:
<fortyfingers:STYLEHELPER ID="STYLEHELPER1" AddCssFile="~/Portals/_default/Skins/MyFirstSkin/SharedHeader.css" runat="server" />
(so with the full path)
in \MyFirstSkin\SharedHeader.ascx the css styles are not being used in \MyFirstSkin\HomePage1.ascx and not in \MySecondSkin\HomePage2.ascx.

If I use:
<fortyfingers:STYLEHELPER ID="STYLEHELPER1" AddCssFile="SharedHeader.css" runat="server" />
(without the full path, but just the name of the css file)
the css styles !are! being used in \MyFirstSkin\HomePage1.ascx but not in \MySecondSkin\HomePage2.ascx.

(I applied MyFirstSkin / HomePage1.ascx to my first portal and MySecondSkin / HomePage2.ascx to my second portal.)

Thx.
 
New Post
4/22/2011 9:56 AM
 
As the default basepath is the skin folder the second example is correct.

You can us another path is you want:

----------------------------------------------

File Path

The path to the files can be set using the BasePath attribute, which default to the skinpath.
You can use tokens for the "BasePath" or for the individual files (in AddCssFile/AddJSFile);
[S] For the SkinPath
[P] For the current Portal folder
[M] For the Skin objects install folder
----------------------------------------------


I'm not sure what your trying to accomplish (are you using an include in as a header?), but normally if the skin object has to be part of the skin for the CSS to load.
 
New Post
4/23/2011 6:45 AM
 
FYI, I posted an example skin to Codeplex, to show how you van include a file in you skin files.
This allows you to create a header file for several skin variations, making it easier to manager them.
(if you make changes to the header, you only have to do that once)

http://dnnskinextensions.codeplex.com...

HTH,

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Adding CSS to Shared Header (and Footer) ASCXAdding CSS to Shared Header (and Footer) ASCX


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