I recently came across an interesting routing issue in SitecoreAI where enabling useDisplayName started generating much cleaner URLs, but those URLs were returning 404 in the rendering host. The interesting part was that the same pages worked perfectly when accessed using their original item-name based URLs. The Requirement The team I was helping had category pages with URLs like: https://testing.mysite.com/Products/1341592/1342427/1342434 These URLs are technically valid, but they aren't particularly user-friendly. The preferred URL was something like: https://testing.mysite.com/Products/category1 display name/category2 display name /category3 display name In Sitecore, this can be achieved by configuring the link provider to use the item's display name when generating URLs. The Configuration Change We deployed the following Sitecore configuration patch in the staging environment: <?xml version="1.0" encoding="utf-8"?> <confi...
Welcome to Sitecore Docs Blog! This blog shares expert tips, best practices, and innovative solutions for your Sitecore application. This blog aims to offer in-depth tutorials, insightful articles, and practical advice to help you master Sitecore’s powerful features. From optimizing performance to crafting custom solutions, this blog can help you to empower your Sitecore journey with the knowledge and tools. Happy reading!