The message: "This update is a major version update which means that it may not be backwards compatible with your currently running version. It is recommended that you read the release notes and proceed at your own risk." is not going away after the module was updated.

Steps to reproduce:

Switched to the latest version
Ran the update.php file (Updates applied with no issues)
Ran Cron
Flushed caches out
Restarted memcache
Ran the Available Updates (Check Manually option)

The new functionality seems to be working OK (new @font-your-face ui is up), the installed module version on admin/modules/list says that the installed version is 7.x-2.0, however on the status report (/admin/reports/status) and in the available updates page (/admin/reports/updates/update) it says that I still have the former version 7.x-1.6. The functionality is fine, just that cosmetic issue that says that I'm still using the unsupported version.

Comments

sreynen’s picture

sreynen commented

That message is from Drupal core, not the @font-your-face module itself, so I doubt this can be solved in the module. Can you describe the "Switched to the latest version" step in more detail? Can you open the file at /sites/all/modules/fontyourface/fontyourface.info (or wherever your module files are) and see what version number it shows?

sreynen’s picture

sreynen commented
Category: bug » support

I'm going to move this to support request until we've identified a specific bug.

Bartox’s picture

Bartox commented

I checked out the fontyourface.info file before posting the issue and it was Ok. This is what it has on the bottom:

; Information added by drupal.org packaging script on 2012-01-09
version = "7.x-2.0"
core = "7.x"
project = "fontyourface"
datestamp = "1326125443"

My servers are on Mac so I use to use rsync to update the modules, I thought something went wrong with that, then I tried a full replace of the module but still getting that message. Not a big deal, the module works just fine.

sreynen’s picture

sreynen commented

Hmm. I'm not sure what might be causing Drupal to see a different version of the module than the .info file reports. Is it possible you have a second copy of the module installed in a different directory? Can you see what is recorded in the system table of the database?

Bartox’s picture

Bartox commented

I've checked that out already and there is not a second copy installed. The system table stores the correct version: 7.x-2.0.

This is the deserialized content of fontyourface module at the system table:

array (
  'name' => '@font-your-face',
  'description' => 'Manages web fonts.',
  'package' => '@font-your-face',
  'core' => '7.x',
  'files' => 
  array (
    0 => 'fontyourface.test',
  ),
  'version' => '7.x-2.0',
  'project' => 'fontyourface',
  'datestamp' => '1326125443',
  'dependencies' => 
  array (
  ),
  'php' => '5.2.4',
  'bootstrap' => 0,
)

Everything seems ok, so not sure what is causing that the Available Updates is not catching up the correct version.

sreynen’s picture

sreynen commented
Title: Unsupported label is not going away after upgraded to the version 7.x-2.0 » Unsupported label is not going away after upgraded module
Project: @font-your-face » Drupal core
Version: 7.x-2.0 » 7.9
Component: Miscellaneous » update.module

Odd. This sounds like an issue with Drupal core's update module, so I'm moving it there.

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented
Status: Active » Closed (cannot reproduce)

if admin/modules/list says you are using 7.x-2.0,
and admin/reports/updates/update says you are using 7.x-1.6
then your cache clear is failing.

check your logs at admin/reports/dblog