Task #82721
closed
Improve documentation of new deprecation strategy
Added by Georg Ringer about 7 years ago.
Updated about 6 years ago.
Description
Since #82438 deprecations trigger an exception. People are used to the deprecation log which doesn't lead to a failing instance. The rst and docs must be improved to have examples for:
- How to disable deprecations showing up
- How to log those into files
- Related to Task #82438: Use native trigger_error and ErrorHandler for deprecations added
Maybe the setting
'exceptionalErrors' => E_ALL & ~(E_STRICT | E_NOTICE | E_COMPILE_WARNING | E_COMPILE_ERROR | E_CORE_WARNING | E_CORE_ERROR | E_PARSE | E_ERROR | E_DEPRECATED | E_USER_DEPRECATED | E_WARNING | E_USER_ERROR | E_USER_NOTICE | E_USER_WARNING)
should be adjusted and the E_DEPRECATED removed.
- Category set to Documentation
Removing the setting 'exceptionalErrors' from LocalConfiguration (and fallback to default value) fixes the problem with the failing instance because of deprecations.
- Category changed from Documentation to Install Tool
- Status changed from New to Accepted
- Complexity set to easy
IMO this is no documentation issue, but default configuration must be adjusted as well as presets.
- Status changed from Accepted to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by