We have upgraded 4 of our 7 Drupal 6.2 sites to 6.3. In every case they report as being 6.2 in the available updates and suggest we need to upgrade the version - after the upgrade is completed.
I have downloaded 6.3 twice from the Drupal website just to make absolutely sure I am upgrading to the correct version. the Changelog.txt file clearly states it is version 6.3.
The only folders / files I don't replace when performing an upgrade are modules, themes and sites. Is there something in here that reports the version?
Whats happening here?

Comments

vm’s picture

vm commented

it could just be that the update status hasn't caught up yet.

you can run cron.php
and also try clearing the cache in adminsiter -> performance

damien tournoud’s picture

damien tournoud commented

The only folders / files I don't replace when performing an upgrade are modules, themes and sites.

Well, modules and themes *are* part of Drupal standard distribution. Your own files should go into sites, and *only there*.

Here is a copy of sites/all/README:

This directory should be used to place downloaded and custom modules
and themes which are common to all sites. This will allow you to
more easily update Drupal core files. These modules and themes should
be placed in subdirectories called modules and themes as follows:

  sites/all/modules
  sites/all/themes
spyjournal’s picture

spyjournal commented

i wish it was that but no. its reporting module upgrade status just fine, and when i upgrade those, they show as being upgraded.
poormanscron is running every 60 minutes and the cache is disabled.
still looking

spyjournal’s picture

spyjournal commented

to clarify - i dont do a bulk replace - but i did replace the core modules and themes
i have now started moving my contributed modules and themes as per this instruction- that was different in previous versions of drupal
still that isnt the issue - the problem is that the modules report their upgrades correctly
drupal 6 to 6.1 and 6.2 reported correctly. 6.2 to 6,3 doesnt

spyjournal’s picture

spyjournal commented

ok i ran the whole thing again and it is now working - weird
so bug is closed
apologies

spyjournal’s picture

spyjournal commented
Status: Active » Closed (fixed)
cwgordon7’s picture

cwgordon7 commented
Status: Closed (fixed) » Fixed

Please don't mark issues directly to closed.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.