Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

AEM 6.5: HTL @ extension = 'html' doesn't work for external links

Avatar

Level 2

${ link @ extension = 'html' } if link is https://www.google.com/resources then the output is https://www.google.com/resources.html. This is not the expected behavior according to the documentation. Any help is appreciated. Thanks, Nikunj Jariwala

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

If you want to remove the extension, you can use something like below:

${'https://www.google.com/resources' @  extension}

View solution in original post

4 Replies

Avatar

Employee Advisor

As per my understanding and the sly documentation at [1], @Extension will add the extension to the path. So, this is working as expected.

URL manipulation

Adds the html extension to a path.

<a href="${item.path @ extension = 'html'}">${item.name}</a>

Adds the html extension and a selector to a path.

<a href="${item.path @ extension = 'html', selectors='products'}">${item.name}</a>

I tried the following on my side:

  ${'https://www.google.com/resources' @  extension='html'}

The output is below:

Screen Shot 2019-09-17 at 8.52.23 PM.png

[1] HTL Block Statements

Avatar

Level 2

https://docs.adobe.com/content/help/en/experience-manager-htl/using/htl/block-statements.html#sly-el... The documentation on this page says "The @Extension works in all scenarios in AEM 6.3, before you could have a result like www.adobe.com.html and also checks whether to add or not add the extension." The use case is that we dont want to add html to external links. Is that something which cannot be solved using @ extension?

Avatar

Correct answer by
Employee Advisor

If you want to remove the extension, you can use something like below:

${'https://www.google.com/resources' @  extension}

Avatar

Employee

I do not think that HTL has such functionality to distinguish internal/external links. You will need to write something custom to handle case a use case. Take a look at this [1] to help you in creating this customization.

[1] https://wcm.io/handler/link/usage.html