Hi there,

I'm currently developing the Card on File 2.x integration for Beanstream and would love to co-maintain the project. It would probably be best as a 2.x branch as it is a partial refactoring as well. When I'm finished shortly I'll upload it in a sandbox.

Best,
JP

Comments

fp’s picture

fp commented

Hi JP - Please let us know when your sandbox is up. I have little time on my hands these days so I like the idea of a potentially invested co-maintainer.

Cheers,
fp

jpstrikesback’s picture

jpstrikesback commented

Glad to hear fp! It should be up either really late tonight or midday tomorrow depending on how much coffee I can handle ;)

Cheers,
JP

jpstrikesback’s picture

jpstrikesback commented

Multi currency with Beanstream is a pain...and delaying my sandbox but likely end of day I'll have it up...

jpstrikesback’s picture

jpstrikesback commented

OMG I can simply clone the payment method and setup enable conditions and not worry about currencies...wowza #facepalm

jpstrikesback’s picture

jpstrikesback commented

Here is a start, more on the way (mainly regarding some cleanup/refactoring & Card on File Update/Delete):

http://drupal.org/sandbox/jpstrikesback/1989622

joshmiller’s picture

joshmiller
he/him
Primary language English
Location Indianapolis, Indiana, USA
commented

What happened to the progress? Has fp had a chance to try out the sandbox above? Is jpstrikesback willing to co-maintain?

:D

jpstrikesback’s picture

jpstrikesback commented

Actually I'm done cardonfile, and a bunch of other items like the abilty to choose between Profile per card or multiple cards per profile (important because only one address may be stored remotley per profile), and duplication handling settings (beanstream allows one to switch between having/not having duplicated card info on separate remote profiles, which could lead to some confusion if the setting was ever switched). I just need to push it all.

I'm still willing to co maintain for sure as I am actively using this. My fork isn't yet battle tested but will be shortly. One thing about my fork is that it uses some partially documented/undocumented methods to achieve some sanity regarding billing profiles and multiple cards (IMO) but beanstream support has told me it is forthcoming.

jpstrikesback’s picture

jpstrikesback commented
Status: Active » Closed (works as designed)

As I've been finishing / cleaning this up I realize that my fork is very specialized as it includes so many edge cases, to the point where I'm not sure I want this out in the wild just yet, not without some more refactoring and a bunch of testing. For now I'm going to withdraw my request until this thing has been put thru it's paces.

Best,
JP

Horroshow’s picture

Horroshow commented

We're using Drupal Commerce with the Beanstream module. I can't code but I would be thrilled to test it with the Card on File module. I'll check here regularly to see any progress.

spiderman’s picture

spiderman
he/they
Primary language English
Location Halifax, NS
commented
Issue summary: View changes

I've just pushed a 2.x branch of the module which includes Card on File integration. Take note, this branch's core Beanstream functionality is a complete rewrite from the 1.x branch, so things will most likely not work exactly the same (settings, etc). I would completely disable/uninstall the 1.x version of this module before installing the 2.x branch.