73704[TASK] TSFE must not unset BE_USER without backup
Commit message
Review
-
Code review CR 0
-
Verified V 0
Issues 2
Files 1
Review log 58
-
Christian Kuhn uploaded patch set 1 02/24/22, 18:37
-
core-ci voted on patch set 1 V -1 02/24/22, 18:43 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/24221
-
Christian Kuhn rebased onto patch set 2 02/24/22, 19:16
-
core-ci voted on patch set 2 V -1 02/24/22, 19:20 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/24225
-
core-ci commented on patch set 2 02/24/22, 21:49 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/24225
-
Stefan Bürk rebased onto patch set 3 02/24/22, 21:52
-
Christian Kuhn commented on patch set 3 02/24/22, 21:56
i'll abandon this approach: this is more a state-issue of ext:solr. and yes, core shouldn't simply unset globals, but this change can have various unknown side-effects that may be hard to track. we *may* come up with something for main-branch again, but v11 is far too risky (security-wise, unsure). we'll reject the issue and may come up with a new approach. -
Christian Kuhn abandoned the change 02/24/22, 21:56