"Name in URL" change fails on toplevel category

I our catalog the top level catagory seems to need to have unique “name in url” acros all catalogs. But all categories below the top level there is no problem with having the same “name in url”. We have multiple catalogs with similar catagories.

We are allowed to edit it to the same “name in url” and publish it, but when we edit that note again it just got a new –something added to the “name in url”. We don’t even get an error during publishing.

 

There is a video below of the problem:

https://www.screencast.com/t/2igoMGFlAQTk

 

This issue seems somewhat similar:

http://world.episerver.com/forum/developer-forum/EPiServer-Commerce/Thread-Container/2015/3/update-catalog-name-name-in-url-doesnt-change/

#181191 Aug 11, 2017 10:08
  • Member since: 2011

    Hi,

    We are aware of this issue, and it should be fixed in upcoming version of Commerce, probably 11.2

    Regards,

    #181192 Aug 11, 2017 10:32
  • Is this fix included in update 175?

    #181323 Aug 16, 2017 12:43
  • Member since: 2011

    It'll be in 11.1.1, which will be probably released next week.

    #181326 Aug 16, 2017 13:02
  • Member since: 2008

    @Morten which Commerce version is used in the video?

    #182434 Sep 19, 2017 9:18
  • Commerce version in video is 10.2.3

    #182438 Sep 19, 2017 9:59
  • Member since: 2008

    Thanks. I think the core issue here was addressed already in Commerce 10.4. The fix in 11.1.1 targets a slightly related issue when a category is moved to a new parent category where another subcategory already uses the same url segment.

    #182440 Sep 19, 2017 10:30
  • Hello,

    I am having a similar issue that was discovered in our testing.  We have just one catalog, and the top-level categories have the additional -randomcharacters added after the "Name in Url" when we try to save any edits.  All the top-level categories are unique, but there are sub-categories that share the same "Name in Url".

    This issue also started happening for us in EPiServer 10, with CMS version 10.9.1.0 and Commerce version 10.6.0, which should include the fix that was mentioned in this post.  We did not have this issue in EPiServer 9 with CMS version 9.12.3 and Commerce version 9.24.1.

    Did you have any luck with the fix in 10.4?

    Thank you

    #184877 Nov 06, 2017 19:15