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

V15 - Model.AncestorOrSelf("home") does not work, yet Model.AncestorOrSelf<Home>() does #17549

Open
asawyermarathon opened this issue Nov 15, 2024 · 1 comment
Labels
state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug

Comments

@asawyermarathon
Copy link
Contributor

asawyermarathon commented Nov 15, 2024

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

15.0.0

Bug summary

In Umbraco 15.0.0, calling Model.AncestorOrSelf("home") does not return the ancestor home page with doctype alias "home", yet Model.AncestorOrSelf<Home>() does. Is this intentional? I think it is not.

Specifics

No response

Steps to reproduce

  1. Create new Umbraco 15 site
  2. Create two doctypes, home and subpage, allowing subpages to be created under the home doctype
  3. Enable strongly typed models (I'm using "SourceCodeManual")
  4. Create a node instance of Home with Subpage node underneath
  5. In the subpage template, call var homeNode = Model.AncestorOrSelf("home"); and output an attribute of the home node: Home Node Name: <strong>@homeNode?.Name</strong>
  6. The data is incorrect, because the call returns the current node instead of the ancestor node.

devenv_v89K4rZtzA

Expected result / actual result

No response


This item has been added to our backlog AB#46060

Copy link

Hi there @asawyermarathon!

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

@bergmania bergmania added the state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks label Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug
Projects
None yet
Development

No branches or pull requests

2 participants