[TYPO3-mvc] RFC #10666: Allow plugins to be registered as new content element

Marc Bastian Heinrichs typo3 at mbh-web.de
Fri Nov 12 23:26:51 CET 2010


Hey Franz,

thanks for your feedback.

> easiest might be to do it the way TYPO3 is doing it by default, so by 
> registering the plugin settings in plugin.tx_extkey_PLUGINSUFFIX and 
> only create a reference to your plugin in tt_content.list.20. Then 
> always only refer to plugin.tx_extkey_PLUGINSUFFIX.

Jep, I also thought about implementing the pluginconfig this way.
But why hasn't Jochen did it this way from the beginning but used
tt_content.list.20.extkey_pi1 = USER?
Another point is, that resolving the configuration from plugin in
Tx_Extbase_Configuration_FrontendConfigurationManager::overrideConfigurationFromPlugin()
is needless then because the configuration given by
tt_content.list.20.extkey_pi1 will be always the same as in
plugin.tx_extkey_pi1

But more imporant is, that the auto detection of the defaultPid in
getTargetPidByPlugin() uses a query to tt_content with "list_type =" and
it would be no nice solution to add an "OR CType = " to the where
condition for me.


Regards,
Marc Bastian






More information about the TYPO3-project-typo3v4mvc mailing list