Info tab shows language entries for non-variant content nodes

[brianlyktwoday]

Which Umbraco version are you using?

17.1.0

Bug summary

I am not entirely sure whether this should be considered a bug or a feature request. But the behavior appears to differ from Umbraco 16. 😊

In multi-language Umbraco solutions where content does not use language variants, the Info tab on content nodes displays links for all configured languages, with entries marked as “Not created”.

This occurs even when the document type does not allow variation by culture and the node can only ever exist in a single language.

Umbraco 17

Umbraco 16

Specifics

No response

Steps to reproduce

The issue can be reproduced on a clean Umbraco installation using the following steps:

1. Create a new Umbraco site.
2. Configure more than one language under Settings > Languages (for example EN-US and DA-DK).
3. Create a document type where "Allow vary by culture" is set to false.
4. Create multiple nodes in the root of the content tree.
5. Assign Culture and Hostnames so that each root node is associated with exactly one language.
6. Open a node and navigate to the Info tab.

Expected result / actual result

Expected result
The Info tab should only show information relevant to the actual language of the node. Since:

• the document type does not allow variation by culture, and
• the node is associated with only one language via Culture and Hostnames,

there should be no indication of other languages or language variants for this node.

Actual result
The Info tab displays a list of all configured languages in the solution. For languages where the node does not exist, an entry is shown with the message “Not created”.

On sites with many languages, this list becomes quite long and can be confusing for editors. This is particularly problematic when editors only have access to part of the content tree. For example, an editor with access only to the US site will still see references to other languages such as DK, even though they should not be aware that these sites exist.

[github-actions]

Hi there @brianlyktwoday!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[AndyButland]

Fixed via #21473 for 17.2.