Improve UX for Bundle Download - Prevent Early Click on “Download Here” Link
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
When users generate and download a bundle in dotCMS, they receive a message popup that says, “You can download the file here” before the bundle is fully built. Simultaneously, the file also begins to auto-download once ready.
We might not need the popup to download when the file is already being auto-downloaded without user action
If the user clicks on the “Download here” link too early—before the bundle is actually ready—it can result in an “Error Building Bundle” message and a failed download.
Steps to Reproduce
Steps to Reproduce:
- Go to a bundle and initiate a download.
- Notice click the “You can download the file here” link. (In case of a customer clicking on it as soon as it appears has given errors) I couldn't reproduce it
- The file will eventually be auto-downloaded if you don't even click on the link/popup
https://github.com/user-attachments/assets/44e407e8-78b4-4e13-8af1-e8d2c74cdb7f
Acceptance Criteria
Expected Behavior:
Auto-download should be the only method used, and the popup should be suppressed to avoid confusion.
Sometimes, customers report that clicking on the download link early throws errors.
dotCMS Version
24.04.24 LTS
Proposed Objective
Core Features
Proposed Priority
Priority 4 - Trivial
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
https://dotcms.freshdesk.com/a/tickets/30092
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named in the issue, so start by tracing the bundle download flow and the UI that displays the “Download here” popup. Done means the bundle auto-downloads when ready, the popup is suppressed, and an early click can no longer trigger a failed download.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100