View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 06716 | Bug reports | Survey editing | public | 2012-10-16 20:55 | 2026-11-19 22:24 |
| Reporter | TMSWhite | Assigned To | |||
| Priority | low | Severity | minor | ||
| Status | closed | Resolution | fixed | ||
| Summary | 06716: question view screen does not syntax-highlight any advanced question options | ||||
| Description | The following advanced question options should be syntax-highlighted on the question summary admin page. None of them are: min_num_value_n | ||||
| Steps To Reproduce | Load /docs/demosurveys/ls2_plurals_test.lss | ||||
| Tags | No tags attached. | ||||
| Bug heat | 4 | ||||
| Complete LimeSurvey version number (& build) | 121017 | ||||
| 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 | ||||
| Git branch / Pull Request URL | |||||
| related to | 06763 | closed | Question attributes are not part of the question objects yet |
|
Hello Thomas, |
|
|
The syntax highlighting makes it easy to see syntax errors; and users can click on the variables within the equations to jump directly to edit screens for those questions (plus see metadata about them in case they don't recognize the question from the variable name). Yes, they could just use the Show Logic File buttons, but having several places to view potential syntax errors enhances usability. I didn't know where to look to implement the syntax highlighting in 2.0; and was asked not to add that feature (the list of all non-empty attributes) to 1.92. |
|
|
Ah ok, I was asking because it sounded like a bug - so it is more of a missing feature. I will have to find out how to make EM do the syntax highlighting first and will add it, accordingly. |
|
|
Correct - it is a missing feature - I mis-categorized it. |
|
|
Moving this to 2.1 because it requires a new inputtype in question attributes. I'd rather not touch this in 2.0 because the implementation in 2.1 will be different (due to the rewrite of question types) |
|
|
Fix me! ;) |
|
|
In LimeSurvey 7 the question summary shows the advanced settings that accept expressions (min/max answers, min/max values, multiflexible min/max, etc.) syntax-highlighted by Expression Manager. Closing as fixed. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-10-16 20:55 | TMSWhite | New Issue | |
| 2012-10-22 15:15 | c_schmitz | Note Added: 21536 | |
| 2012-10-22 15:15 | c_schmitz | Assigned To | => c_schmitz |
| 2012-10-22 15:15 | c_schmitz | Status | new => feedback |
| 2012-10-23 19:03 | TMSWhite | Note Added: 21571 | |
| 2012-10-23 19:03 | TMSWhite | Status | feedback => assigned |
| 2012-10-23 21:10 | c_schmitz | Note Added: 21573 | |
| 2012-10-23 21:16 | TMSWhite | Note Added: 21574 | |
| 2012-10-24 09:05 | c_schmitz | Project | Bug reports => @10@ |
| 2012-10-24 09:06 | c_schmitz | Assigned To | c_schmitz => user16774 |
| 2012-10-24 09:06 | c_schmitz | Product Version | 2.00+ => |
| 2012-10-24 09:10 | c_schmitz | Relationship added | related to 06763 |
| 2012-10-24 09:11 | c_schmitz | Note Added: 21579 | |
| 2012-10-26 17:24 | c_schmitz | Note Edited: 21579 | |
| 2012-11-26 22:25 | c_schmitz | Note Added: 22562 | |
| 2012-11-26 22:49 |
|
Priority | normal => low |
| 2012-11-26 22:49 |
|
Status | assigned => acknowledged |
| 2019-09-23 12:20 | c_schmitz | Status | acknowledged => confirmed |
| 2019-11-01 17:25 | c_schmitz | Category | Survey design => Survey editing |
| 2026-11-19 22:24 | c_schmitz | Note Added: 87747 | |
| 2026-11-19 22:24 | c_schmitz | Status | confirmed => closed |
| 2026-11-19 22:24 | c_schmitz | Resolution | open => fixed |