Skip to main content
added 37 characters in body
Source Link
nielo
  • 1.4k
  • 8
  • 19

I implemented miscellaneous custom tokens and have been using them successfully in mailings and pdf generation.

But in context of greetings I came across some weird misbehaviour. I tested by changing email greeting and running api job.update_greeting w/ force=1.

  1. When extending the token array's "contact" key with a custom token, the {contact.tokenname} markup get's interpreted but not replaced. Result is '{contact.tokenname}'.
  2. When using custom key the markup {keyname.tokenname} is not recognized and even doesn't get into the hook function's token parameter. Result is '' and Smarty reports »unrecognized tag«.

Both tokens run fine in pdf generation.

I'm running latest Drupal 7 and CiviCRM.

Any ideas?

Thanks in advance

I implemented miscellaneous custom tokens and have been using them successfully in mailings and pdf generation.

But in context of greetings I came across some weird misbehaviour. I tested by changing email greeting and running api job.update_greeting w/ force=1.

  1. When extending the token array's "contact" key with a custom token, the {contact.tokenname} markup get's interpreted but not replaced. Result is '{contact.tokenname}'.
  2. When using custom key the markup {keyname.tokenname} is not recognized and even doesn't get into the hook function's token parameter. Result is ''.

Both tokens run fine in pdf generation.

I'm running latest Drupal 7 and CiviCRM.

Any ideas?

Thanks in advance

I implemented miscellaneous custom tokens and have been using them successfully in mailings and pdf generation.

But in context of greetings I came across some weird misbehaviour. I tested by changing email greeting and running api job.update_greeting w/ force=1.

  1. When extending the token array's "contact" key with a custom token, the {contact.tokenname} markup get's interpreted but not replaced. Result is '{contact.tokenname}'.
  2. When using custom key the markup {keyname.tokenname} is not recognized and even doesn't get into the hook function's token parameter. Result is '' and Smarty reports »unrecognized tag«.

Both tokens run fine in pdf generation.

I'm running latest Drupal 7 and CiviCRM.

Any ideas?

Thanks in advance

added 43 characters in body
Source Link
nielo
  • 1.4k
  • 8
  • 19

I implemented miscellaneous custom tokens and have been using them successfully in mailings and pdf generation.

But in context of greetings I came across some weird misbehaviour. I tested by changing email greeting and running api job.update_greeting w/ force=1.

  1. When extending the token array's "contact" key with a custom token, the {contact.tokenname} markup get's interpreted but not replaced. Result is '{contact.tokenname}'.
  2. When using custom key the markup {keyname.tokenname} is not recognized and even doesn't get into the hook function's token parameter. Result is ''.

Both tokens run fine in pdf generation.

I'm running latest Drupal 7 and CiviCRM.

Any ideas?

Thanks in advance

I implemented miscellaneous custom tokens and have been using them successfully in mailings and pdf generation.

But in context of greetings I came across some weird misbehaviour. I tested by changing email greeting and running api job.update_greeting w/ force=1.

  1. When extending the token array's "contact" key with a custom token, the {contact.tokenname} markup get's interpreted but not replaced. Result is '{contact.tokenname}'.
  2. When using custom key the markup {keyname.tokenname} is not recognized and even doesn't get into the hook function's token parameter. Result is ''.

I'm running latest Drupal 7 and CiviCRM.

Any ideas?

Thanks in advance

I implemented miscellaneous custom tokens and have been using them successfully in mailings and pdf generation.

But in context of greetings I came across some weird misbehaviour. I tested by changing email greeting and running api job.update_greeting w/ force=1.

  1. When extending the token array's "contact" key with a custom token, the {contact.tokenname} markup get's interpreted but not replaced. Result is '{contact.tokenname}'.
  2. When using custom key the markup {keyname.tokenname} is not recognized and even doesn't get into the hook function's token parameter. Result is ''.

Both tokens run fine in pdf generation.

I'm running latest Drupal 7 and CiviCRM.

Any ideas?

Thanks in advance

Source Link
nielo
  • 1.4k
  • 8
  • 19

Tokens in greetings not replaced

I implemented miscellaneous custom tokens and have been using them successfully in mailings and pdf generation.

But in context of greetings I came across some weird misbehaviour. I tested by changing email greeting and running api job.update_greeting w/ force=1.

  1. When extending the token array's "contact" key with a custom token, the {contact.tokenname} markup get's interpreted but not replaced. Result is '{contact.tokenname}'.
  2. When using custom key the markup {keyname.tokenname} is not recognized and even doesn't get into the hook function's token parameter. Result is ''.

I'm running latest Drupal 7 and CiviCRM.

Any ideas?

Thanks in advance