Is it possible to use Ogone on a multilanguage site? We have a webshop on .com and .nl through internationalization.

For example, in the Ogone backend we need to fill in 'http://www.yourdomain.com/cart/checkout' under 2.2. Is there a way to send the user back to http://www.yourdomain.nl/cart/checkout when they came through the checkout on the .nl website?

Currently we get the code back 'unknown order/1/r/'

Comments

keesje’s picture

Title: Multilanguage site » Multi return URL
Status: Active » Needs review

Changing title to "Multi return URL". This does also apply to multi site setups and other configurations where more than 1 fixed return URL is needed.
This should be fixed in the current CVS release. Please review.

keesje’s picture

Status: Needs review » Closed (fixed)

Please reopen if still relevant.

robbertnl’s picture

Version: 6.x-1.9 » 6.x-1.4

For me still relevant. Using the latest stable release (1.9).
Defautl language is working but when switching to other language OR using HTTPS, i am getting this error:
unknown order/1/r/ (on checkout page).

My bad: I had an url in the ogone configuration.

robbertnl’s picture

Version: 6.x-1.4 » 6.x-1.9
Status: Closed (fixed) » Active
robbertnl’s picture

Version: 6.x-1.4 » 6.x-1.9
Status: Active » Closed (fixed)
wjroes’s picture

Same issue here. I am in the processing of asking Ogone whether it is possible to use parameters combined with the "Direct HTTP server-to-server request" method. Probably not, in which case I will try the "browser redirect" method. This allows you to provide return-urls together with your request.

UPDATE
I tested the "HTTP redirect in the browser" and that does work. It submits following parameters to Ogone:

'ACCEPTURL' => url('cart/ogone_return_ok', array('absolute' => TRUE)),
'CANCELURL' => url('cart/checkout/ogone_cancel', array('absolute' => TRUE)),
'CATALOGURL' => url(variable_get('ogone_catalog_url', 'catalog'), array('absolute' => TRUE)),
'EXCEPTIONURL' => url('cart/checkout', array('absolute' => TRUE)),

So basically the default paths prepended by the actual domain from which the request is made. The redirect from Ogone is made to the actual domain the request originated from. I did not see any strange behaviour on Ogone side either.

I am using uc_ogone version 6.1-1.x-dev but I do think this works similarly in the 1.9 version.