-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Plip10359 security controlpanel #24
Conversation
pprop = getToolByName(self.portal, 'portal_properties') | ||
self.portal.manage_addProperty('validate_email', False, 'boolean') |
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.
@jcerjak Don't we have to check if that property already exist? I would expect this to fail if we would run it in Plone 4.x.
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.
you're right, I'll fix it
This restores Plone 4 compatibility
Plone 4 compatibility restored. |
pprop = getToolByName(self.portal, 'portal_properties') | ||
try: |
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.
try/except without a specific error are usually a bad idea because they will swallow any exception that might occur.
Read security settings from the registry instead of portal properties. This is part of work on the security control panel migration: plone/Products.CMFPlone#216
This should be merged along with plone/Products.CMFPlone#362