Search 1.9 billion lines of Odoo code on GitHub
email_template_qweb
<a class="reference external image-reference" href="https://www.gnu.org/licenses/agpl"><img alt="License: AGPL-3" src="https://img.shields.io/badge/license-AGPL--3-blue.png" /></a>
<a name="qweb-for-email-templates"></a>
<h2>QWeb for email templates</h2>
<p>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 <code>call</code> 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.</p>
<a name="usage"></a>
<h3>Usage</h3>
<p>To use this module, you need to:</p>
<ol class="arabic simple">
<li>Select <cite>QWeb</cite> in the field <cite>Body templating engine</cite></li>
<li>Select a QWeb view to be used to render the body field</li>
</ol>
<p><strong>Variables</strong></p>
<p>Apart from QWeb's standard variables, you also have access to:</p>
<ul class="simple">
<li><code>object</code> browse record of the current object</li>
<li><code>email_template</code> browse record of email template in use</li>
<li><code>record</code> depending on where the message is sent,
<code>object</code> 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.</li>
<li><code>record_name</code> always provide the display name of current record</li>
<li>In addition to these, you'll find all the variables available for J2 templates:
<code>format_date</code>, <code>format_tz</code>, <code>format_amount</code>, <code>user</code>, <code>ctx</code>.
These will make easier to port existing J2 templates to Qweb.</li>
</ul>
<a class="reference external image-reference" href="https://runbot.odoo-community.org/runbot/205/11.0"><img alt="Try me on Runbot" src="https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas" /></a>
<a name="bug-tracker"></a>
<h3>Bug Tracker</h3>
<p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/social/issues">GitHub Issues</a>. 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.</p>
<a name="credits"></a>
<h3>Credits</h3>
<a name="images"></a>
<h4>Images</h4>
<ul class="simple">
<li>Odoo Community Association: <a class="reference external" href="https://odoo-community.org/logo.png">Icon</a>.</li>
</ul>
<a name="contributors"></a>
<h4>Contributors</h4>
<ul class="simple">
<li>Holger Brunn <<a class="reference external" href="mailto:hbrunn@therp.nl">hbrunn@therp.nl</a>></li>
<li>Dave Lasley <<a class="reference external" href="mailto:dave@laslabs.com">dave@laslabs.com</a>></li>
<li>Carlos Lopez Mite <<a class="reference external" href="mailto:celm1990@gmail.com">celm1990@gmail.com</a>></li>
<li>Simone Orsi <<a class="reference external" href="mailto:simone.orsi@camptocamp.com">simone.orsi@camptocamp.com</a>></li>
</ul>
<p>Do not contact contributors directly about support or help with technical issues.</p>
<a name="maintainer"></a>
<h4>Maintainer</h4>
<a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a>
<p>This module is maintained by the OCA.</p>
<p>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.</p>
<p>To contribute to this module, please visit <a class="reference external" href="https://odoo-community.org">https://odoo-community.org</a>.</p>