Project

General

Profile

Actions
Copy link

Bug #22247

closed

page.jsInline / page.jsFooterInline may fail with config.removeDefaultJS=external

Added by Steffen Ritter about 14 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Jeff Segars
Category:
-
Target version:
-
Start date:
2010-03-06
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
5.1
Tags:
Complexity:
Is Regression:
Sprint Focus:

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

Download all files
inlineINTfix.diff (1.38 KB) inlineINTfix.diff Administrator Admin, 2010-03-06 18:54
rfc13758-inlineJS_v3.diff (2.74 KB) rfc13758-inlineJS_v3.diff Administrator Admin, 2010-04-30 10:27
rfc13758-inlineJS_v5.diff (2.63 KB) rfc13758-inlineJS_v5.diff Administrator Admin, 2010-04-30 15:21
rfc13758-inlineJS_v7.diff (2.7 KB) rfc13758-inlineJS_v7.diff Administrator Admin, 2010-04-30 18:23
Actions
Copy link

Also available in: Atom PDF