Fatal error Call to undefined method CRM_Core_payment_omnipayMultiProcessor::doTransferCheckout(0 in /sites/all/modules/webform_civicrm/includes/wf_crm_webform_postprocess.inc on line 1841

[jvos]

We are using the Drupal modules webform and webform_civicrm with this extension.
Versions older then 2.2 work fine, but in newer releases we get the following error message when we submit the Drupal webform to the mollie payment
"Fatal error Call to undefined method CRM_Core_payment_omnipayMultiProcessor::doTransferCheckout(0 in /sites/all/modules/webform_civicrm/includes/wf_crm_webform_postprocess.inc on line 1841".

[eileenmcnaughton]

arg - I removed that function as part of removing support for 4.6 but it didn't occur to me webform might use it. What version of civi/ webform are you using?

[eileenmcnaughton]

Can you try this patch (against webform_civicrm)

colemanw/webform_civicrm#86

[jvos]

Thanks for the patch, i will try it. Beside, the version of civicrm is 4.7.18 or higher and the version of the webform_civicrm module is 7.x-4.18

[eileenmcnaughton]

I realised you need this change too
a915787

[jvos]

Thanks again ! I have lookes at the file but the last changes (from a915787) are already in release 2.4 !

[jaapjansma]

The problem @jvos is addressing is not fixed yet. It has something to do with the webform and civicrm core payment processor handling. When I setup a payment processor for paypal I get the same error.

The webform module tries to call a function doTransferCheckout but that one does not exist.

[eileenmcnaughton]

That's probably because a new release of webform_civicrm has not yet been tagged

[jaapjansma]

@eileenmcnaughton you mean a new release of webform_civicrm is underway which contains a fix for this?

Mean while I also found this issue on the webform_civicrm module: https://www.drupal.org/node/2558585
That issue is open since 2015

[jaapjansma]

@eileenmcnaughton I see that there is indeed a new version of webform_civicrm which seems to contain a fix

[jaapjansma]

@eileenmcnaughton @jvos I can confirm that this is fixed in webform_civicrm 7.x-4.19

[eileenmcnaughton]

Thanks @jaapjansma