This has been happpening to me. I searched for "site map" module, and installed it, and then was annoyed to see that it installed the dev version instead of the the available stable version. Also, in the "updates" section, dev versions are showing up as well. It also installed the dev version for CCK, which made me none too happy when I realised it.

Comments

traceelements’s picture

I just realized that it also downloaded an alpha version of views instead of the recommended stable version. It also installed a pathauto dev and webform dev, and there's more... Dang it. I now have to go through all of my websites and swap out modules.

Anonymous’s picture

:( I've been working on that for the past few days. I think that I'm fairy close to a fix.

DrewMathers’s picture

Version: 6.x-1.10 » 6.x-1.x-dev

Joshua,

The Administration Menu module is presenting a special case which is not handled correctly. When I select version 6.x-1.5, PM (-dev 2010-Jan-11) installs Admin Menu 6.x-3.0-alpha3. A look at the Admin menu project page illustrates this version confusion.

http://drupal.org/project/admin_menu

DrewMathers’s picture

The above-mentioned special case with Admin Menu is handled correctly in PM 6.x-1.10

sjz’s picture

It's been doing the same thing with YUI Module ... Just had to undo an RC install.

I understand that the module is being rewritten but just thought I'd mention it for the record. I love the module so look forward to seeing the next incarnation.

darioshanghai’s picture

Reporting the same bug here. Installed many development versions including modules like Zen (and related) with several bugs and in some cases, like views module, an "Other release", an alpha2 with a few annoying bugs.

Shouldn't the sense of this module be to simplify installation? Why not installing recommended versions only? It's really confusing.

Scott J’s picture

Oh, so it does. I just got CCK 6.x-3.x-dev , and Views 6.x-3.0-alpha2 . I'm glad that I double-checked.
Thanks for the heads-up.
Scott J.

kmajzlik’s picture

Status: Active » Closed (fixed)

/admin/plugin_manager/settings --> uncheck Choose "Latest Version" -> then you select version on each install.

DrewMathers’s picture

Status: Closed (fixed) » Active

Comment #8 provides a workaround not a solution, so this issue is still active.

The Update module's update_calculate_project_data function provides a complex algorithm for choosing a recommended version of an update. This might be used by Plugin Manager.