7

The instructions you found I have used several times and I think they are still valid. So, in your case first upgrade CiviCRM to a version with both a drupal 6 and drupal 7 version, then upgrade drupal and use the same version of CiviCRM. Then I'd advise to further upgrade CiviCRM to the Long Term Support version 4.6.


6

OK, turns out this was due to erroneous entries in the Drupal settings.php file. The following entries were causing cookies to be missed by Civi:- ini_set('session.cookie_lifetime', 2000000); ini_set('session.gc_maxlifetime', 200000); Others may also cause inconsistencies, such as:- ini_set('session.cache_expire', 200000); ini_set('session....


6

Line 435 in CRM/Export/BAO/Export.php that your error message is referring to says: if (!empty(self::defaultReturnProperty($exportMode))) { This will give an error in all PHP versions below 5.5. From the PHP manual (http://php.net/manual/en/function.empty.php): Prior to PHP 5.5, empty() only supports variables; anything else will result in a parse ...


6

Pete is right that even recent versions of CiviCRM (certainly in the 4.6.x series) work with Drupal 6 sites. The "no longer officially supports" issue is that the core team won't go out of their way to make D6-specific fixes. That said, I have encountered problems with new installations on Drupal 6, but this has been for testing--why else would someone ...


5

We have Drupal 6 sites running just fine on the 4.6.x series. I don't know where you read that 'civicrm no longer supports drupal 6" - is it not more the case that Drupal no longer supports Drupal 6 and hence all module information concerning D6 is incorrect


3

Try disabling the logging functionality using API Explorer. Navigate from the menu link - Support -> Developer -> API Explorer. Or using Drush(if drupal) - drush cvapi Setting.create logging=0


3

SOLVED: For good measure here is a repeat of the above comment. I was able to successfully install the upgrade to 4.7.21 on Drupal 6 after applying the patch mentioned above, and after disabling Views, CTools and Webform (and all related/dependant modules). The upgrade then ran smoothly without any problems.


3

We have had to create this field in the db in several sites we have upgraded. Not sure why the upgrade script is failing to do this correctly Fuzion have provided a patch for this to avoid the problem for future folks doing upgrades


3

From CiviCRM 3.3.2 to 5.x latest is a huge task. Lots of things that can go wrong in the process. And if anyone has ever made any schema edits to your CiviCRM database tables upgrading could be very painful. Have you considered installing a fresh 5.x and then doing an export out of 3.3.2 -> import into 5.x of the data you want to carry forward? It will be ...


3

I have been running Civi 4.7.6 on a Drupal 6.38 production site. Seems to be working just fine :-) Am busy installing to security upgrade 4.7.7 now so hold thumbs nothing breaks :-)


2

Ok... got what the issue. I downloaded latest drupal. that is drupal 8.x.x ... CiviCRM version exists only for drupal 7... Now I am facing different issue. but this is solved.


2

Cesar, I had similar requirement to upgrade 3.3.1 to 4.7.31 few months back. Here is what i did Performed Incremental upgrade for CiviCRM on drupal 6 3.3.1 to last version of 4.0 4.0 to last version of 4.2 4.2 to last version of 4.5 4.5 to last version of 4.7 Installed CiviCRM 4.7.31 on upgraded drupal 7. Replaced the db for CiviCRM from #1 into #2 ...


1

The mention of changing CIVICRM_UF from Drupal to Drupal6 suggests to me that you're downloading the "Drupal" (i.e. Drupal 7) package of CiviCRM. Instead, download the Drupal 6 version. These are available from Sourceforge.


1

You're installing Civi/Drupal and Civi/WP on ... Windows? What's the motivation for doing this? If this is an R&D environment and your machine is up to the task I think this would all work much better as a pair of Linux virtual machines running under Virtual Box. My day to day machine is a MacBook Pro with 16 gig and an SSD for storage. I could easily ...


1

For some the answer has been to resolve the Timezone error, if it is present - see: http://civicrm.stackexchange.com/questions/14841/error-datetimezone-construct-unknown-or-bad-timezone-7200 If you have stumbled upon this thread more recently - we found a blank status page after a recent upgrade from 4.6.30 to 4.7.27 where there was no timezone error, in ...


1

I have a similar setup running Drupal 6 and CiviCRM 4.7.25. My system also showed System Status: Critical and no messages. The issue was is that it first attempts to set the time zone and if that fails it doesn't output any further messages for some reason. In CiviCRM version 4.7.25 you can use the API console to run the System.check action by visiting http:...


1

If you have recently upgraded, make sure you clear your caches, including the contents of /sites/.../files/civicrm/templates_c/*


1

A patch has been accepted for this. https://github.com/civicrm/civicrm-core/commit/76eeb935253f42e836a58e1f9d077caaa498c947


1

Unless there is a good reason why you have chosen to use Drupal 6, I would suggest that you use Drupal 7 instead. As Laryn points out Drupal will reach end of life soon. Things are more likely to go smoothly if you are using Drupal 7 and you also find it easier to get help. I would also recommend that you use the latest version of CiviCRM - currently 4.6....


1

My colleague wrote those instructions and we have continued to use the same method. I would recommend upgrading to the latest version of 4.6 (Drupal 6) right away. Your version is very insecure. This might best be done in two stages. 3.3.5 >> 3.4.8 to get the last and final version of the 3.x series (against which most 4.x upgrade tests were done) 3.4.8 >> ...


Only top voted, non community-wiki answers of a minimum length are eligible