nwells

In case the developer is looking at this, the issue relates to lines 148 & 149 in /modoles/redirection.php:

$details = array_map( 'trim', $details );
$details = array_map( 'stripslashes', $details );

Those two lines assume that all values in the $details array are strings which isn’t the case. If you look at /filio/csv.php it is returned as true/false from the is_regex() function.

The resolution above is correct as it needs to be cast back to a boolean in order for the check to work.

Hey Ross

I’ve tried it out now and it worked just fine – no need to make any adjustments like before.

Well done!

Cheers
Nigel

Yep I’m just keeping it pretty basic at this stage as just needed to test my theory that it would work. I’ve not used any of the additional user creation boxes or other options – just let Gravity Forms do its own thing.

From when I did my last integration with DPS, and compared an A2A response with a CC response they were identical (in terms of fields provided in the response) except for the omission of CC details.

So long as your logic is just paying attention to the normal transaction ids, auth codes, etc… then there is no change required in my opinion. Id say if someone was having issues with other actions then it most likely isn’t related – unless of course they have a custom hook that is relying on specific fields being in the response?

Hey

Yep I initially tried 5 and nothing changed so went the other way and it worked.

I’ve just done a scan through all the themes and plugins installed and there is another plugin that makes use of the parse_request hook and its priority is set to 1. The plugin that uses the hook is designed to restrict visitors to the website by IP so guess that makes sense to be priority 1. Not sure why lowering the priority helped – perhaps there is something in WP core messing with it in my install?

Yes I’d be happy to trial a dev version that works a different way for you – I’ll be out till Monday so can try then if you’re ready.

Cheers
Nigel

Thought I’d let you know that your plugin works perfectly fine for Account2Account payments.
I’ve used Account2Account in the past with my own bespoke websites and it works 99.9% the same as credit card payments. The only difference between the two is the returned response from DPS doesn’t contain any information on the credit card – which makes sense.
It is a shame that DPS don’t provide a facility to test this – I imagine it is because it would require each bank providing their own sandbox and making that publicly available via an API.
Fantastic plugin though – well done!