We are a team of two (one primary programmer) providing a free plugin which combines multiple payment gateways that have to develop and maintain. As much as I wish we could, we can’t make everything perfect over night.
As displayed in the plugin, the PayPal Plus integration is considered BETA because it has not gone through the extensive testing that would typically do. This is because it’s hard for us since we are not in Germany, can’t read German language, etc.
What we have done is follow the documentation as closely as we can to integrate the product, and we’ve followed standards to make that work with WooCommerce as well as we can. It’s possible we missed something.
So, we appreciate the feedback and will do our best to get that resolved in a future update, but calling us irresponsible is a little bit disrespectful if you ask me.
Also, if you’ve made improvements to any code you should submit a pull request back to our GitHub repo so we can merge those changes into the plugin. It’s with help from developers like you that open-source projects like this can grow.
So instead of griping, please, help us out! 🙂
Otherwise, we’ll address as quickly as we can. For now, I’ve added this to our 1.2.1 milestone on GitHub. We’re about to release the 1.2.0 update for the plugin, and then we’ll be working on that.
I can understand all things but actually when i solved a bug another one is coming. Right now i am facing another issue which is that when user completed his payment through credit card(paypal plus option) he redirected order-received page but with “0” order id which is wrong.
Another one is when user select paypal option for for payment he is redirected to homepage instead of paypal plus’ payment page.
Can you help me out for both these things? I want to know how can i solve these things so that i can implement in that way.
I solved some order calculation issue but it is not a proper way to implement in plugin so it should be not commit to GitHub repo.
Thanks
Regards,
Brijesh
Are you running the release branch code from our GitHub repo? I believe we’ve fixed those issues there already.
We’ll be releasing 1.2.0 soon, but if you want to grab it early you can download it here.
