Closed (fixed)
Project:
User Import
Version:
6.x-1.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Jun 2009 at 19:19 UTC
Updated:
4 Oct 2009 at 19:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
bander2 commentedI am getting this problem too. I am looking though the code and it is a little over my head, but it seems there is a safegaurd against creating a username if one already exists, but not a similar safeguard for passwords.
Comment #2
liliplanet commentedAlso have the same. If you select 'update existing users', passwords do not get imported, and does not write to the database.
Presume have to just delete double profiles by hand ..
Comment #3
RAFA3L commentedsame here
Comment #4
stoichyu commentedThe problem lies in how drupal saves users, if it sees that the password value is set and the md5sum does not match with the original, it sets a new password. However, loading a user gets the password already md5-ed so loading a user and saving directly after would change the password.
In order to fix that, I modified the user_import/supported/user.inc in line 93-96:
That clears the password field in case we are not updating it so drupal doesn't change the password value.
Comment #5
d.clarke commentedHere is a patch file for stoichyu's fix suggested in comment 4. It worked like a charm for me. Can we get this committed?
Comment #6
csilver commentedany eta when this will be commited?
Comment #7
robert castelo commentedTotally swamped at the moment. Will try and review this next week.
Comment #8
robert castelo commentedFixed in 5.x-2.10 and 6.x-2.2 - thanks for the patch and testing.