Problem/Motivation

Many sites will be migrating from SwiftMailer to this module. We can speed up that process by migrating configuration settings.

Proposed resolution

Provide an automated conversion of settings if SwiftMailer's configuration is discovered during installation (could also have a drush command to repeat it later?).

The most obvious entry to migrate is the transport configuration.

Remaining tasks

Build the functionality.

User interface changes

n/a

API changes

None

Data model changes

None

CommentFileSizeAuthor
#4 symfony_mailer.swiftmailer-import.3233579-4.patch2.95 KBadamps

Comments

DamienMcKenna created an issue. See original summary.

adamps’s picture

adamps commented

Good idea.

The module's configuration is not as easy as e.g. SwiftMailer, which is used by lots (relatively speaking) of sites.

I would be interested to understand why you feel that. I would hope that it would be easier than the current option of configuring SwiftMailer + mailsystem.

OLD:

  1. /admin/config/swiftmailer/transport
  2. /admin/config/swiftmailer/messages
  3. /admin/config/system/mailsystem

NEW:

  1. /admin/config/system/mailer/transport
adamps’s picture

adamps commented
Issue summary: View changes
adamps’s picture

adamps commented
Status: Active » Needs review
StatusFileSize
new symfony_mailer.swiftmailer-import.3233579-4.patch2.95 KB
adamps’s picture

adamps commented
Status: Needs review » Fixed

  • AdamPS committed 7b70c6f on 1.x 
    Issue #3233579 by AdamPS: Upgrade path from SwiftMailer

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.