Merge conflict Gerrit cannot merge this change. It needs a rebase onto main.
91342[FEATURE] Add the status report in the system toolbar
Commit message
Test this change
Run a command in your clone of the TYPO3 Core. Then try what the change does and vote on Verified in Gerrit. How to review a patch
- Check out patch set 6
-
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/42/91342/6 && git checkout FETCH_HEAD - Cherry-pick onto main
-
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/42/91342/6 && git cherry-pick FETCH_HEAD
Review
-
Code review CR -1 Needs a vote
- Oliver Hader -1
-
Verified V 0 Needs a vote
- core-ci +1 CI
Issues 1
Files 4
- typo3/sysext/backend/Classes/Backend/ToolbarItems/SystemInformationToolbarItem.php+15 −2
- typo3/sysext/backend/Resources/Private/Templates/About/Index.fluid.html+0 −6
- typo3/sysext/backend/Resources/Private/Templates/ToolbarItems/SystemInformationDropDown.fluid.html+36 −17
- typo3/sysext/core/Documentation/Changelog/14.2/Feature-107914-DisplayStatusReportsInSystemToolbar.rstnew+22 −0
Review log 1319
-
Michael Binder uploaded patch set 1 10/29/25, 17:23
-
Georg Ringer voted on patch set 1 CR +1 V +1 10/29/25, 17:36
-
Georg Ringer commented on patch set 1 10/29/25, 17:36
I just wonder if we got some performance issues - just thinking about ext:solr with timeout issues?! -
Michael Binder uploaded patch set 2
CR +1V +110/29/25, 17:53 -
Michael Binder uploaded patch set 3 10/29/25, 18:02
-
core-ci voted on patch set 1 V -1 10/29/25, 18:06 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/88014
-
core-ci voted on patch set 2 V -1 10/29/25, 18:18 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/88022
-
core-ci voted on patch set 3 V -1 10/29/25, 18:24 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/88024
-
Michael Binder uploaded patch set 4
V -110/29/25, 18:36 -
core-ci voted on patch set 4 V +1 10/29/25, 18:47 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/88032
-
Benni Mack commented on patch set 4 10/29/25, 19:39
Reply Unresolved
the good thing to do it via AJAX is that we don't have that problem anymore - with "About modules" as the first login, you might get into timeout issues right away. So we can finally optimize this to load the toolbar item lateron? -
Michael Binder rebased onto patch set 5
V +110/30/25, 16:01 -
Georg Ringer commented on patch set 5 10/30/25, 16:10
AboutController.php:54IMO no need to remove that event. that is not internal and might be used. but we need to remove the eventlistener at WarningsForAboutModule -
core-ci voted on patch set 5 V +1 10/30/25, 16:13 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/88163
-
Simon Schaufelberger uploaded patch set 6
V +101/22/26, 22:49 -
core-ci voted on patch set 6 V +1 01/22/26, 22:56 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/94107
-
Stefan Bürk commented on patch set 6 01/23/26, 00:02
Unresolved
Not looked into 92257: [WIP] Toolbar | https://review.typo3.org/c/Packages/TYPO3.CMS/+/92257 if it only collides or if there are more planes with the toolbar and were it should end. Maybe we should coordinate with @benjamin.kott@outlook.com in case this is doing something which should be end up in another way.AboutController.php:54Reply Unresolved@georg.ringer@gmail.com I disagree here, the event can and should be removed. ---- Commit message tell us `relocated` and I'd expect that that means `moved`. Further, the `ModifyGenericBackendMessagesEvent()` is now dispatched in two places, here and in `AboutController::handleRequest()`. The assigned messages retrieved from the event is no longer displayed (removed in the correspondign fluid template) making this event here obsolete and superflous to dispatch. Do we really need it in both places to be dispatched and gathered ? I mean, the output is removed from the template so it does not make much sense to keep it in the AboutController. Do I miss something ? -
Oliver Hader marked it work in progress 02/05/26, 09:47
-
Oliver Hader commented on patch set 6 CR -1 02/05/26, 09:47
Both comments from @georg.ringer@gmail.com and @stefan@buerk.tech are an indicator for me, that this patch does not seem to be ready yet.