Links to pages that use aliases are referencing incorrect domain inside Personalized container | Adobe Higher Education
Skip to main content
Level 2
March 26, 2021
質問

Links to pages that use aliases are referencing incorrect domain inside Personalized container

  • March 26, 2021
  • 1 の返信
  • 1342 ビュー

Hi All,

 

We are facing an issue when their is a personalized container which have fixed list component configured inside it and it  has the list of pages selected.

Now out of them one page which is selected by the author have an alias configured on it.

Now when the component is rendered on the publish \ dispatcher URL the one which had alias show the incorrect domain and the other which doesn't have the alias points to correct domain.

 

This is happening when their is a combination of aliases and the personalisation container.

As a workaround we removed the alias from the page but any help on how to resolve this issue will be appreciated.

 

Regards,

Shikha

 

 

このトピックへの返信は締め切られました。

1 の返信

Asutosh_Jena_
Community Advisor
Community Advisor
March 26, 2021

Hi @shikhasharma-1 

If I understand this issue correctly:

  1. You have multi domain websites configured on your instance.
  2. You have some personalization container (loaded via adobe target?) which has list of URLs configured on it along with alias.
  3. When the page is accessed via publish/dispatcher URL, the links are showing the correct URL(alias) with wrong domain name. i.e. let's say if you are expecting a link as www.something.com/abc/xyz you are getting it as www.something123.com/abc/xyz where www.something123.com is another domain within your system hosted website?
  4. You also have URL shortening enabled using etc/maps?
  5. If you use alias for other URLs where the content is not served using the personalization block is working perfectly fine?

Please let me know if I understood the issue correctly and then I might be able to help you.

 

Thanks!

March 26, 2021
Hi @asutosh_jena_, You have understood the problem correctly, only thing is we are using custom personalization logic where by making a direct call to the component using SlingRequestProcessor API to get the HTML and adding to the DOM. In this HTML, if there are any links to a page is getting mapped to a wrong domain. Can you please let us know if the links can be corrected in the component HTML response in publisher/dispatcher instance that we receive from this API call. We see the same issue from resource resolver utility on system console, when we try to map a resource path, is adding wrong domain. Thanks.