I’ve been wrestling with ExpressionEngine the whole week with a custom module I’m having to build for a client. The biggest frustration I’ve had is that EE seems to override my default environment in so many places, that I can’t get all my errors output (this project is already frustrating enough given that I have to interface with FileMaker).
Can someone tell me how to turn off or extend error reporting in EE? I’ve already enabled every preference and config I can find, and the warning messages will be output, but for everything else I just get a 324 error when I should be getting messages from PHP… For the record I can test and produce the same intentional error outside of EE and get all my error messages, so It’s just some kind of ini override somewhere I imagine..
Hello Clay,
I am sorry to hear you are running into this snag with debugging.
You mentioned that you have enabled every preference and config. Does that include debugging in the Control Panel?
To turn debugging on please go to your Control Panel and navigate to Admin->System Administration-> Output and Debugging. Please set the last two settings, which are “Display Output Profiler?” and “Display Template Debugging?”, to yes.
Aside from the config file changes and the one I just mentioned, I am not sure there is any more you can do.
Let me know if you have already tried the method I mentioned above and if that is not enough, I can ask a Dev if there is anything else you can do.
Cheers,
Hey Shane,
I did enable the output and debugging in the admin, I’ve formed a hack solution of sorts using var_export() and error_log() but I would love some developer feedback to see what core EE devs use to do stack traces and output errors when doing heavy dev. I’m newer to EE and CodeIgnitor, but I’ve done a lot in the past with Kohana and Zend so debugging is no stranger to me.. as long as I can see messages 😉
Thanks!
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.