So this has happened to me on several of the sites I've worked on - try to enable a bunch of module, operation times out, sometimes leaving half-installed modules (which can sometimes corrupt the settings, and at the very least screw up the caches).
What would be nice is if module enabling worked like updating, that is via the batch operations api. I think module enabling is the cause of 99% of memory hogging by Drupal and so making it function as a series of requests instead of a single one would allow Drupal to run on a lot of different machines.
Of course, some people might not like this way of doing things, so an on and off switch might be nice. I'd propose this as a module, but I'm not sure you can make these sort of changes without hacking the core.
Closed: duplicate
11.0 🔥
Worse Than Failure. Approximates the unpleasant remark made by Drupal developers when they first encounter a particular (mis)feature.
After being applied to the 8.x branch, it should be considered for backport to the 7.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Is this still a problem in D10 or even D7? If not, then we should close it or reassign to D7.
I think this is a duplicate of an issue that was opened the day before this one. #1291592: D8UX: Batch API for the Modules page → .
I am closing this as a duplicate and adding credit over there