View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 6
IDProjectCategoryView StatusDate SubmittedLast Update
10383Bug reportsComfortUpdatepublic2016-02-11 11:382016-02-12 17:57
Reporterasshank Assigned ToLouisGac 
PrioritynormalSeverityminor 
Status closedResolutionfixed 
Product Version2.50.x 
Fixed in Version2.50.x 
Summary10383: Commit version info into db after comfortupdate
Description

After completing comfortupdate the next user/admin is confronted with a button to update the database.
But during the comfort update it is stated that the database is not changed.

So IMHO the DBVersion change should be part of the comfortupdate.

Steps To Reproduce

Do comfortupdate
Login after comfortupdate success

See the message:

"Database upgrade

Please verify the following information before continuing with the database upgrade:
"

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)160210
I will donate to the project if issue is resolvedNo
Browser*
Database type & version253-255
Server OS (if known)*
Webserver software & version (if known)*
PHP Version5.5.3

Users monitoring this issue

There are no users monitoring this issue.

Activities

LouisGac

LouisGac

2016-02-11 17:44

developer   ~34936

https://github.com/LimeSurvey/LimeSurvey/commit/e9443caa4483a46b5ceb6c910a7c0d1d5142bb7f

should be ok now
asshank

asshank

2016-02-11 20:28

reporter   ~34964

Hard to feedback.
Let's await the next comfortupdate (or the one after that). It should be very soon.. the current stable release 160210 is admin-homepage-unstable!
asshank

asshank

2016-02-12 10:57

reporter   ~34990

After comfortupdate to 160212 the DBVersion is still 255. So there was need to update the database after comfortupdate.

So if in a future version 255 bumps to 256 (or heigher) it can be judged if it is resolved.
asshank

asshank

2016-02-12 17:43

reporter   ~35057

after comfortupdate to 160213 the dbversion is upgraded to 256.
This is done by pushing the button after re-login (so not automaticaly after te comfortupdate).

Could me by design now because a db-structure change has been made (so the comfortupdate stated).
c_schmitz

c_schmitz

2016-02-12 17:57

administrator   ~35060

Yes, that is by design.

Issue History

Date Modified Username Field Change
2016-02-11 11:38 asshank New Issue
2016-02-11 11:38 asshank Status new => assigned
2016-02-11 11:38 asshank Assigned To => c_schmitz
2016-02-11 17:44 LouisGac Note Added: 34936
2016-02-11 17:44 LouisGac Status assigned => feedback
2016-02-11 20:28 asshank Note Added: 34964
2016-02-11 20:28 asshank Status feedback => assigned
2016-02-12 10:57 asshank Note Added: 34990
2016-02-12 11:01 c_schmitz Status assigned => resolved
2016-02-12 11:01 c_schmitz Fixed in Version => 2.5
2016-02-12 11:01 c_schmitz Resolution open => fixed
2016-02-12 11:01 c_schmitz Assigned To c_schmitz => LouisGac
2016-02-12 11:01 c_schmitz Status resolved => closed
2016-02-12 17:43 asshank Note Added: 35057
2016-02-12 17:43 asshank Status closed => feedback
2016-02-12 17:43 asshank Resolution fixed => reopened
2016-02-12 17:57 c_schmitz Note Added: 35060
2016-02-12 17:57 c_schmitz Status feedback => resolved
2016-02-12 17:57 c_schmitz Resolution reopened => fixed
2016-02-12 17:57 c_schmitz Status resolved => closed