Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multi-language CMS: misleading/redundant links #17586

Open
shearer3000 opened this issue Nov 20, 2024 · 1 comment
Open

multi-language CMS: misleading/redundant links #17586

shearer3000 opened this issue Nov 20, 2024 · 1 comment
Labels

Comments

@shearer3000
Copy link

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

any version of Umbraco 13, but using 13.5.2 at time of writing

Bug summary

Given a traditional multi language/site setup in Umbraco e.g. English, German and French languages with a content tree for each, The links section of a page will show a link for all of the languages when only 1 is relevant/applicable (i.e. 1 language selected in Culture and hostnames section), and will show a "This document is published but is not in the cache" for all others.

image

Specifics

No response

Steps to reproduce

  1. add multiple languages to CMS settings:
    image

  2. add content tree per language and select
    image
    image
    image

  3. observe Links section on content node
    image

NB "allow vary by culture" not selected on doctypes - this isn't a language variants CMS setup.

Expected result / actual result

Expected: only link relevant to language (culture) are shown on content node

Actual: shows a link per language defined in CMS irrespective of culture settings on specific content tree

Copy link

Hi there @shearer3000!

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 🤖 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant