Thanks! Even with the typo, the issue was resolved with your helpful
comments!
Thanks also for the pointer on using mysql_real_escape to 'sanitize' the
user input, it's definitely become a part of my coding.
On Mon, Feb 21, 2011 at 8:22 AM, Daniel Brown wrote:
> On Sun, Feb 20, 2011 at 16:43,
On Sun, Feb 20, 2011 at 16:43, Donovan Brooke wrote:
>>
>> $insert = "INSERT INTO user_info(login,password)
>>
>> VALUES('".mysql_real_escape_string($login)."',"'.mysql_real_escape_string($password)."')";
>
>
> Look at that one more time Dan. ;-)
Yeah, well, that's why one should neve
Daniel Brown wrote:
On Sun, Feb 20, 2011 at 14:11, Nazish Zafar wrote:
$insert = "INSERT INTO user_info
(login, password)
VALUES
("$login", "$password");
You're using double-quotes to encapsulate your $insert variable
data, then never closing them. What's more, you're also using
double
On Sun, Feb 20, 2011 at 14:11, Nazish Zafar wrote:
>
> $insert = "INSERT INTO user_info
> (login, password)
> VALUES
> ("$login", "$password");
You're using double-quotes to encapsulate your $insert variable
data, then never closing them. What's more, you're also using
double-quotes to encap
Hi there,
I am creating a login page for my website. The users' information will be
stored in a MySQL database. I have a registration form on my home page, and
a separate file called "login.php" to process the user values. However, the
entries are not going to the MySQL database (even though the v