View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 14
IDProjectCategoryView StatusDate SubmittedLast Update
10172Bug reportsComfortUpdatepublic2015-12-20 15:282016-05-12 10:39
ReporterDenisChenu Assigned ToLouisGac 
PrioritynormalSeverityminor 
Status closedResolutionfixed 
Product Version2.06+ 
Summary10172: Easy to do error when use confortupdate
Description

When a security alert is shown : we go to the confort update scree.

Here the 2.5RC is up : it's the first button on the link.

Steps To Reproduce

Go to security updayte

Additional Information

I think we must put after the "security" update (and add a confrim, nbut it's another issue)

ANd : user have ComfortUpdate just not want to update to RC unstable version.

TagsNo tags attached.
Attached Files
Capture du 2015-12-20 15-02-57.png (15,011 bytes)   
Capture du 2015-12-20 15-02-57.png (15,011 bytes)   
Bug heat14
Complete LimeSurvey version number (& build)151205
I will donate to the project if issue is resolvedNo
Browsernot relevant
Database type & versionnot relevant
Server OS (if known)n
Webserver software & version (if known)not relevant
PHP Versionnot relevant

Relationships

Relationship GraphDependency Graph
related to 10294 closedLouisGac Annoying info about unstable release available to all users 

Users monitoring this issue

htwsaar, LouisGac

Activities

Mazi

Mazi

2016-01-28 08:46

updater   ~34401

I totally agree to that. We should:

  1. List the stable version first.

  2. Clearly mark the unstable version as "Not for production use" (or similar).

I also noticed that unstable versions are announced by ComfortUpdate even if someone has the latest stable version installed. Why do we do that?
There have been several complaints at the forums of users who have accidentally updated to a (partly unusable) unstable version because of this.

  1. We should either not show a pop-up for unstable versions (my recommendation) or clearly mark those as "Not for production use" (or similar) at the popup.
southcot

southcot

2016-01-28 08:54

reporter   ~34402

Developing a way of invoking a roll-back would be helpful too. Even a simple flag as to whether the comfort upgrade invokes changes that would conflict with the previous version would be helpful. As in cases where it didn't data entered after the upgrade could be retained.
htwsaar

htwsaar

2016-03-21 18:06

reporter   ~36693

We have the same isue but with the latest version of 2.06 stable (160315), too.

Strange thing, that there is already a stable version of 2.5 (as mentioned on the website = 2.5+ 160317) but we see the link for comfort update to 2.5 RC8 (160331) (instable), still. (using 2.06lts 160315)

I can't see the sense in updating to an older instable version through comfort update, if there is a later stable version available.

Could you check this, please?
htwsaar

htwsaar

2016-03-21 18:10

reporter   ~36694

BTW: above that update link in comfort update we see a process gif and the message that one should wait, it tries to connect to the server ... (Bitte warten, verbinde mit Server ...), all the time and nothing happening.
LouisGac

LouisGac

2016-03-22 09:02

developer   ~36696

Last edited: 2016-03-22 09:03

The RC update is only here to provide a way to update from 2.06 to 2.5 via comfortUpdate.

When 2.5.1 will be released, a direct update from 2.06 to 2.5 will be provided.

In 2.06lts, you can turn off all the notifications in application/config/version.php, set $config['updatable'] to false.
LouisGac

LouisGac

2016-05-11 10:33

developer   ~38302

2.5 update release
no more RC
c_schmitz

c_schmitz

2016-05-12 10:39

administrator   ~38433

Version 2.50 Build 160512 released

Issue History

Date Modified Username Field Change
2015-12-20 15:28 DenisChenu New Issue
2015-12-20 15:28 DenisChenu Status new => assigned
2015-12-20 15:28 DenisChenu Assigned To => c_schmitz
2015-12-20 15:28 DenisChenu File Added: Capture du 2015-12-20 15-02-57.png
2016-01-28 08:46 Mazi Note Added: 34401
2016-01-28 08:47 Mazi Issue Monitored: LouisGac
2016-01-28 08:54 southcot Note Added: 34402
2016-01-28 10:24 c_schmitz Assigned To c_schmitz => LouisGac
2016-02-03 18:43 DenisChenu Relationship added related to 10294
2016-03-21 18:06 htwsaar Note Added: 36693
2016-03-21 18:06 htwsaar Issue Monitored: htwsaar
2016-03-21 18:10 htwsaar Note Added: 36694
2016-03-22 09:02 LouisGac Note Added: 36696
2016-03-22 09:03 LouisGac Note Edited: 36696
2016-05-11 10:33 LouisGac Note Added: 38302
2016-05-11 10:33 LouisGac Status assigned => resolved
2016-05-11 10:33 LouisGac Resolution open => fixed
2016-05-12 10:39 c_schmitz Note Added: 38433
2016-05-12 10:39 c_schmitz Status resolved => closed
2021-08-02 16:18 guest Bug heat 10 => 14