I've run into the same problem. The closest thing I've found is the requestAction() function of the Controller object (I'm using 1.0). Trouble is, requestAction() doesn't seem to load the JavaScript which is problematic if you're doing AJAX.
Ideally, the Controller::redirect() method would handle how it processed the redirect() request: if it were non-AJAX, it would send the HTTP redirect; if it were AJAX, it would "redirect" internally. Yes, it could get out of hand and hard to debug, but that's going to be up to the developer to avoid and remedy. I don't think it's any more complicated than using AJAX -- it would actually make it simpler. Anyway, just wanting to add my vote for this feature. I'm going to check the ticket system now... On 5/4/06, Armando Sosa <[EMAIL PROTECTED]> wrote: > maybe just calling the action? > > $this->action() > > or using controller::setAction() > > > On 5/4/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > I think this could get out of control quickly and be very hard to > debug. Pages coming up from other methods but listed in the browser > under another method. Could get very confusing and no real way to > debug. If you used AJAX at least you could have a program to capture > the XMLHTTPRequests. > > I would rethink what you are doing. > > > > > > -- > Armando Sosa > > www.nolimit-studio.com > www.dospuntocero.info > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
