Yireo tutorials

Learn more about Joomla!TM and Magento
You are here: Home Tutorials MageBridge MageBridge administration Configuring payment methods in MageBridge

Configuring payment methods in MageBridge

Configuring payment methods in MageBridge is nothing more than just configuring the payment method as you would in MagentoTM, except that the URLs you might need to configure point to Joomla!TM instead of MageBridgeTM. Let's walk through all the steps.

The MageBridge URL equals the Magento URL

Make sure SEF is enabled in Joomla!

When you use MageBridge on your site, the usage of SEF URLs is highly recommended. SEF URLs (Search Engine Friendly URLs) can be easily switched on within the Global Configuration in the Joomla! backend, while they are switched on by default within Magento.

Using SEF, MageBridge can fully integrate any Magento URL into Joomla! URLs. It does so by taking the root from the MageBridge shop and appending the Magento URL to it. This way you can easily translate a Magento URL into a Joomla! URL and vice versa. The first step here is to configure a MageBridge Root Menu-Item.

The MageBridge Root Menu-Item

Let's say you have a Joomla! site "http://JOOMLA" running and have a Joomla! menu configured. Within the menu, you will need to point a Menu-Item towards the MageBridge Root (which acts as the Magento homepage). The alias of that Menu-Item is used to create the Joomla! URL. For instance:

http://JOOMLA/shop/

Translating URLs

Now, if you navigate through the webshop, you might end up on the checkout-page which has the following URL:

http://JOOMLA/shop/checkout/cart/

Here, the Magento URL "checkout/cart" is appended to the URL of the MageBridge Root "http://JOOMLA/shop".You can easily navigate to the page within Magento stand-alone by typing the following:

http://MAGENTO/checkout/cart

This method for translating URLs can be very useful when you need to troubleshoot a certain behaviour in MageBridge, or when you need to configure payment methods.

Configuring a Magento payment method

Now, the story above is ment to guide you through the process of translating URLs. But every Magento payment method has its own way of being configured, so for the actual configuration of a payment method we have to refer to the documentation of that payment method.

The main point is that everytime when the manual tells you to enter the URL of your webshop somewhere, it needs to be the translated MageBridge URL and not the original Magento URL.

Example: PayPal

For instance, with PayPal you will need to configure a Return URL like the following:

http://JOOMLA/shop/paypal/standard/success

Example: Ogone

The same that applies to PayPal, applies to Ogone. Note that there are several different Ogone modules that have different procedures. The example below is for the official Ogone extension:

http://JOOMLA/shop/ogone/api/placeform

If you have configured the Ogone extension and after a MageBridge checkout you arrive in the Ogone portal which gives you an error message "unknown order/1/r/", this means you have configured the MageBridge URLs correctly in your Ogone control panel.

Example: Google Checkout

The same that applies to PayPal and Ogone, applies to Google Checkout. Make sure the API Callback URL is entered as follows:

http://JOOMLA/shop/googlecheckout/api

Understanding Magento multi-site

Working with MageBridge assumes you understand the multi-site mechanism of Magento. The Magento Configuration can be configured on a global level, but also per Website or per Store View. MageBridge will override the configuration in run-time by setting all URLs to their Joomla! equivalent automatically. You don't need to modify the Magento Configuration to make MageBridge behave this way.

Still the multi-site mechanism can be used to configure some settings specifically for MageBridge (using the scope for that specific Website or Store View) while using other settings for the Magento stand-alone configuration. This is not specific for MageBridge, but this is specific for Magento multi-site setups. For more support we have to redirect you to Magento.

Warning for sh404SEF

sh404SEF is a third party extension for Joomla! and it allows you to customize SEF URLs. But the technique used by sh404SEF requires you to call any page through Joomla! System URL first ("index.php?option=com_xxx"). Only then sh404SEF is able to cache and generate a new SEF URL.

Any SEF URL created outside of the sh404SEF logic will result in a 404 page. Now most Magento URLs will be created outside of the sh404SEF logic and therefor pose a problem. MageBridge tries to do its best, but this will require you to turn off the MageBridge setting Forward SEF.

Now, this will create always URLs in the form of "index.php?option=com_xxx" so they can be translated by sh404SEF. Unfortunately a lot of Magento payment methods strip such an URL to "index.php" to add their own parameters, causing the URL to stop functioning. The only workaround here is to add the payment method URLs as static URLs to sh404SEF. This is complicated and unsupported, therefor we do not recommend the usage of sh404SEF together with MageBridge.

Artio JoomSEF supports the original Joomla! SEF completely, and is therefor fully supported with MageBridge.

Tutorials on MageBridge administration

Tutorials on MageBridge integrations

 

Payments Methods

Payment Methods