jroper wrote:
The invoicing does need some work, and this is an area that will be vastly improved in 1.4. We have a plan !!
Meanwhile, you may have to deal with post-pay billing outside of A2Billing in the short term, to ensure that you comply with the legalities of your country. This can be done with an export into say MS Access or similar then building your own design template.
In respect of Authorise.net, some may have noticed that it is not perfect, however, we could not test properly as none of us are American Citizens so we could not get a test account. If anyone can offer a sandbox auhorise.net account, We'd be happy to look at it.
Suggestions and requests are always welcome.
Joe
I just thought maybe someone has already addressed these issues on their system and willing to share the actual code
1.4 is great and promising..and far
It's not a problem for me to fix both issues, same I guess for many of us here. The real problem is updating to a newer version of a2b when it comes out. Many of us have little snipets in the a2b already. As for me, I have too much of them and updating to a newer version is a pain for me. Why wouldn't I contribute the code ? I wish I could, but in order to contribute I have to have the latest stable version. If I'll get the latest stable, I'd have migrate all my add-ons and once again check for new bugs and check if all old ones were fixed.
Dont get me wrong here, I'm not whining, just trying to help. From my point of view, before introducing new functionality developers might just fix all bugs and make everything a2b already has work and actually make sence.
P.S. When I'm done fixing Auth.Net module I'll post the code since I dont think it dramatically changed.