Installed unsupported modules breaks Update extensions page

Created on 13 August 2024, 12 months ago
Updated 3 September 2024, 11 months ago

Problem/Motivation

If the website has been installed with a module and it becomes unsupported we are getting page break errors.

The website encountered an unexpected error. Try again later.

RuntimeException: The project 'pdf_serialization' can not be updated because its status is unsupported in Drupal\package_manager\ProjectInfo->getInstallableReleases() (line 103 of modules/contrib/automatic_updates/package_manager/src/ProjectInfo.php).
Drupal\automatic_updates_extensions\Form\UpdaterForm->getRecommendedModuleUpdates() (Line: 97)
Drupal\automatic_updates_extensions\Form\UpdaterForm->buildForm(Array, Object)
call_user_func_array(Array, Array) (Line: 536)

Steps to reproduce

1. Installed any modules that are supported earlier
2. Example pdf_serialization install using the command composer require drupal/pdf_serialization and install.
3. Install and enable the Automatic Updates
4. Visit the /admin/modules/automatic-update-extensions
5. Getting the page break error.

Proposed resolution

Instead of error we can able to show the message on the Update page.

Remaining tasks

Nil

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Needs review

Version

3.1

Component

Automatic Updates Extensions

Created by

🇮🇳India arunkumark Coimbatore

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @arunkumark
  • Assigned to sourav_paul
  • 🇮🇳India arunkumark Coimbatore

    Updated the issue summary.
    Exception already handled. But instead of breaking the page, we can show the message to the site builder about the issue.

  • Status changed to Needs review 12 months ago
  • 🇮🇳India arunkumark Coimbatore

    Created MR for the recommendation. @Sourav_Paul thanks for looking this fix.

  • Pipeline finished with Failed
    12 months ago
    Total: 1387s
    #252434
  • Issue was unassigned.
  • Pipeline finished with Failed
    12 months ago
    Total: 1216s
    #252486
  • Pipeline finished with Failed
    12 months ago
    Total: 1342s
    #252556
  • Pipeline finished with Success
    12 months ago
    Total: 1468s
    #252659
  • 🇺🇸United States phenaproxima Massachusetts

    While I think this is legitimate bug, I'm not entirely sure this is the correct fix. We probably want to keep throwing the exception, but without breaking the page -- most likely that just means using a try-catch in a strategic spot, rather than removing the exception itself.

    Leaving this open because I'd like @tedbow's input here.

  • 🇺🇸United States phenaproxima Massachusetts
  • 🇮🇳India sourav_paul Kolkata

    @tedbow & @phenaproxima It would be nice if you could provide your final input.
    so we can proceed.

  • 🇮🇳India sourav_paul Kolkata

    @phenaproxima If you have some bandwidth, could you please look into it?

  • Pipeline finished with Failed
    4 days ago
    #561485
  • Pipeline finished with Failed
    4 days ago
    #561487
  • Pipeline finished with Failed
    4 days ago
    #561497
  • Pipeline finished with Failed
    4 days ago
    #561520
  • Pipeline finished with Failed
    3 days ago
    #561557
  • Pipeline finished with Failed
    3 days ago
    #561567
  • Pipeline finished with Canceled
    3 days ago
    #561570
  • Pipeline finished with Success
    3 days ago
    #561576
  • Pipeline finished with Skipped
    3 days ago
    #561603
Production build 0.71.5 2024