Bug #23794
After #23766: Wrong text "Content Element: disable" - better: "Hide CE"
| Status: | New | Start date: | 2010-10-19 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| TYPO3 Version: | 4.5 | Complexity: | ||
| PHP Version: | 5.3 | |||
| Votes: | 0 |
Description
The wording is not ideal here:
When the option is clicked, the element can still be edited in the backend. So it is not disabled. What you mean is "Hide Content Element".
The text should be changed accordingly.
(issue imported from #M16068)
Related issues
| related to Core - Feature #23766: Implement new layout and labels for tt_content as result ... | Closed | 2010-10-17 | ||
| related to Core - Bug #23808: Change wording "Link to top of page" from activate to active | Closed | 2010-10-20 | ||
| related to Core - Bug #23814: Label "on-click" for formerly "click-enlarge" does not ma... | Closed | 2010-10-21 |
History
Updated by Jo Hasenau over 2 years ago
We discussed that already during the T3UXW09 and decided to do it this way, since this checkbox is not about the backend, but about the frontend.
The element actually is not "hidden" (display:none) but completely removed from the HTML output, thus the naming "disable".
The tab label is about the topic "General visibility", the checkbox group label then asks "Content Element?" and the checkbox label answers "Disable!"
We tried to follow this rule - Topic => Question => Action - for almost any checkbox by using verbs for the actions that are triggered by activated checkboxes.
Updated by Chris topher over 2 years ago
Topic => Question => Action
Sounds good! This should be documented somewhere. Not that the next extension developer breaks this useful logic, because he does not recognize it.
Updated by Jo Hasenau over 2 years ago
Can this one be closed?
Updated by Chris topher over 2 years ago
Can you still make sure that this gets documented somewhere?
Preferably in one of the official core manuals.
=> http://forge.typo3.org/projects/typo3v4-documentation
That would be great!