Re: multiple controllers on 1 page

[Brian French]

It would mainly be for the view. in the controller i would call the requestAction and assign the output to a view variable using set(): $this->set('someBlock',$this->requestAction('Controllers/_Method',array('foo'=>'bar'))); // i think this is right. correct me if im wrong or (refering to the other thread "Simple question about $this->set") you can do it like this: $someBlock = $this->requestAction('Controllers/_Method',array('foo'=>'bar')); echo $someBlock; // refering to other thread in groups $this->set('someBlock',$someBlock); anyone, correct me if im wrong. Brian French [EMAIL PROTECTED] wrote: bwaters wrote: It seems that the consensus is to put the blocks into elements and if they have data use a requestAction inside the element that returns a data array containing whatever information you need. There are lots of other ways to skin this cat, depending on your situation and how many blocks you are talking about. Using requestAction(controller/action, array('return' => 'true'); is easier but the overhead of multiple views being rendered will kill you if you have several blocks per page. I am currently changing my whole project over to the elements / requestAction combo instead of the RequestAction / view (return => true) way of doing things. Hello Brian. Where are you putting all the elements together? e.g: domain/pages/home.thtml or in view? I am also currently doing a small project where I need to access different controlelrs on each page - so this post is very interresting to me. Best regards. Asbjørn Morell. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---