View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 2
IDProjectCategoryView StatusDate SubmittedLast Update
05270Bug reportsAssessmentspublic2011-06-12 13:342011-06-16 14:22
Reporteruser14234Assigned Toc_schmitz  
PrioritynormalSeveritytweak 
Status closedResolutionfixed 
Product Version1.91+ 
Summary05270: The assessments are not returned in any order - consequently any presentation which requires a fixed order is impossible
Description

The do_assessments function in index.php orders the assessments returned ONLY by scope. This leaves the order in which multiple assessment results for a single scope undetermined.
In practice it is most likely to return them with the most recently modified first - however this will not continue after a database backup and restore.

If you (as I do) make rather complex assessments which depend upon one another both for readability and in terms of javascript logic. This is unacceptable.

Steps To Reproduce

create two assessments for a single scope - the second added assessment will be displayed first on the page and there is no control to change this.

Edit the first survey or backup and restore your db - the presented order of the assessments is reversed.

Additional Information

A very simple work around is to modify index.php and replace
ORDER BY scope

with
ORDER BY scope,id

Then you can ensure the returned order will stay constant. A more permanent fix probably allows people to order the assessments through the web interface - not something I would be able to implement I'm afraid

TagsNo tags attached.
Bug heat2
Complete LimeSurvey version number (& build)10202
I will donate to the project if issue is resolvedNo
Browser
Database type & versionPostgres 8.2
Server OS (if known)Debian
Webserver software & version (if known)Apache/2.2.9 (Debian)
PHP Version5.2.6-1+lenny9

Users monitoring this issue

There are no users monitoring this issue.

Activities

c_schmitz

c_schmitz

2011-06-13 16:55

administrator   ~15418

Thank you. I applied that fix for now.
c_schmitz

c_schmitz

2011-06-16 14:22

administrator   ~15459

1.91+ version released

Issue History

Date Modified Username Field Change
2011-06-12 13:34 user14234 New Issue
2011-06-13 16:55 c_schmitz Note Added: 15418
2011-06-13 16:55 c_schmitz Status new => resolved
2011-06-13 16:55 c_schmitz Resolution open => fixed
2011-06-13 16:55 c_schmitz Assigned To => c_schmitz
2011-06-16 14:22 c_schmitz Note Added: 15459
2011-06-16 14:22 c_schmitz Status resolved => closed