You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 6, 2022. It is now read-only.
I agree that condition is rather odd.
The whole SwiftmailerExtension and SwiftmailerTransportFactory are quite difficult to understand. At one point we are checking that that there's no env vars and configuring transport using a factory, otherwise we use configureMailerTransport method, which seemingly does the same.
UPD.: Here's a guy suffers from the same weird design: #217, so and I did.
I just had the same issue and imho it's not even related to environment vars. The command is just ignored completely. You may check my PR (#286) and provide feedback if that fixes it for you.
In
config/packages/swiftmailer.yaml
next configwill not be interpreted properly:
command
property will be omitted.This happens because of next code:
In case of configuration above
$usedEnvs
is always empty, which requires to store some information in.env
file.The text was updated successfully, but these errors were encountered: