We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug I have an email, where I check, what type, HTML or Text $text_body = $message->hasTextBody(); $html_body = $message->hasHTMLBody();
Used config Please provide the used config, if you are not using the package default config.
Code to Reproduce The troubling code section which produces the reported bug.
$text_body = $message->hasTextBody(); $html_body = $message->hasHTMLBody(); echo "$text_body"; echo "$html_body";
Expected behavior all are empty and not one of them is 1
Screenshots If applicable, add screenshots to help explain your problem.
Desktop / Server (please complete the following information):
Additional context Add any other context about the problem here. i think it has to do with the marked in the screenshot
The text was updated successfully, but these errors were encountered:
As a result, I can't get the body of the message.
Sorry, something went wrong.
maybe related to #562
No branches or pull requests
Describe the bug
I have an email, where I check, what type, HTML or Text
$text_body = $message->hasTextBody();
$html_body = $message->hasHTMLBody();
Used config
Please provide the used config, if you are not using the package default config.
Code to Reproduce
The troubling code section which produces the reported bug.
Expected behavior
all are empty and not one of them is 1
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop / Server (please complete the following information):
Additional context
Add any other context about the problem here.
i think it has to do with the marked in the screenshot
The text was updated successfully, but these errors were encountered: