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|
|Status||closed||Resolution||no change required|
|Summary||0023437: Fatal PHP error when trying to edit a stored filter|
Getting the following error when editing a stored filter for "All Projects"
|Tags||No tags attached.|
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.
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.
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.
|2017-10-05 02:36||atrol||New Issue|
|2017-10-05 02:38||atrol||Description Updated||View Revisions|
|2017-10-05 05:33||cproensa||Note Added: 0057897|
|2017-10-05 06:54||atrol||Note Added: 0057898|
|2017-10-05 18:39||cproensa||Note Added: 0057901|
|2017-10-06 02:40||atrol||Note Added: 0057902|
|2018-02-26 18:31||cproensa||Relationship added||related to 0024045|
|2020-09-06 08:30||atrol||Note Added: 0064369|
|2020-09-06 08:31||atrol||Assigned To||=> atrol|
|2020-09-06 08:31||atrol||Status||new => resolved|
|2020-09-06 08:31||atrol||Resolution||open => no change required|
|2020-09-17 16:40||atrol||Status||resolved => closed|