mstitb / mst-pm2yaml
Powermail-Formulare als YAML-Datei: Datei als Quelle, Powermail arbeitet unverändert mit der Datenbank.
Package info
github.com/mxsteini/mst_pm2yaml
Type:typo3-cms-extension
pkg:composer/mstitb/mst-pm2yaml
1.0.0
2026-11-21 10:14 UTC
Requires
- php: >=8.2 <8.6
- in2code/powermail: ^13.0
- symfony/yaml: ^7.0
- typo3/cms-backend: 13.4.*
- typo3/cms-core: 13.4.*
Requires (Dev)
- phpunit/phpunit: ^11.5
- typo3/testing-framework: ^9.0
Suggests
None
Provides
None
Conflicts
None
Replaces
None
README
A Powermail form (form, pages, fields, translations) is synchronized with a YAML file. Powermail itself stays untouched: it reads from the database as always, the extension keeps file and database in sync. The file contains no uids.
title: 'Contact' pages: details: title: 'Your details' fields: firstname: type: input title: 'First name' mandatory: 1
| Composer | composer require mstitb/mst-pm2yaml |
| TYPO3 / Powermail / PHP | 13.4 / 13.x / 8.2 to 8.5 |
In short
- Select a file (field "YAML-Datei" on the form): versioned in
EXT:…/Configuration/Powermail/(writable in the backend only in the Development context) or in the site folder (fileadmin/_Powermail/, always writable). The file wins. - Displaying the plugin imports a changed file into the database first.
- Saving in the backend (live workspace) writes the file back.
- Commands:
typo3 pm2yaml:export <uid>andtypo3 pm2yaml:sync [--only-locked](deployment).
Documentation
The full documentation is in Documentation/: Concept, Installation, Usage, YAML format, Commands, Configuration, Testing, Troubleshooting.
Tests
# Unit tests (no database) ddev exec vendor/bin/phpunit -c <extension>/Tests/phpunit.xml # E2E tests against a running DDEV instance (Chrome) cd <extension>/Tests/E2E && npm ci && E2E_PROJECT_ROOT=<ddev-project> npx playwright test
Details and requirements: Documentation/Testing.md.