MultiUrlPicker | Chosen Media URL becomes NULL after save

[ViktorAbrahamsson]

Which Umbraco version are you using?

13.5.2

Bug summary

When using Umbraco.MuliUrlPicker and choosing "Link to media" and selecting a file that isn't in the root of the media-library, the URL becomes NULL if the file is in another folder.

On the documenttype however, the URL is still there but it's not accessable through the frontend.

Exampels

1. MultiUrlPicker with chosen media that exists inside another folder, before saving page.
   

2. MultiUrlPicker with chosen media that exists inside another folder, after saving page.
   

3. View inside the MultiUrlPicker, here the URL is still here.
   

4. After submiting, we are back at example 1.

Specifics

Browsers
Checked on the following browsers, all got the same problem.

• Firefox
• Chrome
• Brave (Chromium)
• Safari

Logs
Nothing relevant in the logs.

Other information

• I've tried on another 13.5.2 Umbraco Cloud-site and this bug was not present.
• Tried to copy the URL to a file withing a folder, and not using "Select media", this works.
• It have previously worked, but after an unknown automatic upgrade it stopped to work.

Steps to reproduce

Due to not being able to reproduce it myself on another 13.5.2 Umbraco Cloud-site I doubt it will be easy to reproduce for others.

1. Create a new MultiUrlPicker and make it so it only can select one URL.
2. In Media, upload some files both in the root and in folders.
3. Test if the URL becomes null after saving the page.

Expected result / actual result

Desired outcome is to be able to select media-files that exists inside folders in the Media-library.
Current outcome is that on every page that have a file chosen that exists inside a folder is not visible on the frontend.

[github-actions]

Hi there @ViktorAbrahamsson!

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