We're running XOOPS 2.0.15. When we turn cacheing on any scripts or stylesheets registered with

$xoTheme->addScript(null,null, <<script content>>);

or

$xoTheme->addStylesheet(null,null, <<stylesheet content>>);

get lost in the cache. That is, the scripts and stylesheets are in any refreshed pages but are left out of any content that comes from cache. (Basically, any content rendered by xos_opal_Theme->renderMetas() never comes back out of cache.)

Is this expected? Am I maybe using functions that are incompatible with cacheing?

Thats expected...not "normal" but yes when cache is turned on then styles of module along with every js a module inserts in theme's header will be ignored...i personally know just one module that doesn't drop js/styles when cache is activated...future version of wfdownloads...there might be others as well

Thanks for the info, I was worried that I'd gotten something crosswired deep in the bowels of smarty. I suppose that I could move the scripts & such into the body easy enough. We're still in development so I don't haev any experience with cacheing in production.

Would moving things be worth it? Do you get much of a performance boost?