Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

carp module

Status
Not open for further replies.

audiopro

Programmer
Apr 1, 2004
3,165
GB
My ISP has the carp module installed but it does not work the same on all of my domains.
On most of them, fatalstobrowser does nothing.

Is it possible they are using an old version or can this be configured so it does not display to the browser?

Keith
 
The only reason I use the carp module is to display the errors to the browser. I'm pretty sure you can configure it to send your errors where ever you want.

Make sure when your testing you have your capitalization correct as it's fatalsToBrowser

also it was suggested to check the version of CGI::Carp to make sure you aren't using 1.24

Code:
#!/usr/bin/perl
use CGI::Carp qw(fatalsToBrowser);
print "Content-type: text/plain\n\n";
print CGI::Carp->VERSION, "\n";

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[noevil]
Travis - Those who say it cannot be done are usually interrupted by someone else doing it; Give the wrong symptoms, get the wrong solutions;
 
Are we talking Carp or CGI::Carp? They are two separate modules.

------------------------------------------
- Kevin, perl coder unexceptional! [wiggle]
 
well you said fatalsToBrowser so I assumed you were talking about CGI::Carp

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[noevil]
Travis - Those who say it cannot be done are usually interrupted by someone else doing it; Give the wrong symptoms, get the wrong solutions;
 
by "you" i meant the OP..

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[noevil]
Travis - Those who say it cannot be done are usually interrupted by someone else doing it; Give the wrong symptoms, get the wrong solutions;
 
My local version is v1.14 which works OK.
The version which doesn't report fatalstoBrowser (The case is correct) is indeed v1.24 and another version I have on a remote server is v1.29.

Did someone think it was a good idea to turn off fatals for version 1.24?

ISP say they cannot change the version in case it causes existing scripts to fail.

Keith
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top