Greetings,

We purchased a skin that we think looks pretty cool. We applied it and the site does look nice. However, some modules like events have not changed, the skin did not take effect.

Should the skin apply to built in modules?

Are we doing something wrong?

Thank in advance,

David

Greetings,

Thank you for the reply. Is that the case for all skins that I might try and for all built-in modules? That I have to go and hand edit all the module's CSS files each time I change a skin?

I am new to the skinning of DotNetNuke.

Thanks

I feel this is a little bit of a problem as as module developer. somethimes the modules are quite advanced and more css classes are created than what is covered by the default classes in portal.css. It would be nice if it was possible to add a default skin to your modules as done in module.css however it should be overridden through the portal.css