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

[Jochen Rau]

Hi.

On 2010-11-13, Franz Koch <typo3.RemoveForMessage at elements-net.de> wrote:
>> 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.

Yes. The goal was to hide the low level plugin registration and
configuration. It's a cleaner solution. But I must admit that it might
became a bit more confusing.

>> 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?

Seems that we have to add the OR statement.

Marc Bastian, could you please provide an updated version of the patch.
This should go into Extbase before beta1 (next Tuesday).

Thanks a lot!

Jochen

-- 
Every nit picked is a bug fixed