John Valentine wrote: The only answer I have been able to come up with is to edit the default.css file and keep a change file that I need to merge every time I upgrade. It isn't the best solution, but its a good work around until the DNN dev team can correct this oversite and once again begin adhering to the standard.

Hi John,

it seems to be a good timing for your post, because some volunteers (including myself) formed a new Events team some weeks ago, and although our main goal is to get a debugged DNN 4 / ASP.NET 2.0 version out of the door, we are planning (as a second step) to implement feature requests and enhancements; see post "Any reproducable bugs and/or suggestions for enhancements?" . Perhaps you'd like contribute your suggestions or even help us to create standard conform themes? You're welcome!

Hey Timo,

For my part, I understand what your original post was saying, and I hope you didn't think that my comment was directed at you personally. I was simply explaining that the problem bumps into the conceptual impliementation of CSS in the modules framework.

My copy of DNN Events has "!important" sprinkled throuought the stylesheet same as Dawn's. Unfortunately, I don't know which CSS class you are referencing. I am speaking of the "DesktopModules\Events\Themes\Default\default.css" file. I have traced the use of !important back several releases (even as far back as DNN433 Source version). It is plainly obvious that the developers were not adhering to the standards. The source version stylesheet is called module.css and is distributed in Events 3.2 and later as default.css in the path referenced above.

 BTW, I have posted this as a minor bug in gemeni.

Thanks again.