[#38158] - Show location of cause of deprecation messages
- Fixed in Code Base
- 28 Jun 2022
- Medium
- Build: 4.2-dev
- # 38158
- Diff
- MarkRS-UK:master
User tests: Successful: Unsuccessful:
Pull Request for Issue #38137 .
Summary of Changes
Add file and line reference to deprecation exception messages.
Testing Instructions
Enable deprecated method calls logging (Admin panel -> global configuration -> logging)
Run just about any view in the back end.
View file /administrator/logs/deprecated.php to see reports of deprecated calls.
Actual result BEFORE applying this Pull Request
Deprecation messages appear without any reference to location of the piece code causing the exception.
Expected result AFTER applying this Pull Request
Deprecation messages contain a full file name and line number locating the cause of the exception.
Documentation Changes Required
Documentation Changes Required
None
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Libraries |
| Labels |
Added:
?
|
||
| Labels |
Added:
?
|
||
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38158.
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38158.
| Status | Pending | ⇒ | Ready to Commit |
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38158.
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-06-28 10:33:32 |
| Closed_By | ⇒ | HLeithner | |
| Labels |
Added:
?
|
||
thanks
There was a conflicting file due to the automatic conversion to psr12 code style standard. I've allowed myself to solve that.