@dolphin are you talking about this line of code when you are trying to switch themes/templates if someone is an admin ? https://github.com/dphn/ScContent/blob/master/src/ScContent/Listener/ConfigListenerAggregate.php#L98
On Fri, Jan 24, 2014 at 9:27 AM, Marco Pivetta <[email protected]> wrote: > On 24 January 2014 15:19, dolphin <[email protected]> wrote: > > > "Content" gives the main controller. He attaches the child model to > Layout > > ViewModel as "content". Then automatically generated widgets. With the > help > > of "forward". Theme detector should detect "dispatch" of main controller. > > All other "forward" - is the formation of widgets. The detector should > only > > work once, for the main controller. And apply the theme. Backend theme. > Or > > frontend theme... > > > > But the biggest problems do not begin when the layout is generated > > automatically. They start when the main controller itself for any purpose > > carries "forward". This was not at all like to think ... > > > > If I get it correctly, you are misusing "forward" to assemble a complex > view model. Doesn't seem like that's the right way to do it. > > Also, can you provide some context/links to current code? It is really > really hard to follow your train of thought without some actual code > reference to who/what is doing things... > > What exactly is the unexpected behavior that you are experiencing when > using the forward plugin? (also, I avoid it like the pest in most cases, > since it does a lot of pretty much useless magic) >
