Closed (fixed)
Project:
Migrate Sandbox!
Version:
1.0.1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Sep 2022 at 03:49 UTC
Updated:
26 Sep 2022 at 16:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
danflanagan8Yeah, that probably shouldn't happen, huh?
I'll update the config for that example.
Comment #3
danflanagan8I'm wondering if I want to make a broader change here. The issue is not so much with the node source as it is with trying to use the node destination. MigrateSandboxEntityContentBase could make life easier by giving the node a fake title to avoid validation errors. There could be a message added to alert the user that a stand-in title was used.
I think that's what I'll do.
In the meantime, adding
title: titleto the process pipeline will get rid of that validation error.Comment #4
danflanagan8Here's a patch that makes the sandbox entity destination a bit more forgiving with the entity label validation. This also makes some related changes to the severity of status messages with updates to the corresponding tests. This was also a good opportunity to make use of the relatively new status messages assertions in the tests.
Comment #6
danflanagan8That yaml validation always causes me fits on the test runner here. Let's try this...
Comment #8
danflanagan8oops. Wrong place to wait. Try this...
Comment #10
danflanagan8What!?! How about this?
Comment #12
danflanagan8I give up trying to understand this. This one will pass.
Comment #14
danflanagan8This will be in a new release shortly