Project

General

Profile

Actions

Feature #22708

closed

there is no good way to add inline JS to header from extensions (jsInline is liable to collisions)

Added by Vladimir Podkovanov over 14 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-05-25
Due date:
% Done:

0%

Estimated time:
PHP Version:
5.2
Tags:
Complexity:
Sprint Focus:

Description

There are several PAGE's properties which allow to include user's javascript:
includeJSlibs.[array]
includeJS.[array]
jsInline (->CARRAY)

while first 2 options allow including JS via any text key, jsInline requires number, it is understood as JS lines should be in order
but it is inconvenient in case you create an extension which provides 3rd party JS lib where should be added some inline JS code on every page in order to configure the lib. The only option to include inline config JS is inlineJS but it allows collisions because of numeric keys - any number could be occupied yet in another extension or in main page's template

so is needed some new property to add inline JS from extensions to header

(issue imported from #M14469)

Actions #1

Updated by Vladimir Podkovanov over 14 years ago

workaround for header inline JS from extensions would be not setting it via TS but using a hook in $TSFE object and adding lines to header via $TSFE->additionalHeaderData

Actions #2

Updated by Alexander Opitz about 11 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)

Hi,

as this issue is very old. Is this feature missing in newer versions of TYPO3 CMS (4.5 or 6.1)?

Does $TSFE->additionalHeaderData helps to resolve your problem?

Actions #3

Updated by Alexander Opitz almost 11 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF