Answers.Body: <p>I'd suspect you didn't actually update CiviCRM, as far as CiviCRM is concerned.</p>
  
  <ol>
  <li><p>Perhaps the old code is still kicking around and accessible to your CMS (e.g. perhaps you left it in, maybe renamed?).</p></li>
  <li><p>Perhaps you have a very aggressive opcache that hasn't recognized the new code yet.</p></li>
  <li><p>Perhaps you didn't install the new CiviCRM codebase that you thought you did (I've done that before often enough ...).</p></li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-21T15:40:49.363Z
Answers.LastActivityDate: 2020-02-21T15:40:49.363Z
Answers.UserDisplayName: Alan Dixon
Body: <p>After upgrading CiviCRM on Drupal 7 to 5.22.1 (from 5.21), the system status page says:</p>
  
  <blockquote>
    <p>The site is running 5.21.0. Additional patches are available:</p>
    
    <ul>
    <li>5.21.1 (2020-01-10): Fix recent regressions involving "Enable multiple bulk emails" and "Payment Summary" table.</li>
    <li>5.21.2 (2020-01-23): Fix recent regressions involving contact date-filters, certain receipts, certain smart-groups, and localized installation."</li>
    </ul>
  </blockquote>
  
  <p>An attempt to run the database upgrade again returns the error: <em>The database has already been updated to 5.22.1.</em></p>
  
  <p>Does this mean the upgrade did not succeed? If it did, how can the system status page be updated?</p>
  
  <p>Help will be greatly appreciated. </p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-02-18T22:10:44.007Z
Comments.Text: Maybe the cache didn't get cleared and it's showing an outdated message. I think it caches those. I'd try clearing cache at administer - system settings - cleanup caches.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-02-18T22:21:53.113Z
Comments.Text: The issue still persists even after clearing the cache.
Comments.UserDisplayName: Raj
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-02-19T10:52:59.193Z
Comments.Text: I've seen this previously where the System Status page hasn't recognised the upgrade but I don't recall the reason why.  What version does it show in the page footers?
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-02-19T17:47:10.827Z
Comments.Text: The page footer shows 5.22.1
Comments.UserDisplayName: Raj
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-02-20T11:06:27.240Z
Comments.Text: try manually running the "Update Check" scheduled job.
Comments.UserDisplayName: HomoTechsual
Tags: <upgrade>
Title: System Status page notifications
ThreadText: # System Status page notifications
  
  (Asked by: username_0 on 2020-02-18)
  
  After upgrading CiviCRM on Drupal 7 to 5.22.1 (from 5.21), the system status page says:
  
  > The site is running 5.21.0. Additional patches are available:
  >
  > * 5.21.1 (2020-01-10): Fix recent regressions involving "Enable multiple bulk emails" and "Payment Summary" table.
  > * 5.21.2 (2020-01-23): Fix recent regressions involving contact date-filters, certain receipts, certain smart-groups, and localized installation."
  
  An attempt to run the database upgrade again returns the error: *The database has already been updated to 5.22.1.*
  
  Does this mean the upgrade did not succeed? If it did, how can the system status page be updated?
  
  Help will be greatly appreciated.
  
  **Tags:** upgrade
  
  > **Comments:**
  > **username_1**: Maybe the cache didn't get cleared and it's showing an outdated message. I think it caches those. I'd try clearing cache at administer - system settings - cleanup caches.  
  > **username_0**: The issue still persists even after clearing the cache.  
  > **username_2**: I've seen this previously where the System Status page hasn't recognised the upgrade but I don't recall the reason why.  What version does it show in the page footers?  
  > **username_0**: The page footer shows 5.22.1  
  > **username_3**: try manually running the "Update Check" scheduled job.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_4 on 2020-02-21. Score: 0
  
  I'd suspect you didn't actually update CiviCRM, as far as CiviCRM is concerned.
  
  1. Perhaps the old code is still kicking around and accessible to your CMS (e.g. perhaps you left it in, maybe renamed?).
  2. Perhaps you have a very aggressive opcache that hasn't recognized the new code yet.
  3. Perhaps you didn't install the new CiviCRM codebase that you thought you did (I've done that before often enough ...).
  
  
  ---
  
  