Problem/Motivation

The 'Scan selected' button is not clickable when items under SCAN table are selected, similarly the 2 'Export' buttons are not clickable.

Steps to reproduce

Install module using composer on Drupal 8.9.18 and open Upgrade Status report. Select item under SCAN table and try to click on 'Scan selected' button.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#2 Screenshot 2021-09-01 at 5.31.23 PM.png26.42 KBkunalkursija
screencapture-catablogger-admin-reports-upgrade-status-2021-09-01-13_53_21.png198.3 KBcatablogger

Comments

catablogger created an issue. See original summary.

kunalkursija’s picture

kunalkursija commented
StatusFileSize
new Screenshot 2021-09-01 at 5.31.23 PM.png26.42 KB

Same for me as well - On installing this module today on Drupal-8.9.17 the Scan/Export buttons were in the disabled state.

kunalkursija’s picture

kunalkursija commented

so I looked into this & found the problem. The buttons were disabled due to Drupal environment-related issues.

In my case, /tmp directory was not writeable and upgrade_status module's DeprecationAnalyzer class was not able to create deprecation_testing.neon file. Hence the module was keeping the buttons disabled. If you want to identify your environment-related issues, You will have to look for error logs.

This issue is actually a feature for scenarios where the Drupal environment is configured correctly.

catablogger’s picture

catablogger commented

Not seeing any errors pertaining to this under /admin/reports/dblog so am at a bit of a loss as to how to proceed.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

@catablogger: The error is printed right at the top of the page. Once that error is resolved, the rest should go away. Are you using composer in this Drupal site setup?

catablogger’s picture

catablogger commented

Yes, just started using Composer. So the error that needs to be fixed is this?
The composer.json file was not found at /composer.json.
I have a composer.json file for my site that as far as I can tell is working as it ought to. Is the above error asking for a second composer.json file to be created specifically for the Upgrade Status module? Any idea how to resolve? Thanks.

charly71’s picture

charly71 commented

Same error for me but with error message in top of the page: "The PHP binary was not found. Scanning is not possible until this is resolved."
https://www.drupal.org/project/upgrade_status/issues/3241362
I'm using composer 1.x and a legacy structure (vendor folder INSIDE web root).

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

@kunalkursija: the error is not only shown in the error log but also the top of the page as shown by others. I'm glad you resolved your problem.

@catablogger: is the application name in your composer.json drupal/drupal? See #3229725: Warn if site's composer.json is named "drupal/drupal" but is a Composer build. If so, we can close this one.

@charly71: thanks for opening that issue, let's follow up there.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Closed (duplicate)

Just committed #3229725: Warn if site's composer.json is named "drupal/drupal" but is a Composer build yesterday, which added explicit error message display right above the buttons. So when they are disabled, the error shows right there (as well as in the regular Drupal messages view).

Marking this as duplicate.