jUpgrade:Migrating third-party extensions

From redWIKI
Jump to: navigation, search


Supported third-party extensions

Component-specific migration guides



(Submitted by Rich Taft from the redCOMPONENT forums: http://redcomponent.com/forum/92-jupgrade/121208-problem-copying-jevents-from-joomal-1525-to-25)

Some of you may have had some issues and since I looked here first to find the answer I figured I’d post what I eventually found.

The JEvents developers have created a migration tool and specifically noted what to do in the event you tried to migrate using Jupgrade. I’ll list these steps shortly, but one other thing I will bring to your attention. Jevents version 2.0.11 is NOT compatible with Joomla 2.5. The way classes are handled in 2.5 has changed. The compatible version is now available for non-club members. This version is 2.1.6. they also recommended that you upgrade to Jevents 2.1.6 on your Joomla 1.5 website BEFORE you migrate to Joomla 2.5 The Link for further information, and to Download Jevents & the migration tool is


It assumes you have used the jUpgrade or similar tool to migrate from 1.5 to 1.7/2.5.

To use it:

The script should pick up the database config from both sites automatically and migrate the data from one site to the other, creating the categories it needs along the way with default permissions set.

Please note that the database user for the Joomla 1.7/2.5 site will need read access to the Joomla 1.5 site's database - so if your Joomla 1.7 uses a different database to your Joomla 1.5 site you may need to check your database permissions.



(Borrowed from JomSocial's manual migration guide: http://www.jomsocial.com/blog/migrating-jomsocial-data-into-joomla-25.html)

At this stage, it is assumed that Joomla User information has been successfully migrated to Joomla 2.5, and their information such as userid, username, password and email are intact. Again, userid MUST be intact! If your Administrator userid was 62 in Joomla 1.5, it has to be 62 in Joomla 2.5. This is the point where J2XML failed in our previous migration attempt. What a pity since it could have been one perfectly suited component for our needs.

Before we get started, the first thing that you will need to do on the newly migrated Joomla 2.5 is to install JomSocial. Yes, that’s right. This step is important for Joomla to capture JomSocial as an installed component, and for JomSocial to generate JomSocial Toolbar in the menu system.

But hold on! Before installing JomSocial on Joomla 2.5, I would like to reiterate on one important warning. Please make sure that prior to installation; you have already installed JomSocial 2.4.2 (or above) on the Joomla 1.5 site. If you are using an older version, please upgrade to JomSocial 2.4.2.

Why it must be JomSocial 2.4.2 (or above)? Well, only JomSocial 2.4.2 (or above) is compatible with Joomla 2.5. :D

Once JomSocial 2.4.2 is installed on the Joomla 2.5 site, we are now ready to migrate JomSocial information from Joomla 1.5 to Joomla 2.5.

JomSocial stores submitted data in three locations.

  1. Database (user profiles, discussions, groups, events, photo information, any text)
  2. Local files in /images/ directory (avatar, photo files, video files)
  3. Amazon S3 (depending on your JomSocial setup)

Migrating JomSocial Database into Joomla 2.5

Here’s an open secret. JomSocial database structure is exactly the same in Joomla 1.5 as in Joomla 2.5. They are both identical, which could only mean one thing, you can directly copy these tables into Joomla 2.5!

Using PHPMyAdmin (or any preferred software), go to the database and use the Export tab. Locate all database tables in Joomla 1.5 that start with jos_community_# prefix. All these tables belong to JomSocial. Export them.

Once exported, save the file onto your desktop. Open up the database for Joomla 2.5, and make a backup of the entire database.

Subsequently locate all tables that start with [prefix]_community_# in Joomla 2.5, tick all of them, and select drop. PHPMyAdmin will delete all these tables. Don’t worry, they are blanks and void.

You will then import the tables that you have exported earlier into this Joomla 2.5 database, essentially merging the fresh Joomla tables with JomSocial tables that are filled with information.

To import the tables, simply head over to Import tab, and select the desired file.

In the event that imported Joomla 1.5 tables have different prefix (for example, jos_#) than Joomla 2.5 tables (for example, j25_#), you will have to rename these tables to ensure they match. I have also found a good tutorial on renaming tables using PHPMyAdmin here.

You are now done!

Migrating JomSocial Files into Joomla 2.5

Migrating JomSocial files are really straightforward. You will only need to copy the entire /images directory in Joomla 1.5, and merge it with Joomla 2.5’s /images directory. If you wish to selectively pick on JomSocial files, copy these directories:

/images/files (new feature in JomSocial 2.6)

Migrating JomSocial Amazon S3 Files into Joomla 2.5

Assuming that JomSocial database has been imported correctly into Joomla 2.5, you do not have to do anything with Amazon S3 files. The database fields will correctly link them with the new Joomla 2.5 site. Phase 6: Finalizing the Migration

Congratulations! Joomla 2.5 + JomSocial 2.4.2 is now deployed on your livesite! Take some time to reconfigure the extensions, templates and to ensure that all is in working condition. You might want to get some help from your users to report peculiar issues that they may have encounter after the upgrade. It is a community, after all. :)



(Adapted from the following links:)

As far as K2 component is concern, you need to follow below steps.

  1. Go to Extension -> Extension manager
  2. Select Update option which is next to the install link.
  3. Click on Find Update
  4. Select K2 and Update it.

Now you will have K2 installed for joomla 1.7 and also with appropriate content.

Please refer http://www.youtube.com/watch?v=D0UEKd58zY8 for video explanation.

;Manually migrating K2 content from Joomla! 1.5 to 1.7

Originally posted by Steve Adams in the K2 Community Forum:

  1. Back up J1.5 source and J1.7 destination. Use Akeeba Backup.
  2. Ensure J1.5 and J1.7 table prefixes match. Use Admin Tools.
  3. Log into phpMyAdmin
  4. Export J1.5 k2 tables only
  5. Import k2 tables .sql into J1.7 database, leave k2 tables in MyISAM format
  6. Update k2_items created_by ID to new J1.7 Super User ID by running SQL query:
    UPDATE `PREFIX_k2_items` SET created_by = NEW_ID WHERE created_by = OLD_ID
  7. Update k2_items modified_by ID to new J1.7 Super User ID:
    UPDATE `PREFIX_k2_items` SET modified_by = NEW_ID WHERE modified_by = OLD_ID
  8. All of my k2 items had access set to 0 so I made them all public again:
    UPDATE `PREFIX_k2_items` SET access = 1 WHERE access = 0
  9. Copy k2 media items from J1.5 and paste into J1.7 .../media/k2/
Personal tools