In the readme I noticed it needs a recompile of nopCommerce source. Is this really neccessary? I mean, it should be possible to write an extension without the need for recompiling? (why call it an extension then?)
In the readme I noticed it needs a recompile of nopCommerce source. Is this really neccessary? I mean, it should be possible to write an extension without the need for recompiling? (why call it an extension then?)
Thanks!
I intend to integrate the Ogone Payment plugin in 1.9 and it does indeed require a recompile of the source. Also bear in mind that the current plugin is only for version 1.2. It needs an update urgently !
I was working on a port of some Ogone code as well, but I kept running in to the problem that the user was redirected to:
https://secure.ogone.com/nopcommercedev/
instead of:
https://www.myshopdomain.com/nopcommercedev/
after completing the payment.
I think the problem is related to the view that I return in my post payment handler.
According to ogone I was sending a relative url instead of absolute url in my redirection response (the url in ACCEPTURL is set correctly, it's just the redirection response of the post payment request ):
Yes, I am planning to have a look at the new Nopcommerce 2.5 version and release a new version of the Ogone Payment Plugin in the next few days if everything goes according to plan...