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) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • The Upgrade to 2.1.6 - Finally!!!
Pages: [1]

Author Topic: The Upgrade to 2.1.6 - Finally!!!  (Read 974 times)

Shadow

  • I post occasionally
  • **
  • Posts: 36
  • Karma: 1
The Upgrade to 2.1.6 - Finally!!!
March 08, 2009, 09:52:37 am
Hi all - I am finally ready to update to 2.1.6.  It has been al long week.  First, Let me THANK everyone who offered advice and answered my questions on getting my DRUPAL test site upgraded to version 2..........you were a big help!  Now my test site is ready for the upgrade to 2.1.x and is running 2.0.6.

The background.  I upgraded my live DRUPAL site to DRUPAL 6 without realizing that it could not run any version less than 2.1.  So when I completed the DRUPAL upgrade, I couldn't update CiviCRM to the new versions because CiviCRM 2.0.x would not run under DRUPAL 6 and I needed to do the necessary updates to get my CivicRM installation from 1.9.x to version 2.  The solution was to create a test DRUPAL site running DRUPAL 5 and use it to update my data to version 2.  This has now been completed.  I  am asking the following questions before the upgrade because I don't want to spend hours taking the site back to DRUPAL 5 and CiviCRM 2.0.6 because I forgot something or wasn't aware of something.........the unforeseen!!!!

Now my thought is to

First, update the test site to version 2.1.6. To  do this, the test site needs to run DRUPAL 6.  So my thought is to do BOTH upgrades at the SAME TIME.  Delete the DRUPAL 5 codebase and delete the CiviCRM 2.0.x codebase and run the upgrade routines for DRUPAL 5 to 6 and then run the upgrade routine for CiviCRM 2.0 to 2.1 .  If this is successful, export the data out of the test site.
Question: Is this the method I should use or is there something I am missing?

Second - if the above is correct and successful, I will then go to the live site and do a straight install of CiviCRM 2.1.  Then empty the database and import the data from the test site.
Question: Is this the logical way to do this?

Once again - thanks to all who help get me to this point.

Shadow

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: The Upgrade to 2.1.6 - Finally!!!
March 08, 2009, 02:11:02 pm

your method seems right. To make things more clear, i would do the foll:

1. disable the civicrm module from 2.0

2. upgrade drupal5 to drupal6 and ensure you have it working etc

3. update the civicrm codebase and then run the upgrade script which upgrades the civicrm db

4. enable the civicrm module within drupal and retest

as always, keep backup and a way to get back to step 0 if needed

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

Shadow

  • I post occasionally
  • **
  • Posts: 36
  • Karma: 1
Re: The Upgrade to 2.1.6 - Finally!!!
March 08, 2009, 02:53:46 pm
Thanks once again, lobo.  I now hope that I don't get any errors - would like to finsh this project and get on with another one - One week on this project is enough!

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • The Upgrade to 2.1.6 - Finally!!!

This forum was archived on 2017-11-26.