You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Render a faulty mail message that throws a Swift exception. For example attach a file that does not exist.
What's expected?
If you catch the exception, no extra output should be generated on the web page.
What do you get instead?
When rendering the mail body, PHP output buffering is used. When the exception is thrown, the buffer is obviously not cleared correctly. So the parts of the mail that rendered successful before the exception happened now appear in the web output, even when you catch the exception.
Additional info
Q
A
Yii version
2.0.10
PHP version
7.0.8
Operating system
Ubuntu 14.04 LTS
The text was updated successfully, but these errors were encountered:
Sorry, will not find time for a unit test. It's not a simple test as you somehow have to capture/compare web output. No idea how to handle this in a unit test.
What steps will reproduce the problem?
Render a faulty mail message that throws a Swift exception. For example attach a file that does not exist.
What's expected?
If you catch the exception, no extra output should be generated on the web page.
What do you get instead?
When rendering the mail body, PHP output buffering is used. When the exception is thrown, the buffer is obviously not cleared correctly. So the parts of the mail that rendered successful before the exception happened now appear in the web output, even when you catch the exception.
Additional info
The text was updated successfully, but these errors were encountered: