MultiNode Treepicker allows selection of more than configured maximum number of items

[ProNotion]

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

12.3.10

Bug summary

When a maximum number of items is configured on the datatype users are still able to select more than the maximum number of nodes when selecting multiple content items in the tree picker in a single action. If links are added one at a time the maximum cannot be exceeded.

The node cannot be published while there are more than the maximum number of items, however, the tab is highlighted on which the property exists but the property itself is not. The error message is present but since it is not highlighted can be easily missed.

Specifics

When selecting more than maximum you are still able to add more than you should.

When adding items one at a time you cannot add more than maximum

Steps to reproduce

1. Create a datatype with a Umbraco.MultiNodeTreePicker property editor. Set a maximum number of items that can be selected.
2. Add a property to a content type using the new datatype.
3. Add a new content item using the new content type
4. Click to add new content using the MutliNode Tree Picker and select more than the maximum number of items.

Expected result / actual result

You should not be able to select more than the maximum number of items in the UI, regardless of how you add them.

[github-actions]

Hi there @ProNotion!

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

[NguyenThuyLan]

Hi @ProNotion , thank you for reporting this issue.
However, this is not a bug. We want the editors to be able to save invalid content in a draft state.
The thought behind this is: if one is writing up a page of content and gets interrupted in the middle of it all, they should be able to save whatever they have done so far, so as not to lose their work.
And of course, users can not publish content because of invalid content.
I will close this issue, feel free to reopen it or ask 😊