Problem/Motivation
Sites migrating from swiftmailer need a solution that's as safe as possible, minimizing the required changes.
Proposed resolution
Sites that want the minimum changes should enable symfony_mailer is enabled but not symfony_mailer_bc. This will be quite similar to swiftmailer, although still some differences that could be fixed as follow on issues:
- The name and variables for templates have changed.
- The name of the CSS library for mail CSS has changed.
Details
- Move
MailManagerReplacement,LegacyEmailBuilderandsymfony_mailer_bc_mailer_builder_info_alter()into the main module. - LegacyEmailBuilder calls
hook_mail_alter()
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | symfony_mailer.improve-bc.3315698-interdiff-5-6.txt | 4.09 KB | adamps |
| #6 | symfony_mailer.improve-bc.3315698-6.patch | 42.63 KB | adamps |
| #5 | symfony_mailer.improve-bc.3315698-interdiff-3-5.txt | 633 bytes | adamps |
| #5 | symfony_mailer.improve-bc.3315698-5.patch | 41.38 KB | adamps |
| #4 | symfony_mailer.improve-bc.3315698-3.patch | 41.36 KB | adamps |
Comments
Comment #2
adamps commentedComment #3
adamps commentedFix the tests.
Comment #4
adamps commentedComment #5
adamps commentedComment #6
adamps commentedComment #8
adamps commentedComment #9
adamps commented