Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Tried to import a basic field collection setup. The fields seemed to transfer ok, but they didn't get a UUID during the export, and they got one after importing, so the configuration synchronization screen shows a difference that can't be resolved and trying to import again just causes error messages. This may stop a second import from going smoothly.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | import_problem.png | 24.61 KB | jmuzz |
Comments
Comment #2
jmuzz CreditAttribution: jmuzz commentedNew field collections do not have a UUID in the database in their entries "field_collection.field_collection.{field_name}"
Comment #4
jmuzz CreditAttribution: jmuzz commentedIt seems to be working better but when I try to export a new content type with a basic field collection setup I get an unresolvable difference between active and staging. Re-exporting with this difference seems to make it go away. I looked at the display setup form on both test sites and they seem to be set up the same way so I don't think it should be recognizing a difference.
Comment #5
jmuzz CreditAttribution: jmuzz commentedTurns out this problem happens for basic text fields too so it's a problem with the configuration management system. I also tested a more complex setup with some field collection nesting and it seemed to work fine. If there's any additional problems with configuration management for field collections please open a new issue for it.
Comment #6
jmuzz CreditAttribution: jmuzz commented