Closed (duplicate)
Project:
User Import
Version:
5.x-2.8
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
4 May 2009 at 19:09 UTC
Updated:
11 May 2009 at 18:29 UTC
I have a client that wants to get away from email address as the determining factor as to if a user is new or not. They want the import insert / update process to key off a profile field that contains a unique identifier that has other value to them.
I've poked around in the code a bit but keep hitting duplicate email checks and all my imports keep running as INSERTs, no UPDATEs.
If someone could help point me in the right direction where to add this, I would like to add this as something to contribute back, but if something custom for this case, then thats fine too. I'm sure it's doable, but I'm just a little confused as where to put it.
Thanks.
Comments
Comment #1
dzescsd commentedI'm interested by the reply
Comment #2
robert castelo commentedSee my reply here:
http://drupal.org/node/375544#comment-1386716
This request is covered by the other, so marking it as a duplicate.
Comment #3
emackn commentedOK, thanks for the reply.
I actually got something to work, but it's specific to my data. If you want, I can post what I did with some explanation. Otherwise, I don't want to muddy up the water with a temporary solution, i.e. xml sitemap, heh.
I look forward to seeing a final solution.
Comment #4
dzescsd commentedOK. Can you send what you did and some explanation ?
Thanks.
Comment #5
emackn commentedHere's what I did,
in user_import.module, I changed the _user_import_process from this (around line 1470)
to this