Problem/Motivation
We've seen in other modules some problems with published / unpublished translations, where suddenly either an unpublished translation being created was removing access for the published original node, or the other way around: saving an original node having unpublished translations was allowing access to everything.
The thing is core doesn't mind about a node's status if there are grants on the DB.
So let's write a test:
- create a published restricted node
- check access is ok
- create an unpublished translation
- check access is ok for both translations (original language is restricted, unpublished node does not have lines in the node_access table)
- publish the translation
- check access is ok (restricted for original and translation)
- unpublish the original
- check access is ok (nothing in DB for the original, restricted access for translation)
Issue fork access_by_taxonomy-3466778
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
joey-santiago commentedWorking on this, we realized quite many things:
Doing this, we are writing a ton of tests.
Comment #5
joey-santiago commented