Changing cache to 0 fixes the problem.  It sounds like there may be other issues with 4.x versions of DNN, but for 5.0, it looks like the CSS file isn't being included on the second (and subsequent) views when caching is on.

I haven't tried this, but I if memory serves, DNN has a facility for including a module.css.  This way the DNN module cache can emit the HTML needed for the module, but it doesn't add any included files (Javascript or CSS) that the module adds.  The Events module isn't using a module.css file (it adds a .css file based on the Events Theme) so DNN doesn't know to include it.

Thanks for looking at this.  The page with two Events modules on it loads a little slower than I would like, and events are being added rarely, so this is a good candidate for caching (when it works).

Thanks for looking into this,

Tim

Hi Tim,

Unfortunately I don't know how to resolve this problem. To use themes, the module must dynamically add the theme css at run time. I'm not sure how to make DNN cache that element. I'll continue to think over the problem, but not sure I can resolve.

Cheers
Roger

Though the module doesn't use a module.css (because it allows theming), I notice that a reference to ~/DesktopModules/Events/Module.css is included. So you could put all your theme styling there. It would just need to be a copy of the theme css. I think that would work in the interim.

Cheers
Roger