Open Benjamin-K opened 2 years ago
I also have an error without Dimension and Workspace Restrictions.
https://user-images.githubusercontent.com/1014126/201325464-527ea4bb-8821-4d5f-8c39-1dc89af88b96.mp4
Part of the problem will be solved when Issue neos/neos#3893 will be merged.
We have come across the same issue: Restricting the Workspace and subtrees does not seem to work (@markusguenther I think your issue is not related though, that looks more like an outdated session)
@skurfuerst can you think of a solution without AOP? We rely on this in a project and I think that there are funds available for commissioning a fix
I think the issue needs to be fixed in the Core. IMO the current implementation of the isInWorkspace
privilege matcher makes little to no sense. It will only apply if the current user or any other user already made some changes in the current workspace. But it should actually only match, if the currently selected workspace of the user is in one of the defined workspaces.
Which again leads us to neos/neos#3893. We can also discuss this issue there and i can also create a PR, but i waited for some more responses as changing the existing isInWorkspace
implementation would be breaking.
@Benjamin-K Thanks for your input. Yes, let's discuss the issue in https://github.com/neos/neos-development-collection/issues/3893 <3
Setup
Create a role with the following settings:
Behaviour
When removing the workspace restriction, all works out pretty well.