A client of mine has a need to import a CSV file of users every couple of months, so I was testing out the Update previously-imported content setting.
I noticed that a new profile node was created for each import, even if one already existed. This is contrary to the normal functioning of the Content Profile module, which normally only allows one instance of a profile node per user.
This patch checks to see if a content profile node exists for a user already, and updates it if it does. It also creates a new revision of the profile node, so admins can see what changed and revert those changes if necessary.
The major downside of this patch is that it'll slow down user imports, so it might be worthwhile to try to detect a new user import vs. an update of an existing one, and skip the duplicate node check when it's a new user.
Jeff
| Comment | File | Size | Author |
|---|---|---|---|
| content_profile_migrate_update_fix.patch | 2.06 KB | jeffam |
Comments
Comment #1
kruser commentedThanks for the patch. I found a few other downsides,
- it bypasses the migration of filefields.
- it bypasses my node_prepare module for importing cck location fields (upon updating only, not initial import)
- it doesn't insert dates correctly
This patch is greatly needed because without it, upon updating, all of the content profile nodes are re-created instead of updated which is wrong.
Comment #2
mikeryanMigrate and Migrate Extras V1 are no longer supported.