Conversation:
Notices
-
So what I've done for now wrt !postActiv exception handling improvement, is just put everything together, in a central file for server exception, /classes/ServerException.php This file includes the descendant classes for exceptions that fall under that type. I have also assigned what I believe to be the sanest HTTP status code as error codes for each, but they may …
-
This will be posted to both Nightly and Master soon since it's working in a production environment just fine.
-
Next thing to do is I'll probably make them dump into LOG_ERR verbosely, they are exceptions after all.
-
Should be pushed to both now - let me know if you have issues with either wrt this latest change.
-
One simple common_log line in the ServerException class later, and all exceptions should now be logged at the LOG_ERR severity in syslog, or to the separate postActiv log file if you have one specified.
-
Once everything was pulled together, this was exceeedingly easy to get in there.
Of course, the next step past that will be making sure everything has descriptive error messages, but one thing at a time.
There's still the NoResult exception and Client exceptions to unify.
maiyannah
All Hacker Poesy content and data are available under the