![]() |
|
Tutorial [Release] Basic Registration/Login system - Printable Version +- Sinisterly (https://sinister.li) +-- Forum: Coding (https://sinister.li/Forum-Coding) +--- Forum: Coding (https://sinister.li/Forum-Coding--71) +--- Thread: Tutorial [Release] Basic Registration/Login system (/Thread-Tutorial-Release-Basic-Registration-Login-system) |
[Release] Basic Registration/Login system - Aces - 12-27-2013 I wanted to make another release so I thought I'd make a basic registration and login system. Images: Register.php Spoiler:Login.php Spoiler:install.php Spoiler:Logged in: Spoiler:Download it here Give me your thoughts below! RE: [Release] Basic Registration/Login system - Feat - 12-27-2013 If you ask me you should totes make it centered and fit the page so that way there isn't so much leftover room. RE: [Release] Basic Registration/Login system - Mafia - 12-27-2013 Looks good, I may use this sometime. Nice release! RE: [Release] Basic Registration/Login system - Sean - 01-27-2014 Looks really cool, I will totally use this! RE: [Release] Basic Registration/Login system - 0xDEAD10CC - 02-23-2014 Why are you comparing the return from mysqli_num_rows with "1" as a string? It returns an int unless the value returned to the caller is greater than PHP_INT_MAX, in which case it is a string, but if you compare it with "1" via the equality operator, obviously you're not anticipating it to be such a large numeric value... I'd use some more functions too and gather a collection of error codes that you can check against the function return values to be matched. Those nested if statements could definitely be cleaned up. I'd prefer to not use cookies either for various reasons. edit: btw, it's not a good thing to be solely relying on mysqli_escape_string() to do all of the SQL injection prevention for you. I'd suggest you use Regex and match valid values that are allowed for the charset as input, as long as you know which ones are dangerous to include as valid. |