CiviCRM Community Forums (archive)

This is just a reference post for anyone in a similar situation. I had a Joomla 1.5.26 site running Civi 3.3.5, and migrated / upgraded to Joomla 2.5.8 running Civi 4.2.7. As the migration path wasn't straightforward for this, I thought I'd share the process I used.  Many thanks to Stuart Gaston for sketching out much of what you'll see in this process...

PROCESS FOR MOVING JOOMLA 1.5.26 / CIVI 3.3.5 TO JOOMLA 2.5.8 / CIVI 4.2.7 --  (+) notes
------------------------------------------------------------------------------------------------------------------------------
* install a blank Joomla 1.6 site  /  install Civi 3.3.5 to that
* copy over existing Civi 3.3.5 MySQL data (component will not function properly)   -->  (+) See Note 1.
* install Civi 4.0.0 (Civi detects upgrade and it tells you to run DB upgrade, which runs fine)
* now you're at J16 and Civi 4.0...
* install Akeeba 3.2.7 -- nothing later -- and make a backup. (3.2.7 is the latest version you can use on J16!)
* run Joomla update via the extension manager... (actually a 2-part upgrade)
* this gets you to Joomla 1.7 (mine crashed after part 1, but refreshed to the admin screen ok)
* go back to the extension manager / update screen, and you see that there is a Part 2 to the update
* run that, and now you're at Joomla 2.5.8 ... make another backup
* update Akeeba to current version / make another backup
* download civi4.2.7-joomla.zip / upload to [root]/tmp, then unzip
* install civi from the directory... [root]/tmp/com_civicrm
* run the DB upgrade script, which it should link to upon upgrade     -->  (+) See Note 2.
    or... load: [root]/administrator/index.php?option=com_civicrm&task=civicrm/upgrade&reset=1
* click the Return to CiviCRM home page link
* Confirm by checking the version and revision in the page footer
* backup again!

Best wishes on your Civi / Joomla upgrades / migrations!
-Jim


NOTES:

(+) Note 1:    When you're doing this, you may need to drop all Civi tables from your MySQL at various points. To do this, see your Civi install path at administrator / com_civicrm / sql / civicrm_drop.mysql for a script that will make dropping the civi tables much easier. This process assumes that you know how to import/export using phpMyAdmin.  Also, I don't believe I skipped over any tables on my initial export of my 3.3.5 tables for copying. I only say that because there are posts that recommend skipping out on various cache tables. So, your mileage may vary on this.

(+) Note 2:  Just a quick note. This ran fine for me, but Civi does give you a warning at this point, and it's probably worth mentioning here as well, so here's what Civi tell you...

Upgrade CiviCRM to Version 4.2.7
CiviCRM upgrade was successful.

WARNING! CiviCRM 4.1 introduces an improved way of handling cron jobs. However the new method is NOT backwards compatible. Please notify your system administrator that all CiviCRM related cron jobs will cease to work, and will need to be re-configured (this includes sending CiviMail mailings, updating membership statuses, etc.). Refer to the online documentation for detailed instructions.

The CiviCRM Administration menu structure has been re-organized during this upgrade to make it easier to find things and reduce the number of keystrokes. If you have customized this portion of the navigation menu - you should take a few minutes to review the changes. You may need to reimplement or move your customizations.
Yahoo recently discontinued their geocoding and mapping API service. If you previously used Yahoo, you will need to select and configure an alternate service in order to continue using geocoding/mapping tools.

We have integrated KCFinder with CKEditor and TinyMCE, which enables user to upload images. Note that all the images uploaded using KCFinder will be public. Default versions of the following System Workflow Message Templates have been modified to handle new functionality:

Events - Registration Confirmation and Receipt (on-line)
Pledges - Acknowledgement
Pledges - Payment Reminder

If you have modified these templates, please review the new default versions and implement updates as needed to your copies (Administer > Communications > Message Templates > System Workflow Messages). If you have configured a report instance to allow anonymous access, you will need to reset the permission to Everyone for that instance (under the Report Settings pane).