Bug #14879
closed
TypoScript value assignment order
0%
Description
code example in root template:
objects.CENTER_MENU {
wrap = test_old
}
code example in next level template:
objects.CENTER_MENU {
stdWrap.outerWrap < .wrap
wrap = test_new
}
if objects.CENTER_MENU.wrap has been set in parent template object sdtWrap.outerWrap hasn't the expected value of test_old, instead it is set to the value test_new. the assignment order isn't as expected.
(issue imported from #M1311)
Updated by old_posimis over 19 years ago
We found the cause for this issue.
because the template on the next level is an extension of the root level AND in the rootlevel template the second template is assigned as next level template, it is parsed two times. So outerWrap is first set to test_old and then set to test_new. on another page on the second level (without the extending template) the assignment is valid.
But is this a desired behavior? To avoid this, I have to put all next level templates in a special sysfolder. Or is there another method?
Updated by Sebastian Kurfuerst about 19 years ago
Hi, I don't know if this behavior is "desired", but it works when using a sysfolder for "next level templates" - this is more logical anyways I think, isn't it? I don't know how it should work in a better way...
If there is more information to this bug, please reopen.
Greets, Sebastian