Leaderboard

Warming up the beta forums. We've scheduled Beta 1 to start next Thursday, September 15th. We've had quite a few issues pop up with regard to the minPHP upgrade, and we're really close to having those all resolved. That's not to say we've caught everything. Being a major release, please consider 4.0 beta 1 more of an alpha, and do not under any circumstances run it in production. Looking forward to it!

The libraries provided by providers often leave to be desired, and are not used by other projects. E.g. they fail to include unit tests that simulate requests and responses. As far as my module goes, it only implemented a small subset of the gateways as a proof of concept. For things like merchant gateway support, tokenization (think stripe.js), securecode/3dsecure, and recurring payments changes to Blesta core code would be necessary.

That may work for small code modifications to core modules, but doubt many professional developers would do so for modules they created themselves. It is more common for developers to retain their rights, and even if the client paid to have something custom developed to only grant them a license. Why? Well, it prevents the developer getting sued, if he ever does a similar looking project for another customer. Would personally rather see that Blesta stopped using their own propitiatory modules for things like handling payments, and switched to using something more standard like the Omnipay library. There is no way Blesta or any other billing system can properly test modules for gateways they are not using themselves. So using something used by more projects makes sense. And yes, that would mean the competition could use the exact same set of modules. But so what, find something else to compete on...

Plugins and other extensions should be backwards compatible yes.. but you should *test* this. We've run into some issues where our plugins were not working properly and have had to make adjustments to the minPHP bridge. As Mike mentioned, you may want to update your buttons in your plugins to use the new Bootstrap ones, but if you don't they should still work. Test, test, test, everything you can think of. It's possible we missed something, and being a major release, this version requires extra scrutiny.

Yes they will, the design for v3 modules UI will look a bit weird with the old buttons etc, but it will work that's why they've taken so long to ensure minPHP 1.0 is backwards compatible

A customer reports that the Invoice ID, rather than the Invoice Number is passed along to Stripe. This number is then included on client's credit card statements. It's possible that this issue exists in the official Stripe gateway as well, but I thought I would mention it here in case @Cherry doesn't mind taking a peek.