PHPackages passionweb/form-email-contentblocks - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. passionweb/form-email-contentblocks ActiveTypo3-cms-extension[Utility & Helpers](/categories/utility) passionweb/form-email-contentblocks =================================== Allows adding different content elements at the beginning (introductory text) and/or at the end (email signature) of the email templates. Also, the background color and logo of the fluid email template can be edited. 4.0.0(4w ago)21.7k↓47.9%3[2 issues](https://github.com/passionweb-manuel-schnabel/form-email-contentblocks/issues)GPL-2.0-or-laterHTML Since Jan 23Pushed 2mo ago1 watchersCompare [ Source](https://github.com/passionweb-manuel-schnabel/form-email-contentblocks)[ Packagist](https://packagist.org/packages/passionweb/form-email-contentblocks)[ Docs](https://www.passionweb.de)[ RSS](/packages/passionweb-form-email-contentblocks/feed)WikiDiscussions master Synced 1w ago READMEChangelog (10)Dependencies (4)Versions (29)Used By (0) TYPO3 Extension `Form email contentblocks` ========================================== [](#typo3-extension-form-email-contentblocks) Allows to add a content element at the beginning (introductory text) and/or at the end (signature) of the email templates. Also, the background color and logo of the fluid email template can be edited. Features -------- [](#features) - Add a content element at the beginning of the email to receiver template - Add a content element at the beginning of the email to sender template [![Introductory text finisher for sender/receiver](./Documentation/Introduction/example-introductory-text.png)](./Documentation/Introduction/example-introductory-text.png) - Add a content element at the end of the email to receiver template - Add a content element at the end of the email to sender template [![Signature text finisher for sender/receiver](./Documentation/Introduction/example-signature-text.png)](./Documentation/Introduction/example-signature-text.png) - Edit the background color and logo of the fluid email template for sender and receiver [![ExtendFluidEmail finisher](./Documentation/Introduction/example-extend-fluid-email.png)](./Documentation/Introduction/example-extend-fluid-email.png) Installation ------------ [](#installation) Add via composer: ``` composer require "passionweb/form-email-contentblocks" ``` - Install the extension via composer - Flush TYPO3 and PHP Cache What does this extension do? ---------------------------- [](#what-does-this-extension-do) This extension provides additional finishers for the TYPO3 system extension "Form" ([EXT:form](https://docs.typo3.org/c/typo3/cms-form/11.5/en-us/Index.html "EXT:form")). In order for this extension to work as desired, the extension must be installed and configured correctly. Since version 1.1.0 it is possible to [use form variables in the content elements](#add-form-variables-to-content-elements). Following finishers are available: - `IntroductoryReceiverFinisher` (Adds a content element at the beginning of the email to receiver template) - `IntroductorySenderFinisher` (Adds a content element at the beginning of the email to sender template) - `SignatureReceiverFinisher` (Adds a content element at the end of the email to receiver template) - `SignatureSenderFinisher` (Adds a content element at the end of the email to sender template) - `ExtendFluidEmailFinisher` (Edit the background color and logo of the fluid email template for sender and receiver. The logo accepts an extension path (`EXT:...`), a public URL, a FAL reference (`t3://file?uid=…`, `file:…` or `storage:uid`) or a document-root-relative path. Background color, logo and copyright can also be pre-set site-wide via the site set, see [Configuration](#configuration).) All previous finishers must be placed in front of the associated email finishers (`EmailToSender` or `EmailToReceiver`). Otherwise the corresponding content blocks are ignored. The same applies to the ExtendFluidEmailFinisher variables. For each finisher, the corresponding notes are also displayed in the header of the respective finisher. Configuration ------------- [](#configuration) ### Form configuration (automatic) [](#form-configuration-automatic) As of TYPO3 v14, the form YAML configuration is registered automatically through the form framework's auto-discovery (`Configuration/Form/FormEmailContentblocks/config.yaml`), for both the frontend and the backend form editor. **No TypoScript setup is required.** > The previous TypoScript registration via `plugin.tx_form`/`module.tx_form.settings.yamlConfigurations` was deprecated in TYPO3 v14.2 ([\#109412](https://docs.typo3.org/permalink/changelog:deprecation-109412-1732785703)) and removed here in favour of auto-discovery. ### Site-wide defaults (site set) [](#site-wide-defaults-site-set) The extension ships a site set **`passionweb/form-email-contentblocks`** that exposes site-wide fallback defaults for the `ExtendFluidEmailFinisher`: SettingTypeDescription`formEmailContentblocks.bgColor`stringFallback background color (hex, e.g. `#ffffff`)`formEmailContentblocks.logo`stringFallback logo (`EXT:` path, URL, FAL reference or root-relative path)`formEmailContentblocks.showCopyright`boolDefault for the copyright noteInclude the set in your site: **Site Management → Sites → your site → Sets → add "Form email content blocks"** (or add `passionweb/form-email-contentblocks` to the site's `dependencies` in `config/sites//config.yaml`). Per-form finisher options always take precedence; the site settings only apply when a form leaves the respective option empty. The site set is optional — the finishers work without it. How editors can/should use the extension ---------------------------------------- [](#how-editors-canshould-use-the-extension) 1. Create new or edit an existing form 2. Add the finisher(s) you want to use (and place them in the right order) [![Signature finisher for sender/receiver](./Documentation/Editor/overview-added-finishers.png)](./Documentation/Editor/overview-added-finishers.png) 3. Save the form Add form variables to content elements -------------------------------------- [](#add-form-variables-to-content-elements) Since version 1.1.0 it is possible to use form variables in the content elements or the text fields for the plaintext. You can use it in the same way as in the finisher configurations. [![Form variables in content element](./Documentation/Editor/form-variables-in-content-element.png)](./Documentation/Editor/form-variables-in-content-element.png) Troubleshooting and logging --------------------------- [](#troubleshooting-and-logging) If something does not work as expected take a look at the log file first. Every problem is logged to the TYPO3 log (normally found in `var/log/typo3_*.log`). If something still doesn't work as desired after checking the logs, feel free to contact me. Important notes --------------- [](#important-notes) This extension does not override any of the default EXT:form finisher classes, as it uses the `FinisherVariableProvider` object to share variables between finishers. But the default email templates are overwritten. If you use several extensions that overwrite the default email templates of EXT:form, conflicts can arise. Achieving more together or Feedback, Feedback, Feedback ------------------------------------------------------- [](#achieving-more-together-or-feedback-feedback-feedback) I'm grateful for any feedback! Be it suggestions for improvement, extension requests or just a (constructive) feedback on how good or crappy the extension is. Feel free to send me your feedback to [service@passionweb.de](mailto:service@passionweb.de "Send Feedback") or [contact me on Slack](https://typo3.slack.com/team/U02FG49J4TG "Contact me on Slack") ### Health Score 44 — FairBetter than 90% of packages Maintenance69 Regular maintenance activity Popularity24 Limited adoption so far Community14 Small or concentrated contributor base Maturity57 Maturing project, gaining track record Bus Factor1 Top contributor holds 53% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~55 days Recently: every ~110 days Total 24 Last Release 29d ago Major Versions 2.1.4 → 3.0.02024-11-14 1.1.5 → 2.1.52024-11-14 2.1.5 → 3.0.12024-11-29 1.1.6 → 3.0.22025-04-22 3.0.4 → 4.0.02026-07-09 ### Community Maintainers ![](https://avatars.githubusercontent.com/u/120183093?v=4)[Manuel Schnabel](/maintainers/passionweb-manuel-schnabel)[@passionweb-manuel-schnabel](https://github.com/passionweb-manuel-schnabel) --- Top Contributors [![ManuS3009](https://avatars.githubusercontent.com/u/43109656?v=4)](https://github.com/ManuS3009 "ManuS3009 (35 commits)")[![passionweb-manuel-schnabel](https://avatars.githubusercontent.com/u/120183093?v=4)](https://github.com/passionweb-manuel-schnabel "passionweb-manuel-schnabel (28 commits)")[![dmitryd](https://avatars.githubusercontent.com/u/306133?v=4)](https://github.com/dmitryd "dmitryd (1 commits)")[![infabo](https://avatars.githubusercontent.com/u/3999104?v=4)](https://github.com/infabo "infabo (1 commits)")[![KrisRaszewski](https://avatars.githubusercontent.com/u/162709175?v=4)](https://github.com/KrisRaszewski "KrisRaszewski (1 commits)") ### Embed Badge ![Health badge](/badges/passionweb-form-email-contentblocks/health.svg) ``` [![Health](https://phpackages.com/badges/passionweb-form-email-contentblocks/health.svg)](https://phpackages.com/packages/passionweb-form-email-contentblocks) ``` ### Alternatives [typo3/cms-styleguide TYPO3 extension to showcase TYPO3 Backend capabilities 105768.9k38](/packages/typo3-cms-styleguide)[friendsoftypo3/content-blocks TYPO3 CMS Content Blocks - Content Types API | Define reusable components via YAML 103574.3k64](/packages/friendsoftypo3-content-blocks)[eliashaeussler/typo3-form-consent Extension for TYPO3 CMS that adds double opt-in functionality to EXT:form 15100.9k](/packages/eliashaeussler-typo3-form-consent)[pagemachine/typo3-formlog Form log for TYPO3 23243.0k8](/packages/pagemachine-typo3-formlog)[wazum/sluggi TYPO3 extension for URL slug management with inline editing, auto-sync, locking, access control, and redirects 40543.5k](/packages/wazum-sluggi)[typo3/cms-redirects TYPO3 CMS Redirects - Create manual redirects, list existing redirects and automatically createredirects on slug changes. 167.6M84](/packages/typo3-cms-redirects) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)