We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 7557
    • 61 Posts
    Quote from: dj13 at May 27, 2011, 05:49 AM

    Same problem for me.
    Can’t login after upgrade to 2.1
    After reset passwords, everything is ok now. I can login to Modx 2.1.
      • 22303 MODX Staff
      • 10,725 Posts
      I can’t reproduce any of these problems on upgrade. My users can still login with their existing passwords. I also cannot reproduce Reset Password (I assume on the Manager Login form) to set a plain text password. It uses whatever method the existing user is hashed with, which will be md5 in the case of legacy users from 2.0.x installs.
        • 17173
        • 0 Posts
        Clearing the browser cookies (not only the cache) after updating to 2.1 possibly solve this issue. wink
          • 23491 ☆ A M B ☆
          • 1,056 Posts
          I, too, am running into this exact same issue sad

          I have filed the bug report here: http://bugs.modx.com/issues/4892
            Mike Reid - www.pixelchutes.com
            MODx Ambassador / Contributor
            [Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
            ________________________________
            Where every pixel matters.
            • 23491 ☆ A M B ☆
            • 1,056 Posts
            Quote from: snow889 at May 27, 2011, 06:07 AM

            very dirty hack (but working):

            use the old
            /core/model/modx/processors/security/login.php (from modx 2.08)

            I can confirm this hack works to get you logged into to MODx 2.1.0-pl (as stated above)...however, simply clearing your site’s cookies should be all it takes.

            1. Use the 2.0.8 login processor (path above)

            NOTE: Changing modx_users.hash_class value is not required...in fact, if you do this, subsequent Password Reset attempts via "Profile > Reset Password (tab)" seem to otherwise fail.

            I went through the password reset process, and I was then able to continue logging in without issue or risk of plain text password in the database (?) ...this was all via Firefox, using the 2.0.8 login processor.

            Then, I logged out, replaced "login.php" with the 2.1.0 version, and I was still able to login!

            ...this seemed a bit confusing, because the modx_user record looked identical prior to my success using the 2.0.8 processor.


            Thinking all had been solved, I then attempted to login from a different browser instance (Chrome), only to be met with the same issue as before huh Reviewing my cookies on this browser, I saw only one PHPSESSID cookie, so I cleared it. On my next attempt, everything was working as expected!

            I then repeated this test in a third browser (Safari), and saw the issue again. A simple check for existing cookie (PHPSESSID) and a quick "remove cookie" later, and I was logged in without issue.

            While I cleared my cache and logged out of the MODx Manager prior to the 2.1.0 upgrade, I never actually deleted any cookies (specifically those related to PHP session). There is good reason to follow the recommended instructions, because I believe this issue could otherwise have been avoided. Admittedly, I find it odd that the login refuses to complete successfully under this scenario, but it seems everyone’s advice of simply clearing the cookies is all it takes wink
              Mike Reid - www.pixelchutes.com
              MODx Ambassador / Contributor
              [Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
              ________________________________
              Where every pixel matters.
              • 21606
              • 46 Posts
              I had the same problem on one upgrade, but not a second upgrade (got a few more to go!! grin)- both use the same host and have all same settings except packages that are installed are different. When I couldn’t log in I tried the installation process again and then I could log in. Kept me from dorking with inner works so give re-installing a try as well!