It might happen that Magento behaviour is different under the regular Magento frontend than under the Joomla! frontend. This might be caused a MageBridge bug, but if it can not be replayed on any other testing environment, it might also be related to a third party Magento extension. This guide shows you how to debug conflicts between MageBridge and other Magento extensions.
Within MageBridge, there are various tools that help you troubleshoot problems with the bridge. One of these tools is a Magento controller-class that can be called from Joomla!. The controller-class outputs various types of data to make it easier to check if MageBridge is outputting data or not.
The following FAQ contains questions and answers on general troubleshooting with MageBridge.
When the bridge connection between Joomla! and Magento is unavailable, MageBridge displays the offline message inside the component area. By default, this states that the bridge currently unavailable, but it doesn't state the reason why - something you shouldn't bother your users with anyway. This guide helps you analyse the problems step by step.
With MageBridge, one thing that leads many times to confusion is a 404 error. When you access a certain MageBridge page within Joomla!, you may encounter a 404 error. But why is this 404 error thrown? This guide helps you to analyze this problem properly.
Combining Joomla! and Magento into a single site can be very complicated. If you're new to either Joomla! or Magento, using MageBridge might not be that straight-forward. Knowledge of both Magento as well Joomla! is needed to make your MageBridge shop a succes. This guide tries to help you out with troubleshooting problems that might occur.