-
Notifications
You must be signed in to change notification settings - Fork 36
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
Email is no longer dispatched via Mandrill #37
Comments
Im not seeing such error. Tested again on the latest release and emails are sent out. Maybe its something else on your setup, another extension or something. |
We don't have any other extensions hooking into the mail system. It makes perfect sense to me. The current version instantiates the mandrill transport model but never passes the message data from the transport builder to the instantiated model. It then 'sends' the mail with no message being set. Instead, you hook into transport factory 'create' method which sets that data and switcheroo the model being created (passing in the message data from the plugged-in function). You pretty much have to do it this way because the transport builder doesn't have publicly accessible data, only setters. When it creates the transport model, it passes the message data to the factory. If it makes any difference, we're running Magento 2.1.6. |
can you post here some logs from your Mandrill API logs to see the message without content? |
Same here, Mails not being sent at all (not even the Test Email)... I'm getting the following error: "No body specified". |
@Silarn Can you please elaborate how do you fixed this? I'm having exactly the same problem you reported. Thanks you! |
@centerax The message is never sent because there is no message data in the Transport model. There's no log to show you. I'll try to detail my fix in a second post. |
In my earlier post I opted to use a new module with a plugin as a fix rather than changing the module code. The first portion was the contents of the The second portion is a file you need to create under In addition, you need a basic /etc/module.xml file, composer.json file, and registration.php file. |
@Silarn if the body is empty that should not prevent the message from being sent, you can send an empty email. But if you say there is no log on Mandill, thats ok. |
It's not the mail body. It's all of the message data. There is no data in the transport model so nothing is sent. |
I was not able to replicate this case. Testing on 2.1.7 at the moment without success to have an empty object |
@lgrassini I've recently created a PR containing this change which they've merged into their development branch. You can give that a try instead of relying on this secondary module method. |
Thanks @Silarn ... So far it is working with your fix. I will wait until they merge your PR into the stable branch. |
guys: we will release a new version with this included tomorrow. |
The fix for #30 actually broke Mandrill email. It does allow the system to bypass it when it isn't enabled, but it effectively prevents sending email through Mandrill.
I'll see about creating an official PR tomorrow, but in order to fix this locally I had to create a new plugin and disable the Transport plugin:
and create the new class like so
The text was updated successfully, but these errors were encountered: