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

Allowed child node types is not honoured in ListView #18345

Closed
robertjf opened this issue Feb 15, 2025 · 2 comments
Closed

Allowed child node types is not honoured in ListView #18345

robertjf opened this issue Feb 15, 2025 · 2 comments

Comments

@robertjf
Copy link
Contributor

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

13.6.0

Bug summary

When a node with ListView enabled is created under a node with a different type also with ListView enabled, the allowed types is being inherited from the parent node instead of honouring the configured allowed types of the current node. See video for demonstration.

This does not happen if the node is created underneath a node without ListView.

Screen.Recording.2025-02-16.at.08.17.01.mov

Specifics

Video showing the incorrect behaviour is in the Bug Summary

Steps to reproduce

  • Create two document types with ListView enabled. One should have one or more allowed document types including the second document type, the other should have a single allowed document type not appearing in the allowed list for the first one.
  • Create a node based on the first document type.
  • Create a node under the new node based on the second document type.
  • Now attempt to create a node under the second node.

Expected result / actual result

The ListView should show the list of nodes allowed for the current node, not inherit from it's parent.

Copy link

Hi there @robertjf!

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
Copy link
Contributor

I couldn't replicate this @robertjf and tested with the latest code. I believe it's caused by the same issue as #13355 and, if so, fixed in 13.7 via #17637. I'll close this but if you have chance to try out the 13.7-rc and still see the issue, please re-open.

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

3 participants