-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Laravel9 support #160
Comments
Hey, thanks for the update. I've been testing the Just a few things I encountered while setting this up, the new readme asks for adding these lines into the app.php under boostrap directory:
I get the errors above. If I try to run the app, I get: If I remove the "configure" lines, then I get this
If I remove the unset line then all goes OK. |
@kustomrtr Thank you for your trial and reporting. |
@s-ichikawa omg I feel stupid now, I re-checked the readme and you're in fact right. I was adding those Lumen settings on a Laravel installation, I'm blind hahaha. Thanks again! |
OK, Thank you for your trying! |
Also going to test this out! I did notice a small issue while upgrading: We're using the |
@rjp-thijs Ahh, yes. I changed that const name. |
Just wanted to report back that we've been using this in production for about a week now and havent noticed any issues :) |
@s-ichikawa (FYI @rjp-thijs is my other account ;)) Migtht have cheered a bit too early. It seems that something messes up with our attachments. I'm going to dive into this issue now, but I just wanted to pre-warn you :) PDF and XML attachments get attached as they should, but our CSV's are added as plain text below the mail. |
Figured it out. Left a fix at the PR: #159 |
@Koozza Fixed it! |
I would be fine with releasing this as 1.4 :) Haven't noticed any other bugs! |
I merged #159 and tagged |
I'm working on making support the laravel v9 now.
#159
There was a big change in the mail component from laravel9.
laravel/framework#38481
But I'm not using the laravel recently. so please try the for_laravel9 branch and create an issue if you face some problems.
If there is no critical issue until 2/22/2022, I'll merge into master branch and tag
4.0.0
.The text was updated successfully, but these errors were encountered: