We need to do some fancy footwork with UC role assignment and product kits- would it be possible to get a hook when recurring billing fires so we can add our own logic?
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | uc_payflowpro_roles_hook.patch | 1.11 KB | kwinters |
We need to do some fancy footwork with UC role assignment and product kits- would it be possible to get a hook when recurring billing fires so we can add our own logic?
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | uc_payflowpro_roles_hook.patch | 1.11 KB | kwinters |
Comments
Comment #1
kwinters commentedGive this patch a try. After patching, that section should look like this:
If you define a hook mymodule_uc_payflowpro_roles_renew then it will skip the default uc_roles_action_order_renew call and let you do whatever you want. I didn't test this very thoroughly, so let me know if it doesn't work for you.
Long term, I'm undecided on committing this. It seems like hooking some part of uc_roles is a better plan (may need to file an issue in the ubercart project), because then you don't have to care what the gateway code is doing, and I don't think the 2.x branch is going to call uc_roles_action_order_renew at all anyway (uc_recurring will do that automatically). So, this is really just a temporary situation.
Comment #2
kwinters commented