Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content Editor - Issue with Adding Content #63

Open
dsheffler opened this issue Mar 16, 2015 · 8 comments
Open

Content Editor - Issue with Adding Content #63

dsheffler opened this issue Mar 16, 2015 · 8 comments

Comments

@dsheffler
Copy link

I have the content editor permission and when trying to add a new basic page, I get the following error: "You must choose one or more groups." The only issue is that I don't have access to see anything on the page called groups. I'm also not able to save the content.

@bendygirl
Copy link

checked and the content editor does not have permission to add a new basic page. For our editors, this is probably useful.

@timwood
Copy link
Contributor

timwood commented Mar 16, 2015

Thanks for testing @dsheffler, it really helps that we can identify these issues because there are so few of us working on the site before today and we mostly used admin role or didn't test adding new content like pages. I've added you to the node/1 organic group. I'll add other content editors too.

@timwood
Copy link
Contributor

timwood commented Mar 16, 2015

@bendygirl Content Editor role has this permission, which allows them to do this:

Bypass content access control
View, edit and delete all content regardless of permission restrictions. Warning: Give to trusted roles only; this permission has security implications.

@bendygirl
Copy link

Thanks @timwood Tim

@timwood
Copy link
Contributor

timwood commented Mar 16, 2015

So I've been unable to resolve this issue. If any new page content needs to be created it will have to be done as an admin. For some reason the conference field is "broken" for non-admins for the basic page, news and sponsor content types. Nothing I've tried in changing organic groups reference field has resolved the issue. Meanwhile the other instances of the same field on bof-session, session and chedule-item seem to work fine. They automatically populate with the one conference (event) node in the site.

@timwood timwood added this to the Post launch milestone Mar 16, 2015
@timwood timwood added the bug label Mar 20, 2015
@timwood timwood removed this from the March 30 milestone Mar 20, 2015
@timwood
Copy link
Contributor

timwood commented Mar 20, 2015

Punting to ? Doesn't affect session or bof-session, so only really affects event planners.

@timwood
Copy link
Contributor

timwood commented Mar 20, 2015

I wonder if the issue we encountered here is related to https://www.drupal.org/node/2357459

@bendygirl
Copy link

Work around is admin access.

As long as we aren't making config changes in production, this seems fine for a work around

Sent from my iPhone

On Mar 20, 2015, at 12:11 AM, Tim Wood [email protected] wrote:

Punting to ? Doesn't affect session or bof-session, so only really affects event planners.


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants