Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
There's a bug with InterfaceTokenTransport transports that have a lower batch getMaxBatchLimit() than the number of recipients in the message. It was thought MailHelper::useMailerTokenization was no longer needed as the mail helper was updated to auto handle flushing the queue for these mailers that need access to the metadata of a contact to work. (See #2284). But in the case of transports that sets a low max batch limit (say 1) and a form email had two recipients, the BatchQueueMaxException exception was thrown. The original useMailerTokenization() purpose was for when processing a batch of recipients with unique metadata to each to receive the same email. Thus a new MailHelper::enableQueue() was added to replace useMailerTokenization() to restore it's old functionality and follow the same naming scheme as queue() and flushQueue().
Steps to test this PR:
Steps to reproduce the bug:
List deprecations along with the new alternative: