Introduction
A simple Page-like content type for Plone, to be used with auslfe.formonline.pfgadapter
It provides two possible profiles:
A basic ones (”Form Online: contents configuration”), that simply provide proper interface and workflow for use the “Form Online Adapter”.
An more complete ones (“Form Online: include FormOnline type”) will also register a new content type that automatically use the proper workflow.
This product also include the complete notification by e-mail system of the workflow.
Credits
Developed with the support of:
All of them supports the PloneGov initiative.
Authors
This product was developed by RedTurtle Technology team.
Changelog
0.8.1 (2012-10-03)
fixed incomplete translations for the new workflow [keul]
0.8.0 (2012-09-17)
a new workflow has been added (simple workflow) [nicola.senno]
0.7.0 (2012-07-12)
fix translation of mail_text_rejected, missed literal block [fdelia]
fix error with comment “Literal block expected; none found” in notification email [fdelia]
changed sendNotificationMail for get subject and text of email from the fields of FormOnlineAdapter [fdelia]
hide this from quickinstaller tool [keul]
0.6.0 (2012-02-15)
fixed e-mail layout [keul]
when a workflow comment is given, it’s added to the response e-mail when rejecting it [keul]
0.5.1 (2012-01-20)
fixed error while retrieving e-mail [keul]
Generic Setup profile version was not updated [keul]
0.5.0 (2012-01-20)
downgraded to debug level the print of token URL message (when used) [keul]
fixed workflow’s worklist with right state id (if anybody still using it) [keul]
fixed workflow reject/retract transitions [keul]
the owner of the form is notified when the form is accepted and rejected [keul]
supported notification also for anonymous submitters [keul]
0.4.0 (2012-01-11)
fixed typo in translations [keul]
added a soft dependency on auslfe.formonline.tokenaccess [keul]
0.3.0 (2011-12-13)
First pubic release
added support for “Site Administrator” role (this not mean that we tested this on Plone 4.1) yet [keul]
removed CMF skins directory (having it only for customize the getNotAddableTypes script was not a good idea [keul]
splitted the GS profile in two, a default core ones and another ones for register also the Page-like content. In this way a use could not use the FormOnline content [keul]
FormOnline content set as not searchable and not shown in navigation [keul]
removed the useless FormOnline view, transforming it to a viewlet registered for all content types marked as IFormOnline [keul]
0.2.0 (2011-05-06)
enabled versioning [keul]
changes to the content workflow [keul]
i18n fixes [keul]
some workflow changes [keul]
FormOnline content has its own view [keul]
added warning messages to the FormOnline view [keul]
0.1.0 (2010-07-19)
Initial release [fdelia]
Release files for auslfe.formonline.content 0.8.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 | Actions |
|---|---|---|---|---|
| auslfe.formonline.content-0.8.1.zip | 48.5 kB | Without provenance | Details for auslfe.formonline.content-0.8.1.zip |
Release files / auslfe.formonline.content-0.8.1.zip
| Download URL | auslfe.formonline.content-0.8.1.zip |
|---|---|
| Size | 48.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f726930805d7fc87e4c08c616affd5b02a57ef3ce15e7f1ff28c906f18916f63
|
|
BLAKE2b-256 checksum How to use checksums |
f8cb4620b408a24e0a976ea617a44a6bb48bd8859161db4dd7ee2e854d8603a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for auslfe.formonline.content 0.8.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.
