I have just installed Mollom 7.x-2.14. I am now getting a notification under available updates that the recommended version is 2.13. What's going on? Should I revert to 2.13?

CommentFileSizeAuthor
#4 mollom.png16.08 KBFrank.dev
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Andrew Perriman’s picture

Issue summary: View changes
bestandestravel’s picture

I have the same problem, must be a confusion, I will wait before changing version.

eshta’s picture

That's very strange... I'm not sure of the cause yet - but 7.x-2.14 is the latest D7 version and is listed properly on the project home page as the currently recommended version: https://www.drupal.org/project/mollom

Frank.dev’s picture

FileSize
16.08 KB

Same for drupal6 - see detail-picture from ".../admin/reports/updates":

eshta’s picture

This may seem silly, but was update.php run?

jcerdan’s picture

I'm facing the same problem. update.php has been run, but the problem is still there...

Frank.dev’s picture

same.

eshta’s picture

So what process did you use to update the module? Did you use drush? Trying to reproduce...

eshta’s picture

Actually what I'm seeing is that updates.drupal.org doesn't have the latest release in the XML feed. This is why sites will show 7.x-2.13 as the latest (for the D7 module at least). The project page is correct for latest versions, however. I'm asking around to see what needs to be done to kick the tires on the updates site.

Frank.dev’s picture

okay and thanks, eshta - I 'm waiting for updates.drupal.org. ;-)

eshta’s picture

Status: Active » Fixed

Looks like everything is back to normal now with the drupal.org updates site. This should resolve the confusion.

jcerdan’s picture

I confirm. Everything is ok now. Thanks!

ju1i3’s picture

I'm still getting the red notice that Mollom should be updated to 7.x-2.13. I have Mollom 7.x-2.14 installed.

eshta’s picture

ju1i3 - You'll need to manually check for updates again as Drupal will read the cached local version information until that is run either manually or via cron.

ju1i3’s picture

Thanks, I'm not thinking very well today! I cleared cache, ran cron and it's ok.

eshta’s picture

I know those days well - glad it's working :-)

Status: Fixed » Closed (fixed)

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