Thanks Richard, maybe I haven't explained myself well enough. The scripts are not served by ASP.Net only the script tags.

The module register a client script or stylesheet with the PAGE to be rendered to the client, so when the MODULE's rendered output is cached the client script tags are not included in the rendered MODULE output they are in the PAGE.

Therefore if caching is enabled on the MODULE, the first time the MODULE run it is built client script are registered with the PAGE and all is well, the second time the MODULE's rendered output is called from the cache - code is not executed and client scripts are not registered with the page for inclusion.

Can anyone think how in this situation DNN CE caching can work? Or another way around it?

Hi Jacques,

When you enable built-in cache in the module settings, the firt time the module is called the html code produced is saved in the cache by dnn and when the mdoule is called the content is loaded from the cache and your module IS NOT loaded! That's why your module works the first time and not the second one. You should NOT use the cache module settings and instead cache your data in your Business Layer. I use this technique in the Store module to increase performances.

Gilles

---

We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.