View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005438 | mantisbt | bugtracker | public | 2005-04-15 02:00 | 2005-04-18 10:17 |
Reporter | urkle | Assigned To | thraxisp | ||
Priority | normal | Severity | minor | Reproducibility | sometimes |
Status | closed | Resolution | fixed | ||
Product Version | git trunk | ||||
Summary | 0005438: *_bug_threshold set to an array in the new DB based configuration | ||||
Description | An array can be stored in the config variable in the database if not all thresholds are checked above the lowest. | ||||
Steps To Reproduce | in my mantis install of 0.19.2 I have a new access level of logger for a logging user which logs mantis communication to a list. When I tested a copy of the existing DB on the CVS from yesterday, after I "updated" the configuration in the "Manage configuration" screen for workflow threasholds, arrays were stored in the database for the handle, assign, move, delete, and reopen threasholds as the logger user is unchecked for those. (so it contained 55,70,90). This caused several queries, namely on the advanced filter page to fail and spit the SQL query with "Array" in the SQL where a access level threshold should be. If I go back to the "Manage configuration" and check the logger for those a integer of value "50" is stored instead and the site works. | ||||
Additional Information | I would figure that the "Manager configuration" screen should have a "drop box" or options buttons of what the lowest threshold should be instead of a series of check boxes. Also the code seems to be confused by the fact that my "50:logger" is at the end of the g_access_levels_enum_string instead of in the middle. (as 50 is less than 55 and thus 55 should be stored in the DB) | ||||
Tags | No tags attached. | ||||
moving my 50:logger to before 55:developer in the g_access_levels_enum_string in config_inc.php works around this issue. |
|
There are two issues here: |
|
Fixed in CVS. The relevant modules are: |
|