As discussed in #770870: Access denied when creating node if restricted to a role assigned by og_user_roles and i18n is enabled, an "Access Denied" error is encountered when attempting to translate an existing node if the user only has access granted through a role assigned in og_user_ roles. The problem happens because the og_user_roles module needs some context to know whether or not to assign a role, and it cannot find that context unless the gids[] parameter is passed in the "add translation" link.

Comments

spacereactor’s picture

spacereactor commented

subscribing

mparker17’s picture

mparker17
he/him
Primary language English
Location UTC-5
commented

Subscribing. Thanks @wdouglascampbell !

spouilly’s picture

spouilly commented

I am not sure it is an actual issue with OGUR, I am facing a similar issue and it boils down to 'how do you synchronize the "audience" in nodes that are both "Group Content" (i.e. can be posted in a group) and "translatable'. In a perfect world, when translating the node, the audience for the translation should be the same one as the original node. If we are able to sync the "audience", then the Access Denied issue with OGUR should go away.

I have not seem much information on keeping the "audience" field in sync with translation on the Drupal website.

I started to look at the i18nsync modules ... but it tackles mostly regular fields and CCK fields. Unfortunately, the "audience" field is neither a regular field, neither a CCK field (FYI, the data about the audience is stored in og_ancestry).

Sylvain

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

Can someone clean up the patch from #770870-19: Access denied when creating node if restricted to a role assigned by og_user_roles and i18n is enabled and attach it over here?

I'm not familiar with that "mode" setting, so the comments definitely would have to be clarified. (next to the coding style that needs work ;)

wdouglascampbell’s picture

wdouglascampbell commented

What needs cleaning up??? It is two lines of code and as far as coding style, what are you talking about? I don't get your comment. Did you look at the patch?

The i18n mode setting is basically i18n's language negotiation settings. These determine the site's presentation language.

Also, I am not sure why you are asking for it to be attached to this issue. It goes with the issue it is attached to currently.