---
title: "Use own HTML Templates"
manual: "Femanager"
version: "13.4"
permalink: "https://docs.typo3.org/permalink/in2code/femanager:changetemplates@13.4"
source: "Features/Templates/Index.rst"
rendered: "2026-11-12T07:32:45+00:00"
---

# Use own HTML Templates {#changetemplates}

## Basics {#basics}

If you want to modify a HTML-File of femanager, you should not overwrite them directly in the extension folder.
Think about upcoming versions with important bugfixes or security-patches.

There are two ways to use own HTML-Templates (and Partials / Layouts) instead of the original Templates.

## Replace all HTML Templates from Femanager with own Templates {#replace-all-html-templates-from-femanager-with-own-templates}

You can copy all Files from
\- EXT:femanager/Resources/Private/Templates/
\- EXT:femanager/Resources/Private/Partials/
\- EXT:femanager/Resources/Private/Layouts/

to a new folder in fileadmin - e.g. fileadmin/templates/femanager/ and modify them as you want.
After that, you should say femanager to use the new Templates with some lines of TypoScript setup:

```typoscript
plugin.tx_femanager {
	view {
		templateRootPath = fileadmin/templates/femanager/Templates/
		partialRootPath = fileadmin/templates/femanager/Partials/
		layoutRootPath = fileadmin/templates/femanager/Layouts/
	}
}
```

## Replace single HTML Template-Files {#replace-single-html-template-files}

You can copy only the Files that you want to modify from
\- EXT:femanager/Resources/Private/Templates/
\- EXT:femanager/Resources/Private/Partials/
\- EXT:femanager/Resources/Private/Layouts/

to a new folder in fileadmin - e.g. fileadmin/templates/femanager/ and modify them as you want.
After that, you should say femanager to use the old folders and merge them with the new folders

```typoscript
plugin.tx_femanager {
	view {
		templateRootPath >
		templateRootPaths {
			10 = EXT:femanager/Resources/Private/Templates/
			20 = fileadmin/templates/femanager/Templates/
		}
		partialRootPath >
		partialRootPaths {
			10 = EXT:femanager/Resources/Private/Partials/
			20 = fileadmin/templates/femanager/Partials/
		}
		layoutRootPath >
		layoutRootPaths {
			10 = EXT:femanager/Resources/Private/Layouts/
			20 = fileadmin/templates/femanager/Layouts/
		}
	}
}
```

## Email templates with useFluidMail {#email-templates-with-usefluidmail}

If `useFluidMail` is enabled in the extension configuration, femanager sends all emails via the TYPO3 `FluidEmail`
API. The templates are then taken from the folder `Mail/` instead of `Email/`:

-   EXT:femanager/Resources/Private/Templates/Mail/ (`.html` and `.txt` for the plain text part)
-   EXT:femanager/Resources/Private/Partials/Mail/
-   EXT:femanager/Resources/Private/Layouts/Mail/

You can override them in two ways:

1.  Via TypoScript (recommended). These paths are added after the paths of
    `$GLOBALS['TYPO3_CONF_VARS']['MAIL']` and always take precedence over them. Use the constants
    `plugin.tx_femanager.settings.email.templateRootPath` (`partialRootPath`, `layoutRootPath`) or the setup.
    The configuration follows the email template configuration of the TYPO3 core extension felogin
    (`plugin.tx_felogin_login.settings.email`). In contrast to felogin, the TypoScript paths always
    take precedence over the paths in `$GLOBALS['TYPO3_CONF_VARS']['MAIL']`, regardless of their key:

```typoscript
plugin.tx_femanager.settings.email {
	templateRootPaths {
		20 = EXT:sitepackage/Resources/Private/Extensions/Femanager/Templates/Mail/
	}
	partialRootPaths {
		20 = EXT:sitepackage/Resources/Private/Extensions/Femanager/Partials/Mail/
	}
	layoutRootPaths {
		20 = EXT:sitepackage/Resources/Private/Extensions/Femanager/Layouts/Mail/
	}
}
```

1.  Via the global mail configuration in the `ext_localconf.php` of your sitepackage. Use a key higher than
    `1408` (the key femanager uses), so that your paths take precedence:

```php
$GLOBALS['TYPO3_CONF_VARS']['MAIL']['templateRootPaths'][1500] = 'EXT:sitepackage/Resources/Private/Extensions/Femanager/Templates/Mail/';
$GLOBALS['TYPO3_CONF_VARS']['MAIL']['partialRootPaths'][1500] = 'EXT:sitepackage/Resources/Private/Extensions/Femanager/Partials/Mail/';
$GLOBALS['TYPO3_CONF_VARS']['MAIL']['layoutRootPaths'][1500] = 'EXT:sitepackage/Resources/Private/Extensions/Femanager/Layouts/Mail/';
```

The paths in `plugin.tx_femanager.view` are not used for emails if `useFluidMail` is enabled.

The femanager mail templates use the layout `Default` (EXT:femanager/Resources/Private/Layouts/Mail/Default.html),
which only renders the section `main` without any additional markup. If you want to use the TYPO3 system mail
design, override the template and use the layout `SystemEmail` of the TYPO3 core with the sections `Title`
(optional) and `Main`:

```html
<f:layout name="SystemEmail" />

<f:section name="Title">Please confirm your registration</f:section>

<f:section name="Main">
	...
</f:section>
```