Support the content translation module

I am facing the access denied issue related in https://www.drupal.org/node/2866284.
I do not need separate permissions for each language but the website is translated in a "normal fashion", meaning using the Content Translation module - common node ID for all languages. We could not maintain this large translated website without Content Translation module enabled.

Is there any way PbT can work in this configuration ?

Same problem here like @amairesse.

I think the problem is situated in missing entries in table node_access. I've made some tests and this are my results:

1. add a node and a translation (no tag)

database entries (table node_access – columns nid langcode fallback gid realm grant_view grant_update grant_delete):

1486	de	1	0	all	1	0	0
1486	en	0	0	all	1	0	0

result: each translation is visible for all users

2. edit a node and add a restriced tag (»Only access by authenticated users«)

database entries:

1486	en	0	1486	permissions_by_term	1	0	0

result: english works as expected, but german is only accessible for administrator.

3. update database by duplicate row with changed language key

database entries:

1486	de	0	1486	permissions_by_term	1	0	0
1486	en	0	1486	permissions_by_term	1	0	0

result: each translation is visible for authenticated users – it works

4. update of the node leads delete the translated row ;-(

database entries and result: see 2.

Summary:

The missing entry for the translation in node_access leads to the error.

I would change priority to »Major« because the module is not usable for multilingual sites at the moment.

The description of hook_node_access_records() mentioned the following:

langcode: (optional) The language code of a specific translation of the node, if any. Modules may add this key to grant different access to different translations of a node, such that (e.g.) a particular group is granted access to edit the Catalan version of the node, but not the Hungarian version. If no value is provided, the langcode is set automatically from the $node parameter and the node's original language (if specified) is used as a fallback. Only specify multiple grant records with different languages for a node if the site has those languages configured.

So I've created the attached patch which solved the problem for me. After applying the patch you have to rebuild the permissions by running database updates with running update.php or drush updb or using of /admin/reports/status/rebuild.

@rwam : Tested, this works fine.

Many thanks!

Thank you rwam! #10 worked like a charm!!!