Changes between Version 8 and Version 9 of S3/Notifications

Timestamp:

09/05/13 10:52:36 (12 years ago)

Author:

Dominic König

Comment:

--

S3/Notifications

@@ -60 +60 @@
   - Rendering via web2py view templates (message templates)
 
-The pre-rendering is to convert the extracted data into a suitable format for the message template. The pre-rendering routine is configurable both per deployment-template and per resource (resource-specific overrides deployment-specific), the default pre-renderer is S3Notifications._render().
+The pre-rendering is to convert the extracted data into a suitable format for the message template. The pre-rendering routine is configurable both per deployment-template and per resource (resource-specific overrides deployment-specific), the default pre-renderer is {{{S3Notifications._render()}}}.
 
-The message templates are web2py view templates stored in private/template/XYZ/views/msg (falling back to views/msg).
+The message templates are '''web2py view templates''' stored in ''private/template/XYZ/views/msg'' (falling back to ''views/msg'').
 
-Template names use a prefix (default: "notify"), and the notification method name, like: notify_email.html (=template for email notifications).
+Template names use a '''prefix''' (default: "notify") and the notification method name, like: ''notify_email.html'' (=template for email notifications).
 
-Message templates for EMAIL can further use a format suffix "html" or "text" (e.g. "notify_email_html.html") - where both fall back to the name without suffix.
+The template name '''prefix''' can be configured '''per resource''' (using the "notify_template" setting), the default is "notify".
 
-The template name prefix can be configured per resource (using the "notify_template" setting), the default is "notify".
+Message templates for '''EMAIL''' can further use a '''format''' suffix "html" or "text" (e.g. ''notify_email_html.html'') - where both fall back to the name without suffix.
 
-Any deployment-template-specific message template (including fallbacks) is preferred over any default templates.
+Any deployment-template-specific message templates (including fallbacks) is preferred over any default templates.
 
 === Configuration ===