Body: <p>CiviCRM 4.7.30, current Webform CiviCRM 7.x-4.19</p>
  
  <p>When the user receives their receipt it prints the Date field in the table as this:</p>
  
  <p>20180313115320</p>
  
  <p>Which I assume is....</p>
  
  <p>2018 / 03 / 13 / 11:53:20 </p>
  
  <p>How do we resolve this?</p>
  
  <p>The receipts on line template is:</p>
  
  <pre><code>   {if $receive_date}
    &lt;tr&gt;
     &lt;td {$labelStyle}&gt;
      {ts}Date{/ts}
     &lt;/td&gt;
     &lt;td {$valueStyle}&gt;
      {$receive_date} 
     &lt;/td&gt;
    &lt;/tr&gt;
   {/if}
  </code></pre>
  
  <p>Also, strangely enough, no transaction ID is present</p>
  
  <p>Paypal WPP is the payment processor.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-14T13:10:45.557Z
Comments.Text: What does that receive_date look like in the database? Look in the civicrm_contribution table;
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-14T17:57:08.993Z
Comments.Text: Receive date is: 2018-03-13 11:53:20
Comments.UserDisplayName: Zachary
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-14T23:16:14.720Z
Comments.Text: So which receipt are you sending? Online Contribution or Event or message template via CiviRules/Email API or webform email?
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-15T00:30:13.437Z
Comments.Text: The receipt text is coming from the civicontribute page and it's using the civicrm template for the receipt. We are not using Civirules/email API or webform email (but could if those work better?)
Comments.UserDisplayName: Zachary
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-15T16:44:29.140Z
Comments.Text: For what it's worth it seems like resetting the template to default and re-applying custom formatting may have resolved this issue. That doesn't tell me exactly what went wrong yet, hope to come back and update. Perhaps the template was changed in the 4.6 to 4.7 update in a way that affected date formatting?
Comments.UserDisplayName: Zachary
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-15T19:55:12.333Z
Comments.Text: Phew - glad you solved it; I've not seen this yet on any of ours; I do think smarty templates aren't all that smart - sometimes... I spent some time myself just now trying to explode a string and gave up!
Comments.UserDisplayName: KarinG - Semper IT
Tags: <webform-civicrm>
Title: Webform CiviCRM Date Field corrupted on Receipt
ThreadText: # Webform CiviCRM Date Field corrupted on Receipt
  
  (Asked by: username_0 on 2018-03-13)
  
  CiviCRM 4.7.30, current Webform CiviCRM 7.x-4.19
  
  When the user receives their receipt it prints the Date field in the table as this:
  
  20180313115320
  
  Which I assume is....
  
  2018 / 03 / 13 / 11:53:20
  
  How do we resolve this?
  
  The receipts on line template is:
  
  ```
     {if $receive_date}
    <tr>
     <td {$labelStyle}>
      {ts}Date{/ts}
     </td>
     <td {$valueStyle}>
      {$receive_date} 
     </td>
    </tr>
   {/if}
  
  ```
  
  Also, strangely enough, no transaction ID is present
  
  Paypal WPP is the payment processor.
  
  **Tags:** webform-civicrm
  
  > **Comments:**
  > **username_1**: What does that receive_date look like in the database? Look in the civicrm_contribution table;  
  > **username_0**: Receive date is: 2018-03-13 11:53:20  
  > **username_1**: So which receipt are you sending? Online Contribution or Event or message template via CiviRules/Email API or webform email?  
  > **username_0**: The receipt text is coming from the civicontribute page and it's using the civicrm template for the receipt. We are not using Civirules/email API or webform email (but could if those work better?)  
  > **username_0**: For what it's worth it seems like resetting the template to default and re-applying custom formatting may have resolved this issue. That doesn't tell me exactly what went wrong yet, hope to come back and update. Perhaps the template was changed in the 4.6 to 4.7 update in a way that affected date formatting?  
  > **username_1**: Phew - glad you solved it; I've not seen this yet on any of ours; I do think smarty templates aren't all that smart - sometimes... I spent some time myself just now trying to explode a string and gave up!  
  
  ---
  
  ## 0 answers
  
  