Project

General

Profile

Actions

Bug #91594

closed

Double page tree when be user editor access a single branch of the workspace

Added by Danilo Caccialanza over 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Workspaces
Start date:
2020-06-05
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
medium
Is Regression:
Sprint Focus:

Description

When there are multiple editor accessing a single page tree, advanced editors see the tree in duplicate

See attached pdf for detail and the patch for inspiration.


Files

Double page tree into workspace.pdf (277 KB) Double page tree into workspace.pdf Danilo Caccialanza, 2020-06-05 09:57
patch.txt (2.79 KB) patch.txt Danilo Caccialanza, 2020-06-05 09:57

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #91918: Access to a sub-branch of a workspace for a “limited user”Closed2020-08-03

Actions
Actions #1

Updated by Christoph Lehmann over 4 years ago

In the workspace you have 3 db mounts: root, a and b. I think you can remove a and b since they are children of root.

Does it work for you?

Actions #2

Updated by Danilo Caccialanza over 4 years ago

Dear Christoph, thank you for your interest.

Your proposal solves the "editor-advanced" user problem, but in this way the "editor-simple-a" and "editor-simple-b" in the DRAFT workspace no longer see any trees!

The "editor-simple-a" and "editor-simple-b" provide access to a smaller part of the tree mounted on the workspace.

Actions #3

Updated by Danilo Caccialanza over 4 years ago

  • Related to Bug #91918: Access to a sub-branch of a workspace for a “limited user” added
Actions #4

Updated by Danilo Caccialanza over 4 years ago

  • Related to Bug #91918: Access to a sub-branch of a workspace for a “limited user” added
Actions #5

Updated by Danilo Caccialanza over 4 years ago

  • Related to deleted (Bug #91918: Access to a sub-branch of a workspace for a “limited user”)
Actions #6

Updated by Gerrit Code Review about 4 years ago

  • Status changed from New to Under Review

Patch set 1 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/+/65755

Actions #7

Updated by Gerrit Code Review about 4 years ago

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/+/65755

Actions #8

Updated by Gerrit Code Review about 4 years ago

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/+/65755

Actions #9

Updated by Gerrit Code Review about 4 years ago

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/+/65755

Actions #10

Updated by Gerrit Code Review about 4 years ago

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/+/65755

Actions #11

Updated by Gerrit Code Review about 4 years ago

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/+/65755

Actions #12

Updated by Gerrit Code Review about 4 years ago

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/+/65755

Actions #13

Updated by Gerrit Code Review about 4 years ago

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/+/66206

Actions #14

Updated by Danilo Caccialanza about 4 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #15

Updated by Benni Mack almost 4 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF