Workspace/Publishing improvements #4726
Comments
bwaidelich
added a commit
that referenced
this issue
Jun 17, 2024
Introduces `WorkspacePublishingService` as replacement for the current Neos `Workspace` "active record" model. Introduces `WorkspaceService` as central authority to manage Neos workspaces. Related: #4726
bwaidelich
added a commit
that referenced
this issue
Aug 2, 2024
Extracted from #5146 this just improves stability of the `WorkspaceName` value object by - Restricting the allowed value range to 30 lower case characters and properly enforce it - Adding a `tryFromString()` constructor - Exposing the `MAX_LENGTH` and use that for the corresponding database schemas - 100% test coverage Related: #4726
bwaidelich
added a commit
that referenced
this issue
Aug 2, 2024
Adds a `getContentRepositoryIds()` getter to the `ContentRepositoryRegistry` that allows to iterate over all configured content repositories. This will be useful for enforcing ACL, cross-CR-linking, etc.. Related: #4726
bwaidelich
added a commit
that referenced
this issue
Oct 10, 2024
Adds behat tests that document the current behavior of `WorkspaceService::createPersonalWorkspaceForUserIfMissing()` and `WorkspaceService::getWorkspacePermissionsForUser()` Related: #4726
bwaidelich
added a commit
that referenced
this issue
Oct 11, 2024
…e creation With #5146 a basic workspace access control was implemented. With that, users won't have access to workspaces unless they have a role assigned. This can be achieved via ```shell ./flow workspace:assignrole ``` This bugfix makes sure, that the default behavior (users with the role `Neos.Neos:LivePublisher` can collaborate on the `live` workspace) is automatically ensured when creating/importing a site. Furthermore, the migration command has been fixed to add metadata & role assignments even if no workspace title was set: ```shell ./flow migrateevents:migrateWorkspaceMetadataToWorkspaceService ``` Related: #4726
bwaidelich
added a commit
that referenced
this issue
Oct 15, 2024
This change makes sure that metadata exists for the `live` workspace after running the `cr:import` command. Furthermore it fixes the permission determiniation for administrators in case no metadata is specified for a workspace but the role assignment exists Related: #4726
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Epic for issues related to the UX with workspace handling and publishing
WorkspaceNameinstead ofContentStreamIdin commands (Refer toWorkspaceNameinstead ofContentStreamIdin commands #4694)nullif first login to the site happens via "/neos/switch/to/..." #4401)./flow structureadjustments:fixdoesn't mark workspaces as outdated #4508)The text was updated successfully, but these errors were encountered: