Re: fields template variables in "To:" header
Subject:
Re: fields template variables in "To:" header
In-Reply-To:
fields template variables in "To:" header
Date:
July 28th 2011
On Jul 27, 2011, at 9:11 PM, Mariano Absatz - gmail wrote:
> When I sent a message, the actual To: header I got looked like this:
>
> To: "<!-- tmpl_var subscriber.first_name --> <!-- tmpl_var subscriber.last_name -->" <address@example.net>
>
> When I expected something like this:
>
> To: <address@example.net>
>
> or like this:
>
> To: " " <address@example.net>
I really would have expected the same thing you wanted, as well.
> Is this a bug? Would it be fixable?
If you would, add it to the tracker:
http://github.com/justingit/dada-mail/issues
And I'll certainly take a look at it.
One possible workaround would be to set a default in the tag, like this:
<!-- tmpl_var subscriber.first_name default="First Name" --> <!-- tmpl_var subscriber.last_name default="Last Name" -->
By design, the templating engine should use the values you have in the default parameter, if the values given to it are blank or undefined. Another, slightly more awkward approach would be to use tmpl_if tags:
<!-- tmpl_if subscriber.first_name --><!-- tmpl_var subscriber.first_name --><!-- tmpl_else -->John<!-- /tmpl_if--> <!-- tmpl_var subscriber.last_name -->
Still another idea would be to use the fallback value, when creating the subscriber profile field.
|
<< Previous: Re: edit fields by list admin (not root) |
| Archive Index | |
)
This mailing list is to discuss the nerdy programming development of Dada Mail -
If you are just looking for support Dada Mail, consult the message boards at:
http://dadamailproject.com/support/boards
To post to this list, send a message to:
All subscribers of this list may post to the list itself.
Some on topic... topics include:
- Positive Crits on the program (I like, "x", but, "y" needs some work - here's an idea on how to make this better...)
- Bug/Error reports
- Bug fixes
- Request For Comments on any changes to the program
- Help customizing Dada Mail for your own internal needs
- Patches
- Language Translations
- Support Documentation/Doc editing, FAQ's, etc.
- Discussion of any changes that you would like to be committed to the next version of Dada Mail -
At the moment, there aren't many people with CVS access for Dada Mail - if you would like CVS access, please first talk about the changes you propose and how it will affect the program. If the idea is sound and agreed upon, the change will be comitted. A good track record of this will allow you to have CVS access. Some reasons that patches will not be accepted is if the patch breaks compatibility with a previous version of the program, the patch is too centric to your own problem or the patch simply isn't very good.
Please, please please familiarize yourself with the documentation at:
http://dadamailproject.com/support/documentation/
Since no one wants to answer the same question twice.
Another sneaky reason for this mailing list is to test out the discussion list capabilities of Dada Mail, since Dada Mail is used for the mailing list itself.
NOTE - because of this, there may be times that this list will be somewhat broken. Although we're not planning on breaking the program by using it, we're giving you the heads up that this may well happen anyways.
