By cantthinkofanickname on

I did a manual upgrade. All seems to work but I've run everything I can, all the modules are upgraded but I am still told I need to upgrade because I have 6.13. The DB still has 6.13 in some of it's cache_update and system tables.

Advice appreciated.

⋅ Categories: Drupal 6.x

Comments

cantthinkofanickname’s picture

cantthinkofanickname commented

I have cleared the cache and run cron several times.

Does anyone know where Drupal stores it's version data for the core stuff? Maybe it's in a file somewhere that got missed.

estebandido’s picture

estebandido commented

I've copied the files into the proper directory repeatedly, and yet nothing changes. Very strange.

vm’s picture

vm commented

version information comes from the system.module in drupal core.

The only time I see these issues happen is when users backup their old files and drupal can still see them, thus still uses them. Ensure that all old files are removed from the server. If you must back them up do so on your local machine.

I tend to delete all files and folders except the sites folder and reupload the new ones which ensures I don't have any duplication or leftovers.

veg-o-matic’s picture

veg-o-matic commented

I ran into this problem as well. The instructions say to disable all contributed modules. So do that--disable EVERYTHING except for the core required and optional modules, then click the Save Settings (or whatever) button at the bottom.

Then go back and do it again. You'll probably find that it will take two or three runs through the modules list before you actually get them all disabled. Don't run update.php until ALL modules but core are disabled. Once you do that, you should be good to go.

Of course, then you have to go back and re-enable everything, but at least that's easier.

veg