Distinguish between released versions of the same project when selecting projects to upgrade with Update manager

Created on 15 July 2009, almost 16 years ago

Updated 1 May 2025, 11 days ago

This issue is waiting on it's parent #395474: Plugin Manager in Core: Part 2 (integration with update status) → to be committed.

In the parent issue, DWW's position was that if the Plugin Manager doesn't respect the original Update Status differentiation between different versions of the same project, then users will be unable to choose between a 1.2 security update version and a 1.3 released version (most current).

DWW: Upgrading your Drupal site is *not* as simple as running "software update" on your Mac, and it never will be given how Drupal actually works and exists in the world. This interface has to reflect reality. If you want to completely simplify the interface and hide all the "ugly" details from the "less knowledgeable audience", then you have to change reality. You can't make the interface reflect your ideal vision of reality and then hope reality will magically shift on its own.

Then, later on, Catch summed up the situation with:

We're losing some of the finer grained reasons for upgrading - i.e. I'm on Views 2.6, and Views 3.0 UNSTABLE-1 comes out - the current UI tries to suggest some caution about upgrading to unstable 1 (or alpha, beta, rc), if we only have red and blue, and no descriptive text then we're losing some of that.

There's also the issue of being on 2.5 and having the option of 2.6 OR 3.0-UNSTABLE-1 which the current UI doesn't support. i.e. does it default to 2.6 or 3.0-unstable1. If it defaults to 2.6, will I get nagged to upgrade to 3.0-unstable-1 as soon as I've updated to 2.6? Or do we only ever recommend stable releases from this interface? What if I'm running dev and there's a newer dev build.

There are also other statuses for currently installed modules which are critical but aren't a security update - the main two is when a module author unpublishes a release because it's unsupported - i.e. sites running panels-6.x-2.x which should be prompted to upgrade to panels-6.x-3.x - IMO these should just be red as well.

Then there's the situation where rather than a new security release, modules are so broken that we recommend uninstalling them completely - see http://drupal.org/node/318746 - this status is 'revoked' in the current UI. As far as I can see, the current UI wouldn't show those modules at all, because they don't have updates as such.

Note, I don't think we need to allow for fine-grained updates of contrib modules via this UI, if you want that, use tarballs, drush or cvs - but these particular sitautions where either uipgrading, or not being prompted to do something else can result in a hosed site ought to be dealt with I think.

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

update.module

Created by

🇺🇸United States Senpai

Live updates comments and jobs are added and updated live.

Usability
Makes Drupal easier to use. Preferred over UX, D7UX, etc.

Update manager

Update manager dev

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 11 days ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!
Comment 11 days ago →
🇺🇸United States dww
The Update Manager has been deprecated or removed from core. This is no longer still relevant to the 11.x branch.
Comment 11 days ago →
🇺🇸United States smustgrave
Thank you for checking!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024