-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Require 'List folder contents' permission to use the catalog vocabulary. #261
base: master
Are you sure you want to change the base?
Require 'List folder contents' permission to use the catalog vocabulary. #261
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This is more correct than the View permission.
177b435
to
3aa8f39
Compare
Let's see if Jenkins thinks this is a good idea too. @jenkins-plone-org please run jobs |
Sounds better suited, but it may break something in heavily customized sites. The usual restrictions of the |
I agree that
I am +0 on merging this one now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
But I just wonder if that is a breaking change. OK, for a breaking change the effect is probably too small, but I would mention the different widgets where this change has an effect in the changelog message.
The getVocabulary
seems to be used in:
- plone.app.content folder contents
- plone.app.querystring.
- related items widget (plone.app.z3cform.widgets.relateditems)
- link widget (plone.app.z3cform.widgets.link)
- ajax select widget (plone.app.z3cform.widgets.select)
- related items in TinyMCE (Products.CMFPlone.patterns.settings)
- TinyMCE link widget and related items widget
@mauritsvanrees what the status of this? This PR is somehow assigned to the Plone 6.1 project. Is this correct? Do we aim to include this in Plnoe 6.1? |
Theoretically this is better, and it gives some security hardening, but at the cost potentially breaking stuff. I am not pursuing this currently. I have reverted the PR to draft. |
This is more correct than the View permission.