| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 09298 | Bug reports | Central participant database | public | 2014-10-13 13:26 | 2014-10-20 13:49 |
| Reporter | DLange | Assigned To | c_schmitz | ||
| Priority | normal | Severity | minor | ||
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 2.05+ | ||||
| Summary | 09298: Sort for a numeric token_attribute field in any participant table fails completely | ||||
| Description | If you have a participant or token attribute that contains a number (e.g. a group number) clicking on it (Javascript sort) produces a random result, not a sorted order | ||||
| Steps To Reproduce | Global participant table | ||||
| Additional Information | The bug is the same on the global participant table and individual survey participant tables. | ||||
| Tags | No tags attached. | ||||
| Bug heat | 6 | ||||
| Complete LimeSurvey version number (& build) | 2.05+ (141003) | ||||
| I will donate to the project if issue is resolved | No | ||||
| Browser | |||||
| Database type & version | not applicable | ||||
| Server OS (if known) | not applicable | ||||
| Webserver software & version (if known) | not applicable | ||||
| PHP Version | not applicable | ||||
 |
Further observations: As sorting for numeric data works with the built in fields there seems to be a dependency on extra attribute fields (these are alnum not numeric). Larger sets (150 participants in 15 groups) are rather unmanageable with that bug present. |
 |
What happens if that column contains text? Is that sorted properly? |
|
|
Yes. If it contains text-strings it sorts correctly. |
 |
Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=14559 |
|
|
Version 2.05+ Build 141020 released |
