Posted by marco.robotangel on December 19, 2007 at 3:14pm
4 followers
Jump to:
| Project: | Drupal core |
| Version: | 8.x-dev |
| Component: | base system |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Steps to reproduce: Try to enable a module which has unresolved depencies.
It would make the whole thing a lot easier - especially for newbies who maybe don't understand all this depency-stuff - if there was a javascript which would immedeatly offer to check all required modules - if available - after checking a module with depencies. This was suggested at [1]
Comments
#1
Thanks for your request!
It's unfortunately too late for D6 as features are frozen... otherwise this sounds to be reasonable, though we have to check whether this might be problematic in some cases.
#2
This is not a change in functionality nor a backend feature. It's merely a UI enhancement so that the user can be sure that the correct dependencies will also be enabled -- otherwise they may be uncertain and confused.
Plz tag for newbie
#3
Bumping to d8
#4
We ran into this issue when we upgraded a contrib module (references) from an old dev build to the newest. The contributed module had split its functionality into 2 separate modules. In this instance if it wasn't up to core to detect that a required module wasn't enabled, how should the module have become enabled? By an update hook in the contrib module?
I would say that drupal should make it blatantly obvious to you when you have required modules that are not enabled.