Overview
Currently ftw.journal provides two adapters to store infos.
workflow_history
annotations
How to use:
Simply add a rule through the Plone UI.
Install
Add ftw.journal to your buildout configuration
[instance] eggs = ftw.journal
Run buildout
Add a rule through the Plone UI
Compatibility
Runs with Plone 4.3 or 5.1.
Links
Package will be on pypi: http://pypi.python.org/pypi/ftw.journal
Continuous integration: https://jenkins.4teamwork.ch/search?q=ftw.journal
Copyright
This package is copyright by 4teamwork.
ftw.journal is licensed under GNU General Public License, version 2.
Changelog
1.4.0 (2022-07-05)
Add uuid4 id for new annotation journal entries. [elioschmutz]
1.3.0 (2019-09-05)
Port to Plone 5.1 [njohner]
Drop support for Plone 4.2. [njohner]
Drop support for Plone 4.0 and 4.1. [jone]
1.2.9 (2016-12-12)
Whitelist journal writes for plone.protect > 3.0 [Rotonen]
1.2.8 (2014-09-23)
BugFix: Do not journalize in workflow history if the item has no workflow. [misch]
1.2.7 (2014-02-10)
Update French translations. [jone]
Move plone translations from i18n to locales folder. [jone]
1.2.6 (2013-05-13)
Updated French translations. [tschanzt]
1.2.5 (2012-06-05)
Update German translations. [jone]
1.2.4 (2012-02-28)
Adjust MANIFEST.in: add include for rst files (reamde.rst). [phgross]
1.2.3 (2012-02-28)
Fixed previous Release. [phgross]
1.2.2 (2012-02-27)
Added some French translations [ttschanz]
Added default .gitignore [lgraf]
1.2.1 (2011-11-17)
Changed entry_points target from opengever to plone [eschmutz]
Added integration tests [eschmutz]
Added functional test for events [eschmutz]
Added functional tests for interfaces and adapters [eschmutz]
Added testsetup for jenkins [eschmutz]
Translations updated. [phabegger]
1.2 (2010-11-18)
Adjust Manifest.in and IGNORE.txt
1.1 (2010-09-13)
Translated actions in plone domain [jinfanger]
1.0
Final relase
0.5
Created version.txt [jone]
Fixed Bug in AnnotationsJournalizable-Adapter (AttributeError: context) [13.10.2009]
Fixed Bug in AnnotationsJournalizable-Adapter
There seemed to be multiple journal list instances
Using PersistentList and PersistentDict now
[jone]
0.4
Added contentrule action for journal entries [christian.schneider]
0.3
Moving from teamraum.journal to ftw.journal [christian.schneider]
0.2.3
Fixed bug that prevented journalizer event handler from working [christian.schneider]
0.2.2
Added i18n stuff [christian.schneider]
Make journaling event handler check if an adapter exists before trying to journalize [christian.schneider]
0.2.1
Changed setup.py to try and fix the annoying dependency error when egg-info has not been deleted before running buildout [christian.schneider]
0.2
Implemented journaling mechanism using adapters and event handlers. There are two adapters to journalize something on a context, one for journalizing in the workflow history, and one for an annotations-based journal. Which one is used depends on which marker interface (see interfaces.py) the type implements. The annotations based system is not tested yet. [christian.schneider]
0.1
Initial release
Release files for ftw.journal 1.4.0
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 | |
|---|---|---|---|---|
| ftw.journal-1.4.0.tar.gz | 21.7 kB | Without provenance | Details |
Release files / ftw.journal-1.4.0.tar.gz
| Download URL | ftw.journal-1.4.0.tar.gz |
|---|---|
| Size | 21.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10e7af7d7f319e209023db90a87599c3fabf2c019b271f099353e0605e1b0076
|
|
BLAKE2b-256 checksum How to use checksums |
3ae796557e77f0eaea02d708cecd7079a03a6f3c81dc28f41d4e8905ac73e688
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.54.0 CPython/3.9.12
|
Security for ftw.journal 1.4.0
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.
