This release is a pre-release and may not be stable for production use.
============
collective.wfform gives a developer the ability to present a z3c.form
during a workflow transition.
To implement this for a transition in a particular workflow,
change the transition url from:
%(content_url)s/content_status_modify?workflow_action=submit
to:
%(content_url)s/workflow_transition_form?workflow_action=submit
This will give you a jQuery popup form with a comments field.
To add your own fields, add a method to your content type which
returns a z3c schema based on the transition.
security.declareProtected(permissions.ModifyPortalContent, 'getSchemaForTransition')
def getSchemaForTransition(self, transition):
"""Return a fieldset depending on the transition"""
if transition == 'my_transition':
return IMyTransitionForm
IMyTransitionForm should be a standard interface class with a zope3 schema.
To process the data from the form, add another method onto your class to manage this.
security.declareProtected(permissions.ModifyPortalContent, 'processTransitionForm')
def processTransitionForm(self, data):
"""Return a fieldset depending on the transition"""
if data.has_key('my_field'):
self.setMyField(data['my_field'])
collective.wfform Installation
------------------------------
To install collective.wfform into the global Python environment (or a workingenv),
using a traditional Zope 2 instance, you can do this:
* When you're reading this you have probably already run
``easy_install collective.wfform``. Find out how to install setuptools
(and EasyInstall) here:
http://peak.telecommunity.com/DevCenter/EasyInstall
* If you are using Zope 2.9 (not 2.10), get `pythonproducts`_ and install it
via::
python setup.py install --home /path/to/instance
into your Zope instance.
* Create a file called ``collective.wfform-configure.zcml`` in the
``/path/to/instance/etc/package-includes`` directory. The file
should only contain this::
<include package="collective.wfform" />
.. _pythonproducts: http://plone.org/products/pythonproducts
Alternatively, if you are using zc.buildout and the plone.recipe.zope2instance
recipe to manage your project, you can do this:
* Add ``collective.wfform`` to the list of eggs to install, e.g.:
[buildout]
...
eggs =
...
collective.wfform
* Tell the plone.recipe.zope2instance recipe to install a ZCML slug:
[instance]
recipe = plone.recipe.zope2instance
...
zcml =
collective.wfform
* Re-run buildout, e.g. with:
$ ./bin/buildout
You can skip the ZCML slug if you are going to explicitly include the package
from another package's configure.zcml file.
Changelog
=========
1.0dev (unreleased)
-------------------
- Initial release
Metadata
Release files for collective.wfform 1.0-a1
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.wfform-1.0-a1.zip | 24.2 kB | Without provenance | Details for collective.wfform-1.0-a1.zip |
Release files / collective.wfform-1.0-a1.zip
| Download URL | collective.wfform-1.0-a1.zip |
|---|---|
| Size | 24.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e9d0615e6c23be301bddafc88d430c06a573317e9481f9698992b1207a76b7bd
|
|
BLAKE2b-256 checksum How to use checksums |
ec2730ad00f30a5c724f0778e5562b386bb7c0d10855cb25269924985c13fe88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.wfform 1.0-a1
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.