From 9263f105b1c76c3530d5ab933c8135425bebb4f9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jesu=CC=81s=20Alan=20Ramos=20Rodri=CC=81guez?= Date: Tue, 22 Aug 2023 08:10:48 -0600 Subject: [PATCH] [IMP] base_comment_template: update readme files Change deprecated t-raw to t-out. Rename invoice_comment_template to account_comment_template --- base_comment_template/README.rst | 10 ++++----- base_comment_template/readme/DESCRIPTION.rst | 4 ++-- base_comment_template/readme/USAGE.rst | 6 +++--- .../static/description/index.html | 21 +++++++++++-------- 4 files changed, 22 insertions(+), 19 deletions(-) diff --git a/base_comment_template/README.rst b/base_comment_template/README.rst index 03713a9f6..c094767c4 100644 --- a/base_comment_template/README.rst +++ b/base_comment_template/README.rst @@ -42,14 +42,14 @@ It has a priority field (smaller number = higher priority) In existing reports, if you add this line will get the comment template if you created one like -* ( or without any parameter) +* ( or without any parameter) This module is the base module for following modules: * sale_comment_template * purchase_comment_template -* invoice_comment_template +* account_comment_template * stock_picking_comment_template **Table of contents** @@ -91,13 +91,13 @@ The template is a html field which will be rendered just like a mail template, s Change the report related to the model from configuration and add a statement like: -
+
-
+
@@ -113,7 +113,7 @@ mail.render.mixin with parameters: so you could use it : -
+
diff --git a/base_comment_template/readme/DESCRIPTION.rst b/base_comment_template/readme/DESCRIPTION.rst index 6909ad5d5..bd616e27f 100644 --- a/base_comment_template/readme/DESCRIPTION.rst +++ b/base_comment_template/readme/DESCRIPTION.rst @@ -12,12 +12,12 @@ It has a priority field (smaller number = higher priority) In existing reports, if you add this line will get the comment template if you created one like -* ( or without any parameter) +* ( or without any parameter) This module is the base module for following modules: * sale_comment_template * purchase_comment_template -* invoice_comment_template +* account_comment_template * stock_picking_comment_template diff --git a/base_comment_template/readme/USAGE.rst b/base_comment_template/readme/USAGE.rst index 8800f0741..30343d7ae 100644 --- a/base_comment_template/readme/USAGE.rst +++ b/base_comment_template/readme/USAGE.rst @@ -17,13 +17,13 @@ The template is a html field which will be rendered just like a mail template, s Change the report related to the model from configuration and add a statement like: -
+
-
+
@@ -39,6 +39,6 @@ mail.render.mixin with parameters: so you could use it : -
+
diff --git a/base_comment_template/static/description/index.html b/base_comment_template/static/description/index.html index 71cc9228c..6481ce6ac 100644 --- a/base_comment_template/static/description/index.html +++ b/base_comment_template/static/description/index.html @@ -8,10 +8,11 @@ /* :Author: David Goodger (goodger@python.org) -:Id: $Id: html4css1.css 8954 2022-01-20 10:10:25Z milde $ +:Id: $Id: html4css1.css 9511 2024-01-13 09:50:07Z milde $ :Copyright: This stylesheet has been placed in the public domain. Default cascading style sheet for the HTML output of Docutils. +Despite the name, some widely supported CSS2 features are used. See https://docutils.sourceforge.io/docs/howto/html-stylesheets.html for how to customize this style sheet. @@ -274,7 +275,7 @@ pre.literal-block, pre.doctest-block, pre.math, pre.code { margin-left: 2em ; margin-right: 2em } -pre.code .ln { color: grey; } /* line numbers */ +pre.code .ln { color: gray; } /* line numbers */ pre.code, code { background-color: #eeeeee } pre.code .comment, code .comment { color: #5C6576 } pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold } @@ -300,7 +301,7 @@ span.option { span.pre { white-space: pre } -span.problematic { +span.problematic, pre.problematic { color: red } span.section-subtitle { @@ -381,13 +382,13 @@ You can define one default template per Model and domain, which can be overwritt It has a priority field (smaller number = higher priority)

In existing reports, if you add this line will get the comment template if you created one like

    -
  • <span t-raw=”o.get_comment_template(‘position’,company_id=o.company_id, partner_id=o.parnter_id )”/> ( or without any parameter)
  • +
  • <span t-out=”o.get_comment_template(‘position’,company_id=o.company_id, partner_id=o.parnter_id )”/> ( or without any parameter)

This module is the base module for following modules:

  • sale_comment_template
  • purchase_comment_template
  • -
  • invoice_comment_template
  • +
  • account_comment_template
  • stock_picking_comment_template

Table of contents

@@ -436,12 +437,12 @@ If you create a new template with the same configuration (Model, Domain, Positio

Change the report related to the model from configuration and add a statement like:

<t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position == ‘before_lines’)” t-as=”comment_template_top”>
-
<div t-raw=”o.render_comment(comment_template_top)” />
+
<div t-out=”o.render_comment(comment_template_top)” />

</t>

<t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position == ‘after_lines’)” t-as=”comment_template_bottom”>
-
<div t-raw=”o.render_comment(comment_template_bottom)” />
+
<div t-out=”o.render_comment(comment_template_bottom)” />

</t>

You should always use t-if since the method returns False if no template is found.

@@ -455,7 +456,7 @@ mail.render.mixin with parameters:

so you could use it :

<t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position == ‘before_lines’)” t-as=”comment_template_top”>
-
<div t-raw=”o.render_comment(comment_template_top, engine=’qweb’, add_context={my dict}, postprocess=True)” />
+
<div t-out=”o.render_comment(comment_template_top, engine=’qweb’, add_context={my dict}, postprocess=True)” />

</t>

@@ -514,7 +515,9 @@ If you spotted it first, help us to smash it by providing a detailed and welcome

Maintainers

This module is maintained by the OCA.

-Odoo Community Association + +Odoo Community Association +

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.