[PAGES-132] TemplateTypeHelper spams log that "variants" node doesn't have template assigned Created: 10/Aug/16 Updated: 16/Mar/21 Resolved: 16/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia pages module |
| Component/s: | None |
| Affects Version/s: | 5.4.x |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Milan Divilek | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| 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)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Date of First Response: | |||||
| Description |
|
This happens for variants which are not for root page Reproduce:
2016-08-10 16:16:31,297 WARN agnolia.rendering.template.type.TemplateTypeHelper: Page 'node /travel/tour/variants' doesn't have any template assigned.
|
| Comments |
| Comment by Roman Kovařík [ 02/May/17 ] |
|
The same applies for pages without a template (which are valid when using e.g. PlainTextTemplateRenderer), see integration test webapp fro an example. |
| Comment by Marvin Kerkhoff [ 25/Jul/19 ] |
|
This issue could happen if your variants are not named properly. If you use the URL Translation modul and you have not setup another "name" property through the configuration you could fall easily into this case . If you change your page properties it could change your name property and then the node name is changed as well. Usualy your page variations need to be named as variant-0 variant-1 ... otherwise you get this missleading error.
|