If I don't give "edit any review nodes" permission to translator role, but give "Translate entities of type Node" permission - the translator doesn't see "Add translation" link on "Translate" tab (screenshot: http://pix.am/GdN0/)

If I give "edit any review nodes" permission to him - there is no sense in restricting him by Entity Translation module permissions - since the role seems to get full access to all fields - both in original node and in translated node.

Can someone explain to me which permissions should I give to "translator" role so translators can only translate nodes, not edit the original node?

Comments

plach’s picture

Status: Active » Fixed

To let a translator edit only translations you need to grant an edit permission on the node but not grant the 'edit original values' permission (nor the 'edit shared values' permission probably).

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

candelas’s picture

Component: Base system » Documentation
Category: support » task
Status: Closed (fixed) » Active

thanks for the module.
it took to me a while until i realize that i had also to activate "Enable translation workflow permissions" in admin/config/regional/entity_translation to get the "Edit original values" to show in the permissions page "admin/people/permissions"

it would nice if in the documentation you put step by step how to set that translators can translate without been able to edit original. i would do it, but my english it is not good enough.

again, thanks for this module :)

plach’s picture

it would nice if in the documentation you put step by step how to set that translators can translate without been able to edit original. i would do it, but my english it is not good enough.

If you can provide me an initial draft I can work on fixing any issue I'm able to spot (I'm not a native english speaker too :)

candelas’s picture

@plach, thanks for the offer. i take it :)
but now i am struggling with a shipping method with commerce in a custom module...
next month i will do other shop, come here in the moment that i am doing it and write the process.
also it would be interesting to now if for menus there is a tool to be able to translate all in one time or table that it is compatible with entity translation, instead of having to go to each menu item.

plach’s picture

I think you can use the regular core .po import/export process: i18n_menu should leverage it and ET just builds upon i18n_menu.

candelas’s picture

thanks @plach. i explained bad. i mean custom menu items.
i have used translation_table before but i think it doesnt work with your module... :)
i wanted to ask if i am right and if there is a similar alternative.
thanks a lot for your help :)

plach’s picture

I was referring to custom menu items too, I think. Do you mean the ones you create from the node form in Menu settings? If so I confirm the suggestion in #6: export the strings in the menu group, translate them with poedit or a similar tool and then reimport the resulting .po file.

plach’s picture

Title: Which permissions should I give to translator so he can only translate nodes, not edit the original node? » Improve documentation for wokflow permissions
Status: Active » Fixed
plach’s picture

Status: Fixed » Active

wtf

plach’s picture

Title: Improve documentation for wokflow permissions » Improve the documentation for workflow permissions

aw

candelas’s picture

Assigned: Unassigned » candelas

thanks @plach. i will do that for spanish that i will translate, but we are going to translate for german and french with normal translators... i dont know if they will feel confortable with this way of doing or they prefer going one by one menu item...

i assign this issue to me, so i dont forget the collaboration that you offer and i accepted :)

candelas’s picture

Issue summary: View changes

fix

ciss’s picture

Issue summary: View changes

@candelas: Since you're still assigned: did you make any progress on this? It seems that the "Workflow permissions" section hasn't been updated since your last comment, so the issue might still be relevant.