SiT! Bugs - SiT!
View Issue Details
0000368SiT!otherpublic2009-01-06 20:432009-02-27 16:27
normalminorhave not tried
0000368: Write trigger_errors to disk
We should really write any errors which trigger_error displays to a longer file as this will allow us to:

a) identify problems which are not reported
b) Resolve problems which people see though dont have write down the error

Perhaps use $CONFIG['error_logfile']
No tags attached.
Issue History
2009-01-06 20:43paulhNew Issue
2009-01-06 20:59ivanNote Added: 0000414
2009-01-06 20:59ivanStatusnew => closed
2009-01-06 20:59ivanResolutionopen => no change required
2009-01-06 21:31paulhNote Added: 0000415
2009-01-06 21:31paulhStatusclosed => feedback
2009-01-06 21:31paulhResolutionno change required => open
2009-01-06 21:42ivanNote Added: 0000416
2009-01-07 09:42ivanStatusfeedback => assigned
2009-01-07 09:42ivanAssigned To => ivan
2009-01-07 09:42ivanProjectionnone => tweak
2009-01-07 09:42ivanTarget Version => 3.45
2009-01-07 10:24ivanNote Added: 0000417
2009-01-07 10:24ivanStatusassigned => resolved
2009-01-07 10:24ivanResolutionopen => fixed
2009-01-07 10:24ivanFixed in Version => 3.45
2009-02-27 16:27ivanStatusresolved => closed

2009-01-06 20:59   
Already implemented in trunk svn r4587.
set $CONFIG['DEBUG'] = TRUE and your error_logfile path to a writable file.
2009-01-06 21:31   
Ivan, I think this should run all the time not only when you have debug mode on.

My reasoning is that we regularly get reports of an error on our live system though the end user dont record the error they have and the page redirects before I can get over and have a look. Theres two outstanding bugs which we cant managed to reproduce (errors on update and error on approving billable incidents)
2009-01-06 21:42   
ok, I'm up for that.

I'll make the change later unless you want to dive in. ;)
2009-01-07 10:24   
Resolved in trunk svn r4595