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

[Marc Bastian Heinrichs]

Hej Franz,

>>> 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?
> 
> Well, good question. It's of course a much cleaner code the way it's 
> done now. You have one central plugin configuration and all the 
> "special" configuration like which controllers and actions are allowed 
> are hidden from the average user in tt_content.list.20.
> Now you would have multiple plugin.tx_extkey_suffix entries as well as 
> plugin.tx_extkey (shared settings) in your TS tree, which could become a 
> bit confusing maybe.
> 
>> 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
> 
> Yes, it should be the same so that it could be dropped - except we keep 
> all the persistence and view settings only in plugin.tx_extkey and don't 
> create referenced copies in the plugins configuration itself. Might be 
> less error prone a probably more save for adding new features.
> 
>> 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.
> 
> I know why I never liked the autodetection ;) - but the OR condition 
> would be the only solution, wouldn't it?

okay, you got me. :-)

But I want to hear Jochens position to this first.
If it's okay for him, I could adapt the patch tomorrow.

Another idea is to have an way of pluginregistry where the type is
saved in conjunction with the pluginSignature.


Regards,
Marc Bastian