Crazy frustrated so posting this here to see if anybody can help.
I have a custom artisan command registered for my app, which works just fine.
I have various event listeners in my app, which work just fine.
One of these event listeners listens for a certain event to get fired and sends an email when this happens. Other points throughout my app can fire the event and the email will send properly.
When my custom artisan command is run, that same event gets fired... AND it gets hit (I can produce log records showing the event has been fired, and can see data from inside the event listener), but the email never actually sends.
I'm desperate here :)
Thanks, Jesse
Nevermind this. Finally figured out it's because the overridden mail config for some reason gets ignored when run from artisan. Specifying the config in the mail config file itself enables the mail to be sent when going out from artisan -- but still, no errors or anything else when attempting to use the overridden mail config. Strange. Not sure why the overridden config is getting ignored, but whatever, I've been on this for way too long now and need to get moving along :)
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast