Hey Recrit,

Really interested in what you are doing here as it's going to make some pay to publish and recurring payment scenarios much easier to implement. I'm just wondering if you have a roadmap that you can make public so I can know when to jump in the water.

Cheers!
JP

Comments

recrit’s picture

The development on this forked version is winding down now. The next step will be to merge it back into the main project, exactly how is undecided... ie 1.x, 2.x, etc.

jpstrikesback’s picture

Looking great, thanks for all your work!

jpstrikesback’s picture

One question:

Is there a reference implementation of all the new functionality anywhere public?

Cheers,
JP

recrit’s picture

none right now since a lot of the new features really depend on the gateway module implementing it.

recrit’s picture

@jpstrikesback,
I just pushed an example payment module that demonstrates all the new card on file integration, "commerce_cof_payment_example".
http://drupalcode.org/sandbox/recrit/1810130.git/commit/4eb30a7

jpstrikesback’s picture

Frigging awesome! I owe you a beer or 6!

rickmanelius’s picture

I was just about to ask about an example gateway... nice!

I just posted a request for the "Create Callback" for the commerce authorize.net module #1850100: Add "create callback" functionality for Commerce Authorize.net. I can test beforehand, but my budget on this is limited to getting this to work with that module, so I'll focus my efforts there. But I just wanted to say thanks to @recrit for doing all the heavy lifting so far!

rickmanelius’s picture

BTW @recrit, is there a final punchlist of items/issues that need to be addressed/tested before an official launch (or merge with the official project)? I'm have approximately 4-5 hours worth of budget that I can dedicate towards this because its' a necessary feature/functionality for one of my clients and I'd hate to use it in production without knowing it's going to be officially supported.

Please feel free to ping me in IRC (my IRC handle is the same as my d.o. username) and I can provide additional testing, etc.

recrit’s picture

not really anything pending todo, although, more testing is always welcomed.
I had merged both projects' git history, so really just up to the main module maintainers to decide.

rickmanelius’s picture

Hi @recrit. I've pinged the thread tracking this at the main module. But while we're waiting, are there any issues that you would consider as release blockers at this time? I just want to make sure if/when we get Ryan's attention, we can push for a merge immediately instead of needing a) needing to fix some additional items and then b) waiting for our next opportunity to get his attention!