Saturday, October 25, 2014

Admin Login Problem

Option 1:

Update (For Magento 1.4.*) and higher versions
In Magento 1.4 and higher versions, you have to comment code below which is present around line 80 to 100 in
/*  if (!$cookieParams['httponly']) {
    if (!$cookieParams['secure']) {
        if (!$cookieParams['domain']) {
if (isset($cookieParams['domain'])) {
    $cookieParams['domain'] = $cookie->getDomain();
} */


Option 2:

Stop modifying the core code like that — it may temporarily solve an issue, but it may create future issues that will be almost impossible to track down.
There's a number of different issues that cause the errorless admin login behavior you're seeing, but they all go back to Magento not being able to set or read the session cookie. Magneto uses sessions to pass error messages between pages — that's why you don't see an error message. Magento also uses sessions to store the "is logged in" value, so not setting sessions also causes the core error behavior.
Possible causes include
  • Local computer time vs. server time mismatch, causing instant cookie invalidation. Make sure your server time is correct.
  • Incorrect permissions on var/session, preventing session files from being saved
  • Incorrect configuration of database/redis/other session storage, preventing saving of session values
  • A module is instantiating sessions to early, preventing the correct session names from being set
  • You're a developer using multiple URLs and have multiple cookie domains
  • Another developer has somehow modified app\code\core\Mage\Core\Model\Session\Abstract\Varien.php, creating a hard to track down bug
  • The cookie domain in System -> Configuration -> Web -> Session Cookie Management doesn't match the actual site domain.
  • You're using the localhost as your server domain, and using a version of webkit that has trouble/bugs setting cookies for localhost in some situations.
The short term fix is to just delete your cookie for the domain. That's often enough to solve the problem. If it persists, figure out which of the above reasons is the reason for your error, and take steps to address it (fix permissions, etc.)

No comments:

Post a Comment