Closed jobee closed 3 years ago
Hey @jobee,
we just started using workspaces in the project we developed that package for and stumbled over the same issues.
Additionally to the problems you described, you currently cannot publish workspace to live if you are not an administrator.
Sadly, I did not find a way to prevent changes to workspaces only if the target does not match, as the privilege matcher does not know which target is selected. I guess A good way would be to show changes to internal / private workspaces as warning in the UI and don't prevent further editing.
The feature this package provides works great with no additional private or internal workspaces in place.
Editing workflows:
Editors publish changes to additional workspaces frequently to share them with the team before publishing to Live. Such workflow is pretty common, I guess. Editing a page in private/internal workspaces twice before publishing to Live is currently not possible (without granting the privileges
EditNodeWithChangesInOtherWorkspaces
andEditNodePropertiesWithChangesInOtherWorkspaces
).I'd suggest the following defaults: