- 🇺🇸United States dww
I'm trying to figure it out myself. ;) https://www.drupal.org/project/group/releases/3.0.0-beta1 → states the key differences between V2 and V3 are that some key plugin names (and a bunch of related methods) have been renamed. But I'm not clear on how to migrate a site from V2 to V3 to rename all these plugins. I'll try to document whatever I learn about this. 😅
Cheers,
-Derek - 🇧🇪Belgium kristiaanvandeneynde Antwerp, Belgium
Okay the goal is that when you run v1, you just run the update hooks and you're on v2. But now you still have these old machine names for the entity types and core does not like changing these machine names. How do we fix this?
Well, you install the same v2 website twice and uninstall Group v2 on the 2nd one and then update the config machine names (fields, group relationship types) already and then install Group v3. Then you load data from the website running v2 and just 1:1 copy everything into v3. The only difference is that your source talks about "group_content" and your destination talks about "group_relationship". All of their fields remain the same, so you should be able to have some very simple mappings for those. This is what needs to happen in a nutshell.
Alternatively, we could write a small add-on for v3 that keeps the old entity type definitions so you can do an in-site migration without the need for a second installation. Then, once you're done, you could delete said add-on and be done with it. So for a short period of time you'd have both the v2 and v3 entity types in one installation. But this requires extra code (and I'm quite busy :P) whereas the above approach should be manageable for most people.
- 🇪🇸Spain tunic Madrid
We are facing this issue and we have created an issue with our approach to an upgrade path from Groups 2 to Groups 3. See ✨ Document experiences for manual Group 2.x to 3.x update Active .
Currently, we have an script to does the upgrade and everything seems to work fine but Drupal complains about the "Group Relationship" and "Group Relationship Type" entities need to be installed. We are working on that and any comment on that approach is more than welcome.