Message for an unpublished release doesnโ€™t account for no update available

Created on 22 November 2021, about 3 years ago
Updated 5 August 2023, over 1 year ago

Problem/Motivation

Found in ๐Ÿ› Never show a "Not supported!" version as "Recommended" Needs work which has a similar problem for unsupported releases ,
update_calculate_project_update_status() has the message for the case if the current release is unpublished :

'Your currently installed release has been revoked, and is no longer available for download. Disabling everything included in this release or upgrading is strongly recommended!'

. This message doesnโ€™t account for the case if there isnโ€™t an available update.

It appears this code is 10 yrs old and probably no one has ever filed an issue for this problem, so marking it as minor.

Proposed resolution

Change the message for the case if there is no update available.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

๐Ÿ› Bug report
Status

Needs work

Version

11.0 ๐Ÿ”ฅ

Component
Updateย  โ†’

Last updated 3 days ago

  • Maintained by
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States @tedbow
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States @dww
Created by

๐Ÿ‡ฎ๐Ÿ‡ณIndia kunal.sachdev

Live updates comments and jobs are added and updated live.
  • Usability

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

Sign in to follow issues

Comments & Activities

Not all content is available!

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

  • First commit to issue fork.
  • last update over 1 year ago
    29,378 pass
  • @ranjit1032002 opened merge request.
  • last update over 1 year ago
    29,378 pass
  • Status changed to Needs review over 1 year ago
  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia Ranjit1032002

    Created MR!3935 for the issue mentioned, please review.
    Thank You.

  • Status changed to Needs work over 1 year ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States smustgrave

    Language seems like someone is speaking directly to me vs announcing a description.

  • ๐Ÿ‡ณ๐Ÿ‡ฟNew Zealand quietone

    @Ranjit1032002, thank you for making an MR. However, next time make sure you are changing the correct string. The string changed in the MR is for unsupported releases not revoked as is stated in the issue summary.

    In my opinion, the existing testDisabling everything included in this release or upgrading is strongly recommended!' handles the case where there is no update because it says to 'disable everything'. The suggested 'upgrading' is an option only. I will ask in #bugsmash and #ux.

    This is about the UI, so tagging.

    @smustgrave, what documentation needs to be changed in this issue?

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States smustgrave

    Think I used the wrong tag.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States benjifisher Boston area

    We discussed this issue briefly at ๐Ÿ“Œ Drupal Usability Meeting 2023-08-04 Needs work . That issue will have a link to a recording of the meeting.

    For the record, the attendees at today's usability meeting were @AaronMcHale, @Emma Horrell, @benjifisher, @rkoller, @simohell, and @worldlinemine.

    We decided that we did not have enough context to make an informed recommendation. How does a release get "revoked"? Does that mean unpublished, or is it specifically when the maintainer marks it as unsupported?

    With that caveat, we tend to agree with #9.

    Besides the question raised in this issue, the current message has some other problems. It refers to "disabling" a module, which is only possible in Drupal 7 and earlier.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States benjifisher Boston area
Production build 0.71.5 2024