Question: Why are the hyperlinks in the Termly consent banner showing code instead of links when using ASP.Net?
Answer: This issue arises due to conflicts between ASP.Net Script Manager and the Termly consent banner. Specifically, the Script Manager is interfering with the rendering of hyperlinks, causing the HTML to display the raw hyperlink code rather than functioning links.
Question: Can I remove the ASP.Net Script Manager to resolve this?
Answer: If removing the ASP.Net Script Manager is not an option, it’s important to understand that the core issue stems from how the Script Manager rewires certain parts of the page, which prevents proper execution of libraries like react-intl (used by Termly). Removing the Script Manager could break other functionalities on the site.
Question: Is there a workaround for this issue?
Answer: Unfortunately, there is no current workaround that completely resolves this issue without removing the Script Manager. The conflict happens deep within the third-party library (react-intl) that Termly relies on for rendering. By the time react-intl tries to load, ASP.Net Script Manager has already interfered, causing the hyperlinks to display as raw code.
A possible, though not ideal, approach could involve marking the interfering script as non-essential to block it temporarily, but this would likely result in other issues on the website. This solution is not recommended as it may cause your website to break further.