When "Enable translation" is not enabled for content or taxonomy terms, admin users can still access the translation page and add translations. This behavior contradicts the intended restriction on non-translatable entities. The issue occurs regardless of the source or target languages and affects both content and taxonomy terms.
/node/{nid}/translations/add/{source_language}/{target_language} (e.g., /node/1/translations/add/en/ja)./taxonomy/term/{tid}/translations/add/{source_language}/{target_language} (e.g., /taxonomy/term/1/translations/add/ja/en).Active
11.1 🔥
content_translation.module
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Restoring template. The issue template is used to track progress and various tasks on an issue.
Un-assigning per Assigning ownership of a Drupal core issue → .
Any User with 'Translate any entity' permission will be able to translate an entity even when 'Enable Translation' is not enabled individually.
As an option, we could just add another check if entity is translatable.