Improve user experience of the Updater by changing order of operations (WIP/RFC)
Open
Nobody has claimed this yet.
enhancement
overview
Performance 🚀
UX🙂
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
- Some steps are more likely to take longer than others
- Some steps make others unnecessary if they fail (e.g. if the update can't be downloaded or extracted)
e.g.
- checkForExpectedFilesAndFolders()
- checkWritePermissions()
- downloadUpdate()
- verifyIntegrity()
- extractDownload()
- createBackup() <---- moves here from step 3
- setMaintenanceMode()
- replaceEntryPoints()
- deleteOldFiles()
- moveNewVersionInPlace()
- setMaintenanceMode
- finalize
The current order is as follows:
Other considerations:
- maintenance mode / end-users hitting the server
- entrypoint replacement timing
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
Start at index.php lines 1335-1372 and compare the current operation order with the proposed sequence in the issue. Trace how backup creation, maintenance mode, entrypoint replacement, and the other listed steps interact; done means agreeing on and implementing an order that addresses the stated failure, end-user, and timing considerations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100