[TYPO3-mvc] extbase as new content element

[Jochen Landvoigt]

  Yes great this works for me and i also think thats the better way to 
do it.

But the typoscriptcode to create the new plugin has a little bug. It 
should be tt_content.tx_mypluginascontentmodule instead of 
plugin.tx_mypluginascontentmodule
The complete correct code that works for me is:
plugin.tx_mypluginascontentmodule =< 
tt_content.list.20.[yourextensionkey_and_pluginkey]

So there will be no extended function of 
Tx_Extbase_Utility_Extension::registerPlugin to add the Plugin as CType 
instead of list_type?
I think it could be possible to send an additional parameter to the 
function which defines the type.

Greets

Jochen


Am 08.10.2010 16:45, schrieb Sebastian Kurfürst:
> Hey,
>
>> don't use configurePlugin - add the created typoscript yourself like this:
> I'd like to strongly discourage you from that way, as this can break a
> lot of things!
>
> Instead, use registerPlugin in ext_localconf.php, and then create a new
> plugin like that:
> plugin.tx_mypluginascontentmodule =<
> tt_content.list.20.[yourextensionkey_and_pluginkey]
>
> so let the TS be autogenerated by extbase. In ext_tables.php you can do
> it as described afterwards:
>> t3lib_extMgm::addPlugin(array('FhhLinkliste', 'tx_fhhlinkliste'), 'CType');
> Greets,
> Sebastian
> _______________________________________________
> TYPO3-project-typo3v4mvc mailing list
> TYPO3-project-typo3v4mvc at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-typo3v4mvc
>