[TYPO3-templavoila] Dropping the 'General Record Storage Page' requirement for TV?

[Ernesto Baschny [cron IT]]

Franz Koch schrieb am 18.04.2006 18:32:

>> Yes, I see and understand :) I share your view. I am just trying to tell
>> that it will be hard to change. It is easy to obtain storage PID, it is
>> just a single call to the core.

> I know that it won't be easy to change (never said that ;-) ), but
> that's why I started the discussion here - to find a way or a solution
> that might suite better in future.
> Fetching the storage PID might be a single call in the core - but I
> suppose this single call will also perform a full rootline-scan for a
> storage folder.

Any FE-plugin will get its own parsed $conf which comes from TypoScript
from your template, which is why they are already using it to store
various pid's. I think the main problem are backend modules, where you
don't have a working $conf because the TypoScript from your templates
won't be parsed at this point (I think), only the PageTS.

So you could store the pid in the PageTS and find some method to get it
(there must be a simple API call to do that). But then you would have to
store the pid's twice, which adds more headache to the poor site admin.

I don't like the while idea of separate TS-template and PageTS anyway, I
think one tree would be sufficient and avoid lots of confusion. Parsed
Typoscript from TS-Templates is cached anyway, so it shouldn't be too
hard or costy to get this in backend also (or would it?). If we had
this, everything (BE and FE) could be configured through TS-templates,
with all the benefits we have there (nesting, inheritance, constants,
TypoScript in external files, etc). It also also easier for extensions
to provide TS-templates to be included as static templates than it is to
set "PageTS" settings (those are either set or not sitewise, usually
through checkboxes in the Ext Manager).

Cheers,
Ernesto