|
[Bulk Comment] The fix version for this Unresolved Tasks still indicates 2.6, but the code freeze is well passed now, and no exception was requested for this work. The Fix Version of this issue is being reset to 2.7, with the expectation that you are planning to finish the work in time for that release. If that is not the case, please update the Fix Version appropriately, or if you are not actively working on this issue, consider turning it into a Feature Request.
Reopen this ticket since
This is to make it as the default choice now. So every email send from WSetup tool will be through the EmailTemplateService. Thanks, - Zhen Another checkin r58076 put back the loadTemplate routine in init() function back, but provided some placeholders for various template variables, which avoids the exception during the loading time due to missing template variables.
Thanks, - Zhen Zhen, is this needed for 2.6 as well (looks like
How is it enabled? Is it that there is a sakai property that needs to be =true?
EmailTemplateService is enabled by default in the site-manage module. To change it, one need to change the components.xml file in site-manage-pack/src/webapp/WEB-INF:
Uncomment out the UserNotificationProviderImp: <bean id="org.sakaiproject.sitemanage.api.UserNotificationProvider" class="org.sakaiproject.sitemanage.impl.UserNotificationProviderImpl" And comment out the ETSUserNotificationProviderImpl <bean id="org.sakaiproject.sitemanage.api.UserNotificationProvider" class="org.sakaiproject.sitemanage.impl.ETSUserNotificationProviderImpl" |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Task
Closed
Major
integrate Wsetup tool with email template service
If you are still working to resolve this issue for 2.6, then please post an email to sakai-dev to let everyone now that you need an exception for this JIra, explain what is left to do, and when you plan to have the work completed; please include that information here in the Jira as well.
Otherwise, if the resolution of this task has been postponed, please reset the Fix Version to 2.7 or Unknown, depending on what you're new expectations for completion are. If the issue is no longer relevant, please close the issue as Won't Fix or Incomplete with an explanation of why.
Thanks!