Project

General

Profile

Actions
Copy link

Bug #30460

closed

Misleading label for header_layout in allowed exclude fields list

Added by Nico de Haen about 13 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2011-09-30
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
Tags:
Complexity:
easy
Is Regression:
No
Sprint Focus:

Description

The label for the field tt_content:header_layout in the "Allowed exclude fields" list in the access rights user administration is misleading:
It says "Page Content: Type" in english and "Typ" in german, but there is also a Type (CType) field.
So I guess many other (like me) won't realize that this checkbox is for the header_layout.
Please rename it to "Page Content: Header Layout", and "Seiteninhalt: Überschrift Typ"

By the way, there are many duplicates like "Page Content: Align" (3x), "Page Content: Border" (2x), "Page Content: Link" (2x) etc.

Actions
Copy link
 #1

Updated by Peter Niederlag about 13 years ago

  • Status changed from New to Accepted
  • Complexity changed from no-brainer to easy

This is really anyoing, I agree. However I guess the label is just reused, when it is used in the regular form "layout" is sufficient as the context makes it clear.

Actions
Copy link
 #2

Updated by Alexander Opitz almost 10 years ago

  • Status changed from Accepted to Needs Feedback
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.9)?

Actions
Copy link
 #3

Updated by Riccardo De Contardi over 9 years ago

  • Status changed from Needs Feedback to Closed

I close this, because in both 6.2.12 and 7.2 the "Allowed exclude fields" list shows both the label and the field name for each entry to avoid confusion.
e.g.:

Align (imagecaption_position)
Align (header_position)
Border (imageborder)
Border (table_border)
Link (image_link)
Link (header_link)
Type (header_layout)

If you think that this is the wrong decision, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions
Copy link

Also available in: Atom PDF