v14.3 - RTE does not render links correctly if anchor or querystring is populated

[too-dark-park]

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

14.3

Bug summary

When adding a 'link to page' in an RTE, the link URL doesn't render correctly if an anchor or querystring value has been added. The resulting link renders something like https://localhost:44381/%7BlocalLink:9ba1b48b-71ce-4654-b783-2621077ff8ad%7D?examplequerystring

Specifics

The rendered link

In a block grid RTE, when you try editing the link again the anchor HTML actually replaces the title and you lose the link value and anchor / querystring title.

Steps to reproduce

1. Add an RTE to a doctype
2. In the RTE, add a link with a querystring or anchor
3. Select a page using 'link to page'
4. Save the link
5. Save and publish
6. View the rendered page and click the link
7. You will see the rendered link looks similar to https://localhost:44381/%7BlocalLink:efaa9445-2ab5-4b54-9fd8-95aef6af2770%7D#example-anchor

Expected result / actual result

I would expect the rendered link to represent the URL of the node/document I selected with the anchor or querystring correctly appended. For example; https://localhost:44381/mypageurl#example-anchor.

Instead the link is currently being rendered as https://localhost:44381/%7BlocalLink:efaa9445-2ab5-4b54-9fd8-95aef6af2770%7D#example-anchor

---

This item has been added to our backlog AB#45052

[github-actions]

Hi there @too-dark-park!

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

[iOvergaard]

Hi @too-dark-park, thank you so much for reporting this.

I can confirm this is reproducible and is a problem we want to look into.

[iOvergaard]

This has been fixed and will be included in 15.0.0-rc2, which should be released tomorrow