-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[FEATURE] Updating typoscript view configuration to use the new 6.2 way.
- Loading branch information
Peter Soots
committed
Sep 17, 2014
1 parent
7692447
commit d048af4
Showing
1 changed file
with
9 additions
and
3 deletions.
There are no files selected for viewing
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
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