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

Debugging output #20

Open
torvista opened this issue Dec 22, 2020 · 2 comments · Fixed by #21
Open

Debugging output #20

torvista opened this issue Dec 22, 2020 · 2 comments · Fixed by #21
Assignees

Comments

@torvista
Copy link

I have added quite a few (switchable) debug outputs to the javascript (for console) and the ajax file (for a dpu log in the logs folder).
I was thinking of leaving them all in for now/ in the next PR, at least while this is in development. They can be easily removed for release or left in, as you wish.
It is such a beast to debug, and needs more people to test all eventualities that I think a built-in method to output debugging info is very helpful. Not everyone has Xdebug setup.

@Zen4All
Copy link
Member

Zen4All commented Dec 27, 2020

As long as they are easy to switch off, I am fine with leaving the debugging in place. We can use an admin switch, like the OPC mod from lat9

@Zen4All Zen4All assigned Zen4All and torvista and unassigned Zen4All Dec 27, 2020
@torvista
Copy link
Author

How about debugging levels
0 off
1 jscript only to console
2 php (zcDPUAjax) to logfile
3 jscript to console + logfile

@Zen4All Zen4All linked a pull request Jan 1, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants