Missing $debugHintsPath when sending email via command

[cykirsch]

Preconditions

1. Magento 2.1

Steps to reproduce

1. Create a console command that sends an email, where the email also loads in another block like {{layout handle="sales_email_order_items" order=$order area="frontend"}}

Expected result

1. Email should send without error.

Actual result

1. Email fails with error

main.CRITICAL: exception 'BadMethodCallException' with message 'Missing required argument $debugHintsPath of Magento\Developer\Model\TemplateEngine\Plugin\DebugHints.' in /.../.../magento/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php:45

More info

A workaround was found and posted on these sites:
https://community.magento.com/t5/Programming-Questions/Email-template-with-block/m-p/50061#M1219
https://magento.stackexchange.com/questions/152089/magento2-command-line-sending-email-using-block-templates-error-missing-r

Unfortunately it requires invoking object manager directly, as it seems the object manager's configuration is what needs to be corrected. Since direct loading of the object manager is not best practice, if modifying this config is the only solution then a method should be provided to modify the config without loading object manager directly.

[magento-engcom-team]

@cykirsch, thank you for your report.
We've created internal ticket(s) MAGETWO-81170 to track progress on the issue.

[nemesis-back]

@okorshenko I will work on it #SQUASHTOBERFEST

[orlangur]

Implementation approach described in #11852 (review)

[passtet]

#khcd2018

[magento-engcom-team]

@passtet thank you for joining. Please accept team invitation here and self-assign the issue.

[magento-engcom-team]

Hi @cykirsch. Thank you for your report.
The issue has been fixed in #17984 by @passtet in 2.2-develop branch
Related commit(s):

• a804a3cd485bd4aecabac3aa4203d20c6a6c9a08

The fix will be available with the upcoming 2.2.8 release.

[sidolov]

Hi @cykirsch. Thank you for your report.
The issue has been fixed in #18991 by @p-bystritsky in 2.3-develop branch
Related commit(s):

• 7c86822387cbee24186a1746b373b2bfb381bed8

The fix will be available with the upcoming 2.3.1 release.