In content.ini there is a section with the following settings:
[NodeSettings]
# The node ID of the normal content tree
RootNode=2
# The node ID of the user tree
UserRootNode=5
# The node ID for the media tree
MediaRootNode=43
# The node ID for the setup tree
SetupRootNode=48
# The node ID for the design tree DesignRootNode=58
So, I think, you might need to add a similiar line for the new branch.
Yes, I know about adding a custom tab in the Admin interface using menu.ini.
What I wanted to know was, how to move the new custom node to the top level (along with Content, Media, User etc.). Sorry, if that didn't come through in my last post.
I actually found a solution: http://ez.ryba.eu/index.php/ez_publish/lab/custom_top_level_nodes_is_that_possible_round_i_exploration
but, I am curious if anybody know a less 'crude' way of doing it (not involving direct sql-management).
<i>> I actually found a solution: > http://ez.ryba.eu/index.php/ez_pu...is_that_possible_round_i_exploration</i>
Glad you find that useful. Just remember - this solution has not been challenged, yet. I'm not sure how safe it is... looking for free time to get it further, but who knows when that comes... ;)