Bug #29525
Backend module should have its own controller
| Status: | Rejected | Start date: | 2011-09-06 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
Description
Hi,
maybe I did also something wrong but I added a FE plugin and a BE module and they use the same controller. IMO this should be use a different one?
History
Updated by Bastian Waidelich over 1 year ago
Georg Ringer wrote:
Hi Georg,
maybe I did also something wrong but I added a FE plugin and a BE module and they use the same controller. IMO this should be use a different one?
Why do you think that?
In DDD a controller is bound to one Domain Model - and that should be the case whether you're in FE or BE. Obviously it could use different templates, configuration & access rights depending on the TYPO3_MODE, but if you can avoid multiple controllers for one model you should do so.
Updated by Nico de Haen over 1 year ago
- Status changed from New to Rejected