Content tree sometimes don't load icons

[andersburla]

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

15.1.2

Bug summary

Sometimes the tree icons won't load in the backoffice. Both for root lvl, but also when a tree item is expanded, then the icons of the sub pages also don't load. So either they load or don't

Important note is that we have only seen the error on Umbraco Cloud sites (as we do most there) - but both LOCAL, DEV and LIVE environments.

Specifics

I have attached screenshots of the HTML output and Network tab when the icons don't load, and when they do. Maybe that help in the debugging. icons-settings and icon-globe-alt are two of the icons that we have chosen for document types. The weird part is that icon-globe-alt is loaded in both cases, but icon-settings are only loaded when icons work.

Icons don't load

HTML - icons don't load/icons load

Network - icons don't load/icons load

Steps to reproduce

I'm having a hard time reproducing it time and time again. It's only sometimes it fails. I setup 5+ document types with different icons, and allow all document types as childs for each other. Then create some random content in the root and in lvl 1 + 2 of the content tree. Then hit F5 x times until it happens.

Expected result / actual result

I expect the icons to load every time

[github-actions]

Hi there @andersburla!

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

[jbreuer]

I'm having the exact same issues on an Umbraco 15.1.1 project that uses Umbraco Cloud.