collective.schedulefield
Schedule behaviors for Plone content types.
Features
schedule or multi-schedule (with dates ranges) behaviors to define schedules (morning / afternoon / comment) by day of week
exceptional closure behavior to define closing days
Installation
Install collective.schedulefield by adding it to your buildout:
[buildout]
...
eggs =
collective.schedulefield
and then running bin/buildout
Compatibility
Versions 1.x are developed for Plone 6.
Versions 0.x are developed for Plone 4 & Plone 5. Please note that they do not provide the full functionality (no multi-schedules, no exceptional closures, no RESTAPI serializer).
Contribute
Have an idea? Found a bug? Let us know by opening a ticket.
Issue Tracker: https://github.com/IMIO/collective.schedulefield/issues
Source Code: https://github.com/IMIO/collective.schedulefield
License
The project is licensed under the GPLv2.
Contributors
Gillian Sampont, Original Author [Affinitic]
Benoît Suttor [iMio]
Christophe Boulanger [iMio]
François Bruynbroeck [Affinitic]
Laurent Lasudry [Affinitic]
Martin Peeters [Affinitic]
Rémi Dubois [iMio]
Stéphan Geulette [iMio]
# Changelog
## 1.1 (2025-05-08)
Update locales https://github.com/IMIO/collective.schedulefield/issues/3 [remdub]
Add test environment using pytest, with test coverage reaching 80% https://github.com/IMIO/collective.schedulefield/issues/2 [remdub]
Fix MultiSchedule viewlet https://github.com/IMIO/collective.schedulefield/issues/4 [remdub]
Upgrade dev environment to Plone 6.1-latest [remdub]
## 1.0a3 (2023-01-12)
MANIFEST / release fix [laulaz]
## 1.0a2 (2023-01-12)
Drop support for Plone 4 & Plone 5 [laulaz]
Fix AttributeError traceback when accessing subforms [laulaz]
## 1.0a1 (2022-12-13)
Add basic serializers / deserializers [laulaz]
Display schedule viewlets only on views (not on folder_contents, cropping, etc.) [laulaz]
Fix error when validating an empty value for a schedule [laulaz]
Add missing key_type/value_type for Schedule field. This is needed (at least) to export types schemas information [laulaz]
Fix python3 compatibility : Use @implementer instead of implements [boulch]
Handle multi schedules and exceptional closures [fbruynbroeck]
## 0.6.1 (2018-10-15)
Do not display comment if empty. [bsuttor]
## 0.6 (2018-04-23)
Also view schedule if only comment is set. [bsuttor]
Added missing z3c.form meta.zcml. [sgeulette]
## 0.5 (2017-04-27)
Bugfix: get json schedule. [bsuttor]
## 0.4 (2017-04-25)
Bugfix: do not try to load json value if there is no values. [bsuttor]
## 0.3 (2017-03-01)
Do not render the viewlet if there is no values [mpeeters]
## 0.2 (2016-07-14)
Add the ScheduledContent behavior [mpeeters]
Add a comment field for each schedule day [mpeeters]
## 0.1 (2014-08-26)
Initial release
Metadata
Release files for collective.schedulefield 1.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 | |
|---|---|---|---|---|
| collective_schedulefield-1.1.tar.gz | 31.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| collective_schedulefield-1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 64.7 kB
Release files / collective_schedulefield-1.1.tar.gz
| Download URL | collective_schedulefield-1.1.tar.gz |
|---|---|
| Size | 31.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb725df9d5cddb775a4264374d532166efd19b7f30896c4c98ed18bcbcada069
|
|
BLAKE2b-256 checksum How to use checksums |
1180b2a65d88b7c8ee07cc11e0883e3e0d22d7b7b0e8012e93be6f9a398b688e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Release files / collective_schedulefield-1.1-py3-none-any.whl
| Download URL | collective_schedulefield-1.1-py3-none-any.whl |
|---|---|
| Size | 32.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
13edf05eeeb6926ee72757c738f8a9206f2efdda0fe8211f822f8db4e079f31a
|
|
BLAKE2b-256 checksum How to use checksums |
7a1311f981466d2fbc21abbc3e04be3a10f379a27dc47d8dc072f6f36d7e0f8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Security for collective.schedulefield 1.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.