CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • custom tokens not substituted at run time
Pages: [1]

Author Topic: custom tokens not substituted at run time  (Read 1035 times)

infiton

  • I’m new here
  • *
  • Posts: 1
  • Karma: 0
  • CiviCRM version: 4.2.8
  • CMS version: Drupal
  • MySQL version: 5.5.30
  • PHP version: 5.3.23
custom tokens not substituted at run time
May 04, 2013, 04:25:41 pm
When sending out bulk mail my organization fills a custom field in the civicrm database to append to a link in the body of the email. So for instance an email will contain

notalink.example.com/{contact.custom_xxx}&cid={contact.contact_id}

We do this often and before today this has worked well so that our contacts receive a link that looks like

notalink.example.com/1010&cid=100

Today we sent out an email and it seems during processing some, though not all, of the {contact.custom_xxx} tokens were processed to blank strings so that some contacts received
notalink.example.com/&cid=100

For the contacts that received this I verified in the database that the custom fields were correctly filled and should have been substituted correctly as they usually are. The odd behavior is that this happened only for some contacts and not all of them and also the {contact.contact_id} token was correctly substituted for all contacts.

Does anyone have any ideas how this possibly could have happened?


Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • custom tokens not substituted at run time

This forum was archived on 2017-11-26.