This is the Sitecore structure for wildcard item (*)
- sitecore
- content
- Site name
- Home
- Blogs
- *
- Blogs
- Globals
- Blogs Folder
- Year
- Month
- Blog Article 1
- Blog Article 2
- Blogs Folder
- Home
- Site name
- content
So according to this structure, we have #Wildcard Item(*) under the home node. It is like Blog detail page that is under Blog landing page.
First I have added new configuration file (z.wildcard.config) with the following configurations
- created httpRequestBegin processor as a batch to be executed after Item Resolver to Call Wildcard processor
- Sitecore 8.1 observed the following issues
- 1. Wildcard items no longer work
- 2. Presentation for cloned items not found
Solution:
If you are using MVC with Sitecore 8.1 then add <mvc.getPageItem> after our processor to avoid any route conflict
The last point is to add settings to disable ItemResolving.FindBestMatch because it's enabled in Sitecore 8.1 which may cause wildcard redirect issues
- Add class WildCardItemResolver which include the processor to resolve wildcard
Hi, I am unable to find GetWildCardPageItemProcessor processor in this blog. Please help on same if there is any other blog post. Also i want to understand how are you cloning presentation to resolved items.
ReplyDeletePlease help and suggest.
Hi,
DeleteThank you for letting me know,I just added GetWildCardPageItemProcessor class, hope it is helpful now.
Thanks for helping out :)
DeleteCloning is acheived as soon as he returns "return Context.Item;" from the pageItem pipeline , the next processor has that info in the "args". As we know in Sitecore the data in pipeline args is transferred from processor to processor. Correct me if I my understanding is incorrect @Hanin
Delete