Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Log almost everything" doesn't log (non core) webservices errors (nor does anything else) #39238

Open
MarkRS-UK opened this issue Nov 18, 2022 · 0 comments

Comments

@MarkRS-UK
Copy link
Contributor

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

@MarkRS-UK 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants