1

I recently used drush to update my site. This is the current drush status:

$ drush status
 Drupal version                  :  7.29                  
 Site URI                        :  http://default        
 Database driver                 :  mysql                 
 Database username               :  %$^&*(         
 Database name                   :  %$^&*(         
 Database                        :  Connected             
 Drupal bootstrap                :  Successful            
 Drupal user                     :  Anonymous             
 Default theme                   :  openchurch_theme      
 Administration theme            :  seven                 
 PHP configuration               :  #$%^&*
 PHP OS                          :  Linux                 
 Drush version                   :  6.4-dev               
 Drush configuration             :                        
 Drush alias files               :                        
 Drupal root                     :  #$%^&*  
 Site path                       :  sites/default         
 File directory path             :  sites/default/files   
 Temporary file directory path   :  /tmp                 

But when I visit my admin page, I still get the "You need to upgrade" message. How do I get it to stop?

Here is the update screen: Update screen

  • What message are you getting exactly? There's one for a core upgrade and one for general security updates I think, maybe you're seeing the latter if some of your contrib modules are out of date? – Clive Jul 24 '14 at 17:30
  • @Clive It is asking for a Drupal Core security update. – cwallenpoole Jul 24 '14 at 17:56
  • what does /admin/reports/status show as the current version of Drupal? – Geoff Jul 24 '14 at 20:09
  • OK. Strangely enough, the status page said that version 7.30 was available. Why was 7.29 listed on the upgrade page? – cwallenpoole Jul 25 '14 at 15:39
0

In this particular case, the issue was that Drupal 7.30 had become available, and the UI of the site was reporting that it had 7.28 installed. This was cached by an out-of-date cache, I believe. Everything was resolved when I updated from 7.29 to 7.30.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.