on line 251 of content_profile_create_user.module there is a loop that asks cck for the email fields based on the name of the content type. CCK is expecting the machine name of the content type (at least it is in version 3.x-alpha) but the value provided by Content Profile is the human name. Sending CCK the key of the array returned by Content Profile fixes the problem.
Additionally, the conversion fails with the message "Could not create user, no email found for %title" which is a little cryptic in this case :P
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 1433816-create-user-fails-4.patch | 996 bytes | thedavidmeister |
| #1 | 1433816-create-user-fails-1.patch | 773 bytes | thedavidmeister |
Comments
Comment #1
thedavidmeister commentedpatch attached
Comment #2
ianwremmel commentedWithout having looked at anything but your patch, I'm guessing this is a result of a change between CCK 2 and 3. I'll do a little more digging and most likely get your patch committed this weekend.
Comment #3
thedavidmeister commentedif it *is* due to an API change between CCK 2 and 3 then the patch will need more work to figure out what's going on before it tries to access the data.
Comment #4
thedavidmeister commentedrerolling and modifying the patch slightly so that the variable names make more sense
Comment #5
ianwremmel commentedSorry for the delay in investigating this. Let's just say life's gotten very busy lately.
I've added this patch to the development branch.
Comment #6
ianwremmel commentedI just ran a few minor tests against views-2.16 and views-3.0 and both worked so I'm marking this as fixed.
Comment #7
ianwremmel commentedOf course, this has nothing to do with views, so I still need to test it against cck.
Comment #8
ianwremmel commentedTested against cck 6.x-2.9 and 6.x-3.0-alpha3