Active
Project:
Title
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Apr 2013 at 09:36 UTC
Updated:
17 May 2013 at 13:49 UTC
On the edit forms for the module at Configuration/Content Authoring/Title Settings/ the descriptions for all entities says something like the following:
Label replacement
Hide page title
Hide label in node listings
Check these options if you wish to hide the main page title or each label when displaying multiple items of type Node.If the options provided are to hide the title on the node or the node listings the description is just wrong and for an English speaker damn confusing.
It should read something like the following:
Node title hidden on default and/or teaser display modes:-
Hidden default display mode.
Hidden teaser display mode.
Check one or both of these options if you wish to hide the Node Title Field on the default display mode and/or the teaser display mode. Please note this does not affect inputting the node title into the Node Title Field on the node edit form.The same goes for Taxonomy or Comment or Block.
Comments
Comment #0.0
inventlogic commentedenhanced punctuation
Comment #0.1
inventlogic commentedsubstitute the word disable for hide and emphasis that the Title Field is hidden on the display modes not the node edit forms
Comment #0.2
inventlogic commentedremoved plural forms with form
Comment #0.3
inventlogic commentedadded Node before Title Field
Comment #1
plachUnless I'm misunderstanding it, your suggestion does not seem to describe what will actually happen if you check those options:
Hide page titlewill empty the$titlevariable in page.tpl.php.Hide label in node listingswill empty the$titlevariable in node.tpl.php (or equivalent).Comment #2
inventlogic commentedHow about this amended version?
Comment #3
plachThese descriptions look very developer-oriented. Keep in mind that those options are particularly useful for people having no clue of what template variables are. I'd avoid mentioning technical terms like variable, template and in general any function or template name.
Comment #4
inventlogic commentedHaving thought about what the user is getting in return for checking the boxes I would like to propose that what is happening is the user is taking control of the display of the Title by switching from the Title variable to the Title Field.
My proposed description for taking control of the Title display for the node.
Comment #5
inventlogic commentedAny feedback on the above suggestion?
I think it is a valid description of what is happening to the Title.
Comment #6
plachWell, actually you can take control of the title display even without messing with those checkboxes, but you'd end up with two labels shown. What is actually happening is that the hardcoded entity label is hidden. Hence I'd rather improve the bottom description explaining these uses cases, but I'd keep the "hide" terminology. We may want to rename the top title to "Label display" though.
Comment #7
inventlogic commentedWhat ever you decide you need to stop using the word "Label" when referring to the Title field or Title variable.
When an English speaker says label they are talking about the attached description of the Title field or Title variable not the field or variable itself.
i.e. Title: [Title Field]. The word "Title:" is the label. The [Title Field] should never be referred to as a label.
This point alone is why your descriptions are cryptic to a native English speaker.
Anyway....
I agree with your point about hiding the Title variable but from a user perspective I still say my latest suggestion helps the user understand exactly what they get from the Title module.
With the Title module they are getting control of the Title through using the Title field to display the Title rather than the Title variable.
To me it is a lot clearer than anything else I have seen so far!
These descriptions really do matter. I lost several hours due to the previous poor description.
Please make your own suggestion publicly available so we can get some feedback before committing.
Comment #8
plachOk, I missed this point so far. The reason why I used it is that "Label" is the correct technical term in Drupal language: the generic name of node titles, term names, user names, comment subjects and so on is entity labels. Anyway I agree this might not be the best way to present it to end-users.
The problem I have with your latest suggestion is that it is a bit misleading: you already have control of the title field display without messing with these options, altough obviously there's no point in showing a node title twice.
Perhaps this is suggesting us the current UI is simply wrong? Maybe we should automatically decide whehther the template variables should be empty or not by just checking whether the related title field is hidden or shown in the field display UI?
I'm not going to commit anything since there is no patch here :)
Comment #8.0
plachsimplified the description and identify display modes on which node title hidden