On Tue, 10 Dec 2002 12:35:56 +0100, "Mystik Gotan" <[EMAIL PROTECTED]> wrote:
> #!/path/to/perl -wT
> use strict;
> use warnings;
>
> That might help.
>
Any reason to use -w and use warnings?
http://danconia.org
--
To unsubscribe, e-mail: [EM
#!/path/to/perl -wT
use strict;
use warnings;
That might help.
--
Bob Erinkveld (Webmaster Insane Hosts)
www.insane-hosts.net
MSN: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
To: Dave K <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: script runs in console but
Thanks guys, that was only part of the script.
I am using CGI::Carp qw( fatalsToBrowser );
There are no errors in any of the apache logs, nor from Perl.
This is why I'm struggling to find the source of the problem.
I'm also doing this
print "Content-type: text/html\n\n";
but like so
print $q->h
Merritt,
Works as expected in the console, but not in the browser?
Let me introduce you to a friend of mine
use CGI::Carp qw( fatalsToBrowser );
Your script operates under different permissions in the console and the
browser. Look at the Apache error log (and use cgi carp) to get a better
Idea
pe, but this is automatically done
by HTTP.
--
Bob Erinkveld (Webmaster Insane Hosts)
www.insane-hosts.net
MSN: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: script runs in console but not in browser
Date: Mon, 9 Dec 2002 15:26:35 +0200
Sorry about the vag
Sorry about the vague topic, don't know how to describe the problem.
My code runs OK in the console and does what it is meant to do. In the
browser it doesn't die or give any errors, but only does about half of
what it is meant to do before it magically stops with no errors.
If you look at the be
