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
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
The reason will be displayed to describe this comment to others. Learn more.
at least in AbstractBehavior is there now a problem because
$templateRootPath = \TYPO3\CMS\Core\Utility\GeneralUtility::getFileAbsFileName($extbaseFrameworkConfiguration['view']['templateRootPath']);
is now empty
The reason will be displayed to describe this comment to others. Learn more.
Thanks @georgringer, it looks like you're right. Since making that change, we haven't been using the sendTemplateEmail function from the AbstractBehaviors class.
I have made an issue and will try to get it later today. Ideally, there would be only one place where emails are sent from. That way you can control any logging or email whitelisting in one place. I don't think AbstractBehavior is the best place to have a "sendEmail" function. We have been using an EmailService from a separate extension to abstract away some of the gritty configuration details and put them into typoscript.
d048af4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
at least in AbstractBehavior is there now a problem because
$templateRootPath = \TYPO3\CMS\Core\Utility\GeneralUtility::getFileAbsFileName($extbaseFrameworkConfiguration['view']['templateRootPath']);
is now empty
d048af4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @georgringer, it looks like you're right. Since making that change, we haven't been using the sendTemplateEmail function from the AbstractBehaviors class.
I have made an issue and will try to get it later today. Ideally, there would be only one place where emails are sent from. That way you can control any logging or email whitelisting in one place. I don't think AbstractBehavior is the best place to have a "sendEmail" function. We have been using an EmailService from a separate extension to abstract away some of the gritty configuration details and put them into typoscript.
https://github.com/castiron/cicbase/blob/master/Classes/Service/EmailService.php
#14