David,

If the selectors are the same it should override the default.css as it comes last in the CSS stack.

Any chance you can provide a link to an example so I can have a look with Firebug?

Regards,

Rick.

David,

Thanks for the link to the site, this has helped a lot and I've figured out your CSS issue.

Within the body of the skin you're loading a default.css file which is located here: /Portals/_default/Skins/CrystalSlateSkin/images/default.css. This is the css file loading last and that's why when you make changes to the portal.css file nothing is happening.

DNN uses CSS normally, as it can't actually decide whether to use the first or last css files itself because this is controlled by the device viewing the website and it's doctype e.t.c. and not the framework.

The way you've included the css for the skin is diofferent to the normal use of CSS in a skin pack and I think there's a chance this may casue you more problems in the future. To help with this I'll describe the skinning way of including CSS for your skin designs.

With every skin pack you can use a skin.css file, located in the same directory as your skin files, for general skin style. Use this for the main layout elements and default skin settings, if you're creating more than one skin in your pack. You can then use a SkinName.css file (where SkinName is the actual name of your skin) to control specific skin styling because this file will only load with the skin of the same name.

I hope this helps.

Regards,

Rick.