Expand my Community achievements bar.

SOLVED

Page navigation links on publisher are not having /content/sitename prepended

Avatar

Level 4

Hi members,

Environment AEM6.5.8

Server: Linux

We are running into one issue with site package on AEM 6.5.8 Publisher server where site is created, added multiple pages under it. they are residing under

/content/aemportal/search.html, /content/aemportal/listing.html etc

The pages are working fine on Author Instance and getting desied results as expected but when we are publishing to Publisher server then we are experiencing the pages are not giving full path in url when navigating between pages or during form submit for search

Pages do exist at required path as in Author

but urls are getting created like localhost:4503/seach.html instead of localhost:4503/content/aemportal/search.html

 

We have checked page properties but neither we have ALIAS set nor we are using vanity urls.

 

 

Any advice or session will be helpful from you to debug.

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @manu-gupta 

  Please check you resource resolver properties on publish <org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl>   or check /etc/map/http

 

May be you have added resource mapping for /content/aemportal

 

Thanks

DIpti

View solution in original post

4 Replies

Avatar

Level 10

hi @manu-gupta ,

 

Could you please check if there is any change done in Apache sling resource resolver factory (org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl) OSGI config of publisher run mode.

Avatar

Community Advisor

Hi @manu-gupta 

 

Please check if you have defined any resource reolver mapping for publish runmode with the property as "/content/aemportal/:/" in org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl configuration.

or

if you have defined any sling mappings in /etc/maps for your publish instance.

 

You will have more info here:

https://techforum.medium.com/configure-sling-mapping-for-resource-resolution-in-adobe-experience-man...

 

Hope this helps!

Thanks

Avatar

Correct answer by
Community Advisor

Hi @manu-gupta 

  Please check you resource resolver properties on publish <org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl>   or check /etc/map/http

 

May be you have added resource mapping for /content/aemportal

 

Thanks

DIpti

Avatar

Level 4

thanks all everyone was right it was vanity url was still holding value within JcrResourceResolverFactoryImpl configuration despite I had removed vanity urls from all page properties.

 

Appreciate your guidance and help.

 

Manu