Closed (won't fix)
Project:
UC Recurring Payments and Subscriptions
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 Jun 2009 at 01:58 UTC
Updated:
3 Sep 2009 at 05:35 UTC
Comments
Comment #1
univate commentedComment #2
acsubscribing and reviewing
Comment #3
reubenavery commentedHi,
There were still numerous problems I was finding and ended up putting quite a bit of time into a pretty thorough attempt at getting this uc_recurring 2.x working with uc 2.x and authorize.net ARB.
I put two mutually dependent patches for uc_recurring and various uc core modules up over yonder: http://drupal.org/node/454952#comment-1730126
I thought it would be best to keep them together due to a change I made in hook_order
Comment #4
matt2000 commentedsub
Comment #5
brentratliff commentedGiving it a shot with uc_credit and the Linkpoint API module.
Comment #6
brentratliff commentedAbandoning Linkpoint for Authorize.net, Linkpoint will not work behind load balancers.
Comment #7
socialnicheguru commentedsubscribing
Comment #8
amitaibu@univate,
I think this whole patch can and should live in uc_recurring. Since this module is now in contrib, ubercart doesn't need to implement it's hooks.
A few module_exists('uc_credit') or seperating the code to include files can do the job. For example:
Comment #9
univate commentedThats an interesting idea...
The one issue I have is that I don't want uc_recurring to be tied to any specific payment gateways, I see this module as a an API for payment gateways to implement recurring payments/billing in ubercart.
At the moment ubercart includes a number of payment methods/payments (which I think probably shouldn't be there, but thats a different issue), a number of these have ways of implementing recurring functionality: paypal, authorizenet, google_checkout, 2checkout - are you suggesting we should include all the recurring payment interfaces for these as well in uc_recurring?
Comment #10
amitaibu> The one issue I have is that I don't want uc_recurring to be tied to any specific payment gateways, I see this module as a an API for payment gateways to implement recurring payments/billing in ubercart.
Think of it as Rules module is doing. It provides an API for other modules, but also implements actions/ conditions for Drupal core's module.
uc_recurring could be the same - providing an API, and in a subfolder, it will implement Ubercart core's payment modules.
Comment #11
jday commentedI would love to test this out, I have
UC 6.x-2.0-rc3
Recurring Fees 6.x-2.x-dev
and an Authorize.net ARB account
do I need the patch from the head of this thread on the dev version for recurring fees to work?
Comment #12
bearstar commentedI have everything working OK using authorize.net and CIM but I wonder when I would expect to see items listed at /admin/store/orders/recurring
Would authorize.net Test mode transactions show up there?
Comment #13
murokoma commentedI am a bit confused here - the patch is for the test gateway, right? But doesn't it say in the beginning that this is for the uc_credit module?
Sorry about this, I'm neither into patches nor programming :-)
Thanks for your help!
Comment #14
murokoma commentedI'm sorry, I got it when performing the test, asked for the other two files and patched them correctly.
However, after uploading them nothing seems to happen; is there any "idiot-proof" explanation on WHAT to do ? :-)
Comment #15
univate commentedThe patch here is going to become redundant when this patch is committed:
#534296: Make uc_recurring completely independant from ubercart, uc_recurring will handle all ubercart core payment methods via inc files
Comment #16
univate commentedThis is no longer required, uc_recurring now includes the uc_credit and test_gateway code so you can test out this module without any need to patch ubercart.