Migrate users with pages field

Kirby 3 Solved ✅
1

I am trying to migrate users from kirby2 to kirby3 using the script from the cookbook.

The script works for everything except a page/pages field.

at the moment I have this code:

      $profile              = @$data['profile'];
      $profile              = $profile?Data::encode([$profile], 'yaml'):'';

The data this produces looks good but the $kirby->users()->create function then apparently empties the data for the profile field.

This is the whole script:

<?php
//set_time_limit(360);
require __DIR__ . '/kirby/bootstrap.php';

$kirby = new Kirby;
$dir   = $kirby->root('accounts');

// authenticate as almighty
$kirby->impersonate('kirby');

// loop through each K2 account file
foreach (Dir::files($dir) as $account) {

    // read K2 account file
    $data  = Data::read($dir . '/' . $account, 'yaml');

    if (isset($data['username'])){
      // prepare data to be processed
      $name        = $data['username'];
      $email       = $data['email'];
      $password    = $data['password'];
      $role        = $data['role'];
      $language    = $data['language'];
      
      
      $sitelanguage         = @$data['sitelanguage'];
      $profile              = @$data['profile'];
      dump($profile);
      $profile              = $profile?Data::encode([$profile], 'yaml'):'';
      dump($profile);
      $conditionsagreedon   = @$data['conditionsagreedon'];

      $date = $conditionsagreedon;
      $newDate = DateTime::createFromFormat('d/m/Y H:i:s', $date);
      $conditionsagreedon = $newDate?$newDate->format('Y-m-d H:i:s'):'';
      
      unset(
          $data[0],
          $data['username'],
          $data['email'],
          $data['password'],
          $data['role'],
          $data['language'],
          $data['history'],
          $data['sitelanguage'],
          $data['profile'],
          $data['conditionsagreedon']
      );

      // create new K3 user account
      $user = $kirby->users()->create([
          'email'    => $email,
          'name'     => $name,
          'role'     => $role,
          'language' => $language,
          'content'  => $data,
          'password' => $password,
          'sitelanguage' => $sitelanguage,
          'profile' => $profile,
          'conditionsagreedon' => $conditionsagreedon
      ]);

      // write K2 password hash to .htpasswd
      F::write($dir . '/' . $user->id() . '/.htpasswd', $password);

      // delete K2 account file
      F::remove($dir . '/' . $account);

      echo 'User migrated: ' . $user->email() . '<br>';
    }
}
2

What is stored in $data['profile'].

On a sidenote, instead of @$data['sitelanguage']; I think it would be better to use the null coalescing operator $data['sitelanguage'] ?? null.

3

$data[‘profile’] is a page field from kirby2. In kirby3 it is a pages field.

so $data[‘profile’] has:

profiles/tinus

It is a page that exists and is public.

This is the blueprint for the users:

fields:
  sitelanguage:
    label: Site language
    type: select
    options:
      nl: Dutch
      en: English
  profile:
    label: Profile page
    type: pages
  conditionsagreedon:
    label: General conditions agreed on
    type: text

Excellent suggestion.

4

Any content that is not email, language, name, or role should be stored in the content array (apart from the password, which you should remove, because it is stored in the .htpasswd file in the next step with F::write()-

A user account folder in the end has three basic files (apart from maybe additional files):

  • .htpasswd
  • user.txt (for the content)
  • index.php with the array role, email, name, and language
5

Yes … but
$kirby->users()->create()

creates those files and in the txt file there is an empty Profile field.

I am just using the script from this page:

https://getkirby.com/docs/cookbook/setup/migrate-users#the-migrate-php-script

With some added fields. Apparently I am doing something wrong but I don’t understand what.

6

But you have content => $data and then those additional fields which should be in the $data array (or a new array, because the original $data array needs to be changed). And the password doesn’t belong there at all.

This is the original code from the recipe:

   // create new K3 user account
    $user = $kirby->users()->create([
        'email'    => $email,
        'name'     => $name,
        'role'     => $role,
        'language' => $language,
        'content'  => $data // this array should contain all the fields that should be stored in the `user.txt` file, i.e. all fields defined in your blueprint.
    ]);
7

Aaah, yes. I understand. Thank you.