@s4nt0s, could u run a suggestion by sven next time u chat with him? its about tiers and the project (group) tree structure, when u set up a project to be a lower tier of 'multiple' higher projects, it pops the project out of the group projects tree.
this might be done on purpose as technically u could run a project as a lower tier to
multiple projects in
multiple different groups (i wouldnt think that is common), however perhaps SER could do a check and if the project is actually a lower tier to multiple projects in the
same group, it would be much nicer and easier to find if it was placed under the actual higher tier projects, in the actual group, like other tiers are.
example of my idea:
Code:
group
|_tier1
|_tier2 directories..
|_tier2 web2.0..
[COLOR=#ff0000][B]|___tier3 <----[/B][/COLOR]
unlike creating a tier3 for each tier2 like for example:
Code:
group
|_tier1
|_tier2 directories...
|_tier3
|_tier2 web2.0...
|_tier3
or the way it is now (confusing) with multiple higher tiers:
Code:
[COLOR=#ff0000][B]group1**
|_group 1 tier1
|_group 1 tier2 directories
|_group 1 tier2 web2.0[/B]
[/COLOR]another group
|_tier1
|_tier2
|_tier3
yet another group
|_tier1
|_tier2
[COLOR=#ff0000][B]|_group 1 tier3** (with multiple higher tiers from all the way up in group 1[/B])[/COLOR]
not a high priority of course, just a usability request
