Hi Everyone,

I have worked with uc_recurring in the past, and have a few questions about how I'd like to use it on a new project...

* Is there a good way to get uc_recurring to support multiple products per order recurrence? I see the new uc_recurring_order module. But, uc_recurring seems to be geared toward one product per order. Also, I've had some difficulty with allowing users to change even that one product in the past. They way uc_recurring clones the initial order, then builds the new order object, seems to act funny if I don't update the initial order and the uc_recurring_users table entry.

* I'd like to give customers the ability to edit and change their recurring order. For example, change it from every 1 week to 2 weeks. Or, change the products in their order from one set of items to another. Or, add or remove products. Has anyone created any sort of "my recurring orders" tab from user's account pages, where users can see their recurring orders, and edit what's in them.

* Some items that people can add to orders may become out of stock. If that happens, I'd like users to select "backup" options, that will ship instead of their first choice.

I'm sure I'll have to do some work for all of this, which is fine. Just wanted to see if anyone else had thought about this, or was trying to do the same thing. I'm figuring I'll create some tables to store user order preferences, make a forms api front end to those tables, and do a hook_recurring_renewal_pending() implementation to load items in as recurrences happen.

The new uc_recurring_order module that comes with alpha 4 seems like it sort of does some of this. Mainly it doesn't seem like it's made for users to go back and edit their order. Also there isn't the fallback items thing I want, but that's is pretty specific to my needs.

I'm comfortable with forms api and drupal dev work, and I have some good help on this project. But, I wanted to see if anyone had any existing work to share, ideas, warnings, etc. Especially since I'd like to contribute what I come up with when it's done.

thanks,
Paul

Comments

univate’s picture

univate commented

The -dev version has taken things further and now uc_recurring does nothing on its own, there are separate modules for uc_recurring_products and uc_recurring_orders which are the modules that actually provide the front end feature and uc_recurring is just an api for the recurring payments side of things.

The features your are looking to develop would not be complex and definitely make sense to add into uc_recurring_order (I think at the moment if the gateway support 'edit' operations as an admin you can view what the user has in their orders form that link (check with the test_gateway), the next step is make those details editable.

kevinquillen’s picture

kevinquillen commented

Is there a way to make the recurring fee on a product optional during checkout per product instead of against the order?