Bug #84227
Updated by Markus Klein over 6 years ago
Consider two tsconfig files: foo1.tsconfig <pre> foo = 1 </pre> <pre> foo2.tsconfig <pre> foo =2 </pre> Include them on a page in this order: foo1, foo2 The info module says that on this page the resulting page TSconfig is @foo = 2@, which is correct. Debugging frontend (TypoScriptFrontendController::getPagesTSconfig) though, reveals that @foo = 1@ in FE. The reason is that page TSconfig resolution is implemented differentely for FE and BE. BE walks the rootline and collects TSconfig from top to bottom, whereas FE walks from bottom to top and reverses the array afterwards, BUT the individual tsconfig_includes of each pages are always fetched in the given order in the page record, which mean that their order is reversed too in FE context causing the observed behaviour above.