TYPO3 Core

I've seen this as a feature. In some big TYPO3-installations with a lot of sites I can so set another DB mount for a site branch I often use. So I don't have to (find and) go to this branch which may is some site levels under the site root.

+1

IMO this is not a bug and the integrator has full control over the
configuration of webmounts.

No need to change the default behaviour of showing each db mounts the user has access to, despite if one is inside another, I was looking for a way to change that default behavior for some db mounts either by a checkbox on the record or through typoscript.

I understand the typical usage scenario is to create a db mount for every website root pages in a multisite envrionnement... In my scenario, I have editors that have access to multiple sites within a single instance of TYPO3; they help out other editors that only have access to their domains. Every domains also have different and access-limited groups for managing parts of the website (news, events, publications etc.

In my setup, to ensure everyone has access to what they should have, groups are divided in subgroups for what they can use, and other groups for where they can edit. Everything works well, but it's confusing for some editors to see the same pages/folders outside their main treeview, sometime more than twice, so I was looking for a «simple» way to hide those db mounts that are already included by another db mount. I understand I could refine and add more groups, but it's already complicated for some admins to manage and understand 20+ groups, with the default acl for the access module.

Hi Jean,

I would vote to change this into a feature request with an option to change the behavior. Do you agree?

Yes, go ahead with a feature request. I suppose this kind of change can break other existing websites and it would be better to have some page tsconfig to enable this feature instead.