Posted by Rob Loach on September 26, 2011 at 10:07pm
7 followers
| Project: | Drupal core |
| Version: | 8.x-dev |
| Component: | system.module |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
| Issue tags: | Batch API, d8ux, modules page, Usability |
Issue Summary
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.
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| batchapi-modulespage.patch | 1.62 KB | Idle | FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch batchapi-modulespage.patch. This may be a -p0 (old style) patch, which is no longer supported by the testbots. | View details | Re-test |
| modulesprogress.png | 5.72 KB | Ignored: Check issue status. | None | None |
Comments
#1
Can you elaborate more?
#2
If 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.
#3
#4
The last submitted patch, modules.patch, failed testing.