Hi there @Dark0d3, thank you for this contribution! 👍

While we wait for one of the Core Collaborators team to have a look at your work, we wanted to let you know about that we have a checklist for some of the things we will consider during review:

• It's clear what problem this is solving, there's a connected issue or a description of what the changes do and how to test them
• The automated tests all pass (see "Checks" tab on this PR)
• The level of security for this contribution is the same or improved
• The level of performance for this contribution is the same or improved
• Avoids creating breaking changes; note that behavioral changes might also be perceived as breaking
• If this is a new feature, Umbraco HQ provided guidance on the implementation beforehand
• 💡 The contribution looks original and the contributor is presumably allowed to share it

Don't worry if you got something wrong. We like to think of a pull request as the start of a conversation, we're happy to provide guidance on improving your contribution.

If you realize that you might want to make some changes then you can do that by adding new commits to the branch you created for this work and pushing new commits. They should then automatically show up as updates to this pull request.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

Hi @Dark0d3 thanks for this! I see you have a conversation with @Migaroez about this one on the issue. Before anyone in the core collabs team or HQ can resolve this one, I just wanted to flag that some merge conflicts have appeared in this PR, in case you hadn't seen.

Thanks so much for your contribution and hopefully this one can help us to apply the fix to 14 too.

Emma

Hi @emmagarland, that was my bad I was trying to merge to the wrong branch. I have changed it now.

I am going to close this PR as #17288, which is a more complete solution, has already been cherry picked into v14 1581eb6 and will be part of the next v14 release.