While viewing a container, let's call it 'container A', if you click the 'add child container' option you expect the child container to automatically have the parent set to 'container A', as it once happened and as it still happens when you click 'add child category'. This instead doesn't happen anymore: when you click the 'add child container' option, the Parent option isn't automatically set, and defaults to 'Root' instead.

If you don't set it manually to the container A you wanted, you get 'Root' as the parent, and thus all the hierarchy becomes broken.

This is misleading: the behavior should be the same as in the 'add child category' option, where the parent is already set to the container where you originally clicked the link.

Comments

JirkaRybka’s picture

Status: Active » Closed (duplicate)

Let's call this a duplicate of #68132: Child container not created under correct parent, which have more discussion. Otherwise, I believe this bug is long fixed (I tested), so both issues need to be closed now.