Bug #39126
Forward to Action in Different Controller - TypoScript Configuration is Kept
| Status: | Rejected | Start date: | 2012-07-20 | |
|---|---|---|---|---|
| Priority: | Could have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Extbase: MVC | |||
| Target version: | - | |||
| Has patch: | No | Tags: | ||
| Votes: | 0 |
Description
Hi
I don't know if this is a bug or an intended behaviour:
In a Controller used for a Frontend-Plugin, I forward to an Action of a different Controller in a different Extension using forward(..).
extA:controllerA:actionA >>> extB:controllerB:actionB
If there is a TypoScript-Configuration for extA, this will cause several effects:
- controllerB can't render the view for it's actionB, because it tries to find the template it in the path configured in the TypoScript-Config of extA.
- Also the storagePid of extA from TypoScript will be used in the injected Repositiories.
If extB also has a TypoScript-Configuration, this does not fix the issue, it will not be loaded on forward(). I first used the injected configurationManager to re-load an re-set the framework-configuration to the extB-context before I call forward in actionA. This worked except the storagePid from my extB-config was still not applied. At the end I simply removed all typoscript-configuration for the extensions and set the storage-pid for extB-data also in the FE-Plugin record.
For my understanding, the typoscript-config of extB should be loaded and applied on forward(?).
History
Updated by Alexander Schnitzler 7 months ago
- Category set to Extbase: MVC
Updated by Marc Bastian Heinrichs about 1 month ago
- Status changed from New to Rejected
This intended behaviour. It's not intended to forward between extensions.