AEM- custom links not displaying in the RTE / Custom links getting removed from the RTE | Community
Skip to main content
VeenaVikraman
Community Advisor
VeenaVikramanCommunity Advisor
Community Advisor
July 15, 2020
Question

AEM- custom links not displaying in the RTE / Custom links getting removed from the RTE

  • July 15, 2020
  • 1 reply
  • 1027 views

Hi All

 

   This is a follow up question from https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-how-to-make-href-to-accept-custom-tel-tags/qaq-p/365742 

 

I am trying to add a link to href in RTE with below format. ( this link will be processed by another system and AEM only serves the content via page )

 

format :- tel:${someproperty['value']}  

 

I could get the value rendered by adding the  regex to /apps/cq/xssprotection/config.xml ( the steps I mentioned in the ticket )

But everytime I open the dialog for authoring something else, the href which I authored gets removed and hence I have to re-author this value , each time I open the dialog for editing anything. Do anyone have any idea how to allow this kind of special properties as links in RTE ?

 

Thanks

Veena

 

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    1 reply

    Shashi_Mulugu
    Community Advisor
    Shashi_MuluguCommunity Advisor
    Community Advisor
    July 16, 2020

    @veenavikraman Shashi again 😀

     

    Did you tried the approach of keeping RTE simple with tel:value in the link which will work OOTB and then converting tel:value with the format you are expecting like tel:${someproperty['value']} from backend either from sightly \${test} with escape sequence or using JSP for that piece.

      VeenaVikraman
      Community Advisor
      VeenaVikramanCommunity AdvisorAuthor
      Community Advisor
      July 17, 2020
      Nope @shashi_mulugu I cannot do it. Since RTE , I cannot handle it from backend as it won't be sure where the author places the tel:${someproperty['value']}
      Terms & ConditionsAccessibility statement

      Loading footer...