Vanity URL not displaying in Site Navigation | Community
Skip to main content
Level 3
September 14, 2023

Vanity URL not displaying in Site Navigation

  • September 14, 2023
  • 3 replies
  • 847 views

Hi Team,

 

We have one page lets say /content/mysite/device-hub.  Using Basic Tab, we have given vanity URL for device-hub page as "phone". It means both /content/mysite/phone and /content/mysite/device-hub points to same page which is correct.

 

Issue:

 

In Main navigation, we have added one Menu item "devices" and it should redirect to same above page. but when we ho-over on this "devices" link, it shows us main page url i.e. "/content/mysite/device-hub"  

..

Is there any way that on ho-over or on clicking that meny item, we open/see page using vanity url "/content/mysite/phone"

 

 

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

3 replies

EstebanBustamante
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
September 14, 2023

You need to use the Resource Mapper to achieve such behavior. Below, you can find excellent articles with examples explaining how to use it, and once you configure the mapping you can verify this is working as expected using this URLhttps://<*host*>:<*port*>/system/console/jcrresolver:

 

Hope this helps


https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/deploying/resource-mapping.html?lang=en

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

Esteban Bustamante
Level 3
September 14, 2023

Hi,

 

Thank you very much for your kind reply.

 

May Be I was not clear in my problem statement. I am pretty much aware of resolve resolver, ETC mapping, link Transformer etc. and we are using all these in our project.

 

There is a Page A, I have added vanity URL as B.html for this page.. when I select page A anywhere in my Page as a LINK CTA, I should be able to URL as /B.html, not A.html.

aanchal-sikka
Community Advisor
Community Advisor
September 14, 2023

Hello @arvindpandey 

 

It seems the fix was added as part of https://github.com/adobe/aem-core-wcm-components/issues/559

 

Can you possibly check the version of wcm-core-components being used in the project? 

 

Aanchal Sikka
kautuk_sahni
Community Manager
Community Manager
September 18, 2023

@aanchal-sikka Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

Kautuk Sahni