Details
-
Type:
Bug
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 4.7.18
-
Fix Version/s: None
-
Component/s: CiviEvent
-
Labels:None
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:User and Admin Doc
-
Funding Source:Needs Funding
-
Verified?:No
Description
After upgrading from CiviCRM 4.6.24 to CiviCRM 4.7.18 on Drupal (7.52) we are getting the error "Expected one Contribution but found 25" whenever registering for an event with an event page.
I think that a related issue is that no new transactions are showing up as completed even if the contribution_status_id is equal to one which corresponds to the completed status. I have checked the database and nothing appears to be incorrect from that perspective.
I did not get any errors when upgrading CiviCRM as described above.
I have tested while logged in, not logged in, with and without price sets.
I am running Apache 2.4.25 with PHP 5.6.30.
Attached is the complete error that I have from Watchdog.
Thanks,
Josh
Attachments
Activity
Jitendra Purohit see if this is trivial and if so fix otherwise we might have to see if someone else can pick it up
I see "Completed" status is disabled on the status page with duplicate values for "value" field.
These statuses were added in 4.5 so it should be present on your site prior to the upgrade(as you were on 4.6.24), maybe some other reason might have caused this?
Josh Griffin Can you please update the value of "Partially Paid" and "Pending Refund" to some other value, re-enable Completed status and check if you can replicate this again? Thanks!
Sorry, I never wrote back to this. If you change the value it works fine. The issue is that the value was there twice. I had trouble back in the 4.5 upgrade so that could be it.
-Steve
I am not sure if this is a bug or not. During the upgrade Partially paid and Pending Refund and as you can see in the picture these got added with the value and of 1 and 2 respectfully and this was stopping form any contribution from being completed and causing the query error.