CiviCRM Community Forums (archive)

Can anyone help, I've tried the module from circle interactive but I keep getting an error 500 page when registering for an event using the sagepay payment processor.

PHP version = 5
mysql version = 5
Using drupal.6-22

Hi there,

Apologies, we updated the module a bit for Civi 3.3, but forgot to update the version we had on that page.

Have uploaded the latest version to http://www.circle-interactive.co.uk/help/civicrm/modules/sagepay

That one should work ok with 3.3, 3.4 and 4.0.

Let us know if you have any more problems with it,

Andy

Hi there,

Apologies, we updated the module a bit for Civi 3.3, but forgot to update the version we had on that page.

Have uploaded the latest version to http://www.circle-interactive.co.uk/help/civicrm/modules/sagepay

That one should work ok with 3.3, 3.4 and 4.0.

Let us know if you have any more problems with it,

Andy

Ok, I'm trying it using test payments but I keep getting the following message:

Sorry. A non-recoverable error has occurred.
The following errors occurred when submitting payment to Sage Pay:
malformed
Please contact the site administrator.

With no way for me to figure why this is happening, any suggestions?

Thanks

Hi Dave

Looking at civicrm-version.php the version is 3.4.5, the full contents of this file is as follows:


<?php
function civicrmVersion( ) {
  return array( 'version'  => '3.4.5',
                'cms'      => 'Drupal',
                'revision' => '35590' );
}
Cheers

:::UPDATE:::

Issue solved.

However still getting malformed error message with the test environment.

An update on what the real problem was and how we solved it.

(It wasn't the Error URL field in the Edit Payment Processor page - this has been left blank.)

Surfing to the redirection url in the browser revealed php errors in the page. That's why SagePay was unable to respond to it.

To fix the problem, we solved the issue with php errors on the notification url. Thanks to Dave Jenkins from Circle Interactive who helped us out on IRC. (And, a huge thanks to Circle Interactive for contributing this code to the community in the first place.)

In our case the error was related to the location of the civicrm module in a contrib folder. The solution was to create a settings_location.php file in sites/all/modules/contrib/civicrm/ with the text:

define( 'CIVICRM_CONFDIR', '/home/civicrm/public_html/sites' );

vin, did you resolve the issue you were getting with missing street address, post code, country fields?

it appears that the field ids are different to what the $sageParams are expecting - eg form contains hidden field called #street_address-1 but sage params wants ($contact['street_address'];

we've just upgraded civi to 4.1 so am not sure whether its bailing on new registrants because of that or something else. will report back when i find out.

Hi there,

Did some more work to this at the London code sprint last week - mainly updating it to the new extension format, but have also rolled the changes into the standard payment module in case that helps anyone.

You can download that from http://www.circle-interactive.co.uk/help/civicrm/modules/sagepay

I don't think any of those changes will solve your problem here though. To get hold of that data, the module does a contact search through the api based on contact_id (this has been updated to now use api v3 - not sure if that will help, probably not).

So, if you're ending up with keys like 'street_address-1', that is probably how the api is returning them (you can verify this in the api explorer).

Could maybe add something to deal with this if there's no way to fix it elsewhere, but it sounds more like an issue with the profiles that collect the data, rather than the module itself.

Hope that helps!

Let us know how you get on,

Andy