| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 15547 | Bug reports | Expression Manager | public | 2019-11-08 08:04 | 2019-11-15 08:27 |
| Reporter | DenisChenu | Assigned To | |||
| Priority | none | Severity | minor | ||
| Status | new | Resolution | open | ||
| Product Version | 3.19.3 | ||||
| Summary | 15547: Invalid error count on Survey Logic file for subquestion relevance | ||||
| Description | When there are subquestion relevance : error count is more higher than needed | ||||
| Steps To Reproduce | Create a question with 3 sub questions | ||||
| Additional Information | Issue in SurveyLogicFile function : | ||||
| Tags | No tags attached. | ||||
| Bug heat | 6 | ||||
| Complete LimeSurvey version number (& build) | 3.19.3 github | ||||
| I will donate to the project if issue is resolved | No | ||||
| Browser | not relevant ? | ||||
| Database type & version | not relevant? | ||||
| Server OS (if known) | not relevant ? | ||||
| Webserver software & version (if known) | not relevant ? | ||||
| PHP Version | not relevant ? | ||||
 |
Potential fix ( with related) : add a ExpressionManager::SurveyLogicInfo with errors (and warnings) , used ONLY for SurveyLogicFile … ExpressionManager::HasErrors are used in some relevance system (show question if there are error in relevance) if i remind (unsure). |
 |
I'm more and more confused with labeling of "Product Version". So the current label system is not able to reflect the developement status in between. |
 |
If you use the git version, mention the last commit merged - that would be the ideal case scenario. But in this case, we know Denis is running (I assume) the latest git version :) |
|
|
:) Yes always before reporting. But @jelo are right : here it's a 3.19.3 git, and not a 3.19.4 :). But if it happen in 3.19.3 git, it happen in 3.19.3 (else i put the build number to the link brokin something at github) |
