By tbc_keyworth on

Hi,

I've taken over supporting a Drupal 7.15 site; for the past few days, it has been displaying one security update warning, as well as other not-so-urgent updates to perform. I have been trying to address them using the Update Manager. But after the updates have run fully, within 24 hours I'm getting the same update warnings, for the same versions of the modules.

I follow the on-screen instructions: essentially, having backed-up the database and site files,through Update Manager I download the modules; then agree to the installation; place the site in maintenance mode; then go through the database updating. At the end, I take the site out of maintenance mode, run cron, and check the security updates again; it always comes back clean, but by the next day the warnings reappear for the same versions of the same modules.

To check this, I downloaded the modules which I installed on the live site back onto my machine. When I check the version information, these are the correct, newest versions; so it's not the upload onto the server, but the recording into the database of the active version which is the problem. Is this a known problem and is there a working solution?

⋅ Categories: Drupal 7.x

Comments

Donatas’s picture

Donatas commented

Same here, but with drupal core. Updated to 7.16, but the update manager shows 7.15 and security warning.

tbc_keyworth’s picture

tbc_keyworth commented

Interesting! So at least it's not me.

I'm not a Drupal expert but, for lack of any other workable idea, I used PHPMyAdmin to look at the database. What I found while nosing around in the "cache_update" table is that the most recent entry in the BLOB-format log entry contains a reference to the version of most recent module I updated.

What I deduce (rightly or wrongly) from this, is that at least part of the update is making its way into the database. So what could be preventing it from acknowledging the full update?

charoite’s picture

charoite commented

I'm having the same issue as well, but for me, it is less then 24 hours.
I did the instructions of upgrading it once and it said it was using version 7.16.

Today, it was back to 7.15, so I went through, deleted the old and saved what I needed, and installed the 7.16 again. After about 3 hours of working on it, it told me that I needed to update it because it was now back to 7.15, even though 3 hours earlier it was saying it was on 7.16 without any need for an update.

As halloween is coming up, maybe this is a "ghost in the machine"

tbc_keyworth’s picture

tbc_keyworth commented

Ha! Yeah, that's about how I feel; there's something I can't perceive, but it is haunting me. Quick question- did I even post this support request in the right forum? Is there a better one to post it in? Can't believe that there isn't already a thread regarding module updating failures.

B.P.B’s picture

B.P.B commented

I have the same issue.

http://drupal.org/node/1825024

http://i45.tinypic.com/357m3b9.png

Following...

andyguzman’s picture

andyguzman commented

Similar issue here.
Most of my upgrade to 7.16 went fine but it is refusing to acknowledge that I've updated Entity Reference in the same way.

I was wrong. I had somehow placed a module within another module's folder. Drupal was looking at the nested module instead of the one directly within sites/all/modules. Ugh... silly mistake.