I found that action which change campsite objects (like
$campsite->user->some_property) are processed after the context was
initialized. This means that changed values are not reflected on the first
page after an action was taken.
Is this the reason why login/logout actions causes an reload of the page?
Will this be changed in future?
The request actions are processed after the context initialization because
they need the context to be set up before they run. In the takeAction()
method of the action object you can modify the context objects as needed (as
it happens in the login action). The reason the logout page needs a reload
is because there is no logout action implemented in the template engine.
Instead the logout is done in the template, checking for logout parameter
and if found setting the user cookies to null.
Mugur
On Tue, Feb 26, 2008 at 7:09 PM, Sebastian Goebel
wrote:
> Hi,
>
> I found that action which change campsite objects (like
> $campsite->user->some_property) are processed after the context was
> initialized. This means that changed values are not reflected on the first
> page after an action was taken.
> Is this the reason why login/logout actions causes an reload of the page?
> Will this be changed in future?
>
> Best,
> Sebastian
>