v.15.1.1 Issues with content delivery API after 17.12.2024 small upgrade

[SC-EVS]

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

15.1.1

Bug summary

Hello, yesterday (17th December 2024) our Ubraco cloud upgraded itself to v 15.1.1 (image attached) and I noticed some of the content delivery API stopped working as it should.

I have the following content structure (image attached):
Home
|__ Booter
SharedContent
|__Footer
|__Navigation

Previously, I had the a couple of queries with relative paths as follows:

1. /umbraco/delivery/api/v2/content/item/home/booter (it worked before upgrade, works after the upgrade)
2. /umbraco/delivery/api/v2/content/item/sharedcontent/footer (it worked before upgrade, gives a 404 now)

If I request a footer item directly (/umbraco/delivery/api/v2/content/item/footer) it works, but then if I change the name of the page under the Home (Booter --> Footer), this request will pick the first item it finds which is incorrect.

Sounds like a really nasty bug... Do you guys encounter the same issue? Can I combat this somehow now or is this perhaps going to be fixed in the next "minor upgrade"?

Thanks!

Specifics

Erroneous URL is /umbraco/delivery/api/v2/content/item/_relativePathToItem_

Steps to reproduce

1. On a clean instance, enable the content delivery API
2. Create the same content item structure as on the screenshot
3. Request the same paths as described in the summary

Expected result / actual result

Expected result:
/umbraco/delivery/api/v2/content/item/sharedcontent/footer returns 200 with some JSON

Actual result:
/umbraco/delivery/api/v2/content/item/sharedcontent/footer returns 404

---

This item has been added to our backlog AB#47299

[github-actions]

Hi there @SC-EVS!

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