My next release kept growing and I have been getting so many good ideas for some nice features to add to it, that I decided it would be best to split it up and release some of the changes as soon as possible, so you will have them sooner rather than later, and then do the bigger release, with all the additional database changes and new features a little later this year, hopefully still by the end of Spring, depending on how much I decide to include in it. So you'll be seeing a version 6 update within the next week with some of the more important updates, and then version 7 later this year.

Of particular note is that this update will not allow any storing of credit card data at all out-of-the-box. I looked at trying to improve the encryption and other security measures to allow this...but there is so much more required under PCI Compliance regulations that I can't handle at a software level, and from my past experience, I know most people won't bother to do, putting both their customers and themselves at risk, so it really is not something I can leave as an option in the software. So if you have need to be able to do additional transactions on credit cards (including recurring billing for memberships) you will need to use a processor like Shift4 that uses tokens instead of storing card data. I may look at using recurring billing APIs such as Authorize.Net has in the future...but these APIs do not offer as much flexibility and many features would not work with them, so it's a bit harder to support them.

If you have questions or concerns with updating to the new release and how this will effect your own store, please feel free to contact me.