- Issue created by @chandraraj
- πΊπΈUnited States ljwilson
I have the exact same issue. I tracked it down to two records in the key_value table which still have a reference to group_content_type instead of group_relationship. This sql finds them:
SELECT * FROM key_value WHERE collection LIKE '%entity.definitions.installed%' AND VALUE LIKE '%group_content_type%'
Fortunately I had another site where I had started with Group 3.x initially, so I just replaced the value field for those 2 records in the problem site's db with the ones from the "good" site.
I did a compare on those values first, and it looked "safe" enough to make this change. Time will tell.
...jack
- πΊπΈUnited States ljwilson
A better fix might be from The "group_content_type" entity type does not exist error after upgrade from v2 to v3
https://www.drupal.org/project/group/issues/3494298 π The "group_content_type" entity type does not exist error after upgrade from v2 to v3 ActiveI backed-out my db changes and applied the code from the above issue and it also fixes the uninstall error.
To easily run the code referenced, I created a file update_field_storage.php in the group module folder with the following contents, and ran it with
drush scr update_field_storage.php
<?php use Drupal\Core\Entity\EntityDefinitionUpdateManagerInterface; use Drush\Drush; $field_def = \Drupal::entityDefinitionUpdateManager()->getFieldStorageDefinition('type', 'group_relationship'); // Get the Symfony Console Output interface from Drush. $output = Drush::output(); if ($field_def) { $field_def->setSetting('target_type', 'group_relationship'); \Drupal::entityDefinitionUpdateManager()->updateFieldStorageDefinition($field_def); // Print success message to the console. $output->writeln('<info>Field storage definition updated successfully.</info>'); } else { // Print error message to the console. $output->writeln('<error>Field storage definition not found.</error>'); }
...jack