Bug #22247
closedpage.jsInline / page.jsFooterInline may fail with config.removeDefaultJS=external
0%
Description
jsInline and jsFooterInline are build from cObject-Array.
These may contain _INT objects. INT-Objects are put as markers in content, and replaced before delivery by TSFE.
removeDefaultJS=external moves the inlineJS to an external file. If there are markers for INT-Objects they are moved to external file too (where it never will be substituted).
The result is, that
a, the JS file will raise JS-Errors
b, the INT-Object JS is not present
This means: INT-Object must not relocated to an external file, since this is not compatible with TYPO3 INT-object handling.
Solution: Extract the markers before moving to external file and include INT-Objects still inline .
(issue imported from #M13758)
Files
Updated by Steffen Ritter over 14 years ago
Use following TS to test, have a look at the results with removeDefaultJS=0
and removeDefaultJS=external ( the filecontent then)
with and without the patch.
page.jsInline {
500 = COA_INT
500.10 = TEXT
500.10.value = var INT1 =true;
1000 = TEXT
1000.value = var cachableTest = true;
2000 < .500
}
Updated by Andy Grunwald over 14 years ago
Added the last patch.
see mailling lists for details
Updated by Jeff Segars over 14 years ago
Committed the attached v7 to trunk (r7463) and 4_3 (r7464)