PHP_errors.log – Reveals info about untrapped errors

  • Resolved IRD-dev

    (@ird-dev)


    8 years ago

    Hello. LOVE this plugin and leverage it often.

    One of my custom scripts had an apparent error that was untrapped by this plugin. Whilst looking at the webserver today, via FTP filezilla, I noticed a log under wwwroot named “PHP_errors.log” which outlined the error.

    While this helped, I was dismayed to discover this log which also reveals the hosting path on the physical web server:

    [29-Mar-2016 17:04:42 UTC] PHP Warning: Missing argument 2 for remove_filter(), called in F:\WebSpace\customername\customerdomain.com\wwwroot\wp-content\plugins\code-snippets\php\snippet-ops.php(383) : eval()'d code on line 8 and defined in F:\WebSpace\customername\customerdomain.com\wwwroot\wp-includes\plugin.php on line 321

    My particular issue, while irrelevant to this discussion, was the failure to properly configure the REMOVE_FILTER function (missing a req’d argument).

    My questions are:
    (1) Why wasn’t that trapped by your plugin?
    (2) What dictates this log (its directory, name, contents)?

    Thank you!

    https://wordpress.org/plugins/code-snippets/

Viewing 1 replies (of 1 total)
  • Plugin Author Shea Bunge

    (@bungeshea)

    7 years, 11 months ago

    The error log is generated by PHP. Your hosting provider would have configured for it to be generated and saved in that location – you may want to talk to them about changing this to a non-web-accessible location.

    The error is only a PHP warning, rather than a fatal error, which might explain why it was not automatically picked up when saving the snippet.

Viewing 1 replies (of 1 total)
  • The topic ‘PHP_errors.log – Reveals info about untrapped errors’ is closed to new replies.

Tags