- Issue created by @zenimagine
- πΊπΈUnited States pcate
When I ran into this I manually added back the variationcache module via composer so the module could then be uninstalled.
- πΊπΈUnited States dalemoore
Ran into the same issue. composer require again variationcache and then run all updates (backing up first!), then uninstalling variationcache seems to work fine so far. But this is a new site and I haven't yet done anything with Group, so who knows if all is well.
- π§πͺBelgium kristiaanvandeneynde Antwerp, Belgium
VariationCache is now a dev dependency of Group so that people can upgrade and then get rid of it. It will be fully removed in v4. I'll add instructions to the release notes. Thanks for reporting this, everyone.
The reason Flexible Permissions isn't removed yet while VariationCache is, is that FP got a new major release, dropping VC. Whereas Group hasn't gotten a major version number bump, so we can't drop FP yet.
- π§πͺBelgium kristiaanvandeneynde Antwerp, Belgium
I've added a section to the release notes:
Disabling VariationCache (the module)
This release bumps the version of Flexible Permissions to 2.x.x, which no longer needs the VariationCache module as it now relies on the one from core.
If you are upgrading using composer, you should either
composer require drupal/variationcache
before or after downloading the new Group version (composer require drupal/group:^3.3 -W
). After running database updates, you can then turn off the variationcache module and remove the dependency once and for all.If you are still using manual downloads, just update, turn off variationcache and then feel free to delete said module from your filesystem.
Automatically closed - issue fixed for 2 weeks with no activity.