Answers.Body: <p>After updating to CiviCRM 4.7.14, this issue has disappeared. I am unable to replicate it on the CiviCRM Wordpress demo as well, so I think it must have just been an issue with my version being out of date.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-19T23:56:46.600Z
Answers.Text: Yes - you stumbled on CRM-19153 (https://issues.civicrm.org/jira/browse/CRM-19153), which was fixed in CiviCRM 4.7.14.
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-19T02:56:06.120Z
Answers.LastActivityDate: 2016-12-19T02:56:06.120Z
Answers.UserDisplayName: Justin
Body: <p>When I enable pledges on a contribution form, CiviCRM processes the first payment properly, and records the correct "pledge made date". </p>
  
  <p>However, it records the "next payment date/payments start" as Jan. 1, 1970, and subsequent payments in their proper increments (weekly, monthly, etc.) on the proper day of that period.</p>
  
  <p>Obviously, this error doesn't apply to pledges entered manually.</p>
  
  <p>I am running Wordpress 4.6.1 with CiviCRM 4.7.12. Any ideas as to what's behind the timewarp back to the 1970s?</p>
  
Tags: <civicontribute><civipledge>
Title: CiviPledge "Next Payment Date" automatically set to Jan. 1, 1970
ThreadText: # CiviPledge "Next Payment Date" automatically set to Jan. 1, 1970
  
  (Asked by: username_0 on 2016-12-15)
  
  When I enable pledges on a contribution form, CiviCRM processes the first payment properly, and records the correct "pledge made date".
  
  However, it records the "next payment date/payments start" as Jan. 1, 1970, and subsequent payments in their proper increments (weekly, monthly, etc.) on the proper day of that period.
  
  Obviously, this error doesn't apply to pledges entered manually.
  
  I am running Wordpress 4.6.1 with CiviCRM 4.7.12. Any ideas as to what's behind the timewarp back to the 1970s?
  
  **Tags:** civicontribute, civipledge
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2016-12-19. Score: 1
  
  After updating to CiviCRM 4.7.14, this issue has disappeared. I am unable to replicate it on the CiviCRM Wordpress demo as well, so I think it must have just been an issue with my version being out of date.
  
  > **Comments:**
  > **username_1**: Yes - you stumbled on CRM-19153 (https://issues.civicrm.org/jira/browse/CRM-19153), which was fixed in CiviCRM 4.7.14.  
  
  ---
  
  