Text Component and Internal Link issue

[VictorToledo_]

Hi all,

I have a strange issue with the text component (core/wcm/components/text/v1/text) and a link to an internal page. When I add a link to the internal content, the host name is added to the link and saved in the repository, obviously causing a problem when publishing the page, since the link points to the author.

i'm working with AEM 6.3.0.0, fresh instance (i started the server on port 4505) and We.Retail site

Let me try to explain you the issue with some pics

Then i'm trying to add a text with hyperlink to internal content

In the image you can see the internal path is correct without hostname

But when i apply the changes and debug the code

the variable url has the correct value but the when the code save the attributes and get the href value from the child node the hostname is added

And that is the value that is saved to the repository as you can see in the next image

And then when i published that page, obviously the link is pointing to author. So i dont know the why text component (or jquery, or javascipt) is adding the hostname to the url.

Now, if I update the value of the existing link, everything works fine because another javascript flow is executed

any help will be welcome

Thanks in advance

[Jaideep_Brar]

Tried using we-retail Text component and it does not add the hostname:

Have you customized the component? If not, try comparing linkchecker/sling mapping configuration.

[VictorToledo_]

Hi JaideepBrar, i'm using a new installation of aem 6.3 I've not changed nothing

[smacdonald2008]

I will test this too

[VictorToledo_ · Accepted solution]

Hi all, i found the issue and the solution,

I was testing in aem 6.3.3 and the problem does not occur.

Then, I realized that the problem was in 6.3, comparing the js I see that it has been solved sometime between 6.3 and 6.3.3.

AEM 6.3.0.0

AEM 6.3.3.0

So the solution is to update the instance.

Thanks to all

[smacdonald2008]

Thxs for posting the solution!

[hanishb17637780]

Indeed!

Just to be clear, This issue was fixed in 6.3.0.1. So, an AEM instance upgraded to any CFP/SP would see this issue resolved.