Hi all,
Currently we're facing an issue where our page alias urls are 404ing and unable to redirect to the actual page. We've noticed that when we change the alias values and republish, we are able to properly redirect to the correct alias url. We are able to see the alias working in our author instances.
When checking crx/de, we do see the alias value within the resource properties. Any help or insight would be much appreciated. Thank you.
Solved! Go to Solution.
Views
Replies
Total Likes
In addition to what @h_kataria already stated , please ensure you avoid using duplicate alias values.
Offcourse additional screenshots and examples will be helpful in identifying the underline issue.
Since you mentioned that when you changed the alias value and republished it is working fine, it suggests that alias functionality is working fine but probably the value itself might be missing before that.
Can you cross check once if the sling:alias values are actually present on the pages in publish environment which you are trying to test.
Also, if you can give some examples or screenshots, it will be more helpful.
In addition to what @h_kataria already stated , please ensure you avoid using duplicate alias values.
Offcourse additional screenshots and examples will be helpful in identifying the underline issue.
Hi @h_kataria, after looking into it a bit more I did notice something when looking at the publish instance.
while the actual alias is within this page here:
So it does seem that this is due to the duplicate alias being used
Views
Replies
Total Likes
After checking out more of the broken alias links, I'm noticing the duplicate alias issue is not found for these specific links. These pages have only the specific alias but after unpublishing / republishing, it seems to be working. Wondering if there is a deeper cause that could possibly affect this codewise.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies