QWeb for email templates
This module was written to allow you to write email templates in QWeb instead of jinja2. The advantage here is that with QWeb, you can make use of inheritance and the call statement, which allows you to reuse designs and snippets in multiple templates, making your development process simpler. Furthermore, QWeb views are easier to edit with the integrated ACE editor.
Usage
To use this module, you need to:
Select QWeb in the field Body templating engine
Select a QWeb view to be used to render the body field
Variables
Apart from QWeb’s standard variables, you also have access to:
object browse record of the current object
email_template browse record of email template in use
record depending on where the message is sent, object can be either the real record or the mail message used to send the email. In standard J2 templates this variable is available only for messages and only in the ctx. This variable tries to solve this issue and provides always the same variable.
record_name always provide the display name of current record
In addition to these, you’ll find all the variables available for J2 templates: format_date, format_tz, format_amount, user, ctx. These will make easier to port existing J2 templates to Qweb.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smash it by providing detailed and welcomed feedback.
Credits
Images
Odoo Community Association: Icon.
Contributors
Holger Brunn <hbrunn@therp.nl>
Dave Lasley <dave@laslabs.com>
Carlos Lopez Mite <celm1990@gmail.com>
Simone Orsi <simone.orsi@camptocamp.com>
Do not contact contributors directly about support or help with technical issues.
Maintainer
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
To contribute to this module, please visit https://odoo-community.org.
1 maintainer
Metadata
1 maintainer
Release files for odoo11-addon-email-template-qweb 11.0.1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo11_addon_email_template_qweb-11.0.1.1.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for odoo11_addon_email_template_qweb-11.0.1.1.0-py2.py3-none-any.whl |
Release files / odoo11_addon_email_template_qweb-11.0.1.1.0-py2.py3-none-any.whl
| Download URL | odoo11_addon_email_template_qweb-11.0.1.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 29.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
50ece5de12da970166cb95c54560bedc8672d582b075a0e85e1cfe02ad4732f7
|
|
BLAKE2b-256 checksum How to use checksums |
824b99974b5baeb7ccaa2ec8a7af82dc13bd9ddb080b8161b19790425bced2d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo11-addon-email-template-qweb 11.0.1.1.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.
