This project is not covered by Drupal’s security advisory policy.
When an entity has multiple translations and the untranslated version gets unpublished -- either via the UI or an API call -- the other translations remain visible. This is often not desirable. For example, after using the replicate module to clone an entity, it is useful if the clone is not published immediately. However, if all translations are unpublished then the published status of the translation is lost and also re-publishing becomes a problem. Instead, this module will hide the translations from those who can't view unpublished entities.
By default only nodes are controlled. Node listings are checked as described above but individual node pages are access checked by also taking the untranslated access into consideration. It should only take minimal effort based on untatu.module and untatu_test.module to hook in another entity. There is no UI and no settings.
Project information
Minimally maintained
Maintainers monitor issues, but fast responses are not guaranteed.- Maintenance fixes only
Considered feature-complete by its maintainers. - Project categories: Access control
- Created by ghost of drupal past on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
