View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0017837 | mantisbt | bugtracker | public | 2014-11-05 11:19 | 2019-03-21 12:23 |
Reporter | dregad | Assigned To | dregad | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Target Version | 1.3.0-beta.1 | Fixed in Version | 1.3.0-beta.1 | ||
Summary | 0017837: Add new 'DEPRECATED' error type | ||||
Description | Introducing a specific type error type (based on E_USER_DEPRECATED) instead of relying on WARNING for deprecated functionality allows for differentiated error messages and handling. | ||||
Tags | No tags attached. | ||||
MantisBT: master 7d7fb84f 2014-07-09 09:33 Details Diff |
New DEPRECATED error type Make use of E_USER_DEPRECATED instead of relying on WARNING for deprecated functionality. Allows for differentiated error messages and handling. Fixes 0017837 |
Affected Issues 0017837 |
|
mod - core/constant_inc.php | Diff File | ||
mod - core/database_api.php | Diff File | ||
mod - core/error_api.php | Diff File | ||
MantisBT: master-1.3.x 4ee0da6e 2016-10-12 02:31 Details Diff |
Let Error API capture E_USER_DEPRECATED by default Following introduction of DEPRECATED error type in issue 0017837, it was omitted to add E_USER_DEPRECATED to the list of error types captured by default. This prevented handling when error_reporting=0. Follow-up on issue 0010966, cec454931df5a99d03ff22aabf8901648ff3d549 Fixes 0021795 |
Affected Issues 0010966, 0017837, 0021795 |
|
mod - core/error_api.php | Diff File |