templates in separate workspace (freemarker)
(MGNLINTEMPL-1)
|
|
| Status: | Closed |
| Project: | Magnolia In-place templating Module (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Jan Haderka | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | freemarker | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: |
| Description |
|
Current MultiTL is statefull and keeps track of what loader is used to load what template rather then going every time strictly in order of all TLs it knows of. Hence to enable true overriding of templates we need to make sure it is reset when new template is added to the workspace or when one is deleted. Work around is to touch fmTemplateLoaders configuration to bump MultiTL or restart in case one needs to override template previously served by other loader. |
| Comments |
| Comment by Magnolia International [ 09/Oct/08 ] |
|
My feeling on this is that the FMTemplateLoaderManager should BE a MultiTL itself. But this is something we can tackle later once we've made more progress on templates themselves. |
| Comment by Magnolia International [ 26/Jan/09 ] |
|
This is |