MATTHEW:No, actually. When you set it as you did in preDispatch(), there is
no
check until postDispatch() to see if a redirect occurred. This should
likely be changed; care to file an issue in the tracker?
ME: I had a similar problem, setting a redirect in the preDispatch() w/ the
same code you
Matthew Weier O'Phinney-3 wrote:
-- fab2008 f.napole...@gmail.com wrote
(on Sunday, 18 January 2009, 05:20 PM -0800):
In every case my interpretation to plugin and redirect behaviour is that
when I'm calling setRedirect into the plugin the controller code will not
be
executed? Is that
-- fab2008 f.napole...@gmail.com wrote
(on Sunday, 18 January 2009, 05:20 PM -0800):
In every case my interpretation to plugin and redirect behaviour is that
when I'm calling setRedirect into the plugin the controller code will not be
executed? Is that right?
No, actually. When you set it as
I'm writing some test for an app, I have a controller named Message
accessible only to logged users, with three actions: compose, preview, send.
One cannot access preview if he has not accessed composeAction succesfully
before. I made this check using a session variable and if this variable is
