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
8000
{{ message }}
This repository was archived by the owner on Feb 6, 2022. It is now read-only.
As of the 'mailers' feature came in, the memory spooling has stopped working.
I found out that the 'mailer' service became just an alias, and that's what is causing the problem.
The 'initialized' method of the Symfony\Component\DependencyInjection\Container does not handle aliases (as it is in the ContainerBuilder), but therefore the EmailSenderListener never sends emails.
I don't really know which is better: if it the Container should handle aliases or the EmailSenderListener should check services in a different way. Anyway, I've made a pull request here which resolves the service checking.
The text was updated successfully, but these errors were encountered:
This PR was squashed before being merged into the master branch (closes#44).
Discussion
----------
fix checking of mailer services in EmailSenderListener
The 'initialized' method of the Symfony\Component\DependencyInjection\Container
554F
does not handle aliases (as it is in the ContainerBuilder), but therefore the EmailSenderListener never sends emails.
This fix is related to issue #43.
Commits
-------
33a7015 fix checking of mailer services in EmailSenderListener
As of the 'mailers' feature came in, the memory spooling has stopped working.
I found out that the 'mailer' service became just an alias, and that's what is causing the problem.
The 'initialized' method of the Symfony\Component\DependencyInjection\Container does not handle aliases (as it is in the ContainerBuilder), but therefore the EmailSenderListener never sends emails.
I don't really know which is better: if it the Container should handle aliases or the EmailSenderListener should check services in a different way. Anyway, I've made a pull request here which resolves the service checking.
The text was updated successfully, but these errors were encountered: