- Issue created by @kenorb
I had this problem after upgrading from v2 to v3, but not when installing v2 fresh.
This and another problem with views, made me realise that quite a bit of upgrade code is needed to compensate for the change of entity name from group_content to group_relationship.- πΊπΈUnited States pcate
I've also ran into this issue when trying to upgrade from v2.3 to v3.3. I can also confirm that upgrading from v2.2.2 to v3.3 does not run into this error.
- π©πͺGermany dbielke1986
I've also ran into this issue when trying to upgrade from v2.3 to v3.3.
- π³πΏNew Zealand jlscott
I have just run into this issue when trying to upgrade my site from Group 2 to Group. I have group 2.3.0 going to group 3.3.0 (along with subgroup from 2.0.2 to 3.0.2 and ginvite from 3.0.0-rc3 to 4.0.0-rc3).
- πΊπΈUnited States tomklemnyc
We are running into the same problem with upgrading from 2.2.2 to 3.3.2.
The website encountered an unexpected error. Try again later.
Symfony\Component\DependencyInjection\Exception\ServiceCircularReferenceException: Circular reference detected for service "router.route_provider", path: "options_request_listener -> router.route_provider -> cache_tags.invalidator -> cache.flexible_permissions_memory -> cache.backend.corefix_memory_no_serialize -> maintenance_mode_subscriber -> url_generator". in Drupal\Component\DependencyInjection\Container->get() (line 149 of core/lib/Drupal/Component/DependencyInjection/Container.php). - π§πͺBelgium kristiaanvandeneynde Antwerp, Belgium
There was an issue with group content types that had long names. Have you tried the latest release? 3.3.3
Also #7 seems completely unrelated to this issue.
- πΊπΈUnited States j-barnes
We ran into this issue when upgrading from 2.2.2 to 3.3.3. We realized that we had a
drush cr
before ourdrush updatedb
.Following the correct drush deploy sequence fixed our issue.
drush updatedb --no-cache-clear drush cache:rebuild drush config:import drush cache:rebuild drush deploy:hook