Core WordPress mail interception and Symfony Mailer transport package. Start
with docs/README.md; inspect Resources/config/services.yaml before changing
an extension point.
src/Hook/WordPressMailerBridge.php: thinpre_wp_mailboundary.src/Message/: WordPress input parsing and Symfony email creation.src/Transport/: DSN and provider transport behavior.src/Config/: shared settings contract consumed by Mailer Pro.Resources/ts/: admin source; generated assets are not source of truth.
- Focused PHP:
vendor/bin/phpunit --configuration phpunit.xml.dist --filter <TestName> - TypeScript:
npm run typecheck - Asset build:
npm run build(includes the typecheck) - Full PHP:
composer qa
- Keep hook interception small: parse once, delegate through
MailerInterface. - Preserve valid Symfony Mailer DSNs and provider bridge behavior.
- Never log or expose credentials. Treat message bodies as sensitive; Mailer Pro
persists them only when its
saveBodysetting is enabled. MailerRuntimeGuard::withoutInterception()must restore state after failures.- Keep public interfaces and
MailerSettingsbackward-compatible withsympress/mailer-pro.
Mailer Pro replaces MailerInterface and EmailBodyProcessorInterface and
extends the shared settings object. Search that repository before changing
these contracts, service aliases, or serialized settings.
The hook/transport regression test passes, npm run typecheck and
composer qa pass, docs use manifest-backed commands, and no credentials or
compiled assets are committed unintentionally.