#32545Show only recipients which are responsible for this page/mount
Description
If you have a TYPO3 extension with one workspace but a lot of seperate websites, you have the following problem.
As soon as a user sends a change to the next stage, it will get all responsible users for this stage as suggested recipients for the notification mail. In such a big TYPO3 installation this may be a lot of users.
Now it would be nice if workspaces extension would check the responsible users and only suggest these users which are allowed to see this changed element/page/mount. We developed a proof-of-concept solution, which is not nice and core-like developed but works. Maybe it is a basis to discuss and develop a clean/nice solution.
Further we developed a extEMConf option stageChangeHideMatch where it is possible to insert a preg_match which usernames should not be shown as suggested recipients in the stage change popup.
I attached the modified t3x of the workspaces extension with a tested solution. I know that it is not nice to just attach the t3x and do not create patches. I am very sorry but I have no time this week to create these patches, but I will do this later.
Nevertheless some feedback if you like these features in general would be nice.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 1
Files 1
History 10
-
Sonja Schubert changed attached T3X_workspaces-994_5_1-z-201112141551.t3x 12/14/11, 15:53
-
Sonja Schubert changed
T3X_workspaces-894_5_1-z-201112141530.t3x12/14/11, 15:53 -
Tolleiv Nietsch commented and changed status
NewAccepted assigned to Tolleiv Nietsch 01/27/12, 21:26 -
Michael Stucki changed category 12/10/13, 01:04
-
Michael Stucki changed project id category 12/10/13, 01:06
-
Mathias Schreiber changed target version 01/23/15, 11:33
-
Benni Mack changed target version 09/24/15, 12:09
-
Benni Mack changed target version 10/06/15, 22:41
-
Christian Kuhn changed Related to #32547 06/17/25, 16:03
-
Christian Kuhn commented and changed status
AcceptedClosed 06/17/25, 16:06Hey.
Similar to #32547, I hope it is ok to close here for now for similar reasons: Nobody worked on this for a very long time, I think extensions could implement this on different levels, and it should be possible to configure this using different sys_workspace records. Lets create a fresh issue in case this should still be implemented and someone is actively willing to pick it up.
Also very nice … I’ll try to extract the patch for you