2007/10/17, maschoen <[EMAIL PROTECTED]>: > > > Perhaps the ´flash´ message would be appropriate? > > Thanks for the suggestion, but I don't think you understand the > issue. Which controller would I issue the flash message from? > The login controller is where it needs to go, but doesn't know what > the error message is. The main controller knows the what the error > message is, but issuing the flash message request from it would not > put it where the html is rendered.
I'm not sure if I understand your architecture. Correct me if I'm wrong: You have SomeController, which has SomeAction, which renders SomeView. SomeView includes a login section, which is rendered by, say LoginController, action LoginForm (called by requestAction). LoginForm is submitted to the LoginAction of LoginController. LoginAction processes the data from LoginForm, and redirects back to where it came from (SomeAction in SomeController). If LoginAction would set a flash message, it is perfectly possible for SomeView to show it (in fact, *any* view could render a flash message, irregardless of the controller/action that set it). Martin -- Martin Schapendonk, [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
