Bug #62549
6.2.4 ~ 6.2.6 template analyzer displays wrong constants/setup
| Status: | Accepted | Start date: | 2014-10-30 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | TypoScript | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 6.2 | Is Regression: | No | |
| PHP Version: | 5.5 | Sprint Focus: | ||
| Complexity: |
Description
As suggested by Philipp on the mailing list http://forum.typo3.org/index.php/t/206827/
I'm opening this ticket that may be a recurrence of https://forge.typo3.org/issues/54897
In 6.2.6 I've noticed the template analyzer displays the setup and constants of another different template record when selected. I can't work out a definitive pattern to the differences, as in it does not seem to be an off by one error in UID in sys_template or something like that.
Info/Modify works fine, as does all rendering and typoscript object browser. Adminer shows that the correct setup and constants are in sys_template.
Philipp mentions:
"This bug exists since a while. Downgrading will not help, because it is there since at least the release of 6.2. Most likely the matching of the array and the possible locations of the templates is broken after refactoring some of the code. Therefore wrong links are generated."
I'm happy to provide any troubleshooting info if needed with guidance (not a programmer).
Thanks.
Related issues
History
#1 Updated by Philipp Gampe 9 months ago
- Status changed from New to Accepted
Behavior exists since 6.2.0 at least, most likely longer.
#2 Updated by Philipp Gampe 9 months ago
$GLOBALS->['tmpl']->hierarchyInfo[] is correct. $GLOBALS->['tmpl']->constants[] and $GLOBALS->['tmpl']->config[] have the wrong array keys for some reason.
We should evaluate whether the automatic generated keys are needed or if we can replace them with the template key.
We can replace $GLOBALS->['tmpl'] with this->template without problems.
BTW: This code is a big WTF.