View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|17716||Bug reports||ComfortUpdate||public||2021-11-11 11:31||2021-12-01 09:28|
|Summary||17716: When running ComfortUpdate at v3.19 it only offers LS5.x. Updating to the latest 3.x version is not possible|
|Description||I just wanted to update a customer's 3.19.3 system to the latest 3.x release. After having entered a ComfortUpdate key, I am ONLY presented with the option to go directly to version 5.x. This is NOT intended because we want to stay at the 3.x LTS version. But that option is not offered, see screenshot.|
When trying to update from Version 3.27.3+210615, 5.x AND 3.x are shown as options
|Steps To Reproduce||Steps to reproduce|
Run ComofrtUpdate an 3.19.3
See 3.x and 5.x as options
Only v5.x is offered to update to.
|Tags||No tags attached.|
|Complete LimeSurvey version number (& build)||Version 3.19.3+191023|
|I will donate to the project if issue is resolved||No|
|Database type & version||MySQL 5|
|Server OS (if known)||Ubuntu 18|
|Webserver software & version (if known)||Apache 2.0|
|Strange. @c_schmitz, known issue?|
If the system hasn't changed the ComfortUpdate offering has to be whitelisted for your version/build number.
Looks like the older versions are not on the list.
I was able to get offerings e,g. for Version 3.23.7+201006 ComfortUpdate:
3.27.24 (211108) labeled as unstable
5.2.0 (211110) labeled as stable
|@ollehar, @c_schmitz, would it be possible to (temporarily) add the mentioned version to the supported list?|
The issue is now fixed. This was not bound to a certain LS3 version, but a range of versions.
All current and future 3.x versions now should be offered the latest 3.x, as well as the latest 5.x.
Thanks for the fast fix!
I now see the update available. When trying to run it, I get this error at step 3, see screenshot:
An error occured while creating your update package file. Please contact the LimeSurvey team."
I have seen the same error at various updates. The simply solution is to just run the update again. That has always worked fine. So question is: What is causing this? Should we add a note like "Please try again."? Because this always works at the second run, in this case as well, see screenshot.
|I can second that issue. That is not always the case, but I have seen this from time to time.|
|@c_schmitz, for old 2.06 version only LS v5.x is offered as an update, see screenshot. Is that intended or should we also offer 3.x?|
That is intended.
I will look into the server error thing.
|New version released|
|2021-11-11 11:31||Mazi||New Issue|
|2021-11-11 11:31||Mazi||File Added: image.png|
|2021-11-11 11:35||ollehar||Note Added: 67248|
|2021-11-11 11:35||ollehar||Bug heat||0 => 2|
|2021-11-11 14:35||jelo||Note Added: 67252|
|2021-11-11 14:35||jelo||Bug heat||2 => 4|
|2021-11-11 16:49||Mazi||Note Added: 67257|
|2021-11-11 16:49||Mazi||Bug heat||4 => 6|
|2021-11-11 17:46||c_schmitz||Assigned To||=> c_schmitz|
|2021-11-11 17:46||c_schmitz||Status||new => assigned|
|2021-11-11 19:09||c_schmitz||Status||assigned => resolved|
|2021-11-11 19:09||c_schmitz||Resolution||open => fixed|
|2021-11-11 19:09||c_schmitz||Note Added: 67260|
|2021-11-11 19:09||c_schmitz||Bug heat||6 => 8|
|2021-11-12 09:31||Mazi||Note Added: 67265|
|2021-11-12 09:31||Mazi||File Added: image-2.png|
|2021-11-12 09:31||Mazi||File Added: image-3.png|
|2021-11-12 10:39||jelo||Note Added: 67272|
|2021-11-15 14:17||Mazi||Note Added: 67329|
|2021-11-15 14:17||Mazi||File Added: image-4.png|
|2021-11-15 14:32||c_schmitz||Note Added: 67330|
|2021-11-15 14:38||c_schmitz||Note Edited: 67330||View Revisions|
|2021-12-01 09:28||c_schmitz||Note Added: 67628|
|2021-12-01 09:28||c_schmitz||Status||resolved => closed|