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.
To help make the modules page less intrusive, we should stick the Batch API on there so that the form submit doesn't seemingly take forever to load.
Comment | File | Size | Author |
---|---|---|---|
#3 | modules.patch | 3.16 KB | RobLoach |
Screenshot of Batch API Modules page.png | 5.72 KB | RobLoach | |
batchapi-modulespage.patch | 1.62 KB | RobLoach | |
Comments
Comment #1
Bojhan CreditAttribution: Bojhan commentedCan you elaborate more?
Comment #2
RobLoachIf you have a large number of contributed modules on your site, and you're enabling/disabling some, it can sometimes take up to 15 seconds for the form submission to process. This greatly impedes the user, and generally makes them scared of enabling or disabling modules. It also makes them worried that their site broke during the operation while they are waiting for the page to load. You can easily see this effect if you're enabling/disabling a large number of modules, or installing a new module that has a large install process (like Views or Panels).
By adding the Batch API to the modules page submission, we give the user direct feedback on how their process is taking place. It also lets them know that their site isn't breaking when it is enabling/disabling the modules. The provided patch at #0 just sticks the basics into the Batch API. It would be great to give the user feedback on a module by module basis as to whether it was enabled/disabled successfully.
Comment #3
RobLoachComment #5
lpalgarvio CreditAttribution: lpalgarvio commentedi like this!!
Comment #6
Grayside CreditAttribution: Grayside commented#2 is the first Drupal WTF I had to learn to deal with, and explain to others.
Comment #7
Bojhan CreditAttribution: Bojhan commentedCan't we just have a spinner?
Comment #8
XanoWe should use human-readable module names instead.