I am interested in granting permission for users to translate a certain content type.
Node access permissions (view/edit/delete) are controlled by content type, however, translation content permission are generic and not content type related.
This situation creates some logical conflicts.
For example, assume I grant translation permission to a certain role, grant edit permission to A content type and do not grant edit permission to B content type.

First, any viewing of any content type will now show a “view” tab which is unnecessary if the user does not have “edit” rights.

Second, viewing B content type (which does not have edit rights) will still show a “Translate” tab. If you go to the translate screen, it will look very similar to a standard translate screen, showing you all the translatable nodes, however, the actual “Edit” link is missing, there is nothing under the “Operations” column.
This is very confusing and does not make much sense.

I might be missing something but I would like to see translation permissions on the same level as view/edit/delete , applied per node content type. (Or an entity)

Comments

Jose Reyero’s picture

Jose Reyero CreditAttribution: Jose Reyero commented
Status: Active » Closed (won't fix)

That would be a nice feature for a new module. This one is big enough already and i18n permissions are just consistent with Drupal core ones.

taitai’s picture

taitai CreditAttribution: taitai commented

It might exactly be the point... why Drupal core permissions do not include "translate".

Kojo Unsui’s picture

Kojo Unsui CreditAttribution: Kojo Unsui commented

This is exactly the issue I'm facing.
In a few words, how could I alter the node output so that it doesn't show the unnecessary tabs as explained above ? Thanks a lot for your advices, as I'm not very familiar yet with API and Drupal dev. practices...