checkout cm:folder - bug?

[tgmweb]

I have a custom content model, one type of which extends cm:folder.

Now, when I checkout the object of said type, and then check it back in again (all of which BTW are done via the javascript API), all the parent/child relationships are lost
until I do a bodge, which I'll explain in a minute.

Let me explain:
Root
> Folder1
> >  Folder2
> >  Folder3

If I checkout Folder1 - and then check it back in again (or cancel the checkout), Folder2 and Folder3 are viewable in the nodebrowser as children, but not available via search. So a search for cm:name: "Folder 2" produces no results - and PATH:…./cm:Root//* only returns one result (Folder1).

Now, if I MOVE folder2 to it's parent folder, ie:

Root
> Folder1
> > Folder3
> Folder2

and then move folder 2 back again to where it was before, suddenly everything springs back into life?!?!

Is this a bug - it looks like it. I'm aware that I guess folders shouldn't be checked out - but it would be good if there was a way to resolve this without me having to modify the tree temporarily, which is pretty bodge-like!

[openpj]

Invoking a checkout on a type that extends cm:folder it seems wrong to me.
I never tried a similar configuration, but I think that you don't need to do this.

A checkout, in my opinion, could have sense only when invoked on a type that extends cm:content, I think that this is the correct scenario.

Hope this helps.