Allowing import of system fields (created, access, login, status, language, timezone, init, data, etc.)

Here's a patch against CVS HEAD which allows a field from the CSV file to be mapped to $user['create']

A slightly better patch, again against HEAD. Now assumes the dates will be coming in as a timestamp, and also sets the creation date to time() as a default.

I have this same requirement, plus support for migrating:

• last login
• last access
• language
• timezone

Attached patch does this, needs fully testing.

Happy to put this into another issue if required.

Nice patch boxfresh! It works fine.

Since I'm importing users from an external source, I like the strtotime() use into user_created_date.patch (first patch) instead of simple assuming that date is specified in unix timestamp (drupal-to-drupal).

Is it possible to preserve both using two different options like Date created (as timestamp) and Date created (as string)? This could be useful even on Drupal, if users are exported from a view that expose dates as strings.

Subscribing.

The language option was actually asked before in 2007, see #107500: Language Support. Nice to see a patch finally!

I do think that adding support for user language and timezone to user_import makes perfect sense (and the patch in #7 works, thanks!). "Last access" and "Last login" perhaps satisfy a little bit more of an edge case.

FYI - For those wishing to add something that user_import doesn't support natively , you can implement it's hooks from a custom module. For example, the following would add support for language to vanilla user_import.module:

/**
 * Implementation of hook_user_import_form_field_match().
 */
function mymodule_user_import_form_field_match() {
  $options['user']['language'] = t('Language');
  return $options;
}

/**
 * Implementation of hook_user_import_data().
 */
function mymodule_user_import_data($settings, $update_setting, $column_settings, $module, $field_id, $data, $column_id) {
  if ($module != 'user') return;
  if ($field_id == 'language') {
    $value = trim($data[$column_id]);
  }
  return $value;
}

/**
 * Implementation of hook_user_import_pre_save().
 */
function mymodule_user_import_pre_save($settings, $account, $fields, $errors, $update_setting_per_module) {
  $account_add['language'] = $fields['user']['language'][0];
  return $account_add;
}

Also required if you are trying to send notification emails in the user's preferred language:

#1267352: Not passing message['language'] to _user_mail_text()

Since there has been no action for so long, changing to D7 and updating the original post.
It can be backported later.

We should account for all the columns in the users database table. The module is not useful for drupal to drupal imports otherwise.

For example, look at the fields that can be exported from the Profile CSV.

This is important becase a common use case is importing users from an existing drupal site, from the same or a different major version.

Adding a more detailed description of what the issue is actually about.

I'm really interested in this functionality, especially for the user's language!

I would be interested in the status of this issue. Will development for d7 go on or are there any plans of porting this to d8?

Thanks in advance.

I tried the solution for language integration mentioned in #12 and it seems to work well.

The only thing is that I get the following watchdog messages:

Notice: Undefined variable: value in pso_custom_user_import_data() (Zeile 17 von /Applications/MAMP/htdocs/pso_git/htdocs/sites/all/modules/custom/pso_custom/pso_custom.module).

Notice: Undefined variable: value in user_user_import_data() (Zeile 96 von /Applications/MAMP/htdocs/pso_git/htdocs/sites/all/modules/user_import/supported/user.inc).

Does anybody know where to look for a fix? Unfortunately this would go to far for my php skills.

Thanks in advance for any help!