Status Issue for Drupal > 6.19

Did you run cron (again) and flushed the caches. This should go away after that.

similar problem here, but my drupal says i have i had 6.19 both on the status page and the updates available page.
flushed the cache and ran cron various times.
i uploaded the drupal files twice until now, overwriting everything but the sites folder. do i have to delete the files before uploading or is overwriting them sufficient?

Deleting the old files is strongly recommended.

ok, thanks, i did not know that.
deleted all files but the sites folder and the .htaccess, then re-uploaded everything.
(i had to use the old .htaccess because otherwise i was getting error 500)
flushed the caches, reran cron, but still the status page and the updates page both report version 6.19.
am i missing something basic here?

where do the status and update page read the version from? is the version written down in some file? if so, i would like to check what is written there in my installation.
this is kind of annoying me, because i keep on receiving emails from my druapl saying that i should update...

maybe is php-apc that is caching the files, can you restart apache?

i'm on shared hosting, so i guess i can't reboot the server. i'll try to contact the support of my hosting company, they are usually very friendly.
the status page says i'm not using APC.
anyway, thank you so far for all the comments

isn't an bug for sure! is a support request. maybe you extract the drupal in the wrong folder..

sorry, i did not intend to change the category, but you changed it while i was writing the text and when i saved my text i reverted the category without even noticing it
i only have one single drupal folder on my server, so i guess it is not the wrong folder. extraction is done on my laptop with 7zip.
anyway, as it seems that this is not a common problem it probably has something to do with my setup or configuration...

can you tell me what version says here /includes/bootstrap.inc in this line define('VERSION', '');

i can't find that text in bootstrap.inc

sorry, I was looking in Drupal 7.

in Drupal 6 is in here: /modules/system/system.module line 12.

/**
* The current system version.
*/
define('VERSION', '6.20');

ok, now search in all folders and sub-folders if you have more files called system.module

i did a search for 6.19 before and it was one hit only, in changelog.txt
searching for define('VERSION' in the drupal folder and all subfolders gives me one hit only in system.module

I think it is likely still the APC cache as suggested by @int. The OP said an apache restart fixed the problem. Maybe @deshilachado could use apc_clear_cache() upon update, but for general core, I'd be afraid it would cause problems on larger sites that rely heavily on APC. Since larger sites probably have access to the server and can clear the cache at their discretion, maybe a contrib module for shared hosting sites would be more appropriate? Or possibly an update setting?

thanks once again for all the time you all are spending on my problem.
zendoodles, i would like to try clearing the apc cache, but i don't know how to 'use apc_clear_cache() upon update'. should i just copy that command into update.php?

maybe it would be a good idea to add that command to the admin_menu 'flush all caches' ?

I seem to recall an seeing APC module now I think about it. Might be worth checking to see if it does the trick. Possibly helps manage other APC things you can't do on a hosted system too. Just guessing here, but maybe http://drupal.org/projects/apc

Also, this may be heresy, but if the only problem is the version number on the admin page (which not many people should even have access too), maybe it makes sense to just wait a few days. Since VERSION is correct, I don't think it effects the way the site runs in any way at all. Assuming the problem is cache, which seems likely to me, it will eventually resolve itself automagically.

Otherwise... the devel module ( http://drupal.org/project/devel ) will allow you to flush Drupal caches, and it does do some things with APC. It may have an option to flush your APC cache (or does it silently when flushing caches anyway). If not, it will definitely let you execute php, so I'd choose using it before putting any code into update.php.

Warning: As usual, please make sure you've backed everything up (db and files) and can revert quickly before you start executing arbitrary php with devel. It may not warn you before doing something scary you didn't intend. You may want to take the site offline first too. Look at http://php.net/manual/en/function.apc-clear-cache.php and consider using apc_cache_info() first to have a look before making changes.

Hi,
these days Druapl 6.21 and 6.22 have been released and I updated to 6.22
but I still have problems with the correct version:
http://example.com/admin/reports/updates says Drupal 6.19 is installed
http://example.com/admin/reports/status says Drupal 6.20 is installed
I dont really care because I know there is Drupal 6.22 installed,
but Drupal keeps on sending me emails every day.

I deleted all old files (except the sites folder) before updating,
I ran update.php various times after updating,
I ran cron various times,
I flushed all caches,
I downloaded the /modules/system/system.module and re-checked the version (it is 6.22).
I asked my shared webhosting support and they say APC is not installed (PHP is running as CGI),
and also http://example.com/admin/reports/status says APC is not beeing used.

Are there any other caches that should be flushed?

I've also had this problem and can't figure out how to fix it. Like the last poster, the /modules/system/system.module file says I'm running 6.22 yet I keep getting the message to update. Has anyone had any luck tinkering with the Aggregator module as this post suggests: http://drupal.org/node/1170332?

Hi @mlr1980,
thanks to the post you linked, I looked at my /sites/all/modues directory and I found that someone (well, the other webmaster or me...) has put a copy of all core modules into the /sites/all/modules directory.

Remember:
core modules should go to /modules
all custom or downloaded modules should go to /sites/all/modules

The problem is caused by the core modules inside the /sites/all/modules directory
(So when earlier @int suggested it might have been the wrong drupal folder, it was actualy quite close to the problem).
@mlr1980 could you please check for the file /sites/all/modules/system/system.module

So how to fix this: read this post
http://drupal.org/node/408306
I did not yet have the time to try it step by step in a clean manner, but a long weekend is in sight.

Thanks for the explanation. I've got dual copies of core modules, though not in the locations you provided. In my case, I've got one copy of Drupal's core modules in /drupal/drupal-6.22/modules, and then a second copy in /public_html/modules. So I suspect that this is why the site is not functioning as expected. Now, which set of core modules gets kept and which gets deleted?

Also, I don't have the file you referenced (/sites/all/modules/system/system.module) since, at least in the way that my site is configured, the sites/all/modules would contain non-core modules.

I had this problem when updating a site. It was caused by the old packaging information still being present in the core module .info files. This happened because I patched the installation rather than install from scratch.

; Information added by drupal.org packaging script on 2010-12-15
version = "6.20"
project = "drupal"
datestamp = "1292447788"

The problem was resolved by removing these lines from all .info files. You can check if you are affected by this problem by searching your installation for the version string:

grep -r "version = \"6\.20\"" *

Scenarios:

• You accidentally restored the old modules folder from a backup.
• You tried to overwrite the older install, but this failed for some reason (common on ftp).
• You made a backup of core modules inside the modules or sites folder.
• You copied a core module to sites/default/modules or sites/[site]/modules to override a core module.
• You are looking at the wrong server or folder (embarrassing, but it happens).

Remember, Drupal prefers core files in sites/all/modules or sites/[site]/modules over those in modules when it finds copies.

To identify the actual files in use, check the filename and info columns for core modules in the system table.

I'm having this problem updating to 6.21 or 6.22 from 6.19 using "drush up drupal-6.21". Drush reports:

Project drupal was updated successfully. Installed version is now 6.21.

Yet the status page still says 6.19, all the module versions say 6.19, and the Changelog only goes up to 6.19. What gives?