Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Content Fragment Link field not bring transformed

Avatar

Level 2

Hi Team,

 

I have a Link field added to content fragment. When I give the link as /content/siteA/us/en/page.html, it is not being transformed to /page. Please provide suggestions on how to get the Link field to be resolved correctly.

Any help is highly appreciated.

 

Thanks

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hello @Silvia_Joyce_Balraj - 

 

In AEM, when you use a Link field in a Content Fragment, the links may not be automatically resolved to their shortened or friendly URLs.

 

To get the Link field to be resolved correctly, you may choose from following options : 

 

View solution in original post

4 Replies

Avatar

Community Advisor

I think you need to configure the Apache Sling Resource Resolver Factory. Please refer to this link in case you don't know how to use it: 

 

https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html 

https://blog.3sharecorp.com/shortening-urls-in-aem 



Esteban Bustamante

Avatar

Correct answer by
Community Advisor

Hello @Silvia_Joyce_Balraj - 

 

In AEM, when you use a Link field in a Content Fragment, the links may not be automatically resolved to their shortened or friendly URLs.

 

To get the Link field to be resolved correctly, you may choose from following options : 

 

Avatar

Community Advisor

hello @Silvia_Joyce_Balraj 

 

Is the link shortening working for all other links in the Site? If yes, please check with someone in the team, how it has been implemented for the ones working, and debug accordingly.

 

If the team is working on Link shortening for the first time, please refer to following link. It explain step-by-step whats needed.

https://helpx.adobe.com/in/experience-manager/kb/multi-domain-management-aem-mappings-for-url-shorte... 


Aanchal Sikka

Avatar

Level 3

Hi @Silvia_Joyce_Balraj

I am facing the same issue. Which approach listed by @Tanika02 solved the issue for you?

We re on AEM 6.5.16 on-prem.

--

Krass