Project

General

Profile

Actions

Task #81848

closed

Tooltip for a disabled page should output "disabled" instead of "hidden"

Added by Team Web Web almost 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2017-07-13
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Sprint Focus:
On Location Sprint

Description

When editing the page settings there is the possibility to "disable" the page in the "Access" Tab.

In the pagetree the overlay-hidden.svg symbol is displayed for disabled pages, but the tooltip text shows "hidden", instead of "disabled".

For some editors this could be confusing.


Files

translate.png (33.1 KB) translate.png Team Web Web, 2017-07-13 09:32
en_translate.PNG (26.1 KB) en_translate.PNG Team Web Web, 2017-07-17 15:50
Schermata 2017-10-21 alle 22.27.54.png (9.34 KB) Schermata 2017-10-21 alle 22.27.54.png Riccardo De Contardi, 2017-10-21 22:29
Actions #1

Updated by Xavier Perseguers almost 7 years ago

  • Status changed from New to Needs Feedback

This is something to be tackled within TYPO3 Core, not within "translations". Alternatively, if the text is only "wrong" in German (as in your screenshot) and not in the main language (English), then you could suggest a new translation right away within the corresponding project on https://translation.typo3.org.

You may want/need to enable debugging to figure out which label is being used: http://xavier.perseguers.ch/tutoriels/typo3/articles/managing-localization-files.html#c950

$GLOBALS['TYPO3_CONF_VARS']['BE']['lang']['debug'] = true;
Actions #2

Updated by Team Web Web almost 7 years ago

I moved the bug the Core project. Instead of the label "labels.hidden" (typo3_src/typo3/sysext/lang/locallang_core.xlf) there should be used "disabled". Have a look at the attached screenshot (en_translate.PNG)

Actions #3

Updated by Riccardo De Contardi over 6 years ago

  • Category set to Backend User Interface
  • Status changed from Needs Feedback to New
Actions #4

Updated by Riccardo De Contardi over 6 years ago

Does not happens only to "pages" in pagetree, but also in list module and, in general, for every content element.

We could decide that "hidden" must be changed with "disabled" everywhere, then.

But what happens to the "switch" "Un-hide/Hide record"? (See attached screenshot) - Should it be Enable/Disable record ?

Actions #5

Updated by Team Web Web over 6 years ago

Riccardo De Contardi wrote:

Does not happens only to "pages" in pagetree, but also in list module and, in general, for every content element.

We could decide that "hidden" must be changed with "disabled" everywhere, then.

But what happens to the "switch" "Un-hide/Hide record"? (See attached screenshot) - Should it be Enable/Disable record ?

=> Yes, in our opinion that would be a clean solution!

Actions #6

Updated by Benjamin Kott over 6 years ago

  • TYPO3 Version changed from 7 to 9

Even this one is confusing most people are actually used to this,
so i would not like to see changes here except for master
- otherwise we will create even more confusion with the bugfix releases.

I agree on that we should unify this across all records and in my oppinion a page is not really different fom any other record.
That said i would propose that change the wording across all record types to disabled, since this is actually more reflecting
the actual behavior than hidden is currently doing.

Also the tca pointer that maps to hidden in tt_content is named disabled.
https://docs.typo3.org/typo3cms/TCAReference/Ctrl/Index.html#enablecolumns

Hidden:
to conceal from sight; prevent from being seen or discovered:

Disabled:
having become or having been rendered inoperative:

Actions #7

Updated by Benjamin Kott over 6 years ago

  • Tracker changed from Bug to Task
Actions #8

Updated by Susanne Moog almost 6 years ago

  • Sprint Focus set to On Location Sprint
Actions #9

Updated by Łukasz Uznański over 5 years ago

  • Status changed from New to Needs Feedback

On current master I can see that translation of this element is changed to "Page visible" and for content elements it's "Visibility of content element", so I think this issue is no longer valid? Looks like naming is unified right now.

Actions #10

Updated by Łukasz Uznański over 5 years ago

  • Status changed from Needs Feedback to Closed
Actions

Also available in: Atom PDF