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
Undefined variable $exception when I added variable to Mail construct #224
Comments
@xMrViktorx try remove $order from the constructor. /**
* Create a new message instance.
*
* @return void
*/
public $order;
public function __construct()
{
} |
Hi @xMrViktorx I think the section of the code that is supposed to make use of the new laravel Mail class style and still use the old one is possibly causing this problem. Sorry for the delay in response on this issue and a few others, I have to give priority to some other matters. |
@ReeceM Any update on this? cause I'm also facing the same issue. I can't edit the template. |
So it would be great if you can share a error message / trace. Also as mentioned earlier in the messages, I currently have a few things that need to be given priority. But I am happy to have a look, or if you would like to make a PR those are welcome. |
When creating a new template, it is work fine. However, if you make the template content dynamic and need to pass data to the mailable class constructor, you may encounter an error on the Eclips list page. |
we have tried with the below command but getting the same issue to install on laravel 10, composer require qoraiche/laravel-mail-editor:dev-master composer require qoraiche/laravel-mail-editor:4.1.0-beta.0 |
maileclipse/mailables/view/Testmail page.
Without variable, everything is okey, but If I add variable to __construct I get this error:
I gone deeper and this is because when you add variable to construct, the view is null, and without view It can't render the preview.
$reflector->newInstanceArgs($resolvedTypeHints) doesn't give back view.
Reproduce the bug
Laravel Framework 8.42.1
MailEclipse v4.0.3
The text was updated successfully, but these errors were encountered: