Split friendly admin email #298
Merged
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
aschempp
approved these changes
Feb 12, 2024
|
Thank you @fritzmg |
|
Can I tag this for a |
|
It is already published in 1.7.7 and 1.7.8 |
|
Oh weird, nvm then. For some reason the tag is not visible in the merged commit. |
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.
If a notification is sent in a context without a request, or without
FrontendIndexbeing rendered,$GLOBALS['TL_ADMIN_EMAIL']will be empty. In such a case the notification center currently falls back toConfig::get('adminEmail')- however, this config might contain 'friendly' email addresses such asThis would then be used directly for
$this->objLanguage->email_sender_address, resulting in an invalid sender address.This PR fixes that by splitting the friendly email address.