Contrib.social

[PP-1] The install queue should be tolerant of page refreshes

Open on Drupal.org →
Created on 4 October 2024, 3 months ago

Problem/Motivation

✨ GUI install multiple modules at once. Needs work is adding the ability to choose multiple projects at once and install them in a single batch. The only problem is that it's not refresh-tolerant. If you refresh the page, you don't know an install is in progress, until you try to select more things and install them. When you do that, you get an error that the stage is already locked. Not exactly the greatest user experience!

To be clear, this is not something that was introduced by ✨ GUI install multiple modules at once. Needs work ; it's the existing behavior in HEAD, a holdover from when projects had to be installed one at a time. But it's not really what we want.

Proposed resolution

If you kick off an install queue and you refresh the page, the UI should be able to figure out where you left off. This probably means that the current state of the install queue needs to be sent to the page in drupalSettings, then loaded into Svelte's memory space and dynamically updated as the install process proceeds, triggering re-renders (ideally only project-by-project) as necessary.

✨ Feature request
Status

Postponed

Version

2.0

Component

User experience

Created by

🇺🇸United States phenaproxima Massachusetts

Live updates comments and jobs are added and updated live.
  • Starshot blocker

    A potential blocker for Drupal Starshot. More information: http://www.drupal.org/project/starshot

Sign in to follow issues

Comments & Activities

  • Issue created by @phenaproxima
  • Comment 3 months ago →
    🇺🇸United States phenaproxima Massachusetts

    Ready to go!

  • Comment 3 months ago →
    🇺🇸United States phenaproxima Massachusetts

    This probably means that the current state of the install queue needs to be sent to the page in drupalSettings

    I think this means we should move the state of the installations (basically, whatever's in \Drupal\project_browser\Controller\InstallerController::setRequiringState()) into its own service, then inject that service into the ProjectBrowser element so it can add everything to the drupalSettings object.

  • Comment about 1 month ago →
    🇺🇸United States chrisfromredfin Portland, Maine
  • Comment 26 days ago →
    🇦🇺Australia pameeela
  • Comment 20 days ago →
    🇺🇸United States phenaproxima Massachusetts

    This isn't a stable blocker for Drupal CMS. It might be a stable blocker for Project Browser, but given the way Drupal CMS intends to expose Project Browser (based on the designs I've seen most recently), it's not a blocker for us.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024