[Typo3-dev] General records strategy

[Jean-David Gadina]

May we discuss about a major missing feature in the general storage strategy of Typo3?

Imagine a site made with TemplaVoila. The general record storage field of your root page is set to the sysfolder containing your TV records. Now imagine you need a loginbox in a subsection, and another one with different users, in another subsection.

In order to implement the newloginbox plugin, you need to define the sysfolder containing your fe-users as a general record. If you do that in the subsection, you won't be able to access the TV records anymore from that page.

And what would happen if you also need to use the tt_news plugin? And the CHC forums extensions, which also use the general records field? It will become a complete nightmare.

For now, the only "solution" seems to store everything in the same sysfolder. From my point of view, it's not logical at all. It could maybe work for a small site, with a few records. But it won't if you need to separate your records in different sysfolders. You may need to separate them, for instance, to set the permissions of a be-user group only on a specific sysfolder, in order to give access to specific records and not to all of them. It would also cause problem, in the loginbox scenario, if you don't want to give the possibility of all the fe-users to login everywhere.

I think the problem is in the getStorageSiterootPids() method of the tslib_fe class. In the comments, it's said:

«returns an array with the first occurrance of storage pid»

Why the first occurence only? This method should inherit the general records field from the complete tree. In that way it would be possible to access the general records of a top page. The method should also be recursive to allow the use of records in a sub sysfolder, for instance.

Does that make sense?

- Jean-David Gadina (macmade)

-----------------------
The mailing list archive is found here:
http://typo3.org/documentation/mailing-lists/dev-list-archive/