Media issues with non-admin users

[SandyK-W]

Which Umbraco version are you using?

13.12.0

Bug summary

Users reporting issues with media picker. Admin works just fine but they are getting:
Request error: The URL returned a 404 (not found):
/umbraco/backoffice/umbracoapi/entity/GetPagedDescendants

This is causing issues and I can recreate it easily. Any help is appreciated

Specifics

• This happens when users try to access our /news media folder.
• I've tried in firefox and chrome
• I've tried re-assigning the permissions.
• Error persists

Steps to reproduce

Create a user group and give it content and media access.
Create a non-admin user and assign the new group.
Try and select media (from the content node, media library works correctly)

Expected result / actual result

Expected:

Actual:

[github-actions]

Hi there @SandyK-W!

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]

Thanks for reporting @SandyK-W - I can replicate the issue on 13.12, but it looks to be fixed on 13.13, for which we'll make available a release candidate tomorrow, but it doesn't look to be the same as you are seeing.

Looks like this was related to the similar issue of #20967.

I'll mark this as closed and also as fixed in this release, and you can try an upgrade once it's out to confirm that is resolve the problem you are seeing.