On 1 Apr., 12:22, "Ian P. Christian" <[EMAIL PROTECTED]> wrote:
> Kasper G wrote:
> > On 31 Mar., 22:09, "Mohammad Ali Safari"<[EMAIL PROTECTED]>
> > wrote:
>
> >> You probably want to use flash
> >> instead:http://www.symfony-project.org/book/1_0/06-Inside-the-Controller-Laye...
>
> > Using flas
Kasper G wrote:
> On 31 Mar., 22:09, "Mohammad Ali Safari"<[EMAIL PROTECTED]>
> wrote:
>
>> You probably want to use flash
>> instead:http://www.symfony-project.org/book/1_0/06-Inside-the-Controller-Laye...
>>
>>
>
> Using flash is essentially storing the value in the session with the
>
On 31 Mar., 22:09, "Mohammad Ali Safari" <[EMAIL PROTECTED]>
wrote:
>
> You probably want to use flash
> instead:http://www.symfony-project.org/book/1_0/06-Inside-the-Controller-Laye...
>
Using flash is essentially storing the value in the session with the
added convenience of automated cleanup.
Hi Kasper
You probably want to use flash instead:
http://www.symfony-project.org/book/1_0/06-Inside-the-Controller-Layer#Flash%20Attributes
-Mohammad
On Mon, Mar 31, 2008 at 2:04 PM, Kasper G <[EMAIL PROTECTED]> wrote:
>
> Thank you for your response, Olivier. Storing the value in the session
>
Thank you for your response, Olivier. Storing the value in the session
(through getUser()) is indeed an option. However I do not consider it
a very "clean" one.
The information need only be accessible during the current request
after the forward but not during subsequent requests. Storing it in
t
To retain values, you can do like the filters in Admin generator
To set
$this->getUser()->getAttributeHolder()->removeNamespace('frontend/test/filte
rs');
$this->getUser()->getAttributeHolder()->add($filters,
'frontend/test/filters');
To get
filters =
$this->getUser()->getAttribu
