MageBridge offers a basic integration with ZOO through a ZOO App. Through this app, you are able to build ZOO content-item but using various fields derived from Magento. This guide contains the basic steps to get this working.
Within the Joomla! backend you can set various ACL-rules that restricts users in both the frontend as the backend. When integrating Magento into Joomla! using MageBridge, frontend-permissions on Magento pages are still handled by Magento. However, MageBridge offers a few ways to limit the usage of the MageBridge backend-component, which is discussed here.
The MageBridge System Plugin enables various core features, and should never be disabled for a MageBridge-based site. But it includes features and options worth describing. This whitepaper covers the basic workings of this plugin, and also discusses the parameters it ships with.
The core feature of MageBridge is to integrate Magento into Joomla!, but because of its user syncing abilities, it is also possible to use the Magento application and Joomla! application seperately. In this case, the visual integration is disabled (mostly). This guide explains you how to do this.
Upgrading a Joomla! site with MageBridge from Joomla! 1.5 to Joomla! 2.5 is a task that involves many steps. However, because the codebase of MageBridge is the same under Joomla! 1.5 as under Joomla! 2.5, migrating the MageBridge extensions itself is a piece of cake. This tutorial gives some tips and tricks on this migration.
When setting up a MageBridge/Joomla! shop, enabling Joomla! SEF in the Global Configuration is a must. The reason is simple: Magento uses SEF URLs by default, and for MageBridge to succesfully integrate Magento into Joomla!, Joomla! needs to use SEF URLs as well. But because Joomla! and Magento create SEF URLs in different ways, there could be instances where the two mechanisms are conflicting - resulting in Magento 404-errors. This tutorial explains why and how to prevent this.
The MageBridge extensions offer you a lot of different solutions, but sometimes you might make a mistake that renders your entire Joomla! site offline. You might be locked out of your Joomla! Administrator, or the entire Joomla! Administrator might be even unavailable. By setting MageBridge offline through the database, you might be able to restore your access to the Joomla! Administrator.
Within the Joomla! Menu Manager it is possible to create numerous Menu-Items pointing to various pages. With a MageBridge-based webshop, we advise you to create one special Menu-Item pointing to the MageBridge Root - this is the so-called MageBridge Root Menu-Item. This tutorial explains why and how to create this Menu-Item.
Magento adds the ability to let customers upload their own files when adding a specific Magento product to their cart. MageBridge is able to bridge this functionality to Joomla!, but it is important to make sure your hosting environment meets up to the requirements. This tutorial guides you through all of the steps.
MageBridge is able to integrate many things of Magento into Joomla! - the entire Magento frontend is integrated neatly into the Joomla! template and various other integrations make setting up a Magento site a breeze. One of the areas where the MageBridge functionality becomes a bit hard is the area of Downloadable Products. This tutorial gives you insight in the ups and downs.
The feature URL Replacements allows you to replace Magento URLs with Joomla! URLs. This can be useful for replacing Magento product-pages with your own CCK-built catalog, but perhaps also for replacing pieces of functionality of Magento with Joomla! extensions (for instance the wishlist). URL Replacements uses a simple concept but it has some side notes, when you want to use it in practice.This tutorial explains the bits and pieces.
Often it is needed to set a hard definition of the MageBridge URLs in Magento. MageBridge is able to set the right URLs dynamically from the frontend. But when you send mails from the Magento Admin Panel, the URL is set to the default Magento URL and not the Joomla! URL. This tutorial helps you to reconfigure Magento to solve this.
While one of the key features that MageBridge offers is user synchronization, there are cases in which you want to disable user synchronization. This takes some work - documented in this tutorial - but the end result is that the Magento users are kept separate from Joomla! users.
When you add MageBridge to an existing configuration (an existing Joomla! site or an existing Magento site), you'll want to make sure that existing customers can still use their login. This tutorial discusses the details of migrating users from Joomla! to Magento, or vice versa.
With MageBridge, new users are automatically synchronized: If a new customer has been created in Magento, MageBridge will automatically create a corresponding user in Joomla! - as soon as the user logs in, or as soon as the user-record is edited in the backend. But if you have an existing userbase that you want to migrate at once, you need to follow a procedure which is a bit more complex. This tutorial helps you out.
The JCE-editor is the most popular editor for Joomla!, and allows you to easily add images and links to your content. With the MageBridgeLinks/JCE plugin you can also easily add MageBridge product-links or category-links to your content. This document explains the installation and usage.
Within Magento, you need to create an API-user for usage with MageBridge. This API-user is connected to an API-role, and this API-role implies a set of permissions (Role Resources) to certain parts of Magento. To make it easy to configure, we recommend to select just all permissions for the API-user. But if you want to increase security, you need to know which resources are needed to run MageBridge. Here's a listing.
Within MageBridge, plugins are used to do all kinds of things: With Product Plugins you can do something in Joomla! when a Magento product is being sold. This opens up for tons of opportunities, like selling access to DOCman downloads or adding a customer to a certain JomSocial group. Here are some general guidelines for Product Plugins.
The Magento multi-site concept is flexible but a little complex. It uses three levels which can be used in various ways: Websites, Stores and Store Views. Within the MageBridge Configuration the entire Joomla!-side of the bridge is configured as a Website. But within this Joomla! site you can still use Stores and Store Views for various purposes. For instance: To load a different theme.