Migrating MageBridge from Joomla! 1.5 to Joomla! 2.5

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.

A note to begin with

This tutorial discusses MageBridge under Joomla! 1.5 and Joomla! 2.5. However the MageBridge codebase that works under Joomla! 2.5 is also compatible with Joomla! 1.6 and Joomla! 1.7. Therefor this tutorial also applies to migrating a MageBridge site from Joomla! 1.5 to either Joomla! 1.6 or 1.7.

What has changed within Joomla! 2.5 and therefor MageBridge?

When migrating from Joomla! 1.5 to 2.5, there is a huge list of things that have changed. Dealing with third party extensions, the Joomla! Framework classes were modified, a new format of XML-files was introduced, and various new features were added. When Joomla! 1.6 was released, MageBridge was already modified to include all the neccessary code-changes - which it makes it possible to state that MageBridge is stable enough to use under Joomla! 2.5.0. However, the XML-files of Joomla! 1.5 are not compatible with 1.6/1.7/2.5 and vice versa. Therefor, Yireo has decided to develop separate extension-packages for Joomla! 1.5 and Joomla! 1.6/1.7/2.5. The extension-packages contain the same PHP-code, but different XML-files.

So: The PHP-code of MageBridge remains exactly the same under Joomla! 2.5 as it was under Joomla! 1.5. However, all the XML-files included with MageBridge extensions is different. Copying all files from Joomla! 1.5 to Joomla! 2.5 therefor does not work. To migrate things, you therefor have two possible procedures, which are laid down below.

Procedure 1: Copying things manually

  1. Migrate your Joomla! 1.5 core to Joomla! 2.5
  2. Copy the MageBridge database-tables to the new 2.5 database
  3. Reinstall the MageBridge extensions

The first approach is to migrate the Joomla! core first, and deal with the migration of MageBridge afterwards. There are various ways to migrate from Joomla! 1.5 to Joomla! 2.5: Copying things manually, migrating using your own PHP-scripts and SQL-statements, using the jUpgrade-extension. You can use any of these ways to migrate the Joomla! core. Once you're done, you will have an up and running Joomla! 2.5 site - but without the MageBridge extension being present.

To migrate MageBridge to this fresh Joomla! 2.5 site, you can then export the MySQL database-tables from Joomla! 1.5 to a SQL-file (for instance using phpMyAdmin), and import that SQL-file within the new 2.5 database. After this, you can simply download the MageBridge component for Joomla! 2.5 and install it into Joomla! 2.5. It will not overwrite the existing database-tables, so all of your settings are retained. Afterwards, navigate to the MageBridge Update page within the Joomla! backend, and install all other MageBridge extensions that you need.

Procedure 2: Using jUpgrade more or less

  1. Migrate your Joomla! 1.5 core using jUpgrade
  2. Reinstall the MageBridge extensions

The second approach is to migrate the Joomla! core using the jUpgrade extension. The latest builds of MageBridge include a file components/com_magebridge/jupgrade.xml which allows for transferring the MageBridge database-tables to the fresh Joomla! 2.5 database that jUpgrade generates. This bypasses the need The XML-file also allows you to copy all of the

However, the XML-files are also copied from Joomla! 1.5 to Joomla! 2.5, while not being compatible with Joomla! 2.5. Therefor, once your jUpgrade migration is finished and your new Joomla! 2.5 is up and running, you will need to manually install the MageBridge component again. Afterwards, navigate to the MageBridge Update page within the Joomla! backend, and install all other MageBridge extensions needed.

Migration issues

  • After migrating, make sure to visit the MageBridge Configuration page. Under Joomla! 1.5, it was possible to use XML-RPC as API-protocol. But under Joomla! 1.7, this option was replaced with JSON-RPC. By loading the configuration and saving it, you've made sure that XML-RPC is really replaced with JSON-RPC.
  • It's a good idea to run down the Joomla! Plugin Manager to see whether the ordering of plugins is the same under Joomla! 2.5 as under Joomla! 1.5. Pay special attention to the System Plugins, because their ordering could be vital for the functionality of your site.
  • When using one of our MageBridge Template Patches, it's probably wise to install the latest available version of the template-patch we provide. If you have modified the CSS-contents, make sure to fully test all your MageBridge pages.

We will keep this list of issues updated, if new tips or tricks are found.