Igor Starikov

> It seems the tree itself is recreated anew every time I re-sync. Yes. That's how it works. > Adding a new item to the tree in the admin interface...

So at last I have had a chance to check this issue using demo project — https://github.com/idlesign/django-sitetree/tree/master/demo — and that's what I see after syncing:  Please try the demo...

In the docs that's called `attaching` in dynamic trees, but not `hooking`. See in https://django-sitetree.readthedocs.io/en/latest/apps.html#dynamic-sitetree-structuring ``` compose_dynamic_tree('books', target_tree_alias='main', parent_tree_item_alias='for_books'), ``` Here in `parent_tree_item_alias` is the alias of an item (node)...

Hi, Yeah, that's quite a bunch of changes %) Sounds interesting. Yet nowadays I have a limited time to dedicate to github, so it might take some time to digest....

I'm almost positive about `as` and `include_parent`, the other three need further consideration. I feel especially uneasy about comma-separated fields. I'd also like to ask you to make put those...

There some methods indeed. Please refer to #120, #97, #91, #64, #47.

Thank you. There are still things to improve though. Contributors will be happy to read that, so I'll keep this issue open for some time.

Thank you for the report. This was a compatibility shim — reported in #201, addressed in #204 Right now I can't remember why there is no bypass for breadcrumbs, so...

It seems we need some tests to check breadcrumbs in conjunction with dropdowns (e.g. TreeItemChoiceField). After that it'll probably be safe to bypass admin check for breadrumbs. Tests and pull...

Do you mean fluid layout? If so this should be achieved with css, sitetree by itself has a very little to do with it. You'll probably need to make a...