collective.timestamp
Timestamp Files (or any other content types with a file primary field) in Plone. The collective.timestamp behavior must be activated on content types you want to timestamp.
Features
Allows you to timestamp a file via a toolbar action.
Provides a way to timestamp files through a content rule action executor.
Displays a timestamped viewlet on timestamped content.
The viewlet provides access to a verification view (with files and instructions).
Timestamping service and verification instructions are configurable via a configlet.
Translations
This product has been translated into
French
Installation
Install collective.timestamp by adding it to your buildout:
[buildout]
...
eggs =
collective.timestamp
and then running bin/buildout
Contribute
Issue Tracker: https://github.com/collective/collective.timestamp/issues
Source Code: https://github.com/collective/collective.timestamp
Support
If you are having issues, please let us know.
License
The project is licensed under the GPLv2.
Contributors
Affinitic, support@affinitic.be
Changelog
1.5 (2025-09-10)
Properly translate labels in TimestampInfo. [aduchene]
1.4 (2025-08-26)
Add a new view TimestampInfo to have more info about the timestamp that can also be used as an util view. [aduchene]
1.3 (2025-06-23)
Avoid modifying list passed as argument in utils.timestamp. [aduchene]
1.2 (2025-06-19)
Fixed a bug with utils.timestamp stuck in an infinite loop when use_failover was False. [aduchene]
Changed default values of ITimestampingSettings and set required fields. [aduchene]
1.1 (2025-06-19)
Fix a bug with TimeStamper.timestamp not returning the correct value. [aduchene]
1.0 (2025-06-19)
Refactor the timestamp utils function to be able to use failover urls and exp. backoff retries. [aduchene]
Add settings to manage failover urls and exp. backoff retries. [aduchene]
1.0a2 (2024-10-11)
Added TimeStamper._effective_related_indexes to factorize the list of catalog indexes related to the effective functionality. Make TimeStamper.timestamp return data and timestamp in case it is overrided or called from external code. [gbastien]
1.0a1 (2024-09-17)
Initial release. [laulaz]
Metadata
Release files for collective.timestamp 1.5
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 |
|---|---|---|---|---|
| collective_timestamp-1.5.tar.gz | 42.3 kB | Without provenance | Details for collective_timestamp-1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| collective_timestamp-1.5-py3-none-any.whl | Python 3 | none | any | Details for collective_timestamp-1.5-py3-none-any.whl |
Total release size: 102.7 kB
Release files / collective_timestamp-1.5.tar.gz
| Download URL | collective_timestamp-1.5.tar.gz |
|---|---|
| Size | 42.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
66ed1a733262999da6f63e73659403b7396df30966789af54132ba3dcf244f2d
|
|
BLAKE2b-256 checksum How to use checksums |
aa8a72bdce1a18e3eb20eba62a1f46b71479b802c16a96055a047e0f93199dda
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Release files / collective_timestamp-1.5-py3-none-any.whl
| Download URL | collective_timestamp-1.5-py3-none-any.whl |
|---|---|
| Size | 60.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ee1d130ed681cfa7c6e5bd039f647b8d77fdd8b34feab712312531f001648ff8
|
|
BLAKE2b-256 checksum How to use checksums |
bf7fa3e0c291cafb90fcc1cfa90350a15159ca5c307d534ac337aff08cf27bdb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Security for collective.timestamp 1.5
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.