krileon wrote:
This is an importance and we don't want any to feel it is not as such. It's going to take a lot of implementation due to CBSubs to begin with not having billing address support. Continuing to slam the issue is not helping, just costing us time to reply with the same responses over again.
However, it's not top priority because a feature is already in mid development,
I understand the beating a known issue but I don't think you're hearing the problem..
A: You show that CBSubs Doesnt have Billing Address Support
(IT Does... Invoicing Address will work fine.. Just document this and for US Authorize.net customers make that note.)
B: A feature vs core functionality? Seriously? I'd think Bug / Compliance would trump feature mid stream to repair.
C: I can live with all the above and quit harping on it if we set a timeline / date and treat it like an issue rather than a feature request. Does that make sense?
D: Unfortunately the only reason we chose CBSubs we because it Had Authorize.net Support and now it seems that it doesn't exactly have that without extra liability and penalty does it!?! We don't have a Paypal account and didn't want to have another service to manage when we had one that was supported!
So I plan is merely to get an assigned timeline and yes distract from FEATURES when the CORE has a bug or omission like this...
Maybe say like our expected bug fix is 3-4 weeks?
When I would prefer to see something more like 1-2 Weeks max... Where just passing the Invoicing Fields through to Authorize.net
Post edited by: hmossessi, at: 2009/10/08 00:44
EDIT: changed subject back to thread subject
Post edited by: krileon, at: 2009/10/08 14:17