- 🇧🇪Belgium nils.destoop
An updated patch. The check in DomainAccessNodeTranslationHandler was not using the same logic like the node access. Now it also checks access using the entityAccess helper.
When I use the domain_access module, I can restrict the access for content editing to only people which are assigned to the proper domains. But, the content translate functionality is still not restricted. So even if I can choose to let an editor to edit or not a node on his domains, I cannot choose to let the user translate or not that content.
The domain_access module could expose special permissions for content translation: "Translate any content on assigned domains" and "%type_name: Translate any content on assigned domains".
Active
11.0 🔥
(Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
An updated patch. The check in DomainAccessNodeTranslationHandler was not using the same logic like the node access. Now it also checks access using the entityAccess helper.