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.
Problem/Motivation
I wrote a small submodule which migrates field groups from D6 to D8. Field group module was part of CCK in D6.
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#9 | 2611904-field_group_migrate_d6_only_standard-9.patch | 544 bytes | mvwensen |
Comments
Comment #2
webflo CreditAttribution: webflo at UEBERBIT GmbH commentedComment #3
webflo CreditAttribution: webflo at UEBERBIT GmbH commentedComment #4
askibinski CreditAttribution: askibinski at Merge commentedRelated:
For anybody using CCK version 3.x and the 'content_multigroup' submodule (which offers a "multiple fieldgroup") and looking for a migration path:
The corresponding functionality in Drupal 8 will be the field_collection module.
#2612722: D6 -> D8 migrate cck "content_multigroup" to field_collections
Comment #5
askibinski CreditAttribution: askibinski at Merge commentedModule works! I tested the patch in combination with the migrate upgrade UI module which works as long as you add a path in MigrateUpgradeForm.php:
I think it's also possible to test it without the migate_upgrade module using drush?
Comment #6
webflo CreditAttribution: webflo at UEBERBIT GmbH commentedSmall a bugfix for the d6_field_group_entity_view_display migration.
Comment #7
nils.destoop CreditAttribution: nils.destoop as a volunteer and at Wunder commentedThx for the patch and the testing of it. I don't have a d6 site, so not able to test. But it's confirmed that it works, so committed to dev :)
Comment #9
mvwensen CreditAttribution: mvwensen commentedThe Field Group Migrate module migrates all CCK content groups from D6 to D8 Field groups but should only do this with standard content groups and not the multigroups (as mentioned by @askibinski in #4).
Minor change in the query() needed at the FieldGroup class, condition for group_type 'standard'.
Comment #10
emptyvoid CreditAttribution: emptyvoid as a volunteer commentedHello, thanks for the work everyone has done on this so far.
Please excuse me if this question seems "dumb" but where do I place the module? I'm assuming it should go in the /modules/contrib directory right? Shouldn't the plug-ins be registered in the migration configuration?
The code as it is doesn't appear to be seen by the migration module and or drupal_migration module?
When I migrate using the Drupal 6 site's database none of the fieldgroup "standard" groups get migrated. I'd like to help debug this and improve upon the group's work.
Before I provide any patches I'll continue to read up on the prerequisites on basic D8 concepts such as plugins, etc. I've searched around and haven't found documentation explicitly for writing plug-ins for migrations (that are not core migrations).
Am I just blind? Or does it not exist yet?
-- Update --
For those who are trying to understand how to get this to work do the following:
1) Apply Patch
https://www.drupal.org/files/issues/2611904-6.patch
* At the root of the /modules directory
2) Download and install migrate_upgrade
https://www.drupal.org/project/migrate_upgrade
3) Apply migrate definition
As stated in comment #5 https://www.drupal.org/node/2611904#comment-10557764
You'll need to modify the MigrateUpgradeForm.php in the migrate_upgrade module and include the form and view display definitions.
Then once you run the upgrade the field groups should be included.
I believe there should be a way to extend the MigrateUpgradeForm class and add to the $moduleUpgradePaths property. I would assume that in order to do that the migrate_upgrade module would need to employ the plugin design pattern.
Comment #15
Anonymous (not verified) CreditAttribution: Anonymous at Netuxo Ltd (RIP) commentedI'm trying to get this to work with drush and migrate_tools. I don't use migrate_ui, so adding the form does not help me.
I have installed field_group-8.x-3.x-beta, and now need to configure the migration of two d6-cck groups to D8. This does not seem to work out of the box (I created the config before installing field_group), so I probably need a yml file for this.
At the moment, running drush mi upgrade_d6_field skips the two fields that are in a cck fieldgroup . I assume the field_group needs to be migrated first, but I don't have a migration for that...
Comment #16
anairamzapHi there, wondering if anyone was able to migrate field groups from D6 to D8 using drush and migrate tools?
I had the module enabled (8.x-3.x-beta) but in the metadata templates generated by drush migrate-upgrade --configure-only I can't see any reference to field groups... if not automatically generated, could you please point me how to get this migration working?
In here I see a reference to
d6_field_instance_widget_settings
template, but coulnd't figure out exactly how to add keys/values in migration yml templates.Thanks!
m
Comment #17
heddnLinking in #2906878: [Meta] Support for D7 -> D9 contrib migrate
Comment #18
edysmpMaybe this help https://www.drupal.org/project/field_group/issues/3002645
Comment #19
nils.destoop CreditAttribution: nils.destoop as a volunteer and at Wunder commentedCan you idd verify if issues are solved since https://www.drupal.org/project/field_group/issues/3002645 was committed?
Comment #20
aiphesHello,
Facing no linked media from a D6 fieldgroup container for filefield, when I migrate D6 to D8.9.13.
Where can I find the migration yml file produce by migrate module to see what it done ?
Thanks