-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Two item names returning same content #1
Comments
HI. Sorry for late response. If you drop me your route item I can try to help you. |
HI, I have installed your module in my sitecore instance.It is multi site solution and we are using virtualFolder to resolve different site urls. For Example :
Site URLs: We are not able to resolve home item when we hit test.local/de or test.local/es. It is always resolving wildcard(*) Item.Let me know if you have any solution |
Hi. I don't think I will have time to look at the issue, you are welcome to fork the repo and debug. I must say I didn't test this module with Sitecore 9, not sure it works out of the box... |
I'm trying to figure out why this might be happening, and I'm hoping maybe I can get some help here. I've got the wildcard module installed, but for two particular items when I call the wildcard path, they return the same item. One is the real item, the other name actually does exist but comes back with the first item. This happens even in experience editor - if I go to the item through content editor and click the experience editor button, I get the right one because the ID is used, but if I manually enter the name, I get the wrong item.
I tried rebuilding the link database and master/web indexes to see if that would help, and it seemed to, but now the problem is reversed. It's only two specific items, but I found if I delete/rename the bad item and create a new item with the same name, it still happens. So it's like the names are locked together somehow.
I don't see anything in the logs around this, so I'm not sure why it might be happening. I'm assuming the issues are around this module, but that's based on circumstantial evidence, so if it's something else, I'm willing the be corrected. :) Thanks for any help!
The text was updated successfully, but these errors were encountered: