Project

General

Profile

Actions
Copy link

Feature #7459

closed

Filter allowed content element types by column

Added by Lina Wolf over 14 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Jo Hasenau
Category:
Backend User Interface
Target version:
Candidate for Major Version
Start date:
2010-04-25
Due date:
% Done:

0%

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

Description

When creating a new Content Element the resultiong wizzard should be configurable by column. Lets say in the column for the Header we want to alow only an Imgae an a certain Flash Plugin, in the Cloumn for the footer there should be only Text. The two Content-Columns should alow everything.

TYPO3 contains a hook wich easily alows to create this Feature. I wrote a small non-published Extension wich does this. But I believe the Feature should rather be added to modernbe.

The wish for such a Feature was also voiced onj the TYPO3 Camp Potsdam.

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Feature #67750: Page view > Dropdown to quick create most used contentClosed2015-06-25

Actions
Related to TYPO3 Core - Feature #77842: explicitly allow CTypes for columns in backend_layoutClosed2016-09-04

Actions
Actions
Copy link
 #1

Updated by Jo Hasenau over 14 years ago

  • Status changed from New to Needs Feedback

Can you send me the extension to see how it fits into the current trunk version?

Actions
Copy link
 #2

Updated by Lina Wolf over 14 years ago

I send you an eMail Jo, did you receive it?

Actions
Copy link
 #3

Updated by Jo Hasenau over 14 years ago

Yep - didn't have the time to test it yet, but looks promising :-)

Actions
Copy link
 #4

Updated by Jo Hasenau over 14 years ago

  • Status changed from Needs Feedback to Accepted
  • Assignee set to Jo Hasenau
  • Priority changed from Should have to Must have
Actions
Copy link
 #5

Updated by Lina Wolf over 14 years ago

If you need any help on integration let me know. Cool project by the way.

Actions
Copy link
 #6

Updated by Frank Gerards over 12 years ago

is this feature still under developement ? Would be interested in supporting it, maybe you can send me your patch too, lina ?

Actions
Copy link
 #7

Updated by Michael Stucki over 11 years ago

I am moving this issue into the main "Core" project.

Actions
Copy link
 #8

Updated by Michael Stucki over 11 years ago

  • Project changed from 1180 to 1846
Actions
Copy link
 #9

Updated by Michael Stucki over 11 years ago

  • Tracker changed from Major Feature to Bug
  • Project changed from 1846 to TYPO3 Core
Actions
Copy link
 #10

Updated by Mathias Schreiber almost 10 years ago

  • Target version set to 7.4 (Backend)
  • TYPO3 Version set to 4.5
  • Is Regression set to No
Actions
Copy link
 #11

Updated by Susanne Moog over 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions
Copy link
 #12

Updated by Benni Mack about 9 years ago

  • Target version changed from 7.5 to 7 LTS
Actions
Copy link
 #13

Updated by Mathias Schreiber about 9 years ago

  • Tracker changed from Bug to Feature
  • Target version deleted (7 LTS)
Actions
Copy link
 #14

Updated by Riccardo De Contardi about 9 years ago

  • Category set to Backend User Interface
Actions
Copy link
 #15

Updated by Jo Hasenau almost 8 years ago

  • Subject changed from Integrating Filtering of Availible Content Elements by Column to Filter allowed content element types by column
  • Status changed from Accepted to In Progress
  • Target version set to 8 LTS

Basically this would implement the feature currently provided by Gridelements.

Still there are several places that are not fully covered by Gridelements, so having this feature in the core will have to take care of those as well.

Actions
Copy link
 #16

Updated by Christian Kuhn almost 8 years ago

how does gridelements solve that?

Actions
Copy link
 #17

Updated by Jo Hasenau almost 8 years ago

Christian Kuhn wrote:

how does gridelements solve that?

Gridelements solves that in 3 different places:

1.) Via a hook within the new content element wizard checking some parameters sent by the "add content" buttons
2.) With an itemsProcFunc for the CType dropdown checking some parameters delivered by page backend layouts and/or gridelements backend layouts
3.) With some JS magic during Drag & Drop checking some classes created while rendering the backend layouts based columns in the page module

Still there are things like cut/copy & paste - especially in the list module, references aka "insert records" and other things to take care of, when you want a perfect solution.

I have been contacted by Stucki, since they have got a feature request especially for the "insert records" part, so we should discuss that in a kind of special interest group with you and Benni and maybe create something cool based on sponsoring.

Actions
Copy link
 #18

Updated by Riccardo De Contardi over 7 years ago

  • Target version changed from 8 LTS to 9.0
Actions
Copy link
 #19

Updated by Susanne Moog almost 7 years ago

  • Target version changed from 9.0 to 9 LTS
Actions
Copy link
 #21

Updated by Susanne Moog about 6 years ago

  • Target version changed from 9 LTS to Candidate for Major Version
Actions
Copy link
 #22

Updated by Benni Mack over 4 years ago

  • Status changed from In Progress to Closed

I'm closing this one - for the time being - use content_defender or - if you're already using gridelements - use the gridelements feature. There are no current plans to build this into TYPO3 Core.

We can re-open the issue once people are up for developing this change actively.

Actions
Copy link

Also available in: Atom PDF