CiviCRM Community Forums (archive)

Hello,

We have recently upgraded to the latest code set and we are now unable to record contributions that involve a payment processor.  CiviContribute worked perfectly with the exact same settings prior to the upgrade.  When users attempt to make contributions, the system errors and I don't know how to resolve this.  After weeks of troubleshooting I fear the only solution may be to reinstall and have to re-enter all of our data and I would like to avoid that if at all possible. 

Here is what happens:

The User clicks on one of the following options:

• Contribution Widget on Homepage
• Event registration for paid event (unpaid events requiring no contribution do not have issues)
• Membership Registration/Renewal

Basically anything that requires a payment to go through the Payment Processor. 

Civi successfully shows all information capture screens and the successfully sends the user to the confirmation screen.  When someone clicks on "Make Payment" on the confirmation screen, that is where the issue arises.  The system doesn't actually record the contribution. 

I thought the issue was due to the payment processor since we are successfully accepting registrations for an event that we are offering for free and doesn't require the payment processing.  Because of this I wanted to eliminate payment processing as the point of failure.  We currently use PayPal, however to test I setup a Google Checkout Merchant Account thinking it might be a PayPal issue but that did not resolve anything; the exact same error message is displayed.

Has anyone seen this before?   Any ideas are welcome!

Below is the error message displayed:

"Sorry but we are not able to provide this at the moment.
The system did not record payment details for this payment and so could not process the transaction. Please report this error to the site administrator.

Return to home page."


If it helps, with debugging turned on you get the following details:


backTrace

#0 /home/deolc/www/www/sites/all/modules/civicrm/CRM/Core/Error.php(305): CRM_Core_Error::backtrace()
#1 /home/deolc/www/www/sites/all/modules/civicrm/CRM/Contribute/BAO/Contribution/Utils.php(228): CRM_Core_Error::fatal("The system did not record payment details for this payment and so could not p...")
#2 /home/deolc/www/www/sites/all/modules/civicrm/CRM/Contribute/Form/Contribution/Confirm.php(923): CRM_Contribute_BAO_Contribution_Utils::processConfirm(Object(CRM_Contribute_Form_Contribution_Confirm), (Array:31), (Array:27), "36", "3", "contribution", (Array:0))
#3 /home/deolc/www/www/sites/all/modules/civicrm/CRM/Core/Form.php(246): CRM_Contribute_Form_Contribution_Confirm->postProcess()
#4 /home/deolc/www/www/sites/all/modules/civicrm/CRM/Core/StateMachine.php(159): CRM_Core_Form->mainProcess()
#5 /home/deolc/www/www/sites/all/modules/civicrm/CRM/Core/QuickForm/Action/Next.php(60): CRM_Core_StateMachine->perform(Object(CRM_Contribute_Form_Contribution_Confirm), "next", "Next")
#6 /home/deolc/www/www/sites/all/modules/civicrm/packages/HTML/QuickForm/Controller.php(203): CRM_Core_QuickForm_Action_Next->perform(Object(CRM_Contribute_Form_Contribution_Confirm), "next")
#7 /home/deolc/www/www/sites/all/modules/civicrm/packages/HTML/QuickForm/Page.php(103): HTML_QuickForm_Controller->handle(Object(CRM_Contribute_Form_Contribution_Confirm), "next")
#8 /home/deolc/www/www/sites/all/modules/civicrm/CRM/Core/Controller.php(289): HTML_QuickForm_Page->handle("next")
#9 /home/deolc/www/www/sites/all/modules/civicrm/CRM/Core/Invoke.php(212): CRM_Core_Controller->run((Array:3), NULL)
#10 /home/deolc/www/www/sites/all/modules/civicrm/drupal/civicrm.module(500): CRM_Core_Invoke::invoke((Array:3))
#11 [internal function](): civicrm_invoke("contribute", "transact")
#12 /home/deolc/www/www/includes/menu.inc(516): call_user_func_array("civicrm_invoke", (Array:2))
#13 /home/deolc/www/www/index.php(21): menu_execute_active_handler()
#14 {main}

The DB in question was upgraded. Using a fresh install, it works. I'm not certain what the issue may have been with the old DB but an export/import was sufficient in this case and so debugging that DB won't be necessary. I anyway suspect this is a fairly obscure issue.