related to
child of
duplicate of
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 03825 | Bug reports | Survey taking | public | 2009-11-08 02:12 | 2009-12-11 12:17 |
| Reporter | tpartner | Assigned To | tpartner | ||
| Priority | normal | Severity | minor | ||
| Status | closed | Resolution | fixed | ||
| Target Version | 1.87RC5 | Fixed in Version | 1.87RC5 | ||
| Summary | 03825: List (radio) by columns not behaving | ||||
| Description | If the "Display columns" attribute of a radio question is set to 5 or 7 the lists are not displayed properly. The last column seems to be dropped or empty. In the attached image there should be 5 columns of radio buttons but the <ul class="last"> is empty so only 4 columns are displayed. I've tested all shipped templates with the same results. | ||||
| Tags | No tags attached. | ||||
| Bug heat | 4 | ||||
| Complete LimeSurvey version number (& build) | |||||
| I will donate to the project if issue is resolved | |||||
| Browser | |||||
| Database type & version | |||||
| Server OS (if known) | |||||
| Webserver software & version (if known) | |||||
| PHP Version | |||||
 |
@ tpartner: can you fix this on your own? |
 |
When displaying select/radios in columns and the number of answers doesn't divide nicely into the number of rows, empty columns are sometimes created, messing up the layout and confusing the user. This is because there is a calculation "maxNumberOfRows = numberOfAnswers/numberOfColumns" (rounded up). This calculation then results in the MaxNumberOfRows being inserted into each column which will, in some cases, leave empty columns. An example: My solution is to add another calculation to limit the numberOfColumns - "numberOfColumns = numberOfAnswers/maxNumberOfRows". (common.php checked in at revision 7878) This will get rid of the extra columns but I'm not sure how to articulate it in the documentation wiki. |
|
|
Fixed at version 7878 and I've updated the documentation wiki. |
