- Issue created by @vitch
Language hierarchy is not compatible with content language access. Having both modules enabled breaks language hierarchy functionality. This is not a bug but an incompatibility in modules doing opposite jobs. However it would be nice to be able to use both to obtain the 4xx error if no valid translation exists but only after language hierarchy has tried finding an appropriate translation.
Install language hierarchy and content language access on a Drupal instance.
Configure a hiearchy of languages with a node having a translation in the parent language and not in the child language
accesing this node using the child language url works when logged in (i think this is because drupal assumes we want to edit or create a a translation)
However when logged out, trying to access that node via the child language will result in a 4xx error. Which is the expected content language access behavior.
Not sure how this would be done the goal would be to have content language access do its work after language hierarchy has done in fallback resolution. I have no idea how to translate this in hooks.
Active
Code