search

Drupal4Gov / Drupal-GovCon-2015

Drupal GovCon 2015 website
MIT License
1 stars 2 forks source link

Content Editor - Issue with Adding Content #63

Open dsheffler opened 9 years ago

dsheffler commented 9 years ago

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 commented 9 years ago

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

timwood commented 9 years ago

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 commented 9 years ago

@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 commented 9 years ago

Thanks @timwood Tim

timwood commented 9 years ago

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 commented 9 years ago

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

timwood commented 9 years ago

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

bendygirl commented 9 years ago

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 notifications@github.com 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.