Weird position behaviour about closuretable HOT 5 CLOSED

Oh, that's really weird. Sorry but I'm busy at the time. You can make a pull request with a fix if you wanna help ;)

from closuretable.

Hello @maknz,

Could you please be a bit more precise and specify exactly the operation(s) you do when you say

Now I want to move that most recent tag out to be a root node.

With that I should be able to look into it.

Thanks!

from closuretable.

So given node with ID 10 is a child of 9 as shown in the second snippet, perform a Node::find(10)->makeRoot(0); The position is specified as 0 since there's no other preferable position for it. I would have been fine with omitting it and the library placing it at the end automatically as a default, but 0 should be just as useful. Plus, positions aren't awfully helpful at the root level, since certain users have access to certain root (and child) nodes, and not others -- and position is relative to all roots, not the roots the user owns).

from closuretable.

Hey @maknz,

Would you mind retesting with dev-master (I have done some bug fixes related to position) and let me know if you still have a similar issue?

from closuretable.

@maknz, any news?

from closuretable.