View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011528 | mantisbt | code cleanup | public | 2010-02-19 22:13 | 2010-02-22 14:34 |
| Reporter | dhx | Assigned To | dhx | ||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.2.0 | ||||
| Target Version | 1.2.0 | Fixed in Version | 1.2.0 | ||
| Summary | 0011528: Don't call config_flush_cache() in bug_actiongroup_ext.php | ||||
| Description | There is no need to call config_flush_cache() in bug_actiongroup_ext.php because the configuration cache already takes into account whether a configuration setting is per-user and per-project. Additionally, bug_actiongroup_ext.php needs a round of code cleanup. | ||||
| Tags | No tags attached. | ||||
|
MantisBT: master-1.2.x 00c58a29 2010-02-19 22:14 Details Diff |
Fix 0011528: Don't call config_flush_cache() in bug_actiongroup_ext.php There is no need to call config_flush_cache() in bug_actiongroup_ext.php because the configuration cache already takes into account whether a configuration setting is per-user and per-project. Additionally, bug_actiongroup_ext.php has been cleaned up to reduce code complexity and increase the efficiency of this page. |
Affected Issues 0011528 |
|
| mod - bug_actiongroup_ext.php | Diff File | ||
|
MantisBT: master 99c55618 2010-02-19 22:14 Details Diff |
Fix 0011528: Don't call config_flush_cache() in bug_actiongroup_ext.php There is no need to call config_flush_cache() in bug_actiongroup_ext.php because the configuration cache already takes into account whether a configuration setting is per-user and per-project. Additionally, bug_actiongroup_ext.php has been cleaned up to reduce code complexity and increase the efficiency of this page. |
Affected Issues 0011528 |
|
| mod - bug_actiongroup_ext.php | Diff File | ||
