Feature #19693
Integrate possibility to define additional header data via TypoScript
| Status: | Resolved | Start date: | 2008-12-11 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Oliver Hader | % Done: | 0% |
|
| Category: | Communication | Spent time: | - | |
| Target version: | - | |||
| PHP Version: | 5.2 | Sprint Focus: | ||
| Complexity: |
Description
Imagine you've got an extension that shall add a JavaScript and a CSS file to the HEAD part of the HTML document of the current page. This is possible in modifying $TSFE->additionalHeaderData. However, when your extension does not come with a PHP part and consists only of TypoScript, it's not possible.
Thus, this feature request is about to integrate an accordant possibility.
Example:
10 = HEADERDATA
10 {
data = path:EXT:myextension/res/stylesheet.css
wrap = <link rel="stylesheet" type="text/css" href="|" />
prepend = TEXT
prepend.char = 9
}
- add the CSS file "stylesheet.css" to the HEAD part of the current document
(issue imported from #M9923)
0009923.patch
(1 kB)
0009923_v2.patch
(1.4 kB)
Related issues
History
#1 Updated by Oliver Hader over 6 years ago
Documentation changes:
doc_core_tsref, functions, stdWrap: Property: additionalHeaderData Data Type: cObject Description: Adds the cObject to the <HEAD> part of the current document
#2 Updated by Steffen Kamper over 6 years ago
Hi olly,
This is a nice idea, it allows adding header data depending on defined objects.
+1!
#3 Updated by Johannes von Bargen about 6 years ago
Yeah! That would be cool! I just had a discussion with several people at typo3camp Hamburg about such a possibility.
+1!!!
I am currently working on a extension which integrates jQuery Galleriffic and Galleria into cType Image. That brought the ugly headerData array back to my mind... Additionally it would be cool if headerData was associative and extensions wouldautomatically have a private namespace in the array to add their stuff (the extension key). This way the case where one ext overwrites js /css/meta stuff added by another one would never happen again by accident but otherwise fields of the array could be addressed explicitly if ext B absolutely wants to change something ext A has added.
I think I will open up an own bug for that...
#4 Updated by Vladimir Podkovanov about 6 years ago
+1 for stdWrap.additionalHeaderData
to Johannes von Bargen,
+ 1 for converting page.headerData to assoc array so extension does not bother which numeric keys are used yet. I was running into it too.
#5 Updated by Oliver Hader about 6 years ago
Documentation changes:
add a new entry to "Content Objects (cObject)" (tsref.cObject):
HEADERDATA
HEADER is very similar to the cObject "TEXT". However the result will not be added to the content but to the HTML HEAD section of the page. This can be used to define JavaScript or Stylesheets on an extension level for example.
Property Data type Description
value string text, wrap with stdWrap properties
(stdWrap properties)
Example:
10 = HEADERDATA
10 {
value = script.js
wrap = <script src="|" type="text/javascript"></script>
}
#6 Updated by Oliver Hader over 5 years ago
This is solved with the PageRenderer in issue #20661