CiviCRM Community Forums (archive)

Ran the upgrader today on a 3.3.5 site, newly upgraded (core only thus far) to Drupal 7 and the CiviCRM upgrader seems to have worked perfectly on a DB with 55K contacts, 2500 events and 130K activities.

Regarding the wiki CiviCRM 4.0 upgrade page, however, there is a bit of a catch-22 because the official Drupal 7 Upgrade Instructions include "Disable non-core modules" which includes CiviCRM. However the upgrade process for CiviCRM requires CiviCRM to be enabled. I think I shall put a note in the wiki to that effect.

The second issue is the additional settings in civicrm.settings.php. Due to the issue above, I actually ran the installer to get the civicrm menu item in my D7 and also it built a fresh civicrm.settings.php and I see it has a whole set of globals which didn't exist in previous versions. Does the upgrader add those if one upgrades?

Nope upgrade does not add new variables to civicrm.settings.php. You will have to manually add it

Hmmm. OK, I will try to run some tests to see if that causes any issues, i.e. if one forgets to add those...

Here's a diff showing the new variables I found - your line numbers may differ!  Something should be added to the wiki - preferably more helpful than this.... perhaps we should just suggest people add these lines to the bottom of their civicrm.settings.php (whereas the first diff below is not quite at the bottom).

209a195,200
>  * Setting to disable or enable profile double optini for add to group in profile
>  * This is disabled by default and functions only if Civimail is enabled.
>  */
>  define( 'CIVICRM_PROFILE_ADD_TO_GROUP_DOUBLE_OPTIN', 0 );
>
> /**

234c225,275
<  *
---
>  * Enables or disables workflow support for CiviMail. Also requires
>  * Drupal AND rules module being enabled
>  */
> define('CIVICRM_CIVIMAIL_WORKFLOW', 0 );
>
> /**
>  * Settings to enable external caching using a Memcache server.  This is an
>  * advanced features, and you should read and understand the documentation
>  * before you turn it on.
>  *
>  * @see http://civicrm.org/node/126
>  */
>
> /**
>  * If you have a memcache server configured and want CiviCRM to make use of it,
>  * set the following to 1.  You should only set this once you have your memcache
>  * server up and working, because CiviCRM will not start up if your server is
>  * unavailable on the host and port that you specify.
>  */
> define( 'CIVICRM_USE_MEMCACHE', 0 );
>
> /**
>  * Change this to the IP address of your memcache server if it is not on the
>  * same machine (Unix).
>  */
> define( 'CIVICRM_MEMCACHE_HOST', 'localhost' );
>
> /**
>  * Change this if you are not using the standard port for memcache (11211)
>  */
> define( 'CIVICRM_MEMCACHE_PORT', 11211 );
>
> /**
>  * Items in cache will expire after the number of seconds specified here.
>  * Default value is 3600 (i.e., after an hour)
>  */
> define( 'CIVICRM_MEMCACHE_TIMEOUT', 3600 );
>
> /**
>  * If you are sharing the same memcache instance with more than one CiviCRM
>  * database, you will need to set a different value for the following argument
>  * so that each copy of CiviCRM will not interfere with other copies.  If you only
>  * have one copy of CiviCRM, you may leave this set to ''.  A good value for
>  * this if you have two servers might be 'server1_' for the first server, and
>  * 'server2_' for the second server.
>  */
> define( 'CIVICRM_MEMCACHE_PREFIX', '' );
>
>
> /**
>  *

We'd just get a blank screen on the CiviCRM upgrade page and the apache2 error.log.

I have updated the WIKI at: http://wiki.civicrm.org/confluence/display/CRMDOC40/Upgrade+Drupal+Sites+to+4.0 in case this is not addressed a different way prior to final release.

Sounds good - thanks!