Tyler J
Tyler J
Same issue, fixed it by replacing `return $matches['token'];` with `return explode(";", explode("Set-Cookie: t=", $html)[1])[0];` and commenting out `throw new Exception('Cannot extract login CSRF token.', self::CODE_SCRAPING_LOGIN);` in dropboxUploader.php but now i'm...
@Tms157 That's cool, I'm excited! Any date when the next update will be?
@Tms157 Personally for me I'd probably go for the OOP Version!
@Tms157 that's cool, that's cool! I'm looking forward to it, best of luck!
I've been reading into this too, they mention having v1 as a fallback in case v2 fails for any reason but I'm not sure if that fallback will still exist...
Sagepay and their docs are just not good at all. I'm currently using Sagepay Direct via `dwmsw/sagepay` but depending what has to be changed I'm thinking of switching to omnipay.
This whole thing has still left me a bit confused (hopefully I'm not the only one!). I'm currently using the direct integration (without iframe) - is anything/much changing with that...
@judgej Thanks for the recommendation, I'll definitely take that into consideration and more than likely switch to this repo and SagePay Server. My understanding right now is from the 14th...