Version-specific upgrade tasks¶
In general the steps to upgrade CiviCRM are identical no matter which version you're upgrading from and to — however this page offers some exceptions.
Here you will find special steps needed when your upgrade crosses certain CiviCRM versions.
For example, if you are upgrading from CiviCRM 4.1 to CiviCRM 4.3, then you should check this page for both "CiviCRM 4.2" and "CiviCRM 4.3" since your upgrade "crosses" both of those versions.
Flush CiviCRM cache¶
cv flush to cleanup caches.
Background: Settings are usually stored in the civicrm_setting table, where they're easily maintained. But there are occasions when developers might find it useful to override them. For instance, the development environment might mirror the production environment, except for a handful of settings. Adding a few lines to the civicrm.settings.php file can be much easier and less error-prone than changing production settings for development.
The settings in the
civicrm_setting table are keyed on
name. Here's an example using the CiviCRM 4.1 mechanism:
define('URL Preferences.customCSSURL', 'http://example.com/css');...
domain is determined by the civicrm.settings.php file, the group is 'URL Preferences', the name is 'customCSSURL', and the
http://example.com/css. If you're uncertain of the valid values these can take, inspect the
The change: In CiviCRM 4.3 and later, the format has changed to:
$civicrm_setting['URL Preferences']['customCSSURL'] = 'http://example.com/css';...
Password must be supplied to cron¶
If you are running scheduled jobs using
CLI.php, you will need to reconfigure cron to include a password. Scheduled jobs will no longer run if the password is not provided..
All CiviCRM-related cron jobs will stop working as soon as any site is upgraded from 4.1.x and below. If you are upgrading from a version prior to 4.2, cron jobs will need to be reconfigured using the new Scheduled Jobs method.