[
https://issues.apache.org/jira/browse/SHINDIG-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Baxter resolved SHINDIG-1297.
----------------------------------
Resolution: Won't Fix
Moved PHP to attic so we are closing this issue for now
> Better debugging around the application
> ---------------------------------------
>
> Key: SHINDIG-1297
> URL: https://issues.apache.org/jira/browse/SHINDIG-1297
> Project: Shindig
> Issue Type: Improvement
> Components: PHP
> Reporter: Michiel Eghuizen
> Priority: Minor
> Labels: debugging, logging
>
> Include better debug messages, because that helps a lot when things aren't
> working correctly. For example, in the Config::get() function, the error
> tells the key doesn't exists. But it doesn't tell you which key it is. This
> would help a lot in debugging if it tells you that.
> Also remove the shutOp operator from the code. This is a bad practice as well
> it is also way hard to debug. Because it silences all errors, I cannot locate
> misbehavior of the application correctly. So please remove that operator, so
> we could directly see it when something goes wrong.
> To temporary disable the @ operator, I now use: ini_set('scream.enabled',
> true);
> See also:
> http://derickrethans.nl/five_reasons_why_the_shutop_operator_@_should_be_avoided.php
> I would suggest, when in debug mode, show the errors. When in production
> environment, show a friendly error, or don't give an error at all.
> See: http://php.net/manual/en/function.set-error-handler.php
> Use the error_log function to log the error, so the developers can use that
> file to monitor the errors.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
