[Koha-bugs] [Bug 24574] Broken MARC records cause "invalid data, cannot decode object" on ISBDdetail and MARCdetail pages.

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24574

--- Comment #15 from David Cook <dcook at prosentient.com.au> ---
(In reply to Rudolf Byker from comment #12)
> (In reply to David Cook from comment #10)
> > 1) Is this in dev or production?
> Production
> > 2) Is this using Plack/starman alone, or Plack/starman behind Apache, or
> > just Apache?
> Just Apache (I think...)
> > 3) Do you have the environmental variable DEBUG enabled?
> No (I think...)
> > 4) How did you install Koha? (Via Debian packages?)
> Yes, from Debian pacakges.

Thanks for the information!

When you got the error, did the top of the web page say "Software error:"? 

If so, it was using Apache's generic error response page and not Koha's custom
error response page. 

After some testing, I've noticed that Apache will use Koha's custom more
"user-friendly" error response pages for 4xx errors (like 404 and 403), but not
for a 500 error.

Actually, I've tried a number of permutations for defining the "ErrorDocument
500" line in the Apache configuration and nothing is working. This is
interesting because I know for a fact that I've seen a custom error response
page for a 500 error in Koha before...

Aha! If I put "die" in mainpage.pl, Apache will use its generic 500 response.
If I remove execute permissions for the mainpage.pl file (chmod -x
mainpage.pl), Apache will use the custom Koha 500 response!

--

But... now I understand why Jonathan said my line of inquiry wouldn't be
useful. While I have a legitimate line of inquiry regarding the
user-friendliness of error pages, it may or may not be what you're looking for. 

For instance, with this bug report, are you looking to get a generic
user-friendly web page that says "Sorry, there was an error!" or are you
looking for the majority of the page to function normally and to handle the
MARC error specifically to say something like "Sorry, we could not parse your
MARC record. Please fix the MARC data"?

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.