Project

General

Profile

Actions

Bug #37837

closed

Pagetree "extendToSubpages" does not show different icon

Added by Arjen Hoekema over 12 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2012-06-08
Due date:
% Done:

0%

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

Description

When the "extendToSubpages" flag is checked and the page is access restricted the pagetree shows the default "access restricted" icon.

As far as I can recall the versions of TYPO3 before implementation of the SpriteManager showed a different/combined icon (access restricted + two arrows).

It looks like there is some priority checking in "t3lib_iconWorks::mapRecordOverlayToSpriteIconName", so only 1 overlay is possible.


Files

cattura.png (4.4 KB) cattura.png Riccardo De Contardi, 2017-04-27 14:24
Actions #1

Updated by Jigal van Hemert over 12 years ago

  • Status changed from New to Rejected

There is indeed a priority check in that function. The priorities are set in $GLOBALS['TBE_STYLES']['spriteIconApi']['spriteIconRecordOverlayPriorities'].

To make the overlay less cluttered the Usability team decided to only display the overlay icon with the highest priority. The effect you observed is no bug but a design feature.

Actions #2

Updated by Ingo Renner over 12 years ago

  • Status changed from Rejected to Accepted

I'd like to disagree, I think we really got a missing feature here. It caused me quite a few headaches too already not having this useful information anymore.

Actions #3

Updated by Ingo Renner over 12 years ago

as a compromise, maybe we can have an icon that combines the two informations (being access restricted and being inherited to subpages).

Actions #4

Updated by Arjen Hoekema over 12 years ago

Or maybe the icons of subpages in the pagetree that are affected by "extendToSubpages" could show this information.

Actions #5

Updated by Jigal van Hemert over 12 years ago

@Ingo : see http://forge.typo3.org/issues/9049#note-5 for the decision to show only one property.
I tried to suggest showing more information (see also screenshot http://forge.typo3.org/attachments/4027/pagetree_suggestion.png )

Anyway, we have the Usability Team for these kind of issues and they have to make the decision.

Actions #6

Updated by Ingo Renner over 12 years ago

ok, then as I said, I think we should task them to find a solution for this issue as it really is a problem that needs to be solved. IMO it's not a solution to just say no.

Actions #7

Updated by Mathias Schreiber almost 10 years ago

  • Project changed from TYPO3 Core to 78
  • Category deleted (Backend User Interface)

can you guys please comment on this one?

Actions #8

Updated by Benni Mack about 8 years ago

  • Project changed from 78 to TYPO3 Core
  • Category set to Backend User Interface
  • TYPO3 Version set to 8
  • Is Regression set to No
Actions #9

Updated by Riccardo De Contardi over 7 years ago

Attached: screenshot on the latest master

Actions #10

Updated by Benni Mack almost 5 years ago

With the new Icon API and the priority is configurable but still only one overlay applies as this would make the small icons even more cluttered.

The icons in TYPO3 Core are built in a way that the left site already contains the overlay, but the right side the type of the icon (e.g. "pagetype=shortcut") - I wonder how much more space we can use in a 32x32 icon, and still question this. I think we should expand the tooltip instead, or have a way to show that there are "more things to find out".

Actions #11

Updated by Benni Mack over 4 years ago

  • Status changed from Accepted to Rejected

Closing this for the time being.

Actions

Also available in: Atom PDF