I use a lot of development versions of modules. The plugin manager always recognizes the recommended versions (as mentioned in the updates status report) as an update. Applying the updates in my case would mean a step back. I would prefer to really upgrade to a newer development version.

I admit that in a production environment the default behaviour is best. Maybe a configuration option could switch the behaviour if needed.

I also suggest to improve the module by not only displaying the modules/themes to be updates (the page with the checkbox ahead of each newer module) but also the current and the newer version numbers. Finally I could imaging that a history function for updates would be fine. (I only wanted to get rid of these suggestions, the issue is about updating dev versions).

Comments

FrankT’s picture

FrankT commented

Thinking about how to solve it best, I come to the conclusion that it would be best to list the modules with newer versions with the option which newer version to choose.

For example:

[] Module V6.x-1.0
    [] Module V6.x.1.0     [] V6.x-1.x-dev (10-Oct-08)

[] ModuleB V6.x-2.0
    [] Module V6.x.3.0     [] V6.x-3.x-dev (09-Oct-08)
   
[] ModuleC V6.x-1.1
    [] Module V6.x.1.2

[] ModuleD V6.x-1.0
    [] V6.x-1.x-dev (01-Oct-08)

[] ModuleE V6.x-1.x-dev (25-Sep-08)
    [] V6.x-1.x-dev (01-Oct-08)
jabapyth’s picture

jabapyth commented

I believe that update.module is aware of -dev versions, and suggests accordingly.
PM get all its update data from update.module, so I would assume that it would suggest to upgrade to the latest dev version if thats what you have.

FrankT’s picture

FrankT commented

Yes, the update module is aware of dev versions correctly.

Currently (for example) updates displays the module 'Advanced Forum' installed as 6.x-1.x-dev (2008-Oct-28), recommended is 6.x-1.0-alpha13 (2008-Oct-21), also available is 6.x-1.x-dev (2008-Nov-03).

PlugIn-Manager recognizes, that (among others) the module must be updated. The install screen displays a part of the alpha13-version with the md5_file hash, but there is no way to update to the newer dev version.

So PlugIn-Managaer seems to offer the recommended version only and doesn't let me chose another available version.

FrankT’s picture

FrankT commented
Status: Active » Closed (fixed)