Skip to content

[BUGFIX] Replace removed StandaloneView with ViewFactoryInterface for TYPO3 v14#254

Open
butu wants to merge 1 commit into
georgringer:core-v14from
butu:fix/v14-standalone-view-notification
Open

[BUGFIX] Replace removed StandaloneView with ViewFactoryInterface for TYPO3 v14#254
butu wants to merge 1 commit into
georgringer:core-v14from
butu:fix/v14-standalone-view-notification

Conversation

@butu

@butu butu commented Jun 26, 2026

Copy link
Copy Markdown

Problem

StandaloneView has been removed in TYPO3 v14 (was deprecated in v13). The monitoring extension still uses it in EmailNotification::getFluidTemplate(), which results in a fatal error

Class "TYPO3\\CMS\\Fluid\\View\\StandaloneView" not found

every time a notification email is about to be sent:

  • ClientImport::run()sendClientFailedEmail() (client connection failure)
  • reporting:adminsendAdminEmail()
  • reporting:clientsendClientEmail()

As a consequence the import run aborts and no warning email is sent at all.

Solution

Switch getFluidTemplate() to the v14 standard view API:

  • TYPO3\\CMS\\Core\\View\\ViewFactoryInterface (resolved via GeneralUtility::makeInstance(), consistent with the existing non-DI instantiation of EmailNotification)
  • TYPO3\\CMS\\Core\\View\\ViewFactoryData with templatePathAndFilename + format

Behavior is unchanged: same templates, same format (txt), same assignments.

Notes

  • Follows the v14 recommendation note in FluidViewFactory.
  • Drops the now-obsolete Upgrade v14 todo section from the README.

… TYPO3 v14

StandaloneView has been removed in TYPO3 v14, causing a fatal error
'TYPO3\CMS\Fluid\View\StandaloneView not found' whenever the monitoring
tried to send notification emails (client connection failure, admin
report, client report). Use ViewFactoryInterface with ViewFactoryData
instead, which is the v14 standard way to build fluid views.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant