This is a Plone extension for the plone.stringinterp module.
Adding this to your buildout and you will be able to add full content text in content rules e-mail messages.
How to use
When you are preparing e-mail action for your Plone Content Rules you can now use two additional marker in the text:
- ${text}
The current document full text
- ${indented_text}
Same as above, but right-indent the text using a tab char before every line.
Text is transformed from HTML to plain text (as ussualy are Plone e-mail).
A mail message rule configured like this:
Hi,
the new document "${title}" has been created.
${text}
…will generate this:
Hi, the new document "Welcome to Plone" has been created. If you're seeing this instead of the web site you were expecting...
And a mail message rule configured like this:
Hi,
the new document "${title}" has been created.
${indented_text}
…will generate this:
Hi,
the new document "Welcome to Plone" has been created.
If you're seeing this instead of the web site you were expecting...
Getting text
“Main text field” is an abstract entity. This product try to guess text using adapters, so you can override or provide more specific ones (see the code some example).
Generally, those kind of text extraction is supported:
ATContentTypes based content types with a text field (Event, News Item, Document, Topic)
Comment from plone.app.discussion
Dexterity content types with a text field
Plus, a general adapter that simply try to read if a “text” attribute is provided.
Credits
Developed with the support of Regione Emilia Romagna; Regione Emilia Romagna supports the PloneGov initiative.
Authors
This product was developed by RedTurtle Technology team.
Changelog
1.0.0 (2022-07-14)
upgrade to plone 5.2 and python3.8. [reflab]
0.3 (2017-11-07)
fix adapter when object dexterity content have completely empty text field. [lucabel]
0.2 (2013-09-06)
fix adapter when objects doesn’t have text field (ie Files) [cekk]
0.1.1 (2013-08-02)
locales folder was not registered [keul]
0.1 (2013-05-30)
Initial release
Release files for collective.stringinterp.text 1.0.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 | Actions |
|---|---|---|---|---|
| collective.stringinterp.text-1.0.0.tar.gz | 14.7 kB | Without provenance | Details for collective.stringinterp.text-1.0.0.tar.gz |
Release files / collective.stringinterp.text-1.0.0.tar.gz
| Download URL | collective.stringinterp.text-1.0.0.tar.gz |
|---|---|
| Size | 14.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9e8850719b842f28467475ce1684ee236165dcdad169c5457bd1c330a51a6aa
|
|
BLAKE2b-256 checksum How to use checksums |
272a7dc00241776fed39da3e93d33bb024b8f4b86ec940fc42183ddf4ea626c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.7.7
|
Security for collective.stringinterp.text 1.0.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.
