TYPO3 Core

It seems, that if you have a root page assigned, the error occurs. If you assign a page inside a page root, everything works fine. But we have groups for multiple root pages. So I don't know, what to do.

Hi Robert
Thanks for the report.
Can you explain the "that if you have a root page assigned, "?
Are you saying you have root page (the one with TYPO3 logo, uid=0) assigned to the user group?
Can you attach a screenshot from group configuration? And what is stored in the db for fields be_users.db_mountpoints and be_groups.db_mountpoints ?

AFAIK it's possible to select root page (uid=0) as a db mount for editor or editor group.

I can confirm there is a Problem.

I did not see the red error message myself but it was reported to me.

But the real Problem here is, that my Editors, which are in multiple groups that inherit various DB-mounts, only see their page tree last mount point (i.e. the one that gets added last) in the page tree. As if the mount points are not added to the list but replace the list:

• Group A (DB mount A)
• Group B (DB mount B)
• ...
• Group K (DB mount K)
• MasterGroup (inheriting Group A-K, DB mount L, DB mount M, DB mount N)

None of the mount point pages have is_siteroot set, they are sub pages of a sub site.
One of the mount points is a sys folder ... let's call it "DB mount J" in the example so it's smack in the middle of the List

Only DB mount N is showing up in the page tree for members if the MasterGroup

For Admins everything looks fine.

In 9.5.15 the Editors in the MasterGroup can see DB mount A-N

Hi
I'm investigating the topic.
I managed to reproduce the issue with red error when user did not have access to the page listed as db mount.
Can you please check if this is also the case in your installation?

Another issue I see, which is really a bug is that when the mounted page is under not accessible page it will not be shown.

I have pushed a POC patch. Please check if it solves the issue for you.

The same Problem exist also in TYPO3 10 since 10.4.0. as i wrote in the duplicated Issue.

The Related Patch set 1 works for us on TYPO3 9.5.16 and 10.4.1. Thanks!

Patch seems to fix the issue, thanks

My guess would be this was caused by https://forge.typo3.org/issues/90880 ?

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64346

@Robert Lemke
Are you sure the arrow has changed between 9.5.15 and 9.5.16?
I've just tested it in 9.5.15 and I see the same arrows and in the same places as in 9.5.16

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64346

Hi Tymoteusz,

I'm sorry. I forgot to tell you, that it was a cache issue on my part.

Currently we have to use 9.5.13, because of two bugs regarding multisite setups. One is solved yet. ;-)

Thank you for your effort!

Kind regards

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64346

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64346

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64346

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64346

Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64346

Patch set 1 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64639