Active
Project:
UC Recurring Payments and Subscriptions
Version:
6.x-2.0-beta1
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Jan 2012 at 22:46 UTC
Updated:
17 Jan 2012 at 19:22 UTC
I am using authorize.net with CIM and am now finding that since I upgraded to the 6.x.2.0-beta1 version of uc_recurring and ubercart 6.x-2.7 recurring transactions are NOT being created.
I have had uc_recurring working flawlessly for a year or so now.
This is obviously a major issue. I am happy to provide any input/logs etc I can if someone can guide me as how to do it.
Comments
Comment #1
paulcoghlan commentedAs an aside if someone can indicate whether it is possible to manually create the records required in the tables to replicate what should have been created it would be helpful. It would appear uc_recurring_users is the table of focus.
Comment #2
westwesterson commentedWhat sub uc_recurring modules you are using will effect how it is set up, and also what underlying tables are being used.
For instance, if you are using recurring products, you should check to see if you have your features enabled on each product. And this would also effect your uc_product_features table.
In addition you should look at the uc_recurring_product table for both the uc_recurring_product and uc_recurring_subscription modules.
If you are using uc_recurring_products to manage when roles are given and taken away, you will also need to look at the uc_roles_expirations table.
I am also using the Authorize.net CIM method and have an install of uc_recurring running fine with recurring subscriptions. We changed a site from using recurring products to recurring subscriptions due to some issues with how roles were given and taken away in the product model. (it was an excellent decision things are so much easier to maintain now.) This was done entirely in the database, so yes it is possible to add in users via the database.