You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When developing webservices (ie API) code, it appears that there is no way to log errors that occur (through the normal J! logging system).
I have been able to make it happen by manually putting the name of my component into the parameters column of the com_actionlogs row in the extensions table. This is obviously not satisfactory, nor does it point to an easy solution imho.
Perhaps an entry in that logging control area could offer a multiselect for components (perhaps excluding the core ones)? Selected components would then be included in "everything" logging..
Steps to reproduce the issue
Modify a line of php code in a /api/components area so it will throw an error.
Set logging to "Log almost everything".
Trigger the faulty code.
Expected result
Stack trace &tc in the log.
Actual result
No persistent error reporting at all.
System information (as much as possible)
J! 4.2.5, Linux, Apache,
Additional comments
The text was updated successfully, but these errors were encountered:
MarkRS-UK
changed the title
"Log almost everything" doesn't log webservices errors (nor does anything else)
"Log almost everything" doesn't log (non core) webservices errors (nor does anything else)
Nov 18, 2022
When developing webservices (ie API) code, it appears that there is no way to log errors that occur (through the normal J! logging system).
I have been able to make it happen by manually putting the name of my component into the parameters column of the com_actionlogs row in the extensions table. This is obviously not satisfactory, nor does it point to an easy solution imho.
Perhaps an entry in that logging control area could offer a multiselect for components (perhaps excluding the core ones)? Selected components would then be included in "everything" logging..
Steps to reproduce the issue
Modify a line of php code in a /api/components area so it will throw an error.
Set logging to "Log almost everything".
Trigger the faulty code.
Expected result
Stack trace &tc in the log.
Actual result
No persistent error reporting at all.
System information (as much as possible)
J! 4.2.5, Linux, Apache,
Additional comments
The text was updated successfully, but these errors were encountered: