TYPO3 Core

all three issue were planned as such. they're not bugs.

if changed again, they need proper decision, impact and analysis before. just stating different than before is not good enough.

Please consider that planning might have been insufficient and mistakes can happen.

"different than before" in this case means breaking basic stuff that has been working for years and is relied on by others outside the Core.

Christian Kuhn wrote in #note-3:

all three issue were planned as such. they're not bugs.

If so, where is the deprecation notice, that tells people this would be breaking change(s) in TYPO3 12?

Didn't find one in the official Fluid docs, where just the documentation of f:form changed in v12 but nothing pointed to those changes in v11.

If changed, they need proper decision, impact, analysis and deprecation before. Just stating planned as such is not good enough. #SCNR

It would have been easy to just remove the Extbase dependency from the ViewHelpers too with #98377, since they worked with the fake ExtbaseRequest presented by Standalone Fluid anyway - instead they are documented as requires an Extbase-Request now.

What is the recommended way to link to an Extbase Action from non-Extbase context now? We need to offer a migration path

Just hitting this bug after working on migrating EXT:cf_google_authenticator to TYPO3 v11 and now starting pushing up to TYPO3 v12.

This extension uses a StandaloneView whose template depends on a VH I just created for TYPO3 v11 and bangs! this crashes in TYPO3 v12.

So, how to migrate f:form and f:link.action outside of an extbase context?

Do you have a planned solution, or perhaps a workaround or migration path?

Please see the related ticket #98377 and its changelog entry for details:

https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Breaking-98377-FluidStandaloneViewDoesNotCreateAnExtbaseRequestAnymore.html