CiviCRM Community Forums (archive)

Hello
    We upgraded to CiviCRM 4.2 this past fall.  For a in-honor-of or a memorial contribution, there are two profiles attached.  One captures additional contribution custom data and the other one get the first name, last name, email address plus a couple custom fields for the contact record.  At the last step and after confirming the the donation/payment (the moment the record is written to the db and the next step is Pay Pal or Google Check-out), the "DB Error: constraint violation" message occurs.   This contribution worked prior to the upgrade and I have been trying for hours to find a fix on my own.  Weeding through all of the possible hits is tough.  I think there is a possible patch and I think it may be related to field called $financial_type_id (but that problem is discussed in 4.3).  And I tried to recreate the scenario in the demo database as best as possible but did not get the db constraint there.  So, that leads me back to the question of "Is there a patch for 4.2 CiviContribute that I may be missing?" 

    I also tried to find a patch listing for 4.2 in general, but did not find that.  If that exists somewhere in CiviCRM, please also let me know that.

    I also tried to look at the details of the error in Firefox, but it did not give any more info with the inspect element.  However, I am novice at this and may not have done that correctly.

    These are important contribution for our rescue and I will have to pull them until I can figure out how to address this problem.

    All help would be appreciated.

Holly Bauernsmith
 

Hershel
   Thank you for the reply.
 
    I am unsure if we are 4.2.7. Drupal states just 4.2, so I am guessing that is it. 

    Would you know how many hours of effort, I should expect for just going fromm 4.2 tol  4.2.7 ?

Thanks, Holly