[Koha-bugs] [Bug 1159] New: 2.2.6RC2 - 500 Internal Server Errors

[bugzilla-daemon]

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1159

           Summary: 2.2.6RC2 - 500 Internal Server Errors
           Product: Koha
           Version: branch 2.2
          Platform: PC
               URL: http://thread.gmane.org/gmane.comp.misc.koha/6374/focus=
                    6374
        OS/Version: OpenBSD
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: Templates
        AssignedTo: address@hidden
        ReportedBy: address@hidden
         QAContact: address@hidden


The following is copied from my message to the mailing list.  The thread can be
seen here http://thread.gmane.org/gmane.comp.misc.koha/6374/focus=6374.  Chris
requested I file a bug report on this issue.  If you need more information I'll
provide whatever you request.  Sorry if this doesn't belong under Templates; it
seemed to be the most closely related.

Hi, I'm playing around with 2.2.6RC2 and am having a frustrating time with
500 Internal Server Errors. Using HTML::Template Ver 2.8 I can get
opac-main.pl to load but not opac-search.pl. Using HTML::Template Ver 2.6 I
have the opposite behaviour; I can get opac-search.pl but not opac-main.pl.
This occurs with either Default or NPL themes. In both cases the log file
contains only an error message like this and nothing else:
[Tue Aug 22 21:47:23 2006] [error] [client 172.16.1.10] Premature end of
script headers: /var/www/koha/opac/cgi-bin/opac-main.pl

I went looking for a way to troubleshoot this problem and found this site:
http://htmlfixit.com/cgi-tutes/tutorial_Common_Web_dev_error_messages_and_wh
at_they_mean.php It says to add "use CGI::Carp qw(fatalsToBrowser);" just
below the path to perl to send errors to the browser. And this is where it
gets weird. As soon as I put that line in I no longer get errors and the
page displays. I take it back out and the errors are back.




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.