Hi LindaGLS,
I have been called into troubleshooting this case that looked like a bug at first glance, but that neither Kyle, nor me could reproduce locally (in fact on Joomlapolis we do use Promotions+Taxes, and they both work fine combined).
My first step was to got at history and logs and check for errors.
I found many errors like this one:
Code:
loadSomething::plan id: 10 is missing in database for subscription id: 36
This means that you have subscriptions using Plan number 10, but that plan got deleted.
Now it is impossible to delete a plan with existing subscriptions through the CBSubs admin area. There is a specific check to make such database inconsistencies impossible. We also tested again this check that exists since CBSubs 1.0 and before, and you get an error message like:
Cannot delete row id 10 because: Subscriptions exist for this plan
This means with a 99.99% probability that the plan got deleted in the database directly using phpMyAdmin or another tool.
Now i'm not saying that this is the cause of your issue, but my big question is "What else has been modified directly in the database ?"
It is our policy to help as much as possible our customers for free, but when we are in presence of modified files or database structures or entries, we are sorry that we cannot do the integrity checking and fixing for free.
This will require probably 1-2 hours of trouble-shooting and fixing at our consulting rates published in Services tab on our
main Support page
. If you wish us to go forward, please follow the link and purchase 1 hour to start.
Your other possibility, IF the site is not live yet, and there are no active customer subscriptions and payments, would be to uninstall CBSubs, then delete in the database all tables starting with jos_cbsubs_ and re-install CBSubs and re-configure a clean installation (supposing that CB hasn't been changed). But if there are subscriptions, DO not do that.
Btw, It would have helped a lot in providing you better and faster service, that if you did changes in the database directly or in files (or had a major database server crash if no changes have been made) to tell that in the support thread, as it would have saved our support team several hours of frustrating work trying to troubleshoot something that works fine (on a non-modified installation).