| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 05671 | Bug reports | Other | public | 2012-01-18 08:47 | 2012-01-30 18:41 |
| Reporter | TMSWhite | Assigned To | TMSWhite | ||
| Priority | normal | Severity | minor | ||
| Status | closed | Resolution | fixed | ||
| Product Version | 1.92RC2 | ||||
| Fixed in Version | 1.92RC3 | ||||
| Summary | 05671: validation tips only appear when there are errors, and are not color-coded | ||||
| Description | When there are validation criteria, they are not appearing until errors are found. | ||||
| Tags | No tags attached. | ||||
| Bug heat | 6 | ||||
| Complete LimeSurvey version number (& build) | 12099 | ||||
| I will donate to the project if issue is resolved | No | ||||
| Browser | |||||
| Database type & version | Mysql 5.3 | ||||
| Server OS (if known) | Windows XP | ||||
| Webserver software & version (if known) | XAMPP | ||||
| PHP Version | 5.3 | ||||
 |
Fixed in revision 12105 |
 |
In revision 12106 it seems to work for my own test survey but not for the LS2 Validation Samples survey. When importing the survey (from revision 12105) the same thing mentioned in issue 05658 happend and on the first page the tips are not shown (see valNotShown.jpg). If you enter something wrong an click/move out the question then it is shown in red (see valShownAfterError.jpg) and if you then enter a correct value it will be in green. |
|
|
That is the desired behavior. I modified the sample survey to use 'hide_tip' for most of the questions on the first page so that I could verify that the validation tips would start hidden and show when needed. |
|
|
If it should be so then it's okay. Though I don't think it's very participant friednly if you let them enter a value and don't tell them which value you expect. I mean, 0 to 5 is not that big range that you can surely assume the participant enters a fitting value. |
|
|
I could change the tests. A better one for hiding the tip is the age. It is filtered to be between 0 and 115 years, but I don't think it is critical to state that initially - only if people put in invalid data. |
|
|
That's true. For the min/max question you could set the "Maximum characters" to 1 so there might be better chance that something from 0 to 5 is enterd. |
 |
1.92RC3 released |
