MageBridge System Requirements

These installation steps assume you have already installed Joomla! and Magento on your website. Make sure you understand how to use both applications first, before starting with MageBridge.

First make sure your system meets the minimum requirements for Joomla! and Magento:


We do not support MageBridge-environments that do not meet-up to the requirements on this page. Also, we do not support problems that arise because of limited resources within the hosting environment. If the hosting environment is not tuned for Magento, we do not support MageBridge running on it.

Minimum software requirements

Before purchasing MageBridge, make sure your web environment matches the following requirements.

  • Linux hosting platform (or other UNIX-variations)
  • Apache with mod_rewrite, mod_xml and mod_zlib; Nginx; Lighttpd
  • MySQL 5.1 or higher, with InnoDb support - MySQL 5.6 is recommended
  • PHP 5.4 as a minimum, 5.6 is recommended
    • Either mod_php, PHP-FPM or HHVM
  • PHP settings (see below)
  • Joomla! platform
    • Joomla! 3.3 or higher
  • Magento platform
    • Magento CE 1.7 to 1.9
    • Magento EE 1.11 to 1.14

Please note that MageBridge is not and will not be compatible with Magento 2. Checkout our FAQ for more details. Make sure you know the details on the difference between Magento 1 and Magento 2 before diving deeper into MageBridge.

Minimum system requirements

The Magento System Requirements states you will need at least 256Mb of memory (PHP memory_limit) available. For Joomla! you will need at least a PHP memory_limit set to 32Mb. When Joomla! and Magento are installed in the same webdirectory, you will need at least 288Mb - this is the absolute minimum requirement. It's quite normal to assign 512Mb. It is also quite normal to have a VPS with 2Gb or 4Gb of RAM.

Networking requirements

Joomla! needs to be able to contact Magento through HTTP. This lays down the following requirements:

  • Joomla! needs to know the hostname of Magento through either DNS or hosts-file
  • Outgoing HTTP-access from Joomla! to Magento should not be blocked by a firewall

Required PHP extensions

The following PHP-extensions need to be enabled in both web-environments:

  • Zend OPC or APC (see below)
  • CURL (see below)
  • SimpleXML
  • JSON
  • OpenSSL
  • mcrypt
  • zlib
  • zip

Note that these are the requirements. We assume you are also following the guidelines given by Joomla and Magento.

When you install the MageBridge installer-program for Joomla! these settings will be automatically checked before installing the complete version of MageBridge. The MageBridge installer-program is available for free, however offers no real functionality except for the upgrade to the complete version of MageBridge.

About Zend OPC and APC

Either Zend OPC or APC (Advanced PHP Caching) is highly recommended for running Magento and there for MageBridge. When you have a webshop, it is important that it is able to run fast and smooth. Without a PHP accelerator this will not be the case. A PHP accelerator is not mandatory and MageBridge (and Magento) will run without it. When comparing Zend OPC and APC, APC was the defacto accelerator under PHP 5.4, but currently it is buitl into Zend OPC. With PHP 5.5 or higher, we highly recommend to use Zend OPC. Note that memcache is not an OPC caching mechanism. We will not support performance problems unless a PHP accelerator is used.

About CURL

CURL is being used to communicate between Joomla! and Magento. Be warned that we have seen many hosting environments in which PHP is upgraded frequently but CURL never. This will corrupt the communication between PHP and CURL. In a good hosting environment not only PHP must be kept up-to-date but CURL as well.

Minimum PHP settings

The following PHP-settings are required in both web-environments:

  • safe_mode = Off
  • max_execution_time => 60
  • magic_quotes_gpc = Off

Recommended MySQL settings

Magento requires much more resources than Joomla! does, which means MageBridge will not run successfully unless these resources are available. We highly recommend tuning MySQL to increase performance. This is mostly accomplished by editing /etc/my.cnf by either yourself or your hosting party.

  • query_cache_size = 16M or higher
  • max_allowed_packet = 16M or higher
  • connect_timeout = 30 or higher
  • wait_timeout = 30 or higher

Joomla! requirements

MageBridge offers extensions that need to be installed on top of Joomla!, so this requires Joomla! to be up and running. Because Magento only offers SEF URLs, enabling Joomla! SEF in the Global Configuration is also required. We highly recommend an Apache .htaccess file to be in place (as per the instructions on the Joomla! Documentation Project), or alternative rules when using Nginx or Lighttpd.

Magento requirements

Apart from the original system requirements that Magento itself has, there are no additional requirements for running MageBridge. We do recommend however to make sure Magento is as fast as possible. Having MySQL tuned for Magento usage is a minimum, as well as running a PHP accelerator (Zend OPC, or APC). We highly recommend Redis being configured as Magento caching handler.

Where to install Joomla! and Magento?

With MageBridge the only important thing for installing Joomla! and Magento is that they can talk to each other through HTTP. Both applications could be installed on the same domain in the same directory, on separate domains, or even on separate webservers. Make sure the domain-names of both Joomla! as Magento are accessible from the Internet as well from the webserver itself.

Also note that if you want the MageBridge webshop to become accessible through an URL "shop", do not install Magento in a directory with the same name.

About versions

We recommend keeping your Joomla! installation at the latest version at all times. We make a continuous effort to keeping MageBridge up to date for all current Joomla! versions.

Keeping your Magento installation up-to-date is a bit more complex than with Joomla!. We recommend upgrading in a test-environment, before putting it into production. With minor releases (1.Y.X) we will be able to fix MageBridge-issues due to Magento-upgrades quickly, but with major releases (1.X) this could be more complicated. We urge you to use a test-environment for Magento.

Note that MageBridge is currently not supported under Magento 2.