https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27557
--- Comment #8 from David Cook <[email protected]> --- (In reply to Kyle M Hall (khall) from comment #7) > 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. That's pretty compelling. I like that. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ 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/
