cbfuk

Hi Ross

GF v1.7.2 (I see there’s a 1.7.3 already, so we may up to that)

The client’s site hasn’t had a lot of business through the GF payment forms yet, but they are high-value items and they expect to get a lot busier in a few days so we’re under pressure to make sure this can’t happen again.

Any info you can provide would be great; a colleague posted on the GF support forum also but I’m not sure if she’s had a useful response to that. Do you have any thoughts on a GF failure mode which would cause a glitch like this, you obviously have much more experience of working with GF than us?

Cheers
Colin

Yep, no doubt, DPS info all matches. Interestingly, we’ve found a ghost in the DB; the wp_rg_lead_meta table has an entry with a matching DPS authcode, but form_id and lead_id are both 0 – not a good look! I’m wondering if that entry was made by you on FPRN, but you couldn’t find the lead record? All I can think of is that GF failed to process the form submission for some reason, but did fire your plugin?

Hi Ross

Thanks; yep, that’s all what we thought. Damn, no easy answers then!

Cheers
Colin

Hi Ross
Yeh, a hook to set/override DPS parameters would be good tho given I was just being seriously stoooopid, not sure how much need there is to set MerchantRef dynamically. More useful would be a hook to let us set the TxnRef directly, as I can imagine situations where I would need/prefer to conform it with another UID scheme, for example if other DPS txns are being routed through a different area of the site which doesn’t use your plugin.
Just out of interest, I had a quick go at hooking the MerchantRef change into gform_confirmation, but couldn’t get it to work – again, I was seeing the default value coming through. Probably just something I did wrong tho, anyway there’s probably no point in pursuing it.
Look forward to seeing any changes you make on setting the DPS parameters!
Thanks again
Cheers
Colin

Hi Ross
Fantastic, many thanks for the quick response – I’ll have a go as you suggest and let you know what works best.
Ah, I just dusted off my DPS spec and of course you’re right about Merchant Ref; what I was thinking of is TxnRef which is why I was constructing a 16-byte key in the first place :/ Duh… Yep, I guess so long as you set that to the Lead Id that is doing what I was trying to anyway!
Cheers
Colin