I just figured this out. I had an element in the layout which has a line with a requestAction() call. This was responsible for the second call to beforeFilter(); Also, the cake book for 2.3 is a little misguiding in the way it defines the new parameters for cached elements.
On page 50 it specifies the old format of: echo $this->element(’latest_comments’, array(’cache’ => ’+1 hour’)); While on page 80 the new format is given as: $this->element(’helpbox’, array(), array( "cache" => array(’config’ => ’short’, ’key’ => ’unique value’) ) ); This ensured that my element was never cached. Also, there is no default config / path for view cache (in Config/core.php) so view cache files end up in app/tmp/cache/ On Friday, 15 March 2013 00:15:23 UTC+1, Dr. Fox wrote: > > Please correct me if I'm not. > I noticed the call happens twice when I include a call to > parent::beforeFilter() in my controller's beforeFilter method which puts an > overhead on the app. > > > On Wednesday, 13 March 2013 20:27:36 UTC+1, AD7six wrote: >> >> >> >>> CakePHP calls your controller beforeFilter() which already contains a >>> call to parent::beforeFilter() and then calls the AppController's >>> beforeFilter() again. >>> >> That's not how CakePHP works. >> >> AD >> >>> -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
