kinglozzer on 3
[CVE-2022-29254] Add extra vali… Update unit tests to use Guzzle… Add test to capture payments re… and 1 more (compare)
kinglozzer on 3.2.1
kinglozzer on 3.2
[CVE-2022-29254] Add extra vali… (compare)
kinglozzer on 3.1.4
kinglozzer on 3.1
[CVE-2022-29254] Add extra vali… (compare)
kinglozzer on 3.0.2
kinglozzer on 3.0
[CVE-2022-29254] Add extra vali… (compare)
kinglozzer on 2.5.2
kinglozzer on 2
[CVE-2022-29254] Add extra vali… Merge pull request #2 from silv… (compare)
Payment.allowed_gateways
in your config.
Yeah that't true of course. :) So to use the dummy or manual gateway I just have to run the "composer require omnipay/manual (or /dummy) command and then add the text under here in a payment.yml file in mysite/_config/payment.yml?
Name: payment
Payment:
allowed_gateways:
I was told it could be possible to do it that way but I guess that was wrong then. :) I installed silverstripe with some help some time ago and have only used the same project to practise until now.
Now I have got the two modules installed in the correct folder with composer but sadly it still don't work. But I guess it's something wrong with the database or something else now. It's not easy to learn new things. I had some brainfreeze before and installed the projects to the wrong folder. :D
@sanderha Thanks. I think that is for the PurchaseService when it get a callback from the PaymentService:
(
[ID] => 101
[ClassName] => Payment
[RecordClassName] => Payment
[Status] => Created
[Gateway] => Netaxept
[MoneyAmount] => 94.5
[MoneyCurrency] => NOK
[OrderID] => 110
[Identifier] => 0029xxx....
[Created] => 2018-11-11 12:51:41
[LastEdited] => 2018-11-11 12:51:41
[SuccessUrl] => /min-konto/order/110
[FailureUrl] => /betaling/summary
)
I found that the Omipay ServiceResponse set callback urls like this:
[returnUrl] => http://vestbrygg.lo/paymentendpoint/0029xxx..../complete
[cancelUrl] => http://vestbrygg.lo/paymentendpoint/0029xxx..../cancel
[notifyUrl] => http://vestbrygg.lo/paymentendpoint/0029xxx..../notify
Payment
)