View Issue Details

Related ChangesetsJump to NotesJump to History
This bug affects 1 person(s).
 6
IDProjectCategoryView StatusDate SubmittedLast Update
10296Bug reportsSurvey takingpublic2016-02-03 22:192016-02-10 21:02
Reporterwingman123 Assigned Toollehar  
PriorityhighSeveritypartial_block 
Status closedResolutionfixed 
Product Version2.50.x 
Fixed in Version2.50.x 
Summary10296: Group Order not incrementing when creating brand new survey in Postgres
Description

In Release 2.50+ Build 160202, with Postgres as a DB, when creating a brand new survey the "group_order" field in the "lime_groups" table does not auto-increment, every new group is given a group order value of 0. This leads to issue with survey taking in Group by group mode as only one group is displayed then the survey skips to submit.
I tried deleting a group then adding a new group and that group received a 1. But I tried this again and it didn't work.
I also tried manually updating an existing groups group order from 0 to 1 in the DB. This lead to the expected behavior as any subsequent group added had an incremented group order.

Steps To Reproduce
  • Use Release 2.50+ Build 160202
  • Use postgres as DB
  • Create new survey
  • create a group, add a question to the group
  • create another group, add a question to that group
  • Observe the Group Order under "List Groups" be 0 for both groups
  • Survey navigation should also skip the second or first group.
    (survey attached)
TagsNo tags attached.
Attached Files
limesurvey_survey_673135.lss (12,604 bytes)
Bug heat6
Complete LimeSurvey version number (& build)Release 2.50+ Build 160202
I will donate to the project if issue is resolvedNo
BrowserChrome, Firefox
Database type & versionPostgres 9.4.4
Server OS (if known)Mac OSX 10.11
Webserver software & version (if known)Apache/2.4.16
PHP Version5.6.13

Users monitoring this issue

There are no users monitoring this issue.

Activities

ollehar

ollehar

2016-02-05 17:00

administrator   ~34633

I cannot reproduce this with postgres 9.3.10. Try with a newer version of LimeSurvey 2.5?
c_schmitz

c_schmitz

2016-02-05 19:11

administrator   ~34641

I cannot reproduce this either.
Please use the latest 2.5 Build 160204 and try again to install to a clean database and report if you still have the problem.
wingman123

wingman123

2016-02-05 21:04

reporter   ~34645

Ok thanks, i will try that and report back
wingman123

wingman123

2016-02-05 21:22

reporter   ~34646

With 2.5 Build 160204 I tried creating a brand new db, populating, creating a survey, added one group, a question. Then another group and another question. I still get group order = 0 for both groups however. I also tried with postgres 9.3.5 on another machine. It works fine if theres another survey already in the db. Technically Im not sure why this would happen since the code is checking for it. I could look further perhaps i have some setting incorrect or try with a fresh install of postgres itself but I suppose this can be deprioritized since no one else can reproduce the issue. Thanks
ollehar

ollehar

2016-02-08 10:40

administrator   ~34692

OK, I will try with an empty db, too.
ollehar

ollehar

2016-02-08 11:08

administrator   ~34694

I removed all surveys and groups, then added new survey and two groups. Can confirm the bug: group order is 0 for both groups. Will fix.
ollehar

ollehar

2016-02-08 11:48

administrator   ~34695

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=17195
ollehar

ollehar

2016-02-08 12:02

administrator   ~34696

Works for me now, please test and confirm.
wingman123

wingman123

2016-02-08 16:18

reporter   ~34713

Works for me as well. Thanks a lot guys
c_schmitz

c_schmitz

2016-02-10 21:02

administrator   ~34851

2.5 Build 160210 released

Related Changesets

LimeSurvey: master 29bb025a

2016-02-08 10:39:28

ollehar

Details Diff 		Fixed issue 10296: Problem with 0 equals empty string fixed Affected Issues
10296
mod - application/helpers/common_helper.php Diff File

Issue History

Date Modified Username Field Change
2016-02-03 22:19 wingman123 New Issue
2016-02-03 22:19 wingman123 File Added: limesurvey_survey_673135.lss
2016-02-05 17:00 ollehar Note Added: 34633
2016-02-05 19:11 c_schmitz Note Added: 34641
2016-02-05 19:11 c_schmitz Assigned To => c_schmitz
2016-02-05 19:11 c_schmitz Status new => feedback
2016-02-05 21:04 wingman123 Note Added: 34645
2016-02-05 21:04 wingman123 Status feedback => assigned
2016-02-05 21:22 wingman123 Note Added: 34646
2016-02-08 10:40 ollehar Note Added: 34692
2016-02-08 11:08 ollehar Note Added: 34694
2016-02-08 11:31 ollehar Assigned To c_schmitz => ollehar
2016-02-08 11:48 ollehar Changeset attached => LimeSurvey master 29bb025a
2016-02-08 11:48 ollehar Note Added: 34695
2016-02-08 11:48 ollehar Resolution open => fixed
2016-02-08 12:02 ollehar Note Added: 34696
2016-02-08 12:02 ollehar Status assigned => resolved
2016-02-08 12:02 ollehar Fixed in Version => 2.5
2016-02-08 16:18 wingman123 Note Added: 34713
2016-02-10 21:02 c_schmitz Note Added: 34851
2016-02-10 21:02 c_schmitz Status resolved => closed