offer to run cron or inform users of it after upgrade
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature: upgrade
robustness 💪
UX🙂
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
After an upgrade, cron has to run at least once to finish some things that might take longer. When you're upgrading quickly through major releases (say you go from 12 to 20) you risk problems if you don't run cron in between, but most admins won't know this.
We should warn, or better, offer to run cron after the upgrade is complete.
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 files, tests, or entry points are named in the issue. Trace the updater's post-upgrade flow and cron handling first, then determine where a warning or offer belongs; done means users are clearly informed or can run cron after an upgrade.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100