in reply to Re^2: Debugging a login script using MySQL
in thread Debugging a login script using MySQL

By adding the print header line the 500 error is gone but it doesn't say the login was successfull or the login failed.

So, what does it say now? Just "test" or also "test 2". If something is wrong with the DB, there should be no "test 2". The use CGI::Carp qw(fatalsToBrowser); should print any error messages to your browser. Does it?

  • Comment on Re^3: Debugging a login script using MySQL

Replies are listed 'Best First'.
Re^4: Debugging a login script using MySQL
by coldfingertips (Pilgrim) on Jan 05, 2005 at 07:10 UTC
    Right now it says both test and test 2. But that's it. It prints both my test messages but doesn't appear to even attempt to log in.

    I am not a MySQL expert but if I don't have data in the tables username and user_password, could it be the problem? I set up the tables but I don't know how to setup the rows properly so I don't think either contain any data.

    That's the only idea I have to go about fixing this. And as for your other post, yes I want to use this. The login isn't to anything secure and after I get it to finally work, I can improve it.

    Thanks.