This is resolved by creating a custom implementation of VanityURLServiceImpl from ACS Commons to extract the vanity path after the resourceResolver.map() is executed. This resolved the OOTB logic issue of ACS commons and the original vanity path issue as well.   The OOTB Dispatcher configuration bas...

Trying to implement Vanity URLs in my project. Tried both the dispatcher recommended vanity url approach and ACS commons vanity error mapping approach as well.    For dispatcher recommended vanity url approach - The vanity URL configs in dispatcher is not getting picked up properly since the rewrite...

Is this issue resolved. I am also facing the same issue where the vanity URL configured for a page is not working and dispatcher is trying to prefix it with the tree path like any other page.    Is there a way to escape the rewrite rules for the vanity URLs alone? 

Facing issue with the layout resizing for the components. When using the Drag-and drop functionality i.e. using the blue dots to define the position of the component in the responsive grid, the component is being dragged as well and the changes are not being saved. Not able to see the save tick butt...

Hi @Albin_Issac , Thanks for the reply and we have fixed in kind of similar ways now. Please find the dispatcher PT rewrite rule fix below,   # Rewrite image callsRewriteCond %{REQUEST_URI} !^/content/experience-fragmentsRewriteCond %{REQUEST_URI} !^/content/damRewriteCond %{REQUEST_URI} (.jpeg|.png...