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

Content picker (MNTP) open action doesn't show content model #18210

Closed
bjarnef opened this issue Feb 3, 2025 · 4 comments
Closed

Content picker (MNTP) open action doesn't show content model #18210

bjarnef opened this issue Feb 3, 2025 · 4 comments
Labels

Comments

@bjarnef
Copy link
Contributor

bjarnef commented Feb 3, 2025

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

13.5.2

Bug summary

I can use MNTP to pick content from member, which work fine, although XPath is limited and doesn't work in this context.

However when I enable "Open" button, it doesn't show the correct content node, but seems to use current id from route.

Image

On open it request the correct node id via GetById?id=1442:

Image

but next it requests the GetPagedResults which return no results.

/umbraco/backoffice/umbracoapi/member/GetPagedResults?pageNumber=1&pageSize=100&orderBy=updateDate&orderDirection=Descending&orderBySystemField=true&filter=&memberTypeAlias=1442

Specifics

No response

Steps to reproduce

Add MTNP to member and enabled "Open" in datatype configuration.

Expected result / actual result

It should show something like this from listview in content:

Image

content shown under "Info" app is correct though.

Image

Copy link

github-actions bot commented Feb 3, 2025

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

@bjarnef
Copy link
Contributor Author

bjarnef commented Feb 3, 2025

The change in #17637 may be a possible fix, but I haven't tested it.

@AndyButland
Copy link
Contributor

I've tested this out and can't replicate the issue with the latest code. It does seem to be related to the fix you have linked.

So I'll close this one, but if you have chance to look at the 13.7 RC when it's out and can still replicate the problem, please do re-open.

@bjarnef
Copy link
Contributor Author

bjarnef commented Feb 4, 2025

I think it makes sense as the listview seems to fetch from current node (and of course no children on the member node), while in this case should have fetched children from opened content node.

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

2 participants