wetzel Posted June 7, 2021 Share Posted June 7, 2021 (edited) On our site, some pages are planned which will be accessible to visitors who make regular subscription payments. After quite a bit of research, it seems that the Paywhirl resources will be the best for us for managing subscriptions. I don't know if these changes could ever formalized into a full Add On, but I will keep a diary of the process and trouble shooting for the benefit of anyone in the future. We are integrating their solution as much as possible. Although full cart integration is not possible, our site will be storing a customer's Paywhirl credentials in our own oscommerce tables and interacting with Paywhirl through their PHP kit using webhooks and jSON objects, so that, for example, regular oscommerce log-in will be able to determine a customer's subscriber status. I've written mountains of bad PHP in my life, but some of this stuff will be new to me. I'll try to record our progress in this thread. Also, issues may arise for which I am hoping for the assistance of others. For example, Paywhirl utilizes Composer ("a tool for dependency management in PHP. It allows you to declare the libraries your project depends on and it will manage (install/update) them for you."). This is already installed on our server. I don't think that the oscommerce libraries rely on Composer, though I could be wrong. I am just new starting the process of learning about Composer, and I am interested to hear if anyone has encountered compatibility issues with Phoenix. Thanks! Edited June 7, 2021 by wetzel Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.