Feature #29321
closed
Subheader in TEXT and TEXTPIC
Added by Gone With the Wind about 13 years ago.
Updated about 13 years ago.
Priority:
Won't have this time
Category:
Backend User Interface
Description
There is no documentation on how the palettes changed in TYPO3 4.5. The regular way to make a subheader visible again in the CE TEXT and TEXTPIC is not worling anymore.
Therefore the whole discussion about whether the subheader should be visible or not, should be put to an end by just making it visible.
Why?
- HTML5
<header> groups <hx>s - so the use of the bodytext for any additional h2 is no longer useful. Instead, there should be ways to include more than just one subheader into a header group. Additional subheader fields might be necessary.
- WORKFLOW CONSISTENCY
I don't know of any other case where there are 2 extensions available that bring back a functionality that was hidden by TYPO3 (tv_subheader). This and a google search makes it clear that there are many users out there who need the subheader field way more often than others, which are visible by default anyway! So why not subheader, too?
Well,t he necessary change should be easy: just change the palette 'header' to 'headers' in typo3/sysext/cms/tbl_tt_content.php.
As already mentioned in the usability thread:
The "regular" way of making the subheader visible is:
Use the Header element, since it has been made exactly for this purpose.
No need for an extension or a change in the setup to make it work, since it's just there.
This is the case at least since TYPO3 version 3.8, when you take a look at the original lib.stdheader setup of CSS-styled-content.
- Target version changed from 4.5.6 to 4.7.0
To make more than one subheader work within just one HTML5 <header> group, we could activate the bodytext field within the official Header element, so all the headers can be grouped easily. But this is not a job for 4.5 anymore, since it would be a new feature, that has to wait until 4.7 since even 4.6 already is in feature freeze phase.
Two solutions have already been given by Björn and Jo. As you might know, I've been working on HTML5 for 4.7 in css_styled_content the past 2 months for the Incubator project. When the doctype is html5, the header will be grouped with a <header> tag. If there is a subheader, all <hx> will be grouped with a <hgroup>. Last but not least, when the date needs to be displayed in the header, the <time> tag will be used.
So everything will be in there in TYPO3 version 4.7
Guys, all I ask for - and I am not the only one - is to provide a solution somewhere for making the subheader visible. The simplest and most workflow-optimized would be to just make it visible by default in TEXT and TEXTPIC. If you are against that, then at least provide a solution in the RELASE notes. (As Jo Hasenau did in the Usability post.)
But please stop making everything so complicated for all that is needed is to make the subheader visible!!!
Thanks!
Sorry - but now it's getting ridiculous.
Why should someone put something in the release notes that has nothing to do with this particular release but is a core feature that has been available for ages and is well documented in the core API?
As I already mentioned in the usability thread:
- The core provides what you ask for: Different solutions to make the subheader visible. - You could use either the Header element, or a manual setup of the types/palettes and/or some of the functions of t3lib_extMgm
- The actual solution is to use the functions provided by the core and read the core docs to find out how to use them. - This is nothing new, nothing very special for this particular release and nothing that would be very complicated at all.
IMHO this is more than enough for the few guys who really need the subheader in another place.
Quoting the famous Nike slogan: Just do it!
- Status changed from New to Rejected
- Priority changed from Must have to Won't have this time
- Target version deleted (
4.7.0)
Hi,
please check out EXT:cron_subheadereverywhere. Just install it, and it will enable "subheader" in all CTypes.
We need to have a consistent and clean set of fields available for basic installations of the TYPO3 core, which is suited for most applications. And as Joey pointed out (and which this extension proves) it is easy to enable unique individual setups just by configuring it properly.
Hope to get everybody satisfied with this and thus close this issue.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by