Re: Debugging errors the easy way.

If you aren't all ready, Use strict warnings and diagnostics or die.
Also look at CGI::Carp

Following tachyon's advice should give you more of a clue why you're getting an error, rather than just getting a "500 - Server error".

Comment on Re: Debugging errors the easy way.

Replies are listed 'Best First'.
Re: Debugging errors the easy way. by newrisedesigns (Curate) on Jan 07, 2002 at 21:50 UTC
I did have an "\|\| &error; " appended to the use statement, but it still returned an error. I assume it's a fatal error (thus leading me to believe that the module is not present), however I will try some alternatives to see if I can pinpoint why I recieve that error. No luck with the "manual" creation of .htpasswd files. I double checked to make sure that the .htaccess is pointing to the created file for "AuthUserFile". Perhaps permissions need to be set?	[reply]

Replies are listed 'Best First'.

Re: Debugging errors the easy way.
by newrisedesigns (Curate) on Jan 07, 2002 at 21:50 UTC

I did have an "|| &error; " appended to the use statement, but it still returned an error. I assume it's a fatal error (thus leading me to believe that the module is not present), however I will try some alternatives to see if I can pinpoint why I recieve that error.

No luck with the "manual" creation of .htpasswd files. I double checked to make sure that the .htaccess is pointing to the created file for "AuthUserFile". Perhaps permissions need to be set?

[reply]