Hey TwoQuestions,

First - welcome! I see it's your first post in the forums so I just thought I'd give you an official welcome.

As for clearing the CSS cache - yes - there are a few ways to clear it. You can use the "clear cache" button in the host settings - there's also a shortcut in the Tools section of the DNN 6 control panel as well. There are some other options, but that is going to be the most straightforward way to clear it. This was an existing feature that was updated in DNN 6.1 to also increment the client resource version - which forces the composite files to be rebuilt.

However, it's important to strike a balance between convenience and speed. Ideally once you deploy and turn the combination on - you won't need to build new composite files for awhile. While there is a minimal performance impact due to the server side processing - the bigger concern is that these files are cached in a visitor's browser - and incrementing the version by clearing the cache will force the user to download a new copy - mitigating much of the performance benefit.

The overall goal though - for this release - was to reduce the number of requests, and you will get that either way. But hopefully you don't have to clear the cache *too* often.

Let me know if you have any other questions - would be glad to help

Ian

Hey Rexhep,

I'd suggest using the Client Resource Admin module I've created to manage the features and learn more about what each one does. This is a better alternative to manually merging the web.config files. You can find it on the downloads page here: http://github.com/irobinson/ClientRes....

There aren't any known issues (known by me at least) with the new Client Resource Management functionality and the DNN core, however a few have come up with third party modules. I'd suggest taking a read through the this blog post if you haven't already: http://www.dotnetnuke.c...

If you're still having issues please post the details here about what you see and I'll try to help as best I can

Take care,

Ian