Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Contributor and Editor to Access inactive portal content #4042

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

MrTango
Copy link
Contributor

@MrTango MrTango commented Nov 4, 2024

fixes #3571
This should be safe to do, as Editor and Contributor have the View permission anyway.

@mister-roboto
Copy link

@MrTango thanks for creating this Pull Request and helping to improve Plone!

TL;DR: Finish pushing changes, pass all other checks, then paste a comment:

@jenkins-plone-org please run jobs

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.

Happy hacking!

@MrTango MrTango force-pushed the fix-rolemap-access-inactive-portal-content branch from cd61ca6 to 6fd2a97 Compare November 4, 2024 18:16
@MrTango
Copy link
Contributor Author

MrTango commented Nov 4, 2024

@jenkins-plone-org please run jobs

@MrTango
Copy link
Contributor Author

MrTango commented Nov 4, 2024

@mauritsvanrees this needs an upgrade step to load the rolemap, where in plone.app.upgrade should this be added?

@davisagli
Copy link
Member

this needs an upgrade step to load the rolemap

This is a policy decision we can make. Do we want to force everyone that upgrades to get the new rolemapping for this permission, or do we want to leave it alone for existing sites where it may have been customized?

@MrTango
Copy link
Contributor Author

MrTango commented Nov 5, 2024

I would argue that the new behavior is the better one. Right now only administrators can really work with content which have effective date in the future. For me that's a bug, which needs to be corrected. We also should back port this at least to Plone 6.0.

@davisagli
Copy link
Member

I would argue that the new behavior is the better one.

I agree it's a better default. If an admin customized the permissions to give this permission to non-default roles, I'm not sure we should clobber that.

@petschki
Copy link
Member

petschki commented Nov 6, 2024

@jenkins-plone-org please run jobs

@petschki petschki force-pushed the fix-rolemap-access-inactive-portal-content branch from 6fd2a97 to 02b0c60 Compare November 6, 2024 15:56
@petschki
Copy link
Member

petschki commented Nov 7, 2024

@petschki petschki force-pushed the fix-rolemap-access-inactive-portal-content branch from 02b0c60 to 01dc8f9 Compare November 7, 2024 14:27
@MrTango
Copy link
Contributor Author

MrTango commented Nov 8, 2024

@jenkins-plone-org please run jobs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Published object with effective date in the future is not shown in folder_contents view
4 participants