When setting up a MageBridge/Joomla! shop, enabling Joomla! SEF in the Global Configuration is a must. The reason is simple: Magento uses SEF URLs by default, and for MageBridge to succesfully integrate Magento into Joomla!, Joomla! needs to use SEF URLs as well. But because Joomla! and Magento create SEF URLs in different ways, there could be instances where the two mechanisms are conflicting - resulting in Magento 404-errors. This tutorial explains why and how to prevent this.

Read more: How Joomla! works with MageBridge URLs

The MageBridge extensions offer you a lot of different solutions, but sometimes you might make a mistake that renders your entire Joomla! site offline. You might be locked out of your Joomla! Administrator, or the entire Joomla! Administrator might be even unavailable. By setting MageBridge offline through the database, you might be able to restore your access to the Joomla! Administrator.

Read more: Setting MageBridge offline through the database

The feature URL Replacements allows you to replace Magento URLs with Joomla! URLs. This can be useful for replacing Magento product-pages with your own CCK-built catalog, but perhaps also for replacing pieces of functionality of Magento with Joomla! extensions (for instance the wishlist). URL Replacements uses a simple concept but it has some side notes, when you want to use it in practice.This tutorial explains the bits and pieces.

Read more: Working with MageBridge URL Replacements

With MageBridge, new users are automatically synchronized: If a new customer has been created in Magento, MageBridge will automatically create a corresponding user in Joomla! - as soon as the user logs in, or as soon as the user-record is edited in the backend. But if you have an existing userbase that you want to migrate at once, you need to follow a procedure which is a bit more complex. This tutorial helps you out.

Read more: Importing and exporting users

Within Magento, you need to create an API-user for usage with MageBridge. This API-user is connected to an API-role, and this API-role implies a set of permissions (Role Resources) to certain parts of Magento. To make it easy to configure, we recommend to select just all permissions for the API-user. But if you want to increase security, you need to know which resources are needed to run MageBridge. Here's a listing.

Read more: API permissions with MageBridge

Within MageBridge, plugins are used to do all kinds of things: With Product Plugins you can do something in Joomla! when a Magento product is being sold. This opens up for tons of opportunities, like selling access to DOCman downloads or adding a customer to a certain JomSocial group. Here are some general guidelines for Product Plugins.

Read more: Using MageBridge Product Plugins

The Magento multi-site concept is flexible but a little complex. It uses three levels which can be used in various ways: Websites, Stores and Store Views. Within the MageBridge Configuration the entire Joomla!-side of the bridge is configured as a Website. But within this Joomla! site you can still use Stores and Store Views for various purposes. For instance: To load a different theme.

Read more: Using MageBridge stores to load a different Magento theme