Review main Abandoned Breaking

65998[WIP][!!!][TASK] Require an extension name for <f:translate>

Benni Mack CR 0 V 0 Hard +434 −483 updated 11/30/20, 10:28

Commit message

The "magic" for using <f:translate key="hello" /> to automatically
resolve the extension name for the value is removed, as it is bound
to controller logic from Extbase. This is needed to decouple
the actual view-logic (Fluid) from Extbase and Extbase from EXT:core
and build a more flexible View functionality for the future.

This means:
if you are using <f:translate id="mykey"> you always need to provide
an extension name as well (<f:translate id="mykey" extensionName="myext" />)
to avoid ambiguity. If you are using extensionName already in your templates,
you're safe.

if you are using <f:translate id="LLL:EXT:myext/Resources/Private/Language/myfile.xlf:mykey"/>
already, you are safe as well.

Templates to do:
* beuser
* extensionmanager

Review

  • Code review CR 0

    Imported before Forger kept the single votes, the next import adds them.

  • Verified V 0

    Imported before Forger kept the single votes, the next import adds them.

Files 97

Show 77 more files