Project

General

Profile

Actions

Feature #78426

closed

Page settings > Use as Container in wrong tab?

Added by Urs Braem over 7 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2016-10-25
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

This is micro-minor, but I keep tripping over it.

In the page settings (TYPO3 7), the "use as container; contains plugin" box is in the "behaviour" tab.
I use this to assign a different icon to a folder in the pagetree - nothing else.

Is it correct that it the setting doesn't do anything else than change the icon?

Because, if yes, then it should rather go to the "Appearance" tab


Files

Actions #1

Updated by Mathias Brodala over 7 years ago

  • Status changed from New to Needs Feedback

Since this is not really a bug/missing feature, please first join us on the TYPO3 Slack to ask your question.

Actions #2

Updated by Urs Braem over 7 years ago

According to Mathias on Slack; probably only for legacy extensions like tt_news, so I'd say this could be moved if it's of interest

Actions #3

Updated by Riccardo De Contardi over 7 years ago

Not only for legacy extensions: even if you don't install any extensions, the dropdown "Contains Plugin" still contains "website users".

It is inside the "behavior" tab also on 8.6-dev (latest master)

Actions #4

Updated by Alexander Opitz almost 7 years ago

  • Target version deleted (8 LTS)

IMHO this only changes the Icon of a folder.

Maybe we can do following:

  • Moving to appearance and change naming
  • Provide a nicer API for the Icon
  • Provide some more default Icons?
  • Also allow this on "Non Folder" Pages?

Maybe a first example implementation as extension.

Sounds this fine?

Actions #5

Updated by Urs Braem almost 7 years ago

To me: yes, thanks!

Also allow this on "Non Folder" Pages?

That would be coloring then, as icons come from cTypes already?
Maybe colors would be sufficient, anyway.

Actions #6

Updated by Riccardo De Contardi almost 7 years ago

Would you agree if I change the tracker of this issue to "Feature"?

Actions #7

Updated by Urs Braem almost 7 years ago

  • Tracker changed from Bug to Feature

Of course, you are right. I tend to see UX-"Bugs" sometimes...

Actions #8

Updated by Riccardo De Contardi almost 7 years ago

  • Status changed from Needs Feedback to New
Actions #10

Updated by Urs Braem almost 7 years ago

nice!

Actions #11

Updated by Benni Mack almost 7 years ago

This setting can be used for more than just icons, and I believe this was the original intent, giving it some kind of "subtype" (as we have for tt_content as well).

Example: I have quite some projects that only allow to put in certain records into a storage folder:

  • Adding a option called "Projects" to the dropdown
  • Do a pageTS condition [page|module = projects] to only allow project records (allowedTables) in that folder. Same goes for fields that should be displayed or not displayed.
Actions #12

Updated by Urs Braem almost 7 years ago

Interesting! That's always an issue with custom extensions. Would you be willing to post the complete setup, how you add the option and restrict the table based on the condition?

Actions #13

Updated by Alexander Opitz almost 7 years ago

@Benni Mack

But this functionality is more ore less independent of the move to "Appearance" tab? And maybe rename it from "Contains Plugin" into something which can follow the behavior.
Also adding colored folders/pages icons shouldn't change this behavior ... it extends this IMHO more.

Actions #14

Updated by Riccardo De Contardi over 6 years ago

Update. In version 8.7, The "Use as container - Contains plugin" is in "Behaviour" tab.

Actions #15

Updated by Urs Braem over 6 years ago

thank you for the update!

Actions #16

Updated by Riccardo De Contardi over 5 years ago

There has been no advance on this topic since a lot of time; I write here my considerations:

- on version 9.5.2-dev (latest master) the "Use as container - Contains plugin" is in "Behaviour" tab
- the CSH for the field (the full version) reads

"[...] The Frontend display is largely not affected.[...]" 

I think that the "Appearance" tab contains settings that instead mostly affects the frontend display (apart from Backend Layout stuff) while in the "behavior" tab there is more a "mixed" situation with some settings that are BE-related and some that are FE-related.

Actions #17

Updated by Christian Kuhn about 1 year ago

  • Status changed from New to Closed

Hey.

The location of the 'module' column is currently below 'behaviour' and that's kinda not completely wrong, following the reasons from benni and riccardo.

I hope it's ok to close here for the time being since this is also open for such a long time already and nobody really fought on something in this area.

Actions

Also available in: Atom PDF