Mariano, thanks for the code snippet. Good in theory but proves problematic in practice.
As I'm calling requestAction on the controller immediately after checking that it exists I'm getting a class redeclaration error on the controller class. never mind, thank you again for the code. i might run on the fact that the action simply has to be there for the time being. in the next application i'll look at error handling. thanks again fellas, mikee On 12/12/06, Chris Hartjes <[EMAIL PROTECTED]> wrote: > > On 12/11/06, Mikee Freedom <[EMAIL PROTECTED]> wrote: > > > > It wouldn't so much be an error. i.e. I wouldn't want to report to the > > user that something has gone wrong, I just don't want to perform that > > action if it is not there. > > > > It's more about trapping the errors that CakePHP itself generates. > I've never done anything like that, so I couldn't tell you where to > start. > > Hrm...sounds like a topic for a blog post in the next few days. :) > > -- > Chris Hartjes > > "The greatest inefficiencies come from solving problems you will never have." > -- Rasmus Lerdorf > > @TheBallpark - http://www.littlehart.net/attheballpark > @TheKeyboard - http://www.littlehart.net/atthekeyboard > > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
