Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error if spool config value not set #65

Closed
jasonroman opened this issue Jan 20, 2014 · 13 comments · Fixed by #66
Closed

Error if spool config value not set #65

jasonroman opened this issue Jan 20, 2014 · 13 comments · Fixed by #66

Comments

@jasonroman
Copy link

I just upgraded to Symfony 2.4 and Monolog 2.5.0. If you do not use spooling, you receive the following error:

The service "monolog.handler.swift" has a dependency on a non-existent service "swiftmailer.transport.real".

This occurs since the alias never gets created if you do not set the 'spool' value under the Swiftmailer configuration.

@sgarner
Copy link

sgarner commented Jan 21, 2014

I have the same problem. 👍

@xabbuh
Copy link
Member

xabbuh commented Jan 21, 2014

Please have a look at #66. This should fix the issue.

@zazoomauro
Copy link

Having the same problem with the prod environment... rolling back to 2.4

@peterrehm
Copy link

@zazoomauro Why not set a spooler?

@zazoomauro
Copy link

what do you mean @peterrehm ? I'm still using 2.4 by the way

@peterrehm
Copy link

swiftmailer:
    spool:     { type: memory }

@zazoomauro
Copy link

I'll try

@peterrehm
Copy link

Since https://github.com/symfony/symfony-standard/issues/425 seems to be fixed with 2.5.0 you should be fine using the spool option.

@Seldaek
Copy link
Member

Seldaek commented Feb 19, 2014

OK it should work without spool if you require symfony/monolog-bundle dev-master. If someone can test and confirm then I will tag a new bugfix release.

@peterrehm
Copy link

@Seldaek Error seems to be fixed for me with dev-master. I think you can tag the release.

@Seldaek
Copy link
Member

Seldaek commented Feb 19, 2014

OK thanks for confirming.

@Seldaek
Copy link
Member

Seldaek commented Feb 19, 2014

2.5.1 is out then

@jasonroman
Copy link
Author

@Seldaek, checked with the 2.5.1 tag and it appears to be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants