When you want to sync users between Joomla! and Magento, there are various methods that could be used (CSV-exports, custom scripts, Vm2Mage). But one of the cooler ways is to rely on MageBridge event-forwarding. Simply trigger a customer-event and let MageBridge do the rest.

Read more: Syncing users with MageBridge event-forwarding

MageBridge requires Magento to work as it was intended - but third party extensions (or third party developers) can cause harm here: The Magento architecture fails, and because of this, MageBridge fails. This guide lists some of the bad practices you can check upon.

Read more: Bad coding practices and MageBridge

MageBridge is available through support subscriptions, but its open core is also publicly available through GitHub. This guide helps you to check out the MageBridge sources through Git and use them to setup a MageBridge site. Please note that support is only available to customers who purchased a support subscription.

Read more: Installing MageBridge using Git

While actually the Joomla! plugin-type Magento is much more interesting (because it allows for catching Magento events in Joomla!), the Joomla! plugins of type MageBridge offers some extra functionality when dealing with building the bridge. This tutorial describes the plugin-events.

Read more: MageBridge plugin events

Using MageBridge you can easily call Magento API-methods from within Joomla! to make your own extensions. But sometimes it might also be needed to use this functionality from the command-line, for instance when migrating to new sites or when running cronjobs. Luckily enough, the Joomla! Framework allows for easy script building, and this tutorial shows you how.

Read more: MageBridge from the command-line

The following FAQ contains questions and answers on MageBridge development.

Read more: MageBridge FAQ: Development

MageBridge allows you to integrate Magento into Joomla!, and for this to work, data are transferred in various ways from Magento to Joomla! using the MageBridge API. This API could also be used to fetch data for your own Joomla! extension. This guide helps you with the right steps.

Read more: Fetch your own Magento data from MageBridge

Joomla! offers an architecture of elements (JElements), which allow you to define form-fields to be used in XML-files. Joomla! offers form-fields like a category-dropdown or a modalbox with article-selection. MageBridge is using the same architecture to add its own set of elements to be used by any third party developer.

Read more: Reusing MageBridge parameters in Joomla! extensions

MageBridge integrates Magento into Joomla! and besides the core functionality of MageBridge, you also have the opportunity to extend this behaviour. This is possible by writing Joomla! plugins following the regular Joomla! coding standards. If you are not familiar with writing Joomla! plugins, check the Joomla! Documentation project for more information.

Read more: Catching Magento events with a Joomla! plugin

While MageBridge uses the regular Joomla! plugin-systems to connect various third party applications to MageBridge, there is also a thing called "connectors" that allow you - as a developer - to change the inner-workings of MageBridge. In this tutorial you will learn more on how to create your own store connectors to connect to a specific Magento store (Store View or Store Group).

Read more: Creating custom store connectors

Both Joomla! as Magento use so-called events when something important is happening inside the system, and these events can be picked up by first third party extensions. For instance, in Magento when a shopping cart is checked-out it could be modified through events. MageBridge uses this mechanism by sending the event to the other side of the bridge, thus allowing Joomla! extensions to interact with Magento events, and Magento modules to interact with Joomla! events.

Read more: Handling events with MageBridge (in progress)

If you want to create a language-pack, the best thing is to copy the English language-files and translate them. There are two separate language-packs you need to create: One for the frontend and one for the backend. The frontend only needs one language-file: language/en-GB/en-GB.com_magebridge.ini. For the backend two language-files are used: administrator/language/en-GB/en-GB.com_magebridge.ini and administrator/language/en-GB/en-GB.com_magebridge.menu.ini. The last file only includes the translation of the menu-item, so could be skipped.


Read more: How can I create a language-pack for MageBridge?