Brandon Bernal bjlbernal
bjlbernal
/ 1. Use Controller::afterFilter()
Last active
March 21, 2016 16:47
Cake Events (2.* at least) do not have to block controller logic, and you don't have to have a separate queuing system to process the events. Simply have them handled in the Controller::afterFilter() method. Per cake docs, the Controller::afterFilter() method is called "after the rendering" of the view is complete. This may be a more fragile way…
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <?php | |
| class AppController extends Controller | |
| { | |
| ... | |
| public $afterFilterEvents = array(); | |
| public function afterFilter() { | |
| parent:afterFilter(); |