Timeline for After restoring the database from the live site to development site, the administrator users fails to log in
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 1, 2013 at 15:05 | comment | added | Alfred Armstrong | Yes but when you copy a DB, the salt in settings.php is not relevant to what goes into the database tables. The salt is only used when a user is created on that environment. If their data has been added from a mysql dump, the salt has no bearing. So the password hash in the original DB and the one you copied to should be identical in both cases. | |
| May 1, 2013 at 13:04 | comment | added | gerard | I meant hash are different between LIVE and DEV site. Hash is different which is OK if salt defined in seetings.php is different. Conversely, same salt should produce same hash -- unless some other user-specific info (but invariant) is addded to compose the salt (which is a good practice). | |
| May 1, 2013 at 13:01 | vote | accept | gerard | ||
| Apr 29, 2013 at 21:12 | answer | added | sheldonkreger | timeline score: 0 | |
| Apr 29, 2013 at 20:29 | answer | added | gerard | timeline score: 1 | |
| Apr 29, 2013 at 14:19 | history | edited | avpaderno♦ | CC BY-SA 3.0 | improved grammar and punctuation |
| Apr 29, 2013 at 13:45 | answer | added | pico34 | timeline score: 0 | |
| Apr 29, 2013 at 13:42 | answer | added | Free Radical | timeline score: 1 | |
| Apr 29, 2013 at 13:05 | comment | added | Alfred Armstrong | If you copied the DB exactly the users table should be identical, so the fact that the hash is different suggests the DB restore was incomplete. Did you restore into an empty database? It's always best to do that if possible as any missing tables will be apparent, plus the restore will run much faster. | |
| Apr 29, 2013 at 12:47 | answer | added | AjitS | timeline score: 0 | |
| Apr 29, 2013 at 12:44 | history | asked | gerard | CC BY-SA 3.0 |