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.
Warning

Remaining tasks

Nil

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#3 warning-message.png216.48 KBarunkumark
Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

arunkumark created an issue. See original summary.

sourav_paul’s picture

Assigned: Unassigned » sourav_paul
arunkumark’s picture

Issue summary: View changes
StatusFileSize
new216.48 KB

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.

arunkumark’s picture

Status: Active » Needs review

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

sourav_paul’s picture

Assigned: sourav_paul » Unassigned
phenaproxima’s picture

Issue tags: -exception, -pagebreak

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.

phenaproxima’s picture

Component: Code » Automatic Updates Extensions
sourav_paul’s picture

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

sourav_paul’s picture

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