CiviCRM Community Forums (archive)

Can anyone offer a suggestion for debugging this behaviour, which has been driving me nuts for hours.

We have a mail merge template set up in CiviCRM, which is used to generate PDF letters, not emails.

We use some core tokens (such as {contact.adressee}), some custom data tokens (such as {contact.custom_1}) and some customised tokens (such as {contact.name_of_doctor}).

On my development box (Civi 4.4.1) the template works perfectly, all three types of tokens are translated into their content for each PDF letter generated.

Exactly the same template on our 'test' system (also Civi 4.4.1) fails to translate the custom data tokens - they are simply replaced with white space. The core tokens and the customised tokens still work as expected. I've stripped this down to a template containing just tokens, and the problem continues. Core tokens are translated, customised tokens are translated, but custom data tokens just disappear.

What could possibly be going on? I've tested the behaviour in the Civi demo system, and custom field tokens work as expected. No errors are logged when the letter is generated, other than some php strict warnings, which are common to all our installations of CiviCRM. Any clues gratefully received.

Nick,

When I cleared the caches, normal behaviour was restored. Not sure what is the source of the problem.

Ken