Closed (duplicate)
Project:
Drupal Commons
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
3 Dec 2012 at 20:06 UTC
Updated:
8 Jul 2022 at 00:38 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedAfter further research, I found the uid assigned the node was not in the group. After assigning the user to the group, the error went away.
Changing this to a feature request to create an error message similar to:
The user is not a member of the group to which this node belongs.
Comment #2
geresy commentedWhy not automatically make the user a member of the group?
Comment #3
jpontani commentedIt's not really a feature request, as we want don't want to force a user to join a group if they want to create a node in a public group, or restrict them from creating nodes in public groups. As far as I'm aware, the plan is to allow all users to create nodes in public groups, regardless of membership.
I may be wrong, so I'll have to double check on this though.
Comment #4
ezra-g commented@gr8britton Can you post steps to reproduce?
In general:
- At least one group is required for Commons group content
- Users are automatically added as members of public groups when they create content in that group.
Comment #5
Anonymous (not verified) commentedI installed the 12/12 Dev version yesterday. Now, when I make a post logged in as one of the group's users (George Foreman), I can only add the title. The body and other components are NOT available. However, I did NOT get the message. It looks like this issue is no longer a problem.UPDATED: I found my test user was not in the proper role to be a content editor. I added him to the proper role.
What I am finding now is that if I go to the Group and use the Add Post link there, I only get the Title (no other components) and I can create the node with no body and no error message.
If I use the Admin menu to create a new post, I get the warning message and still only the Title Component.
Comment #6
Anonymous (not verified) commentedComment #7
Topcheese commented@gr8britton, you changed the status to active, but you did not provide any details in order to help get your problem resolved faster. Sounds like it might not be installed properly, what is the environment and the steps taken?
Comment #8
Anonymous (not verified) commentedI had entered updated info in #5 but did not get a response until I change it back to active.
To answer your further questions:
Comment #9
ezra-g commentedThis is a duplicate of #1845050: reference field set to "Autocomplete (Tags style)" not returning any matches. Marking postponed pending resolution of that issue in OG.
Comment #10
ezra-g commentedComment #11
ezra-g commentedLooks like we have a Commons issue for this already - Marking as a duplicate of #1818180: Refactor og_group_ref field definition .
Comment #12
krazykellie commentedI'm not sure if this helps anyone, but all we did to correct this error was remove the permissions under the OG and then reestablish them. It was a quick and easy fix!