Prevent content from being deleted when there is an active workspace

I moved the handling of initial revisions to 🐛 Creating an unpublished entity in a workspace does not set the workspace field on the revision Fixed , and this is the remaining part that needs to be done this issue. Postponing on 🐛 [PP-1] Prevent content from being deleted when there is an active workspace Postponed .

The blocker is in! Here's a reroll :)

Tested this one following the issue summary

Logged in as user with the ability to delete but not bypass access
Switched to stage workspace.
Verified the delete button is no there.
Tried to use bulk delete but got This form can only be submitted in the default workspace.
Created a page
Verified I can delete in that workspace

@smustgrave, thanks for reviewing! I also looked at this patch again and realized we lost the static cache that we had before #57, so now we're doing 1 db query per-entity on admin/content for example. I'll work on bringing it back.

Decided to reroll this patch against 📌 Add mechanism to have workspaces skip processing entity types Fixed because the new isEntityDeletable() method makes more sense in the context of the WorkspaceInformation service added there rather than adding it to WorkspaceAssociation. Leaving at NW for the static caching mentioned in #61.

The way we were altering the entity delete form in this patch doesn't work anymore since delete forms are now opened in a modal. Fixed that by using a service decorator for the entity form controller, and also increased test coverage to also cover the entity access alter.

#62 still applies, so leaving postponed and not bothering with a MR yet until the dependency gets fixed.

Added back the static cache in the workspace association service. Converting this patch to a MR next :)

amateescu → changed the visibility of the branch 11.x to hidden.

amateescu → changed the visibility of the branch 3092247-prevent-content-from to hidden.

Opened a new MR with the latest code against 11.x, the old one can be closed by someone who has access to do that.

Bunch of small stuff.

Fixed all threads in the MR.

Feedback appears to be addressed

Ran test-only feature and test coverage is present https://git.drupalcode.org/issue/drupal-3092247/-/jobs/1037544

Applying the MR
Created content in my main space
Switched to a new one and couldn't delete that first node.
But I was able to delete content I crreated in workspace B.

Issue summary seems clear about the changes being made.

This is looking really good, couldn't find anything to complain about. Committed/pushed to 11.x and 10.3.x, thanks!

Automatically closed - issue fixed for 2 weeks with no activity.