TYPO3 Core

In terms of having at least something on the way to custom content elements I see TS as CE fit in quite well. Also, there's a page in the wiki "extensions for core" which has served in that regard too. It may not have been updated for long, but that may have other reasons. In the end I'd like to see such a CE.

It could also be "the" replacement for the old PHP CE, and in that regard editing should be limited to admin users I guess...

If I get this here right .. there are already some ext. which do that :)

• http://typo3.org/extensions/repository/view/typoscriptce/current/
• http://typo3.org/extensions/repository/view/tscobj/current/

Greez Jens

I don't see a need for that one...
I'd rather see it as an major security problem offering "TS" to everybody... And restricting it to "admins only"... Well I think admins would not need it but work otherway around, or If they wanna needed just add the 2 lines of ext_tables.php Code and 4 lines of TS-Code to add it...

Implementing this feature at expense of security wouldn't be good of course.
But now I see quite artificial difference between two interfaces - you can create TS elements, but you can include them only in TS Setup, on other hand you have "Content elements" and "Special Content Elements" and Sitemap as TS menu in them.
I just think it would bring more flexibility and userfriendliness to the interface.
TS is not only a configuration script - one can create powerful objects in it, so including them via interface would be helpful.

By the way - very similar feature is present in Templavoila - "Element Preset" -> "Typoscript Object Path" and it tends to be useful.

It certainly makes sense for some sites and setup. TS Object path in TV is something you need to map some TS of yours to some part of the template, something you don't need when using the TEMPLATE object because... you already are mapping stuff with TypoScript.

Of course, it still makes sense (and I had to do it more than once) but you have at least 2-3 "good" extensions doing this in TER and I don't see why you could not just use them, they are there for this very reason!

The extensions are indeed good enough for this purpose for the site which need this.
I agree that there is no need to include this in the core.

Maybe could you share your opinion on the categorization of the Content Elements in another issue or the typo3-core mailinglist? Of couse, you can create a sitemap with TypoScript.. but for the end user/editor, I see no reason, why this somehow relates to the TypoScript CE.

I would like to have it ... I use this (via extension) once a while and I always hate to install an extension for something which should work out of the box.

IMHO the TS itself could be restricted to admin users like it is done for tt_news and cal. (They both allow you to include TS inside their plugin CEs.)
The editor should only be able to see and edit the title (any maybe any other field which is displayed for this content element, if any). Of course he should be able to copy the CE to another page. This could save a lot of those little extensions.

Although, I would prefer something like this: http://fedext.net/fluid-typo3/guides/fluid-flexforms/ but I guess this is not an option ;)