- Posts: 21
- Thank you received: 1
Ask the community, share ideas, and connect with other LimeSurvey users!
in documentation wrote: «NOTE: to avoid that, you can force the use to the XML rather than DB. In config.php turn debug mode on and uncommment:
'force_xmlsettings_for_survey_rendering' => true, // Uncomment if you want to force the use of the XML file rather than DB (for easy theme development)»
<files> <css> <add>css/ajaxify.css</add> <add>css/animate.css</add> <add>css/variations/sea_green.css</add> <replace>css/theme.css</replace> <replace>css/custom.css</replace> </css> <js> <replace>scripts/theme.js</replace> <replace>scripts/ajaxify.js</replace> <add>scripts/custom.js</add> <add>scripts/js.cookie.js</add> </js> <print_css> <add>css/print_theme.css</add> </print_css> </files>
custom.css are not related : maybe caching issue (with debug at 2, i think there are no assets).mad99 wrote: @Denis: The problem with the change in config.php is/was, the changed custom.css files had no impact anymore. Maybe it was also the «force_xmlsettings_for_survey_rendering» element itself. I don't now.
You loose user current global config.mad99 wrote: -1. What is the draw-back from the use of «reset» button in Theme-List?
Yes, sure, but then : a new option must be automatically set to "Inherit", right ?LouisGac wrote: We should add a "soft reset" mode that only reload the options setting at global level.