[MAGNOLIA-1729] use FreemarkerHelper in FreemarkerEmail Created: 06/Sep/07 Updated: 23/Jan/13 Resolved: 07/Sep/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 3.5 RC1 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Description |
|
Not as straightforward as it appears, because MagnoliaEmail also uses freemarker to re-process rendered magnolia pages in emails (i.e one can use ${variables} in the pages themselves and it gets replaced in the email) |
| Comments |
| Comment by Magnolia International [ 07/Sep/07 ] |
|
done on svn. FreemarkerEmail now uses FreemarkerHelp, and MagnoliaEmail has its own specific freemarker configuration. |