View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
18187 | Bug reports | Response browsing | public | 2022-06-09 15:58 | 2023-08-31 19:06 |
Reporter | DenisChenu | Assigned To | |||
Priority | none | Severity | partial_block | ||
Status | acknowledged | Resolution | open | ||
Product Version | 3.28.x | ||||
Summary | 18187: No alert shown if there are issue in database | ||||
Description | When some question didn't have columln related : no error is shown when
| ||||
Steps To Reproduce | Steps to reproduce
Expected resultAt 5 : an email sent to admin user, maybe error shown to user ? Actual resultNo error : all is good. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Bug heat | 4 | ||||
Complete LimeSurvey version number (& build) | 3.28.14 + 5.3.19 | ||||
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 | ||||
Is this blocking? |
|
5.X have same issue , 500 : Erreur interne au serveur |
|
Clearly … have the information about a broken survey data 5 month after is totally blocking ! |
|
partial_block because it does not happen to everybody ? |
|
I am not saying is not important. Seems like it is. I believe we could implement an email notification in case of 500 erros (and others). partial_block seems OK. |
|
It's not a 500 error here … in 2.6 : if such error happen : admin user receive an email, It's not related to Yii error or anything else … And about show warning in browse it's really a think to do : "Your database seems to have an issue, some question didn't have related columns" or somthink like that. We surely use an empty() but must use an isset ? |
|
Maybe we should add here https://github.com/LimeSurvey/LimeSurvey/blob/master/application/helpers/expressions/em_manager_helper.php#L5065 Something like this (which is used already on the code)
I would add it to DEV as to have more testing time. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2022-06-09 15:58 | DenisChenu | New Issue | |
2022-06-09 15:58 | DenisChenu | File Added: survey_archive_brokenHackDB.lsa | |
2022-06-09 18:14 | DenisChenu | Summary | No alerte shown if there are issue in database => No alert shown if there are issue in database |
2022-06-09 18:14 | DenisChenu | Complete LimeSurvey version number (& build) | 3.28.14 => 3.28.14 + 5.3.19 |
2022-06-09 18:14 | gabrieljenik | Status | new => acknowledged |
2022-06-09 18:14 | gabrieljenik | Note Added: 70319 | |
2022-06-09 18:14 | gabrieljenik | Bug heat | 0 => 2 |
2022-06-09 18:15 | DenisChenu | Note Added: 70320 | |
2022-06-09 18:15 | DenisChenu | Bug heat | 2 => 4 |
2022-06-09 18:16 | DenisChenu | Note Added: 70321 | |
2022-06-09 18:18 | DenisChenu | Note Added: 70322 | |
2022-06-09 18:29 | gabrieljenik | Note Added: 70324 | |
2022-06-09 18:36 | DenisChenu | Note Added: 70325 | |
2022-06-09 18:36 | DenisChenu | Severity | block => partial_block |
2023-08-31 19:06 | gabrieljenik | Note Added: 76830 |