I know it sounds weird and generally none is expected to do it that way, but it is not the desired behavior IMO :)

 

I had a structure like this:

- Category 1

- Category 2

- Category 3

 

I selected Category 1 and Category 3 and moved them both being sub-categories of Category 2. I expected to have the following structure:

- Category 2

- Category 1

- Category 3

 

In fact in the database it was like that, with the exception that Category 2 had Category 1 as a parent and therefore no category was displayed in the backend :)

Since the category Id's in the table control the subcategory scheme, i think it would be circular if you did not choose category two and make it a top level or subcategory of something else first!

That's exactly what I am saying :)

The question is, that this either should not be allowed or not the expected behavior ;)
William White said:

Since the category Id's in the table control the subcategory scheme, i think it would be circular if you did not choose category two and make it a top level or subcategory of something else first!

Then we are in agreement! If we throw that at excel or open office spreadsheet we get an error....mabee they will add error checking to the pick category pull down in the future....Not simple though as multiple test would need to be run, because we may not be moving it to a top level.