in reply to Re^3: Running in Terminal, but not on Server
in thread Running in Terminal, but not on Server

Ok, I tryed what you said, to find out that what you said was true, Carp is a core module so the fuction as worked.

Very useful, I can now know everything that goes wrong, there's even a message that write my email to report the error message, pretty nice.

Otherwise, I found what it is.... The file can't be found, you had 50% of the answer. This is probably because the directory that got the files is protected with chmod and maybe something else, htaccess. It's a little bit normal because it is a forum.

But I was sure that the server could use it for itself.... as hes the owner of thoses files.... So now, I really don't know what to do... I will maybe try to play with the chmods, but I don't want to create new security hole...

Hmm and wasn't the script suppose to tell me that it was not able to open it with the die information?..

Well, thanks a lots for everything I leanred, I will try to see what I can do with that. There's probably a way, because the forum is also in perl, and it always create and modify files. Gotta try a few things.

Thank!

  • Comment on Re^4: Running in Terminal, but not on Server

Replies are listed 'Best First'.
Re^5: Running in Terminal, but not on Server
by cdarke (Prior) on Jan 25, 2008 at 03:16 UTC
    Hmm and wasn't the script suppose to tell me that it was not able to open it with the die information?..

    Read the reply given by moritz again, particularly the bit about use CGI::Carp qw(fatalsToBrowser);