[MGNLSTK-986] Provide call to methods in TemplateCategoryUtil through STK templating functions. Created: 06/Aug/12 Updated: 23/Aug/12 Resolved: 06/Aug/12 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | None |
| Affects Version/s: | 2.0.4 |
| Fix Version/s: | 2.0.5 |
| Type: | Improvement | Priority: | Critical |
| Reporter: | Robert Šiška | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
Methods getContentListByTemplateName(...) and getContentListByTemplateNames(...) were provided by STKUtil. Since that is deprecated, we need to provide the functionality through STK templating functions. |
| Comments |
| Comment by Robert Šiška [ 06/Aug/12 ] |
|
It might be better idea to allow calling TemplateCategoryUtil from templates right away. |
| Comment by Christian Ringele [ 07/Aug/12 ] |
|
There are in STKTemplatinFunctions the methods: which should provide this functionality. |
| Comment by Jan Haderka [ 09/Aug/12 ] |
|
Critical due to migration tool dependency. |
| Comment by Jan Haderka [ 23/Aug/12 ] |
|
@Christian: The methods you listed retrieve content based on category and sub-category of the template, methods exposed by Robert retrieve content based on the template name(s) directly irrespective of category. However it is questionable whether those methods should be in the TemplateCategoryUtil in a first place since they are generic TemplateUtil methods. |