Magento 1.9.3：结账创建的客户登录提示“无效的登录名或密码”求助

Hey there, let's tackle this frustrating issue you're facing with Magento 1.9.3—where customers created during checkout show up in the admin but can't log back in, getting that "Invalid login or password" error, while normally registered customers work perfectly fine. Here are the most likely causes and actionable fixes to try:

1. Password Encryption Mismatch During Checkout #

Magento 1.9 relies on an MD5-with-salt hashing standard for storing passwords. The checkout flow (especially if you're using a custom one-page checkout module) might be bypassing this core standard, leading to passwords being stored incorrectly.

• Verify password hash format: Check the customer_entity table in your database. Compare the password_hash value of a checkout-created customer vs. a normally registered one. A valid hash should look like md5:$random_salt$hashed_password. If the checkout-created customer's hash is just a plain MD5 string or missing the salt segment, that's the root issue.
• Check custom checkout modules: Disable any third-party checkout modules temporarily. If the issue goes away, the module's password-handling logic is flawed. Fix it by ensuring passwords are set using Magento's core methods: use Mage_Customer_Model_Customer::setPassword() instead of manual encryption, which automatically handles the salted hash correctly.

2. Customer Account State Anomalies #

Even if the customer appears in the admin, hidden database fields might be silently blocking login:

• Check is_active status: In the customer_entity table, confirm the is_active field is set to 1 (active state). If it's 0, the account is disabled and won't allow login.
• Clear confirmation field: If the confirmation column has a value (usually reserved for email-verified accounts), this can block login even if the customer wasn't required to verify their email during checkout. Set this field to NULL for the affected customer and try logging in again.
• Reset password via admin: Edit the customer in the Magento admin, set a new password, and save. If they can log in with this new password, the original password stored during checkout was definitely corrupted.

3. Session/Cache Corruption #

Temporary session or cache glitches can sometimes muddle customer login state:

• Flush all Magento caches: Go to System > Cache Management in the admin, click Flush Magento Cache and Flush Cache Storage.
• Clear session files: Delete all files in your Magento var/session directory (or clear your session store if using Redis/Memcached).
• Test in incognito mode: Browser cache or saved sessions might be interfering—try logging in using a private/incognito window to rule this out.

4. Custom Module Observer Interference #

If you have custom modules that hook into customer creation events (like customer_save_after), they might be altering the customer's password or state incorrectly:

• Disable custom modules: Temporarily disable all non-core modules, then test checkout and login. If the issue resolves, re-enable modules one by one to find the culprit.
• Audit observer code: For the problematic module, check any code that runs when a customer is created during checkout. Ensure it doesn't overwrite the password hash or modify account status fields without following Magento's core standards.

Start with the simpler checks (cache, account state) first, then move to module and code debugging—this should help you narrow down the root cause quickly!

内容的提问来源于stack exchange，提问作者Haseeb Iqbal