Problem/Motivation
If Ludwig is used to manage the library dependency of some early-bootstrap contributed module, the refreshing the "Reports > Packages" page during the module upgrade can produce the "The website encountered an unexpected error. Please try again later." fatal error message due to missing packages not yet being downloaded.
Steps to reproduce
- Install Ludwig module ver. 8.x-1.10 or 2.0.1 (or older).
- Download the Mobile Detect module (-dev version at the moment).
- Visit the "Reports > Packages" page and download mobile_detect module missing packages.
- Install the Mobile Detect module.
- Visit module root folder and imitate the module upgrade by manually deleting the "lib" folder created by Ludwig.
- Try to refresh the "Reports > Packages" page. The "The website encountered an unexpected error. Please try again later." fatal error is displayed.
Proposed resolution
For the majority of the Ludwig users the "Download and unpack all missing packages" action can be the default action embedded into the Reports > Packages page visit. This would fix the issue with the Reports > Packages page refresh during the upgrade steps of the early-bootstrap modules described above.
Remaining tasks
1. Perform the "Download missing packages" action prior to the Packages page load (/admin/reports/packages).
2. For those who need more control over the missing packages (review and download) - add new "Packages list (skip download)" local action link (tab) at the Packages page.
3. Make the "Download missing packages" button always clickable - even if there are zero packages missing.
User interface changes
1. Rename "Download and unpack all missing packages" button to more simple "Download missing packages".
2. Add new "Packages list (skip download)" local action link (/admin/reports/packages_skip).
Post commit changes
Adjust the online documentation accordingly.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | 3256573-06.patch | 5.24 KB | devad |
Comments
Comment #2
devad commentedComment #3
devad commentedComment #4
devad commentedComment #5
devad commentedComment #6
devad commentedComment #9
devad commentedCommitted to both branches.
Comment #10
devad commentedComment #11
devad commented