Has uc_sagepay_token (sub-module of uc_protx_vsp_direct predecessor) been updated for Drupal 7? And is it likely to be?

Comments

hiraethmarkb’s picture

Title: Sagepay Token » Integrate Recurring Fees (was Sagepay Token)
StatusFileSize
new37.49 KB

(Follows on from #585482: Integrate Recurring Fees with SagePay Payment Gateway)

To expand upon my original post, which was made hastily, and ends up being unnecessarily terse for which I apologise.

The reason for the question is that the company I work has been looking at updating both the uc_sagepay_token and recurring fees integration in Drupal 7 for a project that we are working on. With aim being to submit the changes as a patch, for possible inclusion in the module.

Taking the D6 version, we have got so far through, but are hitting similar issues as jahmal in #585482, where we get the error "Checkout cannot be completed without any payment methods enabled. Please contact an administrator to resolve the issue." (see https://drupal.org/node/585482#comment-3626320).

Has anyone attempted anything similar, or may be able to point us in the right direction?

(I have attached a patch file of our current changes - non-working.)

leewillis77’s picture

StatusFileSize
new35.88 KB

Just as an update to this - we've now resolved the checkout pane issue, but seems like the token isn't being saved correctly into uc_sagepay_tokens. Current patch attached. We'll continue looking at this as and when we get time, but any advice welcome in the meantime!

leewillis77’s picture

StatusFileSize
new38.85 KB

We've now got this "working". The code could do with a bit of a tidy-up, coding standards review, and removing temporary debug code, but I'd love to get some feedback on it as it stands.

hiraethmarkb’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

Setting status to'Closed (outdated)' as SagePay no longer support v2.23 of the protocol.