MNTP dynamic root doesn't work inside block list elements

[philipdanielhayton]

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

14.0.0

Bug summary

MNTP with a dynamic root query doesn't work when on an element type within a block list.

https://github.com/umbraco/Umbraco-CMS/assets/19938510/2c2a3704-34b3-45e9-b514-2d087bc5f7a1

Specifics

Some extra info:

• I've tried using both Site and Root start nodes, both fail
• The property editor has 'ignore root node' set. If it's unset, it throws a 401 as you would expect.
• It works when hand picking a specific start node

Steps to reproduce

1. Create a MNTP with a dynamic root query
2. Create an element type, add the MNTP as a property
3. Create a Block List and add the element from (3) as an allowed element
4. Create a new doc type and add two properties; the MNTP and the block list
5. Create a new node in the content tree of type (4) and try to pick a node using both the MNTP and the Block List editor. The MNTP directly on the node will work, the one on the block list nested element will not.

Expected result / actual result

I would expect the MNTP on the block list nested element to resolve to the correct location.

---

This item has been added to our backlog AB#42341

[github-actions[bot]]

Hi there @philipdanielhayton!

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 :robot: :slightly_smiling_face: