View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0023437 | mantisbt | filters | public | 2017-10-05 02:36 | 2020-09-17 16:40 |
Reporter | atrol | Assigned To | atrol | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Summary | 0023437: Fatal PHP error when trying to edit a stored filter | ||||
Description | Getting the following error when editing a stored filter for "All Projects"
| ||||
Tags | No tags attached. | ||||
related to | 0024045 | new | filter_deserialize() calling filter_ensure_valid_filter() with wrong parameter type |
I couldn't reproduce with your steps... Can you show what string is stored in database for that filter id? seems like it has stored literal 'v9#false', so the problem may be at creation+save of the filter. Can you also try your error scenario with https://github.com/mantisbt/mantisbt/pull/1091 ? |
|
Tried a complete other system (XAMPP on Windows) and was also not able to reproduce.
right
Not at the moment, maybe tomorrow |
|
By hardcoding a filter with corrupted data, said PR also throws errors. I'm not sure if it's worth to do the same approach for fixes in current code. The point of rewriting the load and save routines in that PR is precisely to help with these issues. Still, i'd like to know how your scenario got the bad filter saved, in the first place. |
|
Branch cproensa/0023436_edit_filter_project
Me too, but I am not sure if it's better to invest time in reviewing and testing branch 0023436_edit_filter_project. |
|
Tried latest master on Ubuntu 16.04 and was no longer able to reproduce. |
|