CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Alpha and Beta Release Testing »
  • 2.1 Release Testing »
  • Testing upgrade process: Joomla
Pages: [1]

Author Topic: Testing upgrade process: Joomla  (Read 3118 times)

FatherShawn

  • Ask me questions
  • ****
  • Posts: 372
  • Karma: 25
    • C3 Design
  • CiviCRM version: 4.2.11
  • CMS version: Drupal 7.23
  • MySQL version: 5.5.32
  • PHP version: 5.3.10
Testing upgrade process: Joomla
September 13, 2008, 03:33:19 am
The documentation states:
Quote
   "Successful migration SHOULD now have..."
  • Working Joomla 1.5.x site kept separate from the 1.0.x directory.
  • CiviCRM is NOT registered as one the components in the upgraded Joomla site (the steps below will upgrade and register you CiviCRM component).
  • Database with upgraded Joomla tables, along with all your CiviCRM v2.0 tables and data (since your upgraded site uses a copy of your original Joomla 1.0x database).

However, following the migration documentation for Joomla to create this prerequisite results in a Joomla db without CiviCRM data.  The Joomla 1.0->1.5 migration uses an automated tool called Migrator to create an sql dump for the new version. Migrator has a plug-in architecture to also include data from other components.  I cannot find any documentation for the plug-in.  The developer's contact info is here: Sam Moffatt.

Shouldn't we have a plugin to make the data movement process easier?

Sam is a member of the Joomla core team and has a technical blog post on Migrator: How it works: 1.0 to 1.5 Migration.

The folks at Joomlatools also have posted a blog entry on plug-in architecture: Roll your own migrator plugins
« Last Edit: September 13, 2008, 06:09:20 am by FatherShawn »
Lead Developer, C3 Design.
Twitter: @FatherShawn

Deepak Srivastava

  • Ask me questions
  • ****
  • Posts: 677
  • Karma: 65
Re: Testing upgrade process: Joomla
September 13, 2008, 08:52:38 am
Sounds interesting and might consider it in future :) but not sure if we should have spent time on it given that same civicrm-upgrade script worked on -
Drupal, Joomla and Standalone.

Also not sure if this would ease the migration process since -
1. Number of steps i guess would remain same. And you'll anyway have to install the new code base. So even if we had provided migration script the only step which wouldn't be needed is "running the upgrade url (step-5)".

2. The new upgrade script if you have noticed - is only one step i.e not a multi-step wizard whereas /w joomla-migration script it would be a two step process - generating the dump + importing.

3. Most of the problems have been reported /w installation/setup and not migration/up-gradation.       
 
FYI, CiviCRM has already started discussions on how to make up-gradation/migration easier (specially /w joomla).
 
Again these are MO and not sure i am accurate on that (feel free to correct me).
« Last Edit: September 13, 2008, 08:56:22 am by Deepak Srivastava »
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

FatherShawn

  • Ask me questions
  • ****
  • Posts: 372
  • Karma: 25
    • C3 Design
  • CiviCRM version: 4.2.11
  • CMS version: Drupal 7.23
  • MySQL version: 5.5.32
  • PHP version: 5.3.10
Re: Testing upgrade process: Joomla
September 13, 2008, 04:50:15 pm
Quote from: Deepak Srivastava on September 13, 2008, 08:52:38 am
Sounds interesting and might consider it in future :) but not sure if we should have spent time on it given that same civicrm-upgrade script worked on -
Drupal, Joomla and Standalone.

Well, if the upgrade script worked on your Joomla install maybe I missed something.  ??? In trying to test civiCRM on a test server with our own data, I followed the Joomla 1.0 to 1.5 upgrade documentation to create a migrated 1.5 copy of my site.  The civiCRM tables are not present in the migrated site.  Our civiCRM upgrade instructions assume that they are present in the 1.5 database.

I'm comfortable enough with either mysql or phpmyadmin to move the civiCRM tables from the 1.0 database to the 1.5 database.  My post is intended to ask if that is generally true of our user base?

If it is true then we need to change the instructions.  If it isn't true then we should consider making the plug-ins because Joomla users are going to use the Migrator as it is necessary to move the core content and is specifically states it does not move third-party component data without a plug-in.

If I've missed something, just let me know...
« Last Edit: September 13, 2008, 05:00:16 pm by FatherShawn »
Lead Developer, C3 Design.
Twitter: @FatherShawn

Deepak Srivastava

  • Ask me questions
  • ****
  • Posts: 677
  • Karma: 65
Re: Testing upgrade process: Joomla
September 13, 2008, 10:43:25 pm
Quote
Well, if the upgrade script worked on your Joomla install maybe I missed something.  Huh In trying to test civiCRM on a test server with our own data, I followed the Joomla 1.0 to 1.5 upgrade documentation to create a migrated 1.5 copy of my site.  The civiCRM tables are not present in the migrated site.  Our civiCRM upgrade instructions assume that they are present in the 1.5 database.

Looks like step 1: "Migrate Joomla site 1.0.x -> 1.5.x", of documentation - http://wiki.civicrm.org/confluence/display/CRMDOC/Upgrade+Joomla+Sites+to+2.1 is not very clear. Let me clarify:

1. Lets assume you have working Joomla v1.0.x site /w CiviCRM v2.0.x, and a db (of course) consisting of tables from both joomla and civicrm.

2. As per joomla migration doc - http://docs.joomla.org/Migrating_from_1.0.x_to_1.5_Stable (step 3), create a migration sql file. And since CiviCRM didn't provide any migrator, the migration-sql file will only have queries for migrating joomla data (and any other third party component's data who provided migrator plugins).

3. As per joomla migration doc (step 4), you would install Joomla 1.5.x in separate directory (other than that of joomla 1.0.x).
During this installation (joomla 1.5.x) -
   * You would use/specify the same db that was being used for joomla 1.0.x (mentioned in step1).
   * In the final step where you are prompted for the site name you are given the opportunity to initiate the migration process, where you can use the migration-sql file created at step 2.

4. So after completing step-3 you should have:
    *  Working Joomla 1.5.x site kept separate from the 1.0.x directory.
    *  CiviCRM NOT registered as one the components in Joomla 1.5.x site.
    *  Database with upgraded Joomla tables, along with all your CiviCRM v2.0 tables and data (since your upgraded site uses a copy of your original Joomla 1.0x database).

Note: If you don't have civicrm tables, probably you didn't use the old-db OR old-db didn't have civicrm tables. 

5. And now follow rest of the steps 2-5 from - http://wiki.civicrm.org/confluence/display/CRMDOC/Upgrade+Joomla+Sites+to+2.1
« Last Edit: September 14, 2008, 02:25:07 am by Deepak Srivastava »
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

FatherShawn

  • Ask me questions
  • ****
  • Posts: 372
  • Karma: 25
    • C3 Design
  • CiviCRM version: 4.2.11
  • CMS version: Drupal 7.23
  • MySQL version: 5.5.32
  • PHP version: 5.3.10
Re: Testing upgrade process: Joomla
September 14, 2008, 03:30:42 am
Quote from: Deepak Srivastava on September 13, 2008, 10:43:25 pm
3. As per joomla migration doc (step 4), you would install Joomla 1.5.x in separate directory (other than that of joomla 1.0.x).
During this installation (joomla 1.5.x) -
   * You would use/specify the same db that was being used for joomla 1.0.x (mentioned in step1).
   * In the final step where you are prompted for the site name you are given the opportunity to initiate the migration process, where you can use the migration-sql file created at step 2.

Note: If you don't have civicrm tables, probably you didn't use the old-db OR old-db didn't have civicrm tables. 

Ahh!  We've found the point of confusion.  My 1.0 test db is a full copy of my live data and has all the civicrm tables.  I'm procedure testing here as well as trying to test 2.1 on our real data.  The step 4 of the joomla migration doc http://docs.joomla.org/Migrating_from_1.0.x_to_1.5_Stable states:
Quote
Note: Create your new Joomla! 1.5 install in a separate directory and database to your existing install (or different prefix if you cannot create a new database)
Since the strongly emphasized instruction was a new database, that's what I followed.  Then I returned to our upgrade doc and hit the glitch.  So if our procedure it to be compatible with theirs, then we should update our instructions to migrate, use the same db with a different prefix than the default jos_ for the install.
« Last Edit: September 14, 2008, 09:51:00 am by FatherShawn »
Lead Developer, C3 Design.
Twitter: @FatherShawn

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Testing upgrade process: Joomla
September 14, 2008, 07:29:14 am

I've fixed the upgrade instructions and put a statement in bold to use the same database for the joomla migration process

FatherShawn, can you take a look and edit it if needed to make it more clear

thanx

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

Deepak Srivastava

  • Ask me questions
  • ****
  • Posts: 677
  • Karma: 65
Re: Testing upgrade process: Joomla
September 14, 2008, 10:26:10 am
Even if same prefix is specified (e.g jos_ ), new installation would move/rename old tables to bak_* (default behavior i guess) and install new tables as jos_*. You may even choose not to keep the backup of old tables.
« Last Edit: September 14, 2008, 10:30:42 am by Deepak Srivastava »
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Alpha and Beta Release Testing »
  • 2.1 Release Testing »
  • Testing upgrade process: Joomla

This forum was archived on 2017-11-26.