View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0021404 | mantisbt | filters | public | 2016-07-21 10:09 | 2018-05-13 16:53 |
Reporter | raedor | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.3.0 | ||||
Fixed in Version | 2.13.0 | ||||
Summary | 0021404: System Error on changing filters | ||||
Description | I updated my mantis installation succesfully to 1.3.0 (at least the check script ran through without problems). But now, evyer time I am on the "View issues" page and trying to change the filters, I get: SYSTEM ERROR | ||||
Steps To Reproduce |
| ||||
Tags | No tags attached. | ||||
Seems that json_decode fails (delivers NULL) and filter_ensure_valid_filter is called with it. A bit strange, as I would have expected that the upgrade fails if filter can't be converted to JSON. EDIT (dregad): fix markdown |
|
Does that mean that there are probably other things broken in my installation? What could be a reason for the filter conversion to fail? |
|
The problem is I can't use the filters at all at the moment. Is there any workaround to get them back working? |
|
Hello there, I am facing the same problem with mantis 1.3.3 after I have upgraded from 1.2.12. The problem is actually that $t_setting_arr[1] is either a json string which json_decode can handle perfectly or a serialized php object which will result json_decode to return a JSON_ERROR_SYNTAX error. In this situation $t_filter_array will be a null object and filter_ensure_valid_filter function will fail. The workaround that I have is checking if the $t_filter_array is null after the json decoding and if it is just unserialize the object.
Is there an explanation for this behavior? Is that a bug that is not present in clean installations? Any information will be really appreciated! EDIT (dregad): fix markdown |
|
Hello, I have same problem. |
|
I could't solve it with the browser cookies cleaned. I have read about this solution many times, that's strange! |
|
Some of my staff had this same issue with using Chrome. |
|
I have the same issue here. It appears when switching Projects or when applying filters. It appears on Chrome and IE ! |
|
some of my staff figured out that if you delete your cookies, it will temp solve this problem. But it also will come back later on until you delete out cookies again. |
|
I upgraded from 1.2.19 to 2.0.0 - the faulty behavior in 2.0.0 is the same as described above. |
|
I updated to mantis 2 and i still have the issue. Is there a solution available already? SYSTEM ERROR |
|
This is what helped me to solve the problem, for project I went on query_view_page.php once. |
|
Suggested change for 2.0, "core/filter_api.php", line 486:
Since filter_ensure_valid_filter is almost always called before json_decode and json_decode can return null, this seems the appropriate global resolution. EDIT (dregad): fix markdown |
|
@cproensa, 0021404:0055272 seems like a good idea, what do you think ? |
|
That is covered in PR https://github.com/mantisbt/mantisbt/pull/1091 |
|
Hi, I have also had this issue upgrading from 2.1.19 to 1.3.12. The patch found in the following post "fixed" this issue: https://www.mantisbt.org/forums/viewtopic.php?f=2&t=24034 Thanks |
|
@cproensa's PR 1091 was merged on 05-Mar-2018, so I would assume that this is no longer an issue starting with MantisBT 2.13.0. |
|