Disable role aquisition - Plone 5

AnanthaBalaji · December 21, 2018, 11:36am

Guys,
I have created a content type and I want to disable_role_aquisition in default wherever I add the content type. Can I do it without going to sharing tab.

zopyx · December 21, 2018, 12:34pm

Option: set __ac_local_roles_block__ = 1 as class variable in your code
Option: https://docs.plone.org/develop/plone.api/docs/api/content.html

plone.api.content.disable_roles_acquisition(obj=None)¶

which could be set inside an event subscriber

https://docs.plone.org/develop/addons/components/events.html

for zope.lifecycleevent.IObjectCreatedEvent

AnanthaBalaji · December 27, 2018, 1:47pm

Thanks, but you are telling for the particular object but I want to disable for the content type

zopyx · December 27, 2018, 1:52pm

Again, take your time for reading and understand my answers.

Option 1 allows you to set the property on the class which is obviously what you are asking for and that is what I clearly mentioned. What is unclear here?

AnanthaBalaji · December 27, 2018, 2:39pm

class VersionsView(DefaultView):
	__ac_local_roles_block__=1

Is this what you are recomending

zopyx · December 27, 2018, 4:42pm

Try it out and report back if it does not work.

AnanthaBalaji · December 28, 2018, 5:24am

Nothing happened

zopyx · December 28, 2018, 6:56am

Nothing happened means what? Nobody can and will help you if you do not provide further details.

Both options are perfectly working (basically since almost 20 years, since the existence of Zope).

See the implementation

github.com

plone/plone.api/blob/master/src/plone/api/content.py#L508-L517


      
          
          :param name: [required] Name of the view.
          :type name: string
          :param context: [required] Context on which to get view.
          :type context: context object
          :param request: [required] Request on which to get view.
          :type request: request object
          :raises:
              :class:`~plone.api.exc.MissingParameterError`,
              :class:`~plone.api.exc.InvalidParameterError`

which is doing the same as suggested.

zopyx · December 30, 2018, 7:13am

The only thing that might be needed for existing content objects is that you need to reindex them or call
obj.reindexObjectSecurity() for every affected content object after the particular change to the base class.