Answers.Body: <p>I suppose, <em>never mind</em>... By the morning it started showing everything correctly. Still curious, where this information is coming from - maybe running <code>cron</code> in CRM changed it. I ran <code>cron</code> in Drupal - but probably not in CiviCRM</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-20T19:19:03.907Z
Answers.Text: Did you flush all Drupal caches too?
Answers.UserDisplayName: themak
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-20T19:24:37.803Z
Answers.Text: You mean, like here: https://docs.civicrm.org/sysadmin/en/latest/upgrade/drupal7/#clear-cached-files - Delete all files in `sites/default/files/civicrm/templates_c/`? Yes, I did. Or some other way?
Answers.UserDisplayName: Felix
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-23T14:58:44.330Z
Answers.Text: https://www.drupal.org/docs/7/managing-site-performance-and-scalability/caching-to-improve-performance/caching-overview
  
  There are tools - such as the Administration menu which gives you an easy link to flush all caches in Drupal.
Answers.UserDisplayName: themak
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-20T16:21:39.657Z
Answers.LastActivityDate: 2018-10-20T16:21:39.657Z
Answers.UserDisplayName: Felix
Answers.Body: <p>I find sometimes upgrading via drush does not run the db upgrades but instead gives a message about being already upgraded. Drush prints the URL that you need, and pasting that to your browser completes the upgrade.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-23T21:59:14.593Z
Answers.Text: Thanks. In this case I saw that database update *did* run; and when I pasted the URL also told me that db already ran. Probably, just cron did something...
Answers.UserDisplayName: Felix
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-23T09:30:03.803Z
Answers.LastActivityDate: 2018-10-23T09:30:03.803Z
Answers.UserDisplayName: Aidan
Body: <p>I have CiviCRM for Drupal 7. Just upgraded from 5.4.0 to 5.6.0 via drush. Everything seems OK, including database. Drupal module page shows 7.x-5.6.0. However, CiviCRM status page still thinks that I have 5.4.0 and suggests that I either apply patch to 5.4.1 or upgrade to 5.6.0. I deleted template_c files... How come?</p>
  
Tags: <drupal><upgrade>
Title: After upgrade to 5.6 status still shows 5.4.0
ThreadText: # After upgrade to 5.6 status still shows 5.4.0
  
  (Asked by: username_0 on 2018-10-20)
  
  I have CiviCRM for Drupal 7. Just upgraded from 5.4.0 to 5.6.0 via drush. Everything seems OK, including database. Drupal module page shows 7.x-5.6.0. However, CiviCRM status page still thinks that I have 5.4.0 and suggests that I either apply patch to 5.4.1 or upgrade to 5.6.0. I deleted template\_c files... How come?
  
  **Tags:** drupal, upgrade
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2018-10-20. Score: 1
  
  I suppose, *never mind*... By the morning it started showing everything correctly. Still curious, where this information is coming from - maybe running `cron` in CRM changed it. I ran `cron` in Drupal - but probably not in CiviCRM
  
  > **Comments:**
  > **username_1**: Did you flush all Drupal caches too?  
  > **username_0**: You mean, like here: https://docs.civicrm.org/sysadmin/en/latest/upgrade/drupal7/#clear-cached-files - Delete all files in `sites/default/files/civicrm/templates_c/`? Yes, I did. Or some other way?  
  > **username_1**: https://www.drupal.org/docs/7/managing-site-performance-and-scalability/caching-to-improve-performance/caching-overview  There are tools - such as the Administration menu which gives you an easy link to flush all caches in Drupal.  
  
  ---
  
  ### Answer by username_2 on 2018-10-23. Score: 0
  
  I find sometimes upgrading via drush does not run the db upgrades but instead gives a message about being already upgraded. Drush prints the URL that you need, and pasting that to your browser completes the upgrade.
  
  > **Comments:**
  > **username_0**: Thanks. In this case I saw that database update *did* run; and when I pasted the URL also told me that db already ran. Probably, just cron did something...  
  
  ---
  
  