CiviCRM Community Forums (archive)

I've configured DPS as my payment processor in CiviCRM 4.3.4. I'm currently testing with a developer account.

When I try to complete a membership signup using DPS as the payment processor (rather than Pay later - both are enabled), I get the following error when submitting the form for payment:

Notice: Use of undefined constant CURLOPT_POSTFIELDSIZE - assumed 'CURLOPT_POSTFIELDSIZE' in CRM_Core_Payment_PaymentExpressUtils->_initCURL() (line 67 of /var/www/[drupal_root]/sites/all/modules/civicrm/CRM/Core/Payment/PaymentExpressUtils.php).

Warning: curl_setopt() expects parameter 2 to be long, string given in CRM_Core_Payment_PaymentExpressUtils->_initCURL() (line 67 of /var/www/[drupal_root]/sites/all/modules/civicrm/CRM/Core/Payment/PaymentExpressUtils.php).

Has anyone else encountered this issue? Any suggestions?

For the record, I have another site that is also using DPS. It was recently upgraded from 4.2.x to 4.3.5 and had no problem with that site before or after the upgrade.

Thanks in advance.

David

Thanks - I'll check both options out.

Wasn't aware of DrupalSouth 2014, but am now! Yeah, I'd be interesting in coming along, especially if there's an opportunity for a Civi meet up as well.

I'd be up for a sprint although my developer skills need a bit of work. We could try and convince Lucas to join us though.....

Yeah, we've worked together on and off for 5 years.

Which little one - there are 2 now! Time you caught up with him!

Probably the bug has always been there but you have e-notice turned on now. Or else it's a setting that has changed in curl

http://curl.haxx.se/libcurl/c/curl_easy_setopt.html

You can either remove that line or turn e-notice off.

Hmmm.

E_notice wasn't enabled, so that's not the issue.

I then commented the offending line in PaymentExpressUtils.php which stopped the error appearing, but nothing else changed. When I click Continue to confirm the details I should be taken to the DPS hosted page. Instead, the page simply reloads with no message. The contribution is recorded as payment pending (incomplete transaction). Clicking the Continue button a second time generates a DB Error: already exists error from Civi (no surprise there).

I then configured the dummy payment processor for the site, just to check if that worked. No problem there (not that I was expecting one ...)

I then tried creating a contribution page on another site I'm developing, also hosted on the same server. Same problem. And, to clarify my original post, the other site I'm running where this is working is on a different server. So I figure the issue is to do with my server configuration, but I'm not sure what might be missing/misconfigured. I have the latest version of curl. There are no errors in the log files on the server. Is there a set of configuration requirements that I might have missed?

Yeah so that IS the problem. For some reason, from what I recall, if you are using pxpay you need to use the url ending in pxaccess & vice versa.

Also, if you have mcrypt installed you can use either as the one that requires a mac (I think it's that one) just outsources the encryption that mcrypt could do. I think the api key has the mac appended to it for the other one (I really can't remember which is which)