https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27557
--- Comment #7 from Kyle M Hall (khall) <[email protected]> --- (In reply to David Cook from comment #6) > Looking at this again and wouldn't the best solution be to improve our > coding practices to gracefully handle errors in context-specific situations? Yes, and being able to get those errors from librarians would make finding and handling those errors much easier. I wish we had some real world examples. To continue off my itype example, there are times we can know ahead of time that an unpopulated itype will trigger and error, and times we may not know. We can probably use transactions to more gracefully handle unknowns at the cost of performance. What may be a good solution halfway between giving user's entire stack traces and giving them a generic 500 error would be something along the lines of what CloudFlare does where the user is present an id ( named Ray ID in the case of CloudFlare ) and we can store the full stack trace in the database with the corresponding ID. That way the librarian or patron can make a report with the ID to the library IT staff or support organization. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
