Answers.Body: <p>Hi there there was an issue due to a change made in 4.7.14, It has been fixed in the up coming 4.7.15 version however I would suggest probably the better option is to upgrade and apply the following patch to your code base. <a href="https://github.com/civicrm/civicrm-core/pull/9530/" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/pull/9530/</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-02T20:27:50.487Z
Answers.LastActivityDate: 2017-01-02T20:27:50.487Z
Answers.UserDisplayName: Seamus Lee
Body: <p>CiviCRM version: 4.7.14<br>
  previous version: 4.7.12<br>
  Wordpress version: 4.7<br></p>
  
  <p>My contribution form experience problem at the "Confirm contribution" page.<br>
  Upon pressing Confirm Contribution, user is brought back to the "Confirm Contribution" page with error "Please confirm birth date"<br>
  The error does not make sense as a birthdate is already in place.<br>
  And multiple tries of replacing birthdate with a different value did not help<br></p>
  
  <p>A forced downgrading to CiviCRM 4.7.12 resolved the issue - a contribution can now go through.</p>
  
  <p>Please advise! :)</p>
  
Tags: <contribution-page><4.7.14>
Title: 4.7.14 Wordpress 4.7 problem with contribution form Birth Date
ThreadText: # 4.7.14 Wordpress 4.7 problem with contribution form Birth Date
  
  (Asked by: username_0 on 2017-01-02)
  
  CiviCRM version: 4.7.14  
  previous version: 4.7.12  
  Wordpress version: 4.7
  
  My contribution form experience problem at the "Confirm contribution" page.  
  Upon pressing Confirm Contribution, user is brought back to the "Confirm Contribution" page with error "Please confirm birth date"  
  The error does not make sense as a birthdate is already in place.  
  And multiple tries of replacing birthdate with a different value did not help
  
  A forced downgrading to CiviCRM 4.7.12 resolved the issue - a contribution can now go through.
  
  Please advise! :)
  
  **Tags:** contribution-page, 4.7.14
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-01-02. Score: 1
  
  Hi there there was an issue due to a change made in 4.7.14, It has been fixed in the up coming 4.7.15 version however I would suggest probably the better option is to upgrade and apply the following patch to your code base. <https://github.com/civicrm/civicrm-core/pull/9530/>
  
  
  ---
  
  