Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I can't create subspaces anymore for some reason. I get the error, "The referenced group (node: ##) is invalid." when selecting the parent space within the inheritance section. I was running version 2.18 and noticed this problem. The issue still exists when upgraded to 2.19.
Comments
Comment #1
Argus CreditAttribution: Argus commentedComment #2
mpotter CreditAttribution: mpotter commentedI cannot reproduce this. You'll need to provide more details on how exactly to reproduce this in the latest 2.23 version.
Comment #3
Adam Fermier CreditAttribution: Adam Fermier commentedHi Guys - I was able to reproduce after some research!
1) As Admin - go to a space where you are not listed as a member
2) Create Content
Results: The content is not linked to the defined section/space - so it is essentially hanging in space. Trying to "override" and put in the space gave me the clue as it was calling it invalid.
To fix: If Admin - add yourself to the space :)
Adam
Comment #4
mpotter CreditAttribution: mpotter commentedAdam: That is "by design". Organic Groups is one of the few modules in Drupal that does not automatically grant access to the Admin user. You need to add the Admin user to the space for it to work properly.
Also, be careful replying to closed issues as it only notifies the module maintainer and isn't seen by the overall community.
Comment #5
Argus CreditAttribution: Argus commented... and users active in the thread...
Comment #6
pmusaraj CreditAttribution: pmusaraj commentedFWIW, there should be a clearer indication to the user that he/she should first become a group member before doing this kind of operation. The "referenced group (node: ##) is invalid" message doesn't explain much.
Comment #7
pgancarski CreditAttribution: pgancarski commentedI believe I have the same issue with 7.x-2.43
Administrator member of a space gets the "The referenced group (node: xxx) is invalid" error whenever he tries to edit the space description.
node: xxx is a public, parent space. The user is not its member. I use it just for the purpose of structuring the content and the space administrator should not change it.
The walk around I give to the users is to remove Inheritance/Parent reference before saving the node. The strange thing is that after the node is being saved the reference to parent space remains (which is good as I don't want the space to hang in space whenever it is being edited). As I have non-IT users administrating spaces and I don't want them to break the website structure, I am going to hide the Inheritance field from the edit page and override access checks on it.
In my understanding the fix here is to allow space inheritance from any public space.
Comment #8
mpotter CreditAttribution: mpotter commentedPlease don't re-open old bug reports and change them to support requests, always create a new support request. Also, the "needs review" status is only for issues that have patches posted. Finally, we can only give support for the latest releases of Atrium to you'll need to upgrade to the 7.x-2.50 version. If you still have trouble with that then you can post a question to a new issue.