openerp-community-reviewer team mailing list archive
-
openerp-community-reviewer team
-
Mailing list archive
-
Message #00286
[Merge] lp:~therp-nl/server-env-tools/7.0_email_template_template_rst into lp:server-env-tools
Holger Brunn (Therp) has proposed merging lp:~therp-nl/server-env-tools/7.0_email_template_template_rst into lp:server-env-tools.
Requested reviews:
Server Environment And Tools Core Editors (server-env-tools-core-editors)
For more details, see:
https://code.launchpad.net/~therp-nl/server-env-tools/7.0_email_template_template_rst/+merge/189108
This should explain everything:
https://apps.openerp.com/apps/7.0/email_template_template/
--
https://code.launchpad.net/~therp-nl/server-env-tools/7.0_email_template_template_rst/+merge/189108
Your team Server Environment And Tools Core Editors is requested to review the proposed merge of lp:~therp-nl/server-env-tools/7.0_email_template_template_rst into lp:server-env-tools.
=== modified file 'email_template_template/__openerp__.py'
--- email_template_template/__openerp__.py 2013-06-17 09:03:49 +0000
+++ email_template_template/__openerp__.py 2013-10-03 14:58:45 +0000
@@ -32,8 +32,9 @@
in the other templates. Changing the layout is then only a matter of changing
the template template.
-
-Usage:
+-----
+Usage
+-----
Create an email template with the related document model 'Email Templates'. Now
most of the fields gray out and you can only edit body_text and body_html. Be
sure to use ${body_text} and ${body_html} respectively in your template
@@ -43,48 +44,50 @@
templates.
For example, create a template template
------
-Example Corp logo
-Example Corp header
-${object.body_text} <- this gets evaluated to the body_text of a template using this template template
-Example Corp
-Example street 42
-Example city
-Example Corp footer
------
+
+::
+
+ Example Corp logo
+ Example Corp header
+ ${object.body_text} <- this gets evaluated to the body_text of a template using this template template
+ Example Corp
+ Example street 42
+ Example city
+ Example Corp footer
Then in your template you write
------
-Dear ${object.partner_id.name},
+::
-Your order has been booked on date ${object.date} for a total amount of ${object.sum}.
------
+ Dear ${object.partner_id.name},
+
+ Your order has been booked on date ${object.date} for a total amount of ${object.sum}.
And it will be evaluated to
------
-Example Corp logo
-Example Corp header
-Dear Jane Doe,
-
-Your order has been booked on date 04/17/2013 for a total amount of 42.
-Example Corp
-Example street 42
-Example city
-Example Corp footer
------
+::
+
+ Example Corp logo
+ Example Corp header
+ Dear Jane Doe,
+
+ Your order has been booked on date 04/17/2013 for a total amount of 42.
+ Example Corp
+ Example street 42
+ Example city
+ Example Corp footer
Given the way evaluation works internally (body_text of the template template is evaluated two times, first with the instance of email.template of your own template, then with the object your template refers to), you can do some trickery if you know that a template template is always used with the same kind of model (that is, models that have the same field name):
In your template template:
-------
-Dear ${'${object.name}'}, <-- gets evaluated to "${object.name}" in the first step, then to the content of object.name
-${object.body_html}
-Best,
-Example Corp
-------""",
+::
+
+ Dear ${'${object.name}'}, <-- gets evaluated to "${object.name}" in the first step, then to the content of object.name
+ ${object.body_html}
+ Best,
+ Example Corp
+""",
'website': 'http://therp.nl',
'images': [],
'depends': ['email_template'],
Follow ups