[TYPO3-mvc] storagePid makes trouble in some cases

[dennis ahrens]

Hi,

i think it would also be nice to tell the whole persistence layer that
it doesn't have to take care about the storagePid

plugin.tx_blogexample {
       persistence {
               storagePidUsage = 0/1
       }
}

Instead of using a special parameter it may behave like this, when i
do not configure any storagePid for my plugin/module.

regards
Dennis

2010/3/2 Martin Kutschker <masi-no at spam-typo3.org>:
> Jochen Rau schrieb:
>> Hi.
>>
>> I agree with you that the current solution to configure the storage pid
>> is not the best solution. I'd like to define a storagePid for every
>> Domain Model sparately by overriding a default storagePid.
>>
>> Any suggestions about how the TS config should look like? I suggest to
>> have it in the config.tx_extbase namespace:
>
> Sounds reasonable.
>
> But this raises a question for me: is there any distinction of configuration between
> installation-wide and site/page-wide options? For me stuffing like mapping should be installation
> wide, but the storage pid isn't.
>
> Of course it's easy to override a TS setting per page, but now all the configurations are clumped
> together in config.tx_extbase.
>
> Masi
> _______________________________________________
> TYPO3-project-typo3v4mvc mailing list
> TYPO3-project-typo3v4mvc at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-typo3v4mvc
>