Products.MeetingBEP
Changelog
4.2.1 (2025-08-06)
Fixed testing import_data configs title. [gbasiten]
Removed override of MeetingItem.isPrivacyViewable, we go back to default behavior. [gbastien]
Use config.DU_ORIGINAL_VALUE and config.DU_RATIFICATION_VALUE in CustomBEPMeetingItem.adaptDecisionClonedItem, do not know hy it was not already the case, was only used in testCustomMeetingItem.test_AdaptDecisionClonedItem. [gbastien]
4.2 (2024-03-15)
Fixed tests now that MeetingConfig.at_post_edit_script is no more used. [gbastien]
Adapted code as field MeetingConfig.useCopies was removed. [gbastien]
Adapted code as isPowerObserverForCfg was moved from ToolPloneMeeting to utils. [gbastien]
4.2a1 (2022-06-23)
Adapted code for PloneMeeting 4.2.x. [gbastien]
Added Migrate_To_4200, cleaned unused files. [gbastien]
Added utils.hr_group_uid to manage UID of the HR confidential group as we can no more rely on HR group id. [gbastien]
4.1.2 (2020-10-29)
Removed CustomBEPMeeting.getPrintableItemsByCategory, we use the method from MeetingCommunes. [gbastien]
4.1.1 (2020-08-21)
Adapted zbep import_data regarding DX meetingcategory. [gbastien]
4.1 (2019-10-14)
Reintegrated CustomBEPMeeting.getPrintableItemsByCategory waiting for another final solution. [gbastien]
Install profile ‘profile-Products.MeetingCommunes:zcommittee_advice’ at install time. [anuyens]
4.1b3 (2019-08-13)
Adapted call to ToolPloneMeeting.isPowerObserverForCfg now that parameter isRestricted=True is replaced by power_observer_type=’restrictedpowerobservers’.
Use PloneMeetingTestCase._setPowerObserverStates to define power observers states.
4.1b2 (2019-01-31)
Configure profile
4.1b1 (2018-12-04)
Restricted power observers have… restricted access to some informations of the item, no access to : - history (of every content, item, meeting, advice); - item observations.
Items are not privacyViewable by restricted power observers when : - using HR confidential proposing group; - item is returned to proposing group for corrections.
When an item is accepted_out_of_meeting_emergency, the decision of duplicated item is automatically adapted to manage “ratification”.
Hide field ‘Observations’ on advice using CSS.
Override message ‘No access’ with something smoother.
3 maintainers
Metadata
3 maintainers
Release files for Products.MeetingBEP 4.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| Products.MeetingBEP-4.2.1.tar.gz | 124.5 kB | Without provenance | Details for Products.MeetingBEP-4.2.1.tar.gz |
Release files / Products.MeetingBEP-4.2.1.tar.gz
| Download URL | Products.MeetingBEP-4.2.1.tar.gz |
|---|---|
| Size | 124.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aacea1913c12855046cc25e0a609b306a841ae7397db46b33dc67a120286b366
|
|
BLAKE2b-256 checksum How to use checksums |
924f675197d8eb1472b618d248127e0133e82f62373eb700aa20835763984dac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.7.0 requests/2.25.1 setuptools/44.1.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/2.7.18
|
Security for Products.MeetingBEP 4.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
