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.

Read more: Debugging conflicts with other Magento extensions

A common error in some hosting environments is the 500 Internal Server Error. It hides the actual PHP error, and tells you to contact the system administrator. This tutorial helps you to solve these errors.

Read more: Solving 500 Internal Server Errors

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.

Read more: MageBridge output tests

The following FAQ contains questions and answers on installation-related issues with MageBridge.

Read more: MageBridge FAQ: Installation issues

The following FAQ contains questions and answers on user-related issues with MageBridge.

Read more: MageBridge FAQ: User-related issues

The following FAQ contains questions and answers on general troubleshooting with MageBridge.

Read more: MageBridge FAQ: General Troubleshooting

The Magento checkout is heavily based on JavaScript, and when wrapped in Joomla! using MageBridge, the majority of all problems is related to JavaScript. This guide helps you troubleshoot problems with the MageBridge-based Magento checkout step by step.

Read more: Magento checkout doesn't work

When Joomla! users are not synchronized to Magento, or Magento users are not synchronized with Joomla!, most likely this is due to some settings in MageBridge. This guide gives you some clues what to check for.

Read more: Users are not synchronized

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.

Read more: Bridge is not available

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.

Read more: Solving 404 Not Found errors

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.

Read more: MageBridge Troubleshooting Guide