#SITESUCKER COOKIES LOGINS CODE#
#SITESUCKER COOKIES LOGINS PASSWORD#

In contrast, I cannot set a $_SESSION on your server. Using cookies is completely fiddly to try to make it secure and so users cannot set certain data themselves, as you are fighting with now. Have it at the start of your very first file somewhere before anything else.Īnd perhaps use this: if (!isset($_SESSION)) If you use the cookies anywhere else you would need it there anyway. I wouldn't call session_start() within the function.

If anyone has a more secure without going over the top method, I am happy for someone to enlighten me further on this. The cookie array is a bit weird how it seems to be based on two different versions based on whether you setcookie or call the cookie. I couldn't really make much sense of the original code, so I am not even sure where to begin. if (isset($_COOKIE) & encrypt($_SERVER etc. However, the problem is, when a user has already logged in, it should be checking the code. Currently, it logs in fine, adds the cookies etc. In addition it uses a hidden field with action to set the value, login or logout for the case switch. It is called by checkLogged(login) for example and that outputs the login message if there is a problem. $loginMess = 'echo 'Successfully logged out ''

#SITESUCKER COOKIES LOGINS PASSWORD#

$loginMess = 'The username or password you entered is incorrect ' $userData = checkUserCreds(stripslashes($_POST), stripslashes($_POST)) If we are not on the login page, redirect. $_SERVER) = $_COOKIE & (!isset ($_COOKIE) || (isset ($_COOKIE) & checkUserCreds($_COOKIE, $_COOKIE)))) Check if already logged in and check session information against cookies If (password_verify($password, $hash) = $hash) $st->bindParam(':username', $username, PDO::PARAM_STR) $st = $db->prepare('SELECT id, login, email, pass FROM users WHERE login =:username') My code: setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION) //Set error mode Destroy all session and cookie variables Destroy the session if we received a logout or don't know the action received Setcookie('project-name', $userData, false) Setcookie('project-name', $userData, time () + (3600 * 168)) ĭatabaseHelpers::blowfishCrypt($_SERVER. This will leave the user logged in for 168 hours, or one week We set a cookie if the user wants to remain logged in after the $userData = Users::checkCredentials (stripslashes ($_POST), If we're not already logged in, check if we're trying to login or logout If we're not already the login page, redirect us to the login page Only redirect us if we're not already on a secured page and are not Restore the session variables, if they don't exist Regenerate the ID to prevent session fixation credentials to protect against session hijacking Check if we're already logged in, and check session information against cookies

#SITESUCKER COOKIES LOGINS CODE#

The ORIGINAL code that I have used for the tutorial function checkLoggedIn($page) I am having an issue with something I have already posted but I thought I would ask the problem again as I have more code with it now.

Sitesucker cookies logins