Body: <p>Event online receipt system workflow messages are missing values for many fields that were working reliably before recent Civi update.</p>
  <p>Are there token changes that might be causing this?</p>
  <p>Is there a way to find any errors for token problems?    Would one problem token cause all following tokens to fail?   (Values in earlier portion of message are being completed)</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-02-18T03:55:37.857Z
Comments.Text: There were LOTS of token changes in 5.43+ although not specifically for the event receipt template. Which tokens?
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-02-18T11:12:36.720Z
Comments.Text: Hard to say, there are a lot that represent custom fields and profiles using fields.
Comments.UserDisplayName: Dave T
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-02-18T12:03:42.820Z
Comments.Text: Is there any way to get a list of token syntax that is correct vs. those that might have been deprecated?
Comments.UserDisplayName: Dave T
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-02-18T15:41:49.547Z
Comments.Text: It's not that tokens were deprecated, it's that the underlying processing is different, and some smarty variables, e.g. `{$contact.X}` are replaced with a replacement `{contact.Y}` token. But something like `{contact.custom_12}` should still work.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-02-18T19:54:09.673Z
Comments.Text: So removing the $ might do the trick?
Comments.UserDisplayName: Dave T
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-02-18T19:59:11.443Z
Comments.Text: If the X and Y are the same yes. You might need to look in the tokens dropdown to get the right replacement if they're slightly different. Something like {$contact.contact_id} might now be {contact.id}
Comments.UserDisplayName: Demerit
Tags: <civievent><system-workflow-messages>
Title: System workflow message tokens missing after recent Civi upgrade
ThreadText: # System workflow message tokens missing after recent Civi upgrade
  
  (Asked by: username_0 on 2022-02-18)
  
  Event online receipt system workflow messages are missing values for many fields that were working reliably before recent Civi update.
  
  Are there token changes that might be causing this?
  
  Is there a way to find any errors for token problems? Would one problem token cause all following tokens to fail? (Values in earlier portion of message are being completed)
  
  **Tags:** civievent, system-workflow-messages
  
  > **Comments:**
  > **username_1**: There were LOTS of token changes in 5.43+ although not specifically for the event receipt template. Which tokens?  
  > **username_0**: Hard to say, there are a lot that represent custom fields and profiles using fields.  
  > **username_0**: Is there any way to get a list of token syntax that is correct vs. those that might have been deprecated?  
  > **username_1**: It's not that tokens were deprecated, it's that the underlying processing is different, and some smarty variables, e.g. `{$contact.X}` are replaced with a replacement `{contact.Y}` token. But something like `{contact.custom_12}` should still work.  
  > **username_0**: So removing the $ might do the trick?  
  > **username_1**: If the X and Y are the same yes. You might need to look in the tokens dropdown to get the right replacement if they're slightly different. Something like {$contact.contact_id} might now be {contact.id}  
  
  ---
  
  ## 0 answers
  
  