Tests failed on "selection" profile field type:
Running d6_filter_format [ok]
Running d6_user_role [ok]
Running d6_user_picture_field [ok]
Running d6_user_picture_field_instance [ok]
Running d6_user_picture_entity_display [ok]
Running d6_user_picture_entity_form_display [ok]
Running d6_user_picture_file [ok]
Running d6_user [ok]
Running d6_user_profile_field [ok]
The configuration property settings.allowed_values.etc. doesn't exist. [error]
(/var/www/drupal/core/lib/Drupal/Core/Config/Schema/Mapping.php:66)
Running d6_user_profile_field_instance [ok]
Attempt to create an instance of field profile_color that does not exist on entity type user. [error]
(/var/www/drupal/core/modules/field/src/Entity/FieldInstanceConfig.php:472)
Running d6_user_profile_entity_display [ok]
Running d6_user_profile_entity_form_display [ok]
Running d6_profile_values:user [ok]
The reason it failed is because I had a profile field of type "selection" (aka. list) called profile_color. The selection options were:
"Red
Blue
Green
etc." < the dot is the problem.
| Comment | File | Size | Author |
|---|---|---|---|
| #16 | 2302253-16.patch | 10.03 KB | ultimike |
Comments
Comment #1
Anonymous (not verified) commentedComment #2
Anonymous (not verified) commentedComment #3
ultimikeI suspect this has something to do with #2293773: Field allowed values use dots in key names - not allowed in config.
-mike
Comment #4
chx commentedYes, since that's in is this an issue still?
Comment #5
joemoraca commentedI just tested this and it "passes" now.
Added profile field with 3 options one of which had . in it
created new user (with . in username - just to see) then choose option with .
ran D6Manifest-User.yml and it migrated correctly
also checked "field settings" and they also were migrated.
Comment #6
chx commentedThanks. This indeed should indeed be fixed now. Could you retest with slashes please? (It's the new CMI separator.)
Edit: / this slash.
Comment #7
joemoraca commentedTested with both / and \ and we are good with either.
Comment #8
ultimikeI chatted with joemoraca about this - he is updating the d6_user test for this issue.
Joe - when you see this, please assign it to yourself.
-mike
Comment #9
ultimikeToo slow, Joe :p
I just updated the Drupal6User dump and MigrateProfileValues test to test for dots, forward slashes, and backward slashes in configuration values.
While I was in there, I did a few other minor-cleanups:
Patch attached.
Thanks,
-mike
Comment #11
ultimikeWhoops! Forgot to put the rename in the previous patch...
New patch attached.
-mike
Comment #12
chx commentedThanks!
Comment #13
alexpottDo we have any tests with migrating options fields with options values with a . in?
Comment #14
alexpott@ultimike if you set up your git config to use renames = copies then that patch would be way smaller and easier to review. See https://www.drupal.org/documentation/git/configure
Comment #15
alexpottSetting back to needs work for #13 since the current patch and issue title are misaligned. It would be good to prove that options with dots in can be migrating - which is what caused the original report.
Comment #16
ultimikeAddressing Alex's comments:
Updated patch attached.
Thanks,
-mike
Comment #17
chx commentedThis seems to address Alex's concern.
Comment #18
alexpottCommitted f34368b and pushed to 8.0.x. Thanks!
Yep all my concerns addressed.