Introduction
This package installs a JavaScript handler (using jQuery) that will present a prompt box inviting the user to enter a comment before triggering a workflow transition from the ‘state’ drop-down in a standard Plone site.
The handler will only be used for workflow actions using the standard content_status_modify script.
You can restrict this behaviour on some transitions through a control panel.
You can make the comment required or not.
Screenshot
If enabled, you’ll see a popup as shown below when initiating a workflow transition.
Requirements
Plone 4.0+ (tested under Plone 4.0, 4.1, 4.2 and 4.3).
Tested with ie6, ie7, ff3, ff4, chrome.
Languages
English
French
German
Credits
Martin Aspeli, release 1.0
Vincent Fretin and Thomas Desvenain, release 2.0
Daniel Widerin [saily]
Changelog
2.1.5 (2013-05-31)
Split up robottests into keywords.robot which is reusable in your tests, by adding:
*** Settings *** Resource plone/app/robotframework/selenium.robot Resource plone/app/robotframework/keywords.robot Resource collective/wfcomment/tests/robot/keywords.robot ...
[saily]
Use id or name selectors to make keywords.robot more generic and reuseable for any languages. [saily]
2.1.4 (2013-05-17)
Add a new test and remove unneeded ones. [saily]
Add support for dexterity content types. [saily]
Update permissions for comment view and javascript viewlet. [saily]
2.1.3 (2013-05-16)
Add tests using robotframework, travis integration and . [saily]
Add german translations and add an update_translations script to be generated through buildout. [saily]
‘form.buttons.cancel’ in prepOverlay closeselector has to be in quotes to avoid unrecognized expression javascript errors. [saily]
Set correct javascript filter for prepOverlay. [saily]
Move from svn to collective, merge tdesvenain’s remote repo into collective. Please maintain in collective in future. [saily]
Restructure buildout for Plone 4.3 and Plone 4.2. [saily]
2.1.2 (2013-04-18)
Really removed kss dependency (unused imports) [cedricmessiant]
2.1.1 (2012-07-29)
Full jquery: kss behaviours entirely replaced. Fixes under 4.1.x [thomasdesvenain]
2.0.2 (2011-05-02)
controlpanel: hide transition selection if ‘all transitions’ option is selected. [thomasdesvenain]
fix when ‘all transitions’ option is selected. [thomasdesvenain]
fix plone.app.registry dependency [toutpt]
2.0.1 (2011-05-02)
Fixed profile.
2.0 (2011-04-28)
Complete rewrite:
uses ajax internationalized form,
allows to select a list of transitions,
kss compliant.
[vincentfretin, thomasdesvenain]
1.0b2 - 2009-08-31
Fix ‘undefined’ error in IE.
1.0b1 - 2009-03-19
Initial release
Metadata
Release files for collective.wfcomment 2.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.wfcomment-2.1.5.zip | 87.2 kB | Without provenance | Details for collective.wfcomment-2.1.5.zip |
Release files / collective.wfcomment-2.1.5.zip
| Download URL | collective.wfcomment-2.1.5.zip |
|---|---|
| Size | 87.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
97adf8e853016bed22a9d3a6a8567f54a7cda8bb355490336291a4312cd8335a
|
|
BLAKE2b-256 checksum How to use checksums |
178c9a018c5a40b59c0c03622d24d938a17ab44dace0b7356d41880a09b21110
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.wfcomment 2.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.