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

MNTP Xpath with $current doesn't work correct on site node itself #17519

Open
bjarnef opened this issue Nov 12, 2024 · 1 comment
Open

MNTP Xpath with $current doesn't work correct on site node itself #17519

bjarnef opened this issue Nov 12, 2024 · 1 comment
Labels

Comments

@bjarnef
Copy link
Contributor

bjarnef commented Nov 12, 2024

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

13.5.2

Bug summary

We have a content structure as following.

image

In a block used on both home page and child pages, it has a category property using MNTP and the following:

Xpath: $site/settings

It select correct settings node as start node on child pages, but on home page, it just use root as start node.

Workaround is the following:

Xpath: $current/ancestor-or-self::homePage/settings or $current/ancestor-or-self::*[@level=1]/settings

I guess it is because $site is a placeholder for ancestor, but not ancestor-or-self

image

Specifics

No response

Steps to reproduce

Follow steps mentioned before.

Expected result / actual result

No response

Copy link

Hi there @bjarnef!

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