CiviCRM Community Forums (archive)

I am getting concerned with D6 coming to End-Of-Life that I need to get onto D7.

The site is currently limping with Civi 3.4.8. There are various problems / issues which I have not had the time nor expertise to get to the bottom of. Various things which once worked, and due to Civi upgrades have become broken.

Is Civi 4.0.8 essentially the equivalent Civi code as 3.4.8, only married to D7 in place of D6? Perhaps migrating to that version would not introduce much new breakage? Thoughts of how to get up to D7 without having to invest lots of time fixing yet more Civi bugs? Thank you!

Known exploits in the current Civi build available for D6? That is not encouraging to hear. 

Thank you for confirming my thought an accurate impression.

rrrrr?

I recalled reading in the release notes that Civi 4.x branch was primarily intended for D7, D6 users are operating on their own risk for going to that branch. With as sick as Civi currently is, that has kept me from venturing into such waters.

So, has Civi 4.x on D6 become well tested in the community?

Is that the same code version we will need to be on to do the D6--->D7 upgrade anyway? That would certainly be appreciated... not having to big-bang upgrade both Drupal AND Civi in one fell swoop. You have my interest perked, Eileen! 

My my, apparently it 'tis documented at least...
Upgrade Drupal Sites to 4.3 - Drupal 6
http://wiki.civicrm.org/confluence/display/CRMDOC43/Upgrade+Drupal+Sites+to+4.3+-+Drupal+6

And it looks like all prerequisites are satisfied by the current server configuration. (Specs accurate in my Civi forum profile.) Oh, no it's now... Requirement for PHP 5.3.3+ and our server currently is running PHP 5.3.2. hhhmmmm... Do I dare attempt with the version our current server has?

Oh, more fine print...

A direct upgrade from 3.x series will probably fail, try upgrading to 4.1 first and then 4.2.x before continuing with 4.3.

So what should my stop-off's be from 3.4.8 to 4.3.4? Stopping at each highest release in the last number for the middle version number? Highest in 4.1.x, then highest in 4.2.x to arrive at 4.3.4?

We have probably around 10 + sites running drupal 6 with CiviCRM on 4.2 and the only customers we have on 4.3 are drupal customers (although we haven't upgraded any existing customers to 4.3 - these are drupal 6 sites that are joining our stable). Most of our larger customers,  and indeed most of the customers we deal with who have contributed code to core or $ to MIHs are still on drupal 6.

The disclaimer on drupal 6 is because Core doesn't want to be responsible. But the only drupal 6 specific problems we have had over the past 2 years has related to OG integration and is fixed. I  consider drupal 6 integration to be rock solid as far as 4.2 and, although we haven't upgraded to 4.3 yet the drupal 6 aspect does not give me any cause for concern.

I would upgrade your site to 4.1 first because that is the point you edit your civicrm.settings.php. You then have a call as to whether to upgrade to 4.3.4 or 4.2.10 - since you need to get php upgraded to run 4.3. 4.2.10 is not out yet but is pretty much  - & it has all the latest security fixes (although hopefully it will be really released very soon)
http://baalbek.net5.bidon.ca/civi-lts-testing/civicrm-4.2.10-drupal6.tar.gz
 

So, going to the Civi 4.3.x branch requires the higher level of PHP... while Civi 4.2.x would be compatible with our current PHP 5.3.2?

I believe so.

Re OG - the problem I mention is fixed - I only mention it because it did cause problems