Hi, I'm implementing a custom design in a dnn-skin. The problem that I'm facing is that some of my custom css style definitions are overwritten by the default style definitions for DotNetNuke. This is for example the case with the a:link definition. How can I prevent dnn style definitions overruling my custom style definitions? Thanks, Anthony www.webmove.be

Styles defined in your skin.css file should override those defined in _default.css.

If you have a single portal installation, though, you can delete definitions from _default.css without too many worries.

Hi Joseph,

Thanks for replying on this. I am having a similar problem and I was wondering if it is possible to exclude the default.css file from my font end design altogether?

I am trying to get my DNN projects to a Blueprint layout where I can just drop it in and start working but the default.css file overrides some of the resest css rules which is what I am trying to avoid.

If it's possible to exclude it from my front end but have it working only for the back end stuff, that would be great.

Thanks,
James

Take a look here. 

"This skin object allows you to unload any CSS file that the DotNetNuke® framework injects in the head of the page.
It can be used to unload Default.css for instance, or a spcific modules CSS file."

hello,

That is useful skin object and well worth checking out. If you need information on how to override the default DotNetNuke styles, you can also look at the code in the skin:
Andreas 01

in this tutorial we show you:

• How to create a DotNetNuke CSS skin from an XHTML template – part 1
• How to create a DotNetNuke CSS skin from an XHTML template – part 2

and in there we show you the process of overriding the default styles.

The new skin object will be a more efficient method however, thanks,

Is there something we have to do to get this behavior? The default.css seems to take priority on my site. My specific example occurs in the A:links style. I see it being disabled in the developer view in IE. It laves the default.css as active and marks out the conflicting skin.css as well as the div css I placed. Edit: I found my issues to be that the font color css was not taking over for the A:link color.

If you are looking for coding examples of overriding styles in the default.css check out the Andreas 01 skin mentioned above.