That is what I am saying Nate. exit() does indeed break normal CakePHP functionality. Albeit you can break it if you want to. It is just that it indeed does. So, I am wondering why not ever time we see this instead recommend return false which gives the same result without breaking CakePHP.
I mean I know more people don't use the after callbacks than do, but do see what I am saying. Also, return false and exit() would both end the action there. What if one was to call a requestAction() that had an exit in it? Would that stop CakePHP altogether or just that requestAction run of it? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
