Imio.pm.ws

Latest version: v3.9

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

Scan your dependencies

Page 1 of 7

3.10

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

- Nothing changed yet.

3.9

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

- Adapted code as `Products.PloneMeeting.utils.add_wf_history_action` was moved
to `imio.history.utils.add_event_to_wf_history` and `ToolPloneMeeting.getUserName`
is removed, we use `imio.helpers.content.get_user_fullname` instead.
[gbastien]

3.8

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

- Make sure `createItemRequest` returns a response status of `200` or
it raises a `SOAPException` (even if item is created anyway?!).
[gbastien]
- Fixed `SOAPView._getItemInfos` when computing `preferred_meeting_date`, it was
always `None` because using the `uid_catalog` and Meeting is a DX content type.
[gbastien]

3.7

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

- Fixed `test_ws_getItemInfosWithShowAssembly` regarding changes in default
contacts gender in PloneMeeting testing profile `import_data`.
[gbastien]
- Completed `test_ws_meetingAcceptingItems` to check that it works when using
`inTheNameOf` (was actually not working before `Products.PloneMeeting==4.2rc30`).
[gbastien]
- Adapted code regarding removal of `MeetingConfig.useGroupsAsCategories`.
[gbastien]

3.6

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

- Whenever a `ZSI.Fault` error is raised, display also the message in the log manually
because `z3c.soap` will not display the error string, only the traceback...
[gbastien]

3.5

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

- Fixed bug in `_createItem` where it could happen that user used `inTheNameOf`
had cached `_listAllowedRolesAndUsers` resulting in seeing too much or not
enough in the dashboard. Accessing an item that should not be displayed ended
in an Unauthorized though.
Every method using inTheName of now use
`setup_user_in_the_name_of`/`teardown_user_in_the_name_of` to handle it correctly.
[gbastien]

Page 1 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.