By alexJohnston on

I performed an upgrade exactly according to the instructions in UPGRADE.txt.

Site works fine. 'system.module' says it is version 6.16 but the status report still says my site is not secure and available updates tells me I'm still running 6.15 and should upgrade to 6.16.

UPDATE: I DID run update.php...repeatedly.
UPDATE: I checked the system table in the database and it says the the files used from /modules/ and /themes/ are version 6.15 even though the actual .module and .info files in these folders say they are version 6.16. Is the table just not updating? If so, how do I force it to update?

Please hlep!

⋅ Categories: Drupal 6.x

Comments

ambientdrup’s picture

ambientdrup commented

Did you run update.php?

-backdrifting

alexJohnston’s picture

alexJohnston commented

sure did

heine’s picture

heine commented

See http://heine.familiedeelstra.com/drupal-shows-old-version-after-update for a module to help you.

alexJohnston’s picture

alexJohnston commented

I checked the system table and it says everything in my modules and themes folders (not the ones inside of 'sites' folder) are running 6.15. However I look at each of the .info and .module files and they say they are version 6.16. (Yes, I checked on the server). I guess the table isn't being update when i run update.php. Any suggestions?

heine’s picture

heine commented

The table is correct. You still have 6.15 modules somewhere in your installation. Are you looking at the right directory / server?

alexJohnston’s picture

alexJohnston commented

I'm absolutely positive that I'm looking in the right directories on the right server and in the right database. System table says ALL files in use from the root/themes and root/modules folders are version 6.15. ALL .module and .info files in both of those folders all say they are version 6.16. There are no version 6.15 files anywhere else according to the system table. I've flushed all caches (though I doubt this has anything to do with my issue) and run update.php after every change. I've deleted the root/modules and root/themes directories from the server and then uploaded the corresponding files from the 6.16 version (so I KNOW they've been replaced).

Is there any new functionality in any of the core modules that I can check for in my admin menus to verify that they've been changed?

heine’s picture

heine commented

Can you install the doh module, then paste the results here?

alexJohnston’s picture

alexJohnston commented

Doh! You are correct, sir.

john54’s picture

john54 commented

These updates are very complex and many things usually don't but can possibly go wrong.

I've done probably 15 of these types of updates and never experienced a problem until 6.16

I experienced the same thing you did. From the system report page it indicated on the top that I was on 6.16 but below that I had a whole page full of core module related red errors that were referencing all the old releases, 6.1, 6.2, 6.3 and so on. Though my site would run this way I also had no access to my admin area. I would get a parsing related error when attempting to access the admin area.

Turns out in my case I had the bizarre situation of during the update process it somehow reset my PHP back to version 4. Went into the control panel of my site, put it back on PHP version 5, hit rebuild a few times and all was perfect.

??

alexJohnston’s picture

alexJohnston commented

Thankfully my case is not as severe. Site runs perfectly well I just want to complete the update so the red alert box will go away and I can feel safe from the bad people again. :-P