🇺🇸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 Active

I 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

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

We just migrated a production site from 10.1.8 to 10.2.6, and noticed for one of our custom blocks the contextual nested links were overlaying on top of each other. I tracked it down to this change:
core/modules/contextual/js/contextual.js

I asked Chat-GPT what the difference might be, and it recommended adding 'px' since the version in 10.1.8 probably interpreted it as pixels but the 10.2.x version does not. Adding the units of 'px' fixed the problem. My change below:

diff --git a/core/modules/contextual/js/contextual.js b/core/modules/contextual/js/contextual.js
index 52fb138e9..324fe7766 100644
--- a/core/modules/contextual/js/contextual.js
+++ b/core/modules/contextual/js/contextual.js
@@ -72,7 +72,7 @@
 
       // Adjust nested contextual link's position.
       $nestedContextual[0].style.top =
-        $nestedContextual.position().top + height;
+        $nestedContextual.position().top + height + 'px';
     }
   }

Looks like multiselect 2.0.0-beta4 r changed some var variables to constants. For the error above, try changing the const to let for the $submit in line 11 of multiselect.js (with the patch already applied, of course).

That worked for me.

I've attached a re-rolled version of #6 which includes this one-word change.