TYPO3 Core

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... It would be cool if headerData was associative and extensions would automatically 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. For example tt_news could add its own meta-description, meta-author and overwrite the things brought by tt_content. Stuff added to the head should be put out sorted by tag-type simply for clean nice-looking HTML code.

Let me point this out in with some pseudo HTML code

head

meta blabla /
meta lululu /
meta brrrr /

link type="text/css" href="path/to/file/one" /
link type="text/css" href="path/to/file/two" /
link type="text/css" href="path/to/file/three" /

script type="javascript" src="path/to/file/one" ... /script
script type="javascript" src="path/to/file/two" ... /script
script type="javascript" src="path/to/file/three" ... /script

// space for stuff included the old way (old extensions)
// here the usual wild-west-code would show up

/head

Greetings to all Typo3Camp Hamburg people!

There already is an issue plus patch which adds a function to simply add something to headerData without having to specify a field number which prevents the overwriting issue. This leaves open the changeability after something has been added since you don't know the "address".

Issue #0009923
(issue imported from #M11333)