Possibility to see debug in server logs instead of the interface

When enabling logs, they are displayed in the interface, for all users.

I would like to see logs in servers logs on the server instead.

It can be done with error_log: https://www.php.net/manual/en/function.error-log

Simple patch:

diff --git a/include/functions.inc b/include/functions.inc
index f305e99e..d78c6543 100644
--- a/include/functions.inc
+++ b/include/functions.inc
@@ -193,6 +193,7 @@ function DEBUG ($level, $line, $function, $file, $data, $info = '')
     }
     echo '<div class="debug_div">';
     echo $output;
+    error_log($output);
     if (is_array($data)) {
       print_a($data);
     } else {

There should be a better patch, which can route the output depending on an option: interface (default) or server.

added fusiondirectory-core label

assigned to @MCMic

By bmortier on 2020-02-05T08:13:16 (imported from GitLab)

changed milestone to %FusionDirectory 1.4

By bmortier on 2020-02-05T08:13:23 (imported from GitLab)

changed due date to February 05, 2020

By bmortier on 2020-02-05T08:13:28 (imported from GitLab)

@coudot This is not supposed to be log but debug help which is why it’s only shown in the interface. In which cases would you think it useful in a file? (I mostly use TRACE level which would be too much lines for logging I think, but maybe MAIL level or such would indeed be useful)

Also note that you can ask FD to log things by checking the checkbox in configuration, which will log all objects modifications. And you can install audit plugin to log some of this to LDAP and see it in FD. (Search calls to logging::log in the source code)

By Côme Chilliet on 2020-02-05T08:33:36 (imported from GitLab)

I was for example using the debug to track the execution of a trigger.

Another feature I need is debug when using webservices. With webservices, you can't use the web interface at all.

I don't want an audit feature here, just redirect logs in web server logs.

By coudot on 2020-02-05T08:55:10 (imported from GitLab)

added PJ1802-0188 label

If this is added we’ll need a checkbox in the configuration so that it’s not active by default to avoid problems. Something like «Log debug output» in the «Debugging» section.

It should call fusiondirectory_log directly I think, because methods from logging class are made to log information about an action/event and debug lines are more random.

By Côme Chilliet on 2020-02-13T11:12:37 (imported from GitLab)

hello @MCMic,

could we not add a debug clas to the logging class to keep it clean ?

Cheers

By bmortier on 2020-02-13T11:12:37 (imported from GitLab)

added 15m of time spent at 2020-02-13

By Côme Chilliet on 2020-02-13T11:10:08 (imported from GitLab)

created merge request !741 to address this issue

By Côme Chilliet on 2020-02-18T09:36:51 (imported from GitLab)

mentioned in merge request !741

By Côme Chilliet on 2020-02-18T09:36:51 (imported from GitLab)

mentioned in commit ebdbe5c5

By Côme Chilliet on 2020-02-18T12:51:26 (imported from GitLab)

mentioned in commit 3ac26e51

By Côme Chilliet on 2020-02-18T12:51:26 (imported from GitLab)

added 2h 30m of time spent at 2020-02-18

By Côme Chilliet on 2020-02-18T13:52:20 (imported from GitLab)

added To Be Tested label

assigned to @coudot and unassigned @MCMic

By Côme Chilliet on 2020-02-18T13:52:20 (imported from GitLab)

changed title from Possibility to see logs in server logs instead of the interface to Possibility to see debug in server logs instead of the interface

By Côme Chilliet on 2020-02-25T13:25:37 (imported from GitLab)

created merge request !744 to address this issue

By Côme Chilliet on 2020-02-25T13:50:09 (imported from GitLab)

mentioned in merge request !744

By Côme Chilliet on 2020-02-25T13:50:09 (imported from GitLab)

mentioned in commit 740cc93c

By Côme Chilliet on 2020-02-25T13:51:50 (imported from GitLab)