According to Drupal, I need to update CCK from 6.x-2.1 to 6.x-2.2 (2009-Mar-18).
For some reasons, Plugin Manager seems it doesn't "see" this update.

No problem, I'll update it manually. But if you hit the same "bug", please check it.

Thanks and congrats for your work.

Giovanni

Comments

PghFreeNet’s picture

I used the plugin_manager's search page to locate the module and added it to the install queue, then clicked the plugin_manager update link in the menu. Everything seemed to work the same from that point on and it shows up as updated now .

Antinoo’s picture

Version: 6.x-1.9 » 6.x-2.x-dev
Status: Active » Closed (fixed)

Yeah, it worked also in this way.
However, I think it's not the normal behaviour, it should be showed also on admin/plugin_manager/update.
I'm going to close this issue, if any other should hit it, reopen it.

Giovanni

ps. I cannot select the 6.x-2.1 version for this issue.

Anonymous’s picture

Status: Closed (fixed) » Active

I have the same two little problems like Antinoo:

  • Plugin Manager doesn't offer me the Update for CCK on Version 6.x-2.2
  • and there is no possibility to choose Version 6.x-2.1 from the drop-down-list for this issue; the last entry is 6.x-1.9. So we have to take 6.x-2.x-dev.

It's not the end of the world, but it's a strange behaviour for this - apart from that - great module!

Regards
Stefan

slinc’s picture

Version: 6.x-2.x-dev » 6.x-1.9

Same problem. Seems quite strange. This problem also happens with modules that have become "not supported".

rallycivic’s picture

I have this problem too.

The Available Updates page admin/reports/updates says "Security update required!" for CCK, and wants this version:

Security update: 6.x-2.2 (2009-Mar-18)

Is it because it is listed as a security update rather than a normal update?

bsimon’s picture

I have the same problem

Also the CCK version dropdown on the /admin/plugin_manager/install page has 6.x-2.2 listed 3 times. Maybe there's a connection between these issues?

Otherwise I had no problem upgrading to CCK 6.x-2.2 with plugin manager

slinc’s picture

I realized that this problem always occurs when the update is a SECURITY update. This happens with wikitools also. I'm not sure if this is by design or if this is a bug.

Alex Andrascu’s picture

Any news on this one ? Seems it's still happening.