View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|13250||Feature requests||[All Projects] Theme editor||public||2018-01-26 09:59||2019-06-20 11:15|
|Target Version||Fixed in Version|
|Summary||13250: Update button instead of Uninstalling/Reinstalling the theme to reflect config.xml changes|
As it can be seen from Issue 13232 ( https://bugs.limesurvey.org/view.php?id=13232 ) , the only way to reflect changes on the config.xml file of an extended theme, is by uninstalling and reinstalling the theme, which is not only unintuitive, but also tedious since sometimes it is necessary to set back the theme in the survey, and for sure it is always necessary to select again the theme variation and set other parameters (like inheritance or logo).
The idea would be to have theme versions, just like asset versions in the version.php file, by changing the version, a update button located right over the uninstall button will be clickable, triggering a reload of the theme and thus reflecting the config.xml changes.
IMHO, only extended themes can be updated, and the version should be in a version file in the theme folder (that is, in the upload folder)
|Tags||No tags attached.|
Anyone on this? What's the use of theme "version" and "last_update" fields inside config.xml
Reset button recall config.xml
Need a better system when we can update theme via Store
And we need an theme API control …
I've just tried to import a same-name theme but using a newer version number and recent last_update value inside config.xml.
If we are not comfortable with deletions, maybe is an idea to rename old «custom_theme» as «custom_theme_version» and new custom_theme can be uploaded.
|2018-01-26 09:59||Gabryxx7||New Issue|
|2019-06-19 11:52||tassoman||Note Added: 52455|
|2019-06-19 14:08||DenisChenu||Note Added: 52456|
|2019-06-20 11:08||tassoman||Note Added: 52484|
|2019-06-20 11:14||DenisChenu||Relationship added||duplicate of 14207|
|2019-06-20 11:15||DenisChenu||Relationship added||related to 14208|