[5.x] Make email config data accessible in email templates #10949
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In some of our projects, we are using some of the form email configuration data in the email content. (Specifically, we added a custom field that lets us set email content in this configuration---however you may also consider using the email subject, for example).
Before a recent Laravel update (11.16.0 to be exact), we were able to get the right data in a sort of hacky way. However, this doesn't work anymore as a side effect of a small change in the Laravel mailer where the email data only gets built after setting the content, rather than before.
This small change fixes our very specific use case when having more than 1 email for a form active and wanting to use some of the email configuration fields inside of those emails' content :)