After database updates have been run from Drupal's admin UI, it would be swell if there was a link to the Status Report, please.
Before:
After:
thanks,
-mike
Run database updates from the Status Report page of the admin UI and when it is complete, see the lack of a link back to the Status Report page.
Add a link to the post update page if the user has permission.
None.
The addition of a "Status Report" link.
None.
None.
| Comment | File | Size | Author |
|---|
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
compare
Comments
Comment #4
cilefen commentedComment #5
nicxvan commentedThe code changes look good, since this is a front end change a screenshot is needed I think.
I added the needs issue summary tag to get the standard issue template back, it's helpful to have all sections to review as issues progress.
I did confirm that the administration pages links are tested elsewhere.
Comment #6
cilefen commentedSince @ultimike asked for this...
Comment #7
ultimike@nicxvan, @cilefen,
Wow - thanks so much for hopping on this so quickly!
Some background on this request: each year at Florida DrupalCamp, during lightning talks, I share my list of "Drupal grievances" from the previous 12 months. The lack of the "Status Report" link was one of my original grievances a few years ago. At the time, I found a different core issue (which I have been unable to find again) that mentioned this, but its scope was bigger and never went anywhere.
Fast-forward to a few days ago, and I decided that this would not only make a good item for my "grievance rewind" for this year's lightning talk, but also a good issue to tackle (and possibly mentor someone new on) for Florida Drupal Camp's contribution day. Imagine my surprise (and joy!) when I opened this issue a few minutes ago to see the MR!
Hopefully, the narrow scope of this issue will allow this MR to be merged.
Marking as RTBC.
-mike
Comment #8
nicxvan commentedI agree it's a good change, it's still needs work though because issues affecting the UI need before and after screenshots.
I added the default template back in.
If a section of the template is not applicable you can just leave it blank rather than deleting it, it makes it easier to see what is missing.
Comment #9
nicxvan commentedComment #10
ultimike@nicxvan - just to clarify, are you saying that all that is currently needed is a before-and-after screenshot (and perhaps some better information in the issue template)?
-mike
Comment #11
nicxvan commentedYep! Just a before and after screenshot.
I already added the template back into the issue summary.
Comment #12
ultimikeScreenshots added.
Comment #13
nicxvan commentedLooks great! Not sure if this needs a change record or not.
Comment #14
mstrelan commentedI have reviewed the MR and the code looks good to add the link to the page, however I suggest opening a follow up issue to convert both links to use Url::access instead of User::hasPermission. Currently if the required permission changed to "access site reports", for example, the test would still pass even though the link would not work. Since we're already using this pattern I suggest we keep it for now and get this one in. Looks good to me.
Comment #17
quietone commentedNice little improvement!
Thanks to @larowlan for manual testing. And to all the help at DrupalSouth 2025.
Committed 6d097f1 and pushed to 11.x. Thanks!