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

Duplicate property alias does not trigger which tab and which property the error is found on #18417

Open
JeffreyPerplex opened this issue Feb 21, 2025 · 1 comment

Comments

@JeffreyPerplex
Copy link
Contributor

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

15.2.1.

Bug summary

If you create or edit a document type and you accidently create a property with a duplicate propertype alias you get a nice error message.

In v13 and before the UI also highlighted the tab where the error was found and the property that was duplicate. That made it way easier to fix it than in v14+. So hopefully somebody can give that some UX love!

Specifics

No response

Steps to reproduce

In v13 and before this was shown:

Image

Image

Superusefull and you could directly fix it.

In v15.1.2 it shows this:

Image

Image

So you miss the indication what you should do or fix

Expected result / actual result

Highlight of the tab that has the error + highlight of the property on that tab.

Or, if you want bonus points, it should directly navigate to the property

Copy link

Hi there @JeffreyPerplex!

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
Projects
None yet
Development

No branches or pull requests

2 participants