Collective-contact-plonegroup

Latest version: v1.36

Safety actively analyzes 623567 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 7

1.37

-----------------

- Nothing changed yet.

1.36

-----------------

- Added logging using `collective.fingerpointing` in the
`manage-own-groups-users` view when a user was added or removed.
[gbastien]
- Added `available_expr` to the action displaying the `Manage own groups`,
action will be displayed if at least one value is selected in the
`groups_management` field in the configuration.
[gbastien]
- Use `imio.helpers.SortedUsers` vocabulary in the
`manage-own-groups-users` view.
[gbastien]

1.35

-----------------

- Fixed `addOrModifyOrganizationGroups` called when an organization is modified,
that was creating Plone groups for every suffixes without considering
`enabled` or `fct_orgs`. Added upgrade step to `v8` that will delete Plone
groups that were wrongly created.
[gbastien]

1.34

-----------------

- Fixed `settings.detectContactPlonegroupChange` where sometimes `event.oldValue`
is None when value is set several times from different testing layers.
[gbastien]

1.33

-----------------

- Do not grok the package anymore.
[gbastien]
- Override vocabulary `PositionTypes` from `collective.contact.core`, when
`context` out of a directory, get `position_types` from `DEFAULT_DIRECTORY_ID`.
[gbastien]

1.32

-----------------

- Fixed `DisplayGroupUsersView.group_title` when `DisplayGroupUsersView.short=True`
to only apply if we have a format like `My config (My suffix)` or it removed
last letter.
[gbastien]
- Added parameter `PloneGroupUsersGroupsColumn.short=True` so
`display-group-users` is rendered short by default.
[gbastien]

Page 1 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.