By holljac on

I've updated from 7.34 to 7.35 and run the update.php ,cleared all caches and run cron. According to available updates, I still need to update to 7.35. Why? I don't know if it's relevant, but when I updated the db it showed no updates needed. Is that correct?

⋅ Categories: Drupal 7.x

Comments

VM’s picture

VM commented

sounds like you've more than one set/or variation of a set of Drupal core files on your server. you'll need to manually inspect the folder structure or perform a search on the server for system.module. If you're 7.34 files are backed up on the server you will need to make sure the backups are outside the webroot so that Drupal can't see them.

holljac’s picture

holljac commented

I don't think so. I deleted everything except the sites folder, then uploaded 7.35. I searched in the db and found references to 7.34 and not 7.35. Is there a way to change these or do I need to? Why no reference to 7.35? On my local version, everything is fine.

VM’s picture

VM commented

I know its seems silly to ask but there are multiple discussions on d.o. forums where this was overlooked: are you sure you are looking at the right site/db versus the server account? Are you sure the files you uploaded again are indeed 7.35?

Where in the database are you seeing references to the drupal version? have you checked the system module .info file?

holljac’s picture

holljac commented

Positive I'm looking at the correct site and db. System.info file says 7.35. I am seeing the reference to 7.34 in the following tables.

cache_bootstrap
cache_menu
cache_update
menu_router
queue
system

VM’s picture

VM commented

I'd clear the cache tables and run update.php again. I don't recall there being any database updates between 7.34 and 7.35 but the version should definitely update. The only other thing I can think of is some 3rd party caching on your server.