MageBridge Development Tutorials

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

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/ 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?