Hey!I'm running into an issue where when I publish a top level category, it updates the UriSegment table for each language, to have different random encoded values on the end.
We are currently in the process of QAing an upgrade of commerce from 9.11 to 10.10.1. Any ideas as to what might cause something like this?
Edit: This was fixed in Commerce 11.1.1 (see Quan's post below)
I recall something like this (unsure if it was CMS hierarchy or commerce, but..), do you have the "Optics" somewhere else in the commerce hierarchy? Even though it might be at another level they perhaps are globally unique.
There was a bug that requires the UriSegment for node to be unique globally, therefore when you save a node and the system finds that you have another UriSegment with same value (even if that is in another category and should not conflict with this one), it will try to add some random values to make UriSegment unique. That bug (COM-4964) was fixed in Commerce 11.1.1
Hey Quan,Thanks for answering this question. I'll update our project to 11.1.1 and see what happens.
We've also seen extremly poor performance when publishing. Sometimes it take up to a minute to publish. Could this be related to the same bug?
Also, I read the bug notes on this. This almost makes it sound like the bug here is that the catalog UI allows you to have non-unique urisegments, not that it appends the alpha codes.
When we do this update, are we still going to be able to have duplicate urisegments?
We need duplicates because we have a /optics/ category, but also a /clearance/optics catagory.
I can't say for sure if it relates to that bug - you can always use some profiler (dotTrace, for example) to profile why it is slow and get back to us.
The bug fix actuallys lifts the restriction quite a lot, so yes, you will (be able to) have duplicate urisegments, as long as they are not in the same parent
ok, sounds good. Thanks!
Upgrading to Commerce 11.1.1 resolved this issue. Thanks!