revraz

You should be checking your query's each time you execute them for errors.

You don't say what the actual problem is.

Set a session in your login.php and then check that session variable on your other pages to determine if they are logged in or not.

I would suggest posting in the freelance section and get someone to do it for you. Plenty of people are willing to help out.

Also found in the FAQ Section of the Forums http://www.phpfreaks.com/forums/index.php?topic=95867.0

Do you have a space in your email address? Paste the echo.

This is what your query looks like: Select movie_name, movie_typefrom moviewhere movie_year>1990 order by movie_type

And what is the URL that brings you to this page?

So you are storing your password in plain text?

What are you trying to accomplish here? $query = "SELECT ip, username FROM users WHERE ip<>'$ip' AND username<>'$username'";$result = mysql_query($query); while($row = mysql_fetch_assoc($result)){mysql_query("INSERT INTO users (ip, username, password) VALUES('$ip', '$username', '$pass')"); $msg="You registered successfully!"; $window="login.php"; Also, you should count rows that are returned and use IF statements instead of GOTOs, would much more standard.

If you only need to work with that data that you pulled, then yes, you can close the connection to the DB.

Huh? You have to pull it from the DB to populate the Array. After that, you reference the Array.

Could just process the form on the same page, or set a session variable and when you return back to the signup page display the error.

Can you post the actual SQL error? And why don't you just use the MySQL NOW() for current date/time?

I think he wants the SUM, so why not just add them together?

Nope, hard to say without seeing your code.

The LIMIT would be the current row# -5. So if you were on record 10, it would be LIMIT 5, 15

Of course, why not? Since each row returns can have a ID, you just update that ID.

$sessionid = ""; Why does it have to be destroyed, just overwrite it? I think you are confusing variables with session variables.

$sessionid isn't destroyed, $_SESSION is destroyed.

Any string can be a variable.

A better way would to not use the ID in the URL and use a session to pass it instead.

sha or md5 with a salt are both effective.

No, output to the browser is causing it.

Depends on what your site does. If you are asking, I'm assumming you know know what SSL is?