2082 Posts in 1002 Topics by 452 members
|Go to End|
5 March 2014 at 8:20am Last edited: 5 March 2014 8:44am
After setting up and developing with the latest SS code base, SS-shop, omnipay and its dependencies, I seem to be having some trouble and find myself meeting with confusion around getting the paypal payment gateway to work properly.
I could use some help! (either pointers to example docs that are current, tips here in forum, or any other means I can access right now that are most likely to lead to getting up and running with this ASAP):
1. To Know for certain what is current and production ready in this setup
2. To understand the best way to get this setup live for processing paypal payments in the here and now
3. To effectively debug problems in general with this setup that may arise
After reading through all I can find on SS-Shop I'm presently confused about what is a current viable production ready solution for SS3.1+
If I understand correctly the mod is undergoing some substantial changes and developments right now based on what Willr discussed in another topic in recent months? Anyone know what the situation is there as of today?
In a nutshell, I'd like to know if this omnipay solution actually works in the 'dirty here and now' or is still considered to be in testing etc?
If it does work I'd like some guidance on exactly what I need to setup in order to get payal payments up and running successfully (so far I tried the yml config with both live and sandbox paypal accounts and I receive a security header warning)
If it does not work yet fully, I'd like to know my options, as I currently have this setup installed and ready to hit production, and as I understand it the solution that used to work is the payments module but that is no longer a viable dependency in composer install.
Its all rather unclear right now and I'm hoping someone can help me get straight with this! Many thanks : )
8 March 2014 at 3:17am
After pulling in breaking changes (composer), we branched just before here: https://github.com/burnbright/silverstripe-omnipay/commit/8882a7a4e769b69b1b0b19cdc069e527679428f5#diff-dca4c8dd54277aadc2721776bb521a40
This is what Mark mentions here: https://github.com/burnbright/silverstripe-shop/issues/1#issuecomment-36945361
I can't answer if the latest code is working now. Sounds like it is not according to: https://github.com/burnbright/silverstripe-shop/issues/1#issuecomment-36966349
19 March 2014 at 12:02am
Appreciate your insights!
A brief update: there have been a number of code changes in past few days to shop and omnipay so pulled in those, though still have same error.
However, reading briefly the code changes you present in links here, it triggered an obvious thought about PHP versions, checking on their server (doing this is a favour for a collective of organic farmers) they're running 5.2.* hmmm?!
Asked them to upgrade to 5.3.2 (as that appears to be current SS requirement in json)
Will find out if this fixes/changes anything and write back...
26 March 2014 at 11:17pm
No, I can confirm I still have same error on paypal payment submission as before, after upgrading php to 5.3.2
Here is the current github thread for anyone encountering similar difficulties with SS-Shop and Paypal: https://github.com/burnbright/silverstripe-shop/issues/1#issuecomment-36945361
Anyone know how to solve this?
@Cumquat reports it is working with live paypal but not sandbox, I don't fancy doing setup and testing with a live account though right now it seems there are not many options left to try...
|Go to Top|