Available updates status doesn't change

Hi,

Try running cron again.. I have never encountered the problem you're reporting, and I find it very strange..

Anyway, if you really do have a problem, it would nothing to do with the module itself, but with the update status functionality of core Drupal.

João

No one else reported such a problem, so it was probably some mistake during the module's upgrade process.

I can produce this in 6.12.

I'm using the Mobile Theme. An update is available, so I did like I usually do and just over-write the existing mobile_theme directory with the new stuff. No dice.

So then after struggling with that, I just cleared the mobile_theme directory out completely (deleted the entire directory), then cleared the Performance Caches.
The Theme then went away from the Themes page, but (even with the entire directory gone), Drupal still thinks there was an update ready for the "Mobile Theme" theme, even though it's not there.

It's like the update cache is bad. Anyway to reset that?

At any rate I applied the update, but Drupal still thinks that it's the old version (when the .info file tells me it's not).

I'm seeing this after an upgrade from 6.12 to 6.13. The status report shows 6.13 for core, but Update status shows it as 6.12. I updated a number of modules also, and they all show the older version.

In my case this turned out to be nothing more than a failed svn update. In other words, it wasn't drupal's fault at all. When I finally tracked it down, I had a mix of files between 6.12 and 6.13. A very annoying episode, but not related to Drupal code.

SVN Update????

My issue is with Mobile Theme, still do this day (even after upgrading to 6.13), still persists. Like I said, I cleared out the ENTIRE mobile_theme directory. Made it go bye-bye.
It disappears from the themes page but Drupal update still thinks that it's installed and needing an update... That's why I think it's something wrong with the update cache or something.

Try the check manually link on the updates page. If that doesn't work you can go to admin/build/modules and submit the form - that will clear out update.module's cached data.

I have the same thing. I have deleted everything in the directory and the FTP's the fresh files and still have this. Anything else you need or to check? I attach a printscreen

I'm guessing the problem is from here #166333: Visually display a warning if there are version mismatches within a single project ... you probably have a mix of versions, and update_status is confused, but it's not shouting at you about it to warn you were the problem lies.