Closed (fixed)
Project:
Drupal core
Version:
5.5
Component:
user system
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Dec 2007 at 23:33 UTC
Updated:
27 Jan 2008 at 12:33 UTC
As already posted at http://drupal.org/node/201555, this problem is very serious to my site.
New users are not able to register.
After checking the DB for the information I posted I found them in another, already existing account.
The entered User data are dropped but data from the profile module are stored.
The problem: No new record in the database for the new user!
Comments
Comment #1
RaRi commentedOK, works now.
Somehow the pointer to the user table was missleading to somewhere close to the end of the user table.
Would be nice to know how this can happen.
What I did was using a new database and importing all data from 4.7.7 to the database.
Then running update.php.
But - a few days later I had to import the users table again because of new users in 4.7.7.
So therefore I made an update of the users table (sql insert).
I assume that this causes the error because also in the meanwhile, some inactive users were deleted.
Could this be and how can I overcome the problem in the future, by the means of migrating to v6?
Comment #2
bart jansens commentedWhen you re-imported the users table a few days later, you most likely forgot to update the sequences table. That table keeps track of the next UID to assign.
When the next user tried to register, drupal would assign a uid that you had already added to the users table, causing the errors you experienced.
In the future, always be sure to update the sequences table as well. This is only true for D5, if i'm not mistaken that table got removed in D6 and regular auto-increments are used, so you won't have to worry about this anymore.
Comment #3
bart jansens commentedComment #4
RaRi commentedMany thanks for the explanation... makes sense and I was not aware about the dependencies.
Comment #5
bart jansens commentedComment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.