68134[BUGFIX] Handle multiselect fields properly
Commit message
Review
-
Code review CR 0
-
Verified V -1
- core-ci -1 CI
Issues 1
Files 3
Review log 4971
Show 3146 earlier messages
-
Philipp Kitzberger uploaded patch set 1 02/26/21, 20:39
-
TYPO3com voted on patch set 1 V -1 02/26/21, 20:39 Completed build in 13s on Fri, 26 Feb, 08:39 PM Test Summary: No tests found Find logs and detail information at https://bamboo.typo3.com/browse/CORE-GTC-9740
-
Georg Ringer commented on patch set 1 03/01/21, 10:30
IMO multiple support requires far more work, I just spent some hours to make that work in v10 and will release that as custom extension. contact me on slack if interested -
Benni Mack commented on patch set 1 11/04/21, 11:23
Any way on how to continue here @philipp or @georg? Do you have an extension ready yet? -
Philipp Kitzberger commented on patch set 1 11/04/21, 12:04
@Benni, Georg and I had a little chat on slack that very day and figured out that Georg was talking about something unrelated to this topic here. -
Benni Mack commented on patch set 1 11/04/21, 12:05
Reply
Ah, OK. So we need to make sure to get the tests "green", correct? -
Benni Mack rebased onto patch set 2 11/04/21, 12:05
-
core-ci voted on patch set 2 V -1 11/04/21, 12:08 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/18873
-
Benni Mack commented on patch set 3 11/09/21, 12:43
Published edit on patch set 2. -
core-ci voted on patch set 3 V -1 11/09/21, 12:56 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/19067
-
Benni Mack updated the commit message in patch set 4 11/18/21, 10:45
-
core-ci voted on patch set 4 V -1 11/18/21, 11:58 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/19465
-
Benni Mack wrote 11/28/21, 22:06
Removed cc Benni Mack. -
Benni Mack wrote 11/29/21, 10:21
Change destination moved from master to main -
Benni Mack updated the commit message in patch set 5 11/29/21, 14:11
-
core-ci voted on patch set 5 V -1 11/29/21, 18:36 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/20117
-
till-s till-s commented on patch set 5 V +1 12/16/21, 13:23
The field values area returned correctly now. -
Benni Mack rebased onto patch set 6 12/16/21, 13:29
-
core-ci voted on patch set 6 V -1 12/16/21, 13:45 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/21181
-
Benni Mack commented on patch set 6 12/20/21, 09:56
Hey Philipp, quick check here. Wouldn't it make sense to give the Element a "valueToString" method? -
Philipp Kitzberger uploaded patch set 7 12/22/21, 15:05
-
core-ci voted on patch set 7 V -1 12/22/21, 15:19 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/21401
-
Björn Jacob updated the commit message in patch set 8 06/29/22, 08:02
-
core-ci voted on patch set 8 V -1 06/29/22, 08:03 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/28469
-
till-s till-s commented on patch set 8 09/28/22, 06:56
Hi, is this bug still being tracked? The issue still persists and it seems that the PR just needs to be merged. -
Philipp Kitzberger rebased onto patch set 9 10/13/22, 13:24
-
Philipp Kitzberger commented on patch set 9 10/13/22, 13:26
Reply
i guess ;-) what do you think of patchset 8? -
core-ci voted on patch set 9 V -1 10/13/22, 13:35 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/32290
-
Stefan Bürk commented on patch set 9 10/13/22, 15:17
Reply
You should have a look into the "red" pipeline. Tests are failing, bevause of type errors. Either not properly setup in tests or real issues. And phpstan is complaining also. Simply repushing will not get them green. -
Philipp Kitzberger uploaded patch set 10 10/13/22, 15:18
-
Philipp Kitzberger commented on patch set 10 10/13/22, 15:22
Reply
The previous test run failed due to some other error (network?). Only the re-run showed me the cause of the problem. Didn't know how to trigger a re-run without pushing... Sorry. Patch set 10 should be fine though. -
core-ci voted on patch set 10 V -1 10/13/22, 15:26 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/32298
-
Stefan Bürk commented on patch set 10 10/13/22, 15:34
Reply
Running them locally (docker + docker-compose cli script required ). For still failing unit tests: ``` Build/Scripts/runTests.sh -s unit -p 8.1 ``` Pipeline displays which commands are executed, so can be reproduced locally. And with adding "-x" to the mix xdebugged if breakpoints are set etc. ``` Build/Scripts/runTests.sh -h ``` display a generic list of tasks and options. Yeah ... the "OCI runtime " failers has been a issue with gitlab runners while back. Not saw them, just peeked into the last failed pipeline and not into all of them. But still, unit tests are still failing. -
Benni Mack updated the commit message in patch set 11
V -105/03/23, 09:24 -
core-ci voted on patch set 11 V -1 05/03/23, 11:10 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41407
-
Oliver Hader rebased onto patch set 12
V -105/03/23, 12:39 -
core-ci voted on patch set 12 V -1 05/03/23, 13:09 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41529
-
Parikshit Pingle updated the commit message in patch set 13
V -105/04/23, 09:14 -
core-ci voted on patch set 13 V -1 05/04/23, 09:22 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41569
-
Jasmina Ließmann updated the commit message in patch set 14
V -105/04/23, 12:06 -
core-ci voted on patch set 14 V -1 05/04/23, 12:14 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41571
-
till-s till-s commented on patch set 14 04/18/24, 14:33
Reply
@benni@typo3.org is there any chance this patch can be merged? -
Philipp Kitzberger uploaded patch set 15
V -104/18/24, 15:21 -
core-ci voted on patch set 15 V -1 04/18/24, 15:26 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/56267
-
Benni Mack commented on patch set 15 04/18/24, 21:35
Reply
once the CI pipeline is green, yes. -
Philipp Kitzberger rebased onto patch set 16
V -110/20/24, 15:22
-
core-ci voted on patch set 16 V -1 10/20/24, 15:28 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/68262
-
Philipp Kitzberger uploaded patch set 17
V -110/21/24, 09:38 -
core-ci voted on patch set 17 V -1 10/21/24, 09:44 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/68291
-
Philipp Kitzberger uploaded patch set 18
V -110/21/24, 10:24 -
core-ci voted on patch set 18 V +1 10/21/24, 10:30 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/68293
-
Philipp Kitzberger commented on patch set 18 10/21/24, 10:32
Reply
I've just rebased this patch. AbstractFinisherTest was failing, so I adjusted those. One is obsolete now and got removed: substituteRuntimeReferencesThrowsExceptionOnMultipleVariablesResolvedAsArray -
Philipp Kitzberger rebased onto patch set 19
V +103/26/25, 14:02 -
Benni Mack updated the commit message in patch set 20 03/26/25, 14:03
-
core-ci voted on patch set 19 V +1 03/26/25, 14:11 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/76386
-
core-ci voted on patch set 20 V +1 03/26/25, 14:12 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/76387
-
Benni Mack voted on patch set 20 CR +1 V +1 03/26/25, 14:48
-
Benni Mack commented on patch set 20 CR 0 V 0 03/26/25, 16:15
how about we add then StringableFormElementInterface to the Select instead? -
Stefan Oswald commented on patch set 20 CR +1 V +1 05/06/25, 06:54
The bugfix message should also explain that not only "mustiselect" fields are fixed with this, but also "multicheckbox" fields. -
Ayke Halder commented on patch set 20 CR -1 12/17/25, 19:33
AbstractFinisherTest.php:160AFAIK this is the test input, isn't it? By changing the input from `array` to `string`, the test of course does not fail anymore - as it tests with `string` input now. The intention of this test actually was to show if the code works with an input of type `array`. So if we keep the test input type as `array` here, the test still fails: ``` Cannot convert object value of "element-identifier-1" to string ``` -
Ayke Halder uploaded patch set 21
CR +1V +112/17/25, 20:09 -
core-ci voted on patch set 21 V +1 12/17/25, 20:18 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/92372
-
Ayke Halder commented on patch set 21 CR +1 12/17/25, 20:29
AbstractFinisherTest.php:160ReplyThe test is refactored. -
Christian Rath-Ulrich voted on patch set 21 CR +1 V +1 01/15/26, 11:29
-
Josua Vogel commented on patch set 21 01/19/26, 08:40
Unresolved
Some time ago, I provided a similar bug fix that fixes additional issues and, in my opinion, structures everything a little better (not everything in GenericFormElement): https://review.typo3.org/c/Packages/TYPO3.CMS/+/90056GenericFormElement.php:37UnresolvedAs far as I can see, there is no indication anywhere that there is a “glue” property. In my opinion, this should be defined in MultiSelect.yaml, e.g. as a predefined default. -
Benni Mack wrote 04/21/26, 14:54
Removed reviewer Benni Mack. -
Benni Mack updated the commit message in patch set 22
CR +1V +104/22/26, 06:48 -
core-ci voted on patch set 22 V -1 04/22/26, 11:28 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/100805
-
Benni Mack abandoned the change 11/10/26, 13:32