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

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