 |
Ubercart |
|
|
|
||
|
Tue, 05/26/2009 - 15:29
 Hi all, I'm in the process of setting up a subscription based site (Drupal 6/Ubertcart 2). I'm wondering if anyone else around here has done such a thing. I'm trying to figure out what the difference between uc_recurring and uc_subscribe are. Uc_subscribe is not released yet for 6.x, but I've got it mostly ported. Just wondering if there's something really compelling about using it vs recurring fees and role assignments. thanks  
Re: Subscription-based sites: uc_recurring vs uc_subscribe
I'm also interested in this subject. I want different membership levels for users and have the fee be automatically recurring (with admin or the user to be able to change the fee before the next billing cycle). I'm trying to decide how best to do this. Spreedly? (www.spreedly.com) uc_recurring? uc_subscribe? I'm not sure how to start the discussion, except to ask if anyone else has done something like this.
Re: Re: Subscription-based sites: uc_recurring vs uc_subscribe
I've been in uc_subscribe's code for a few days now.. I'm not really feeling confident about it. I'm kind of beginning to reconsider and go the uc_recurring route. I'm still investigating. uc_recurring is a stable D6 release, uc_subscribe is not but has a few patches available for it. I've already seen some pretty big bugs with it, though.. Your need sounds similar to mine. I'm thinking uc_recurring in combination with uc_role. Seems pretty straight forward: Create a role for each of your membership levels, and create a product node with a role assignment feature that assigns the respective role along with an expiration point. |
|
