Closed (fixed)
Project:
Group
Version:
3.3.2
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Dec 2024 at 17:12 UTC
Updated:
5 Mar 2025 at 15:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
classiccut commentedComment #3
muaz7731Having the same problem. the code provided fix the problem.
Comment #4
jbuttler commentedI have the same issue, but I am not as experienced with coding. Could you tell me where you added this code to resolve the issue?
Comment #5
muaz7731see related issue comment #4 here https://www.drupal.org/project/group/issues/3487012#comment-15905538
Comment #6
j-barnes commentedAttaching patch with update hook that we used to fix the issue.Removing, didn't take into account this could effect future updates if not merged.
Comment #8
j-barnes commentedComment #9
j-barnes commentedComment #10
j-barnes commentedComment #13
classiccut commented@jbuttler I placed that code in an update hook in one of my custom modules. I suppose you could also run the same code throught drush php:cli
Comment #14
marcos318888 commentedComment #15
marcos318888 commentedComment #17
kristiaanvandeneyndeAdding credit from #3487012: Uninstall module page not working
Comment #18
kristiaanvandeneyndeAssigning credit to @classiccut for correctly identifying the problem and offering a solution.
For this to get committed, we need to update the update path test to prove the fix works. Setting to NW for that, but that should be rather easy to test for. I can take care of that either tomorrow or next week I hope.
Comment #21
kristiaanvandeneyndeThis seems to fix it. I was contemplating updating all ER fields pointing to group_content_type just like we do with ER fields pointing to group_content, but I'm a bit on the fence as you really shouldn't be creating ER fields pointing to that entity type.
There's a reason the label is: "INTERNAL USE ONLY -- @group_type -- @plugin"
Comment #22
kristiaanvandeneyndeComment #24
kristiaanvandeneyndeGonna go ahead and release this soon as this is quite a major obstacle to upgrading from v2.
Comment #25
classiccut commentedThis is great! Thanks so much for all the hard work.