? No Code Attached Yet
avatar MarkRS-UK
MarkRS-UK
18 Nov 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

avatar MarkRS-UK MarkRS-UK - open - 18 Nov 2022
avatar joomla-cms-bot joomla-cms-bot - change - 18 Nov 2022
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 18 Nov 2022
avatar MarkRS-UK MarkRS-UK - change - 18 Nov 2022
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)
avatar MarkRS-UK MarkRS-UK - edited - 18 Nov 2022
avatar Hackwar Hackwar - change - 22 Feb 2023
Labels Added: ?
avatar Hackwar Hackwar - labeled - 22 Feb 2023

Add a Comment

Login with GitHub to post a comment