[TYPO3-core] subheader for all types, not just "header"?

Alexander Stehlik alexander.stehlik at gmail.com
Wed Jan 29 12:24:42 CET 2014


One additional suggestion on this topic:

If the subheader is available in all content elements should we remove 
the condition that checks for the html5 doctype in lib.stdheader?

Then we could also remove the extra subheader rendering in 
tt_content.header.


Am 27.01.2014 17:47, schrieb Stefan Neufeind:
> On 01/27/2014 05:34 PM, Ernesto Baschny wrote:
>> Stefan Neufeind schrieb am 26.01.2014 00:28:
>>
>>> for content-types (tt_content) we currently have two palettes defined in
>>> TCA. One is "header", the other is "headers". It seems the basic
>>> difference is that "headers" also contains a field "subheader".
>>>
>>> The "subheader" is available for content-type "header", while for "text"
>>> or "image" it simply isn't shown (other palette used).
>>> Of course you can "easily" enable that yourself by changing TCA in a
>>> small extension. And you need to extend css_styles_content for those
>>> types as well to show subheader (oneliner per type).
>>>
>>> But is there really a reason why "subheader" is not commonly shown?
>>> Or if not, might we consider to just use the palette "headers" instead
>>> of "header" for all content-types?
>>>
>>> If you don't want the file shown to your editors, you can easily hide it
>>> as all other fields (excludefields). But imho it would be good to have
>>> "subheader" in the first go, don't you think? It "is there already".
>>>
>>>
>>> In case nothing speaks for a separate palette "header" and we can use
>>> "headers" for all cases, I'd be happy to contribute a patch for review
>>> (also extension css_styled_content).
>>
>> Note that this issue emerges from "time to time", see:
>>
>> http://forge.typo3.org/issues/29321
>>
>> Funny enough back then I even made an extension that does that:
>>
>> http://typo3.org/extensions/repository/view/cron_subheadereverywhere
>>
>> Since the topic keeps popping up from time to time, I would have no
>> problem in making it available by default in new 6.2 installations. A
>> nice "new feature". :)
>
> I'll make it a "task" (enable what is there already) so we don't run
> into problems with feature-freeze :-) Will send a patch ...
>
>
> Kind regards,
>   Stefan
>
>



More information about the TYPO3-team-core mailing list