Doh. Not exactly a bug but not exactly intuitive behavior either.
I think that the correct behavior in the MVC model is for a controller function X to map to view X - both in invocation and on return. I would not have assumed that the view needs to explicitly specify return of control to the controller function that invoked the view in the first place. That behavior is a bit inconsistent I think. But - now I know Danny On Mar 11, 1:40 pm, majna <majna...@gmail.com> wrote: > yes, set controller and action params in form helper. > > On Mar 11, 12:05 pm, Danny Lieberman <onlyj...@gmail.com> wrote: > > > I have a controller with the usual CRUD functions and I added an > > additional function called fu (followup) > > > The fu function has it's own fu.ctp view and after the user enters > > data in the form, it saves the data to the database using a save > > method > > > The only problem is that cake always returns control after the form > > submit to the edit function, not the fu function. This is bolloxing > > up the application to say the least. > > > I guess that this is some kind of automagic stuff but I have not been > > able to figure out how to ensure that control after save will not be > > automagically passed to an edit function > > > Be happy to get an explanation how to fix this issue > > > Danny --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
