To automate the process you could make a myactions.class.php file in the lib dir that extends sfActions then change all of the actions under your modules folder to inherit from myactions. Then create a forward404WithMessage($msg) function that automatically sets the msg as an attribute, say named __404Msg or something and then calls forward404. I do a similar thing in most of the projects I work on, except I don't do a 404, I just create an error module, that way there isn't a 404 status header. I have found though that creating a custom actions class that all actions inherit from has helped me automate things like this a lot. Most specifically email.
On Sep 15, 2:44 am, Davide Borsatto <[email protected]> wrote: > I think a flash message for the user object would do the job --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
