CiviCRM Community Forums (archive)

there is another thread with eileen on sending parameters to tokens in the last couple of weeks. I think reusing the smarty syntax makes sense (with named params), so something like:

{donation_sum:start=2011-01-01:end=2011-12-31:}

or something like that. We should then ensure that the token parsing considers the above as one token and let the hook do the needful

lobo

ok, for now if we agree that we always call the tokenValue, even if the name isn't in the token list, we should be futurerpoof, no matter the syntax.

I'm going to try and think about a syntax (will try if we can use space, = ...)

Something that would be super useful is being able to use variables between token.

eg

{assign:event_id=42}

You can register online <a href="/civicrm/event/register?event_id={$event_id}">...

{event_info} (new token that would fetch and display based on the event_id assigned earlier on)

Aim: having one template that is safer to reuse (the number of times the event id wasn't updated on a url...)
Risk: people likes inventing languages, and it starts smelling like it.

Nice work Eileen.
I want to put in my little plug for efficiency. Currenly CiviMail loads tokens in bulk (a recent improvement), whereas other BAOs, (like print PDF letter) load them one at a time. I've been dreaming about a centralized token loader (rather than implementing it ad-hoc by several BAOs) which would always load in bulk.