Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Drupal 7 features two installation profiles by default: 'Drupal' and 'Drupal (experts only)' (which will be changed if somebody can help me get this patch right). Drupal is meant for users who want a point and click installation, e.g. users that have no technical knowledge. However, if you choose this installation profile you will encounter this profile's requirements if one of those requirements isn't met. The user is being presented with all requirements, whether they are met or not.
I doubt novices need to see the requirements if they are met. I, as a more experienced user, don't even need to see them. I suggest removing them from view from the 'Drupal' profile at least and perhaps even from the 'Drupal (experts only)' profile as well.
| Comment | File | Size | Author |
|---|---|---|---|
| requirements.png | 112.45 KB | Xano |
Comments
Comment #1
dddave CreditAttribution: dddave commentedTime has fixed this...
Comment #2
David_Rothstein CreditAttribution: David_Rothstein commentedIf I'm reading this proposal correctly, it isn't fixed.
I believe the idea of the proposal is that all the green checkbox rows in the screenshot would be removed, and you would only see the two red rows (i.e., the ones indicating errors that you need to fix), and presumably yellow rows (indicating warnings) if there are any.
I don't think we should do this, though. The green rows are there to inspire confidence, frankly ("hey, everything isn't totally broken!") and also to allow the user to keep track of progress; e.g., if they have two requirement errors and fix one, then when they reload the page they should see the one that was fixed rather than having it disappear. The rationale for the current behavior is discussed further in #281446: Add 'status report' for installer requirements (the issue that added it), and I don't think we should go back to something more like we had in Drupal 6 which is the direction that the proposal here would be going in.
Comment #11
quietone CreditAttribution: quietone as a volunteer commentedDavid_Rothstein is correct that that this issue has not been fixed. And like him I agree that this is something that should not be implemented, for all the reasons stated in #2.
Closing this as won't fix. If you disagree, just restore the status to 'Active' and add a comment explaining why you think this is worth doing.
Thx.