Both Joomla!TM 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 MagentoTM when a shopping cart is checked-out it could be modified through events. MageBridgeTM 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.
There's only one downside: Every time when an event is promoted to the other side of the bridge, it takes up extra resources. It might be smarted to turn off those events you don't need. In this whitepaper you can see which events are used for what, and if they are used in the MageBridge core or not.
Joomla! plugin-events
Magento events
Through the MageBridge Settings inside the Magento Control Panel you can turn off event forwarding for all events supported. The tab Event Forwarding allows you to enable certain events to be forwarded through the bridge. We do not recommend enabling all events, because this will downgrade your performance dramatically. However, we recommend the following events to be enabled:
- address_save_after
- adminhtml_customer_save_after
- customer_save_after
If you want Joomla! users to be deleted as soon as the corresponding Magento customer is removed, you need to enable the following events as well:
- adminhtml_customer_delete_after
- customer_delete_after
Other events may need to be enabled, depending on extra MageBridge plugins existing in Joomla! - for instance, the integration with Community Builder will require you to enable extra events.
Tutorials on MageBridge development
- How can I create a language-pack for MageBridge?
- Creating custom store connectors
- Fetch your own Magento data from MageBridge
- Catching Magento events with a Joomla! plugin
- Reusing MageBridge parameters in Joomla! extensions
- MageBridge FAQ: Development
