typo3-powermail
TYPO3 Powermail Development
Compatibility: Powermail 13.x currently targets TYPO3 13.4 per Packagist — do not assume v14 until the package declares it. Examples use modern TYPO3 APIs where possible; adjust for your Core version. All examples use PHP 8.2+.
TYPO3 API First: Always use TYPO3's built-in APIs, core features, and established conventions before creating custom implementations. Do not reinvent what TYPO3 already provides. Always verify that the APIs and methods you use exist and are not deprecated in TYPO3 v14 by checking the official TYPO3 documentation.
Supplements:
- SKILL-CONDITIONS.md - Conditional field/page visibility (powermail_cond)
- PHP 8.4 patterns for finishers, validators, and conditions are covered directly in this skill
- SKILL-EXAMPLES.md - Multi-step shop form with Austrian legal types, DDEV SQL + DataHandler CLI
Powermail vs Core EXT:form
These are different systems. Do not mix migration advice between them.
Powermail (in2code/powermail) |
TYPO3 Core EXT:form | |
|---|---|---|
| Purpose | Mail forms built in the Powermail backend module; stored in tx_powermail_* tables |
Declarative forms (often YAML), form framework, finishers defined in YAML/PHP |
More from dirnbauer/webconsulting-skills
document-processing
>-
187ai-search-optimization
>-
184typo3-content-blocks
>-
89typo3-ddev
Use when providing DDEV URLs, accessing TYPO3 backend in browser, performing any ddev command (e.g. start, stop, restart, describe, exec), setting up DDEV for TYPO3 extension development, or testing across multiple TYPO3 versions. Triggers on: ddev URLs, backend URLs, local development, docker environment, PHP version management, multi-version testing.
85webconsulting-branding
>-
78legal-impressum
>-
75