---
title: "Important: #105653 - Require a template filename in extbase module template rendering"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:important-105653-1732210472"
source: "Changelog/13.4.x/Important-105653-RequireATemplateFilenameInExtbaseModuleTemplateRendering.rst"
typo3-version: "13.4.x"
typo3-major: 13
type: "important"
issue: 105653
forge: "https://forge.typo3.org/issues/105653"
tags: ["Backend", "ext:backend"]
rendered: "2026-09-23T19:53:57+00:00"
---

# Important: #105653 - Require a template filename in extbase module template rendering {#important-105653-1732210472}

See [forge#105653](https://forge.typo3.org/issues/105653)

## Description {#description}

With the introduction of the FluidAdapter in TYPO3 v13, the dependency between
Fluid and Extbase has been decoupled. As part of this change, the behavior of
the `ModuleTemplate::renderResponse()` and `ModuleTemplate::render()`
methods has been adjusted.

The `$templateFileName` argument is now mandatory for the
`ModuleTemplate::renderResponse()` and `ModuleTemplate::render()`
methods. Previously, if this argument was not provided, the template was
automatically resolved based on the controller and action names. Starting from
TYPO3 13.4, calling these methods with an empty string or without a valid
`$templateFileName` will result in an `InvalidArgumentException`.

Extensions using Extbase backend modules must explicitly provide the
`$templateFileName` when calling these methods. Existing implementations
relying on automatic template resolution need to be updated to prevent
runtime errors.

**Example**:

Before:

```php
$moduleTemplate->renderResponse();
```

After:

```php
$moduleTemplate->renderResponse('MyController/MyAction');
```

Note, that it is already possible to explicitly provide the
`$templateFileName` in TYPO3 12.4. It is therefore recommended to
implement the new requirement for websites using TYPO3 12.4.