tpartner wrote: Hmm...maybe a link/button in the admin configuration screen to clear them would be worthwhile.
Yes, I understand that point view that can appear logical: such a button is very easy to do. Here why I refuse to do it:
I think it would make an extra level of complexity and stress. People don't understand how asset manager works, so it would very quickly become a magic button: each time they'd face a problem they would try to go clean the assets as a superstition, and it would just be useless and stressful. The goal of an asset manager is that user completely forgets about it, and ignores its existence. If instead of the magical operation of "first clean the browser cache" when facing a bug, they must use a new superstition which is "clean the assets" when facing a bug: it's useless. No, you don't have to clean the assets:
www.yiiframework.com/wiki/148/understanding-assets/#hh4
Many newcomers ask: "What do we do with the assets folder?", and the answer is "Mostly nothing".
In limeSurvey specific case:
When using the template editor, assets are refreshed when the page is saved.
When using comfortUpdate, assets are refreshed.
So for normal users, assets are refresh when they need it and they never have to worry about cleaning the assets cache, and they don't need to have a magical button to press as a superstition when they face a problem.
Advanced users editing a template via FTP should use debug mode, then the asset manager is not used. When they upload their working template to the live server: new fresh assets are created. If they go in the quick and dirty way by directly editing a template on a live server via FTP: then they need to know the trick of the asset number. But only those users in this very specific case need it.
So, we avoid that situation where each bug report or complaint in the forum receive a systematic first answer: "please press the magical button that we don't really understand but that maybe will magically solve your problem".
