[TYPO3-dev] Protection of a bug WAS: ext_typoscript_setup.txt

[Elmar Hinz]

Elmar Hinz wrote:
>> TS-objects as we currently have. We might move all this to lib.*, which
>> is also being used for example for parseFunc_RTE (content renderers just
>> reference to that).

> Both of your proposals would be possible, a function or a
> "lib.plugin.tx_xyz" tree. Using a function would be backward compatible
> with the old addPItoST43() so that a lot of plugins could be used within
> the new renders without alteration.  A "lib.plugin.tx_xyz" tree could be a
> future move.
> 

We already have this plugin tree as:

"plugin.tx_mypinboard_pi1."

But in the tt_content list field the key for it is:

"my_pinboard_pi1"

That is the reason why we need to do a connection by hand (or by function
that builds both ends) for each plugin in position:

"tt_content.default.list.20.my_pinboard_pi1."

An automated connection could be build by any renderer, if we would rename
the plugin tree a little so that the key matches the database entry:

FROM: plugin.tx_mypinboard_pi1
TO:   plugin.my_pinboard_pi1

Then the path "tt_content.default.list.20." could become flexible.

The successor of addPItoST43() would just drop plugins in
"plugin.my_pinboard_pi1". Any renderer could pick them up and use them in
the way it likes.

Regards

Elmar