[6.x] Fix entry publish permission#13827
Merged
jasonvarga merged 5 commits intostatamic:6.xfrom Feb 6, 2026
Merged
Conversation
… entry, and use it in the controller.
jasonvarga
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes an issue where an author can publish collection entries without having the
Manage publish statepermission set. It will also take care of theManage publish state of other authors' entriespermission.It will also show the toggle switch as grayed out and with a cursor-not-allowed CSS.
Can possibly be taken as a breaking change as the previous behaviour has been changed (user without manage publish state can no longer publish new content).
Let me know if I forgot something.
Changes (Before/after):
WITHOUT MANAGE PUBLISH STATE PERMISSION
REVISIONS DISABLED
Before: User can enable/disabled published state
After: User can not enable/disable published state, it will always be "unpublished"
Edge case: When the "Publish by default" toggle is activated on the collection, the user will still not be able to publish the entry, the permission takes priority over the configuration.
REVISIONS ENABLED
No changes.
WITH MANAGE PUBLISH STATE PERMISSION
REVISIONS DISABLED
No changes.
REVISIONS ENABLED
No changes.