CiviCRM Community Forums (archive)

I attempted to upgrade from 2.2.6 to 4.1.1 on Drupal 6.22.  I used the instructions from the civicrm wiki.

When I got to step 8, I ran the upgrade script and I got the initial upgrade screen.  I clicked the button to upgrade and got a white screen with this message in my apache log:
PHP Fatal error:  Call to undefined method CRM_Core_BAO_Preferences::value() in /var/www/html/drupal-6.latest/sites/gfn.org.mbea/modules/civicrm/CRM/Upgrade/ThreeZero/ThreeZero.php on line 203

I have performed a similar upgrade in the past without any issue, but it was only upgraded to 3.something and not to 4.  Should I do this in steps?  Anybody know how to solve?

I was able to update from 2.2.6 to 3.1.6.  I havn't tried yet to go from 3.1.6. to 4. 

@devfloppy did you figure this out?  Did you end up upgrading from 3.1 to 3.2, then 3.2 to 3.4?

@devfloppy did you figure this out?  Did you end up upgrading from 3.1 to 3.2, then 3.2 to 3.4?

To upgrade from 3.1 to 3.4, or even from 3.1 to 4.1 should be fine.

I need help with a few steps beyond the installation and upgrade process above.  I am getting the same error that devfloppy listed at the start.  The site I am trying to work with runs Drupal 5.x with a 2.2.6 CiviCRM module.  Before starting I made sure to back things up as best as I could in order to make sure I didn't lose the web content or the CiviCRM database.

My hope is to update to Drupal 7 and CiviCRM 4.1.2.  My expectation is that by doing this (and following the support documentation for maintaining the database schema) the CiviCRM database will be made compatible with 4.x.  From there, I hope to supply the database to Wordpress, since I read elsewhere on the forums that the database should be portable between Drupal and Wordpress for CiviCRM 4.x.

I think it would be alright to keep using Drupal if that is the necessary outcome.

The failed attempts I have made so far:

• Replacing all Drupal 5.x files with 6.x, while preserving the 'sites' folder, visiting install.php, and then replacing the CiviCRM module with 4.1.2, visiting upgrade.php
• Replacing all Drupal 5.x files with 6.x, while preserving the 'sites' folder, and replacing the CiviCRM module with 4.1.2, visiting either install.php or upgrade.php
• Replacing all Drupal 5.x files with 6.x, while preserving the 'sites' folder, visiting install.php, then replacing 6.x with 7.x, while preserving the 'sites' folder, visiting install.php again (I have not tried to replace the CiviCRM module yet for this)

I didn't get the same errors each time.  One of them has to the with the images module being upgraded while installing Drupal 6.  Regardless of the error, I have been restarting from my backups every time, since I need to keep the database useable.  I read elsewhere that installation/upgrade errors can damage the database.  I can build the site all over, but the database is too critical to let go of right now.  I don't know enough about working with databases in order to get it to work with Wordpress, otherwise I would just do that.

At this point, I am at a loss for what to do.  I believe I have accurately listed my failed attempts, but I am willing to try all the installation/upgrade combinations again.  If the consensus is to upgrade CiviCRM to 3.1 before 4.x, then my question turns to:
Do I replace the Drupal and CiviCRM module files all at once, or do I do one before the other?
Which step do I take next - Installing Drupal 6, or Upgrading to CiviCRM 3.1?


Edit:
As a mention, I have always changed the civicrm.settings.php file appropriately for the installation of Drupal being used with CiviCRM.

Also, I forgot to ask if I need to remove the old CiviCRM module files before extracting the new ones.

Thank you Hershel!  I appreciate the help.  I will write back if I get any other errors that I can't explain.

Cheers!

As part of my testing on CRM-10007, I tried doing a 2.2.8 = > 4.2 (trunk) upgrade and ran into the same issue. I patched the obvious/fatal errors in trunk (r40252, r40259, r40262), and the standard web-based upgrade appears to complete without errors.

Here are some cases that I tested:

CMS	From	To	Medium	Outcome
D6	2.2.8 (tar)	4.2.x (trunk+branches/v3.4)	Web (civicrm/upgrade)	Completes without any obvious errors
D6	2.2.8 (tar)	4.2.x (trunk+branches/v3.4)	Drush	"civicrm-upgrade-db" runs w/o obvious errors, but "civicrm-update-cfg" fails
D7	4.0.x (branches/v4.0)	4.2.x (trunk)	Web (civicrm/upgrade)	Completes without any obvious errors
D7	4.0.x (branches/v4.0)	4.2.x (trunk)	Drush	Completes without any obvious errors

I don't currently have plans to test upgrades from 2.2 diligently, but maybe this is a helpful starting point for someone with a keener interest.

Unfortunately, no, and I probably should have used less developer-speak.

The most recent release, 4.1.2, hasn't changed -- it still suffers from the issues which prevent a direct upgrade, and your best bet is to proceed with the intermediate upgrade (as other folks advised).

When the next release, 4.2.alpha1, comes out, it will include some fixes for direct 2.2=>4.2 upgrades. The next release is at least a few weeks away, so it may be too late to help with your current project. But I wanted the folks here to know that some action was taken to fix this issue.