[TYPO3-dev] Writing to page type <> 0

[Christian Lerrahn (Cerebrum)]

Hi Joey,
hi Wolfgang,
thanks for these insights. I never thought that you would use an
additional trigger to get this to work. However, these explanations
still use me with the question why my plugin would be considered an
"Unredered content element" in a wrong context if apparently it doesn't
matter to the extension. Is it just that the core would ignore the
extensions output if it doesn't come with the appropriate TS?
"Unrendered" gives the impression that the plugin did refuse to provide
input but, of course, it could also just never have been called.

In any case that has clarified things a lot for me. Thanks for that.

Cheers,
Christian

On Sat, 17 Feb 2007 12:08:02 +0100
Wolfgang Klinger <wolfgang at stufenlos.net> wrote:

> *hiya!*
> 
> Christian Lerrahn (Cerebrum) wrote:
> > If this is it, it probably is. However, I need to know more than
> > this if I want to use it. How can the plugin react to the typeNum
> > if it is only defined like this? It will not know what kind of
> > context it is run in. That is what has always been (and remains) a
> > mystery to me. E.g. if I wanted a plugin to write a different kind
> > of output on typeNum=99 that typeNum=0, how would I do this. That's
> > the reason why I ask the question here. I know how the TS works but
> > how does it work in the plugin? I just haven't been able to
> > disentangle the whole concept at all.
> 
> $GLOBALS['TSFE']->type
> is what you're looking for
> 
> HTH
> bye
> Wolfgang