Le 10 sept. 08 à 10:24, Thomas Rabaix a écrit :
> Hello,
>
> You can used your own caching mechanism with a filter.
>
> You may have a look to sfFunctionCache to store and retrieve your
> breadcrumb. The only problem is to invalidate the cache breadcrumb
> when the view change.
Yes, I could use
Hello,
You can used your own caching mechanism with a filter.
You may have a look to sfFunctionCache to store and retrieve your
breadcrumb. The only problem is to invalidate the cache breadcrumb
when the view change.
Thomas
On Wed, Sep 10, 2008 at 8:06 AM, Nicolas CHARLOT <[EMAIL PROTECTED]> wr
Le 10 sept. 08 à 04:52, Kris Wallsmith a écrit :
> If you want to store a variable to the request scope in sf1.1, use the
> request attribute holder:
>
> sfContext::getInstance()->getRequest()->setAttribute('foo', 'bar');
>
> Is that what you're asking?
No, I'm asking for a way to store one or m
If you want to store a variable to the request scope in sf1.1, use the
request attribute holder:
sfContext::getInstance()->getRequest()->setAttribute('foo', 'bar');
Is that what you're asking?
Kris
On Sep 9, 2008, at 8:27 AM, Nicolas CHARLOT <[EMAIL PROTECTED]> wrote:
>
> Le 9 sept. 08 à 16
Le 9 sept. 08 à 16:48, CaffeineInc a écrit :
> it does support parameterHolder.. but the way you access it is
> different as context is now a singleton.
>
> sfContext::getInstance->getRequest()->getParameterHolder();
>
> will work the same way.
> or $this->getRequest()->getParamterHolder() from y
it does support parameterHolder.. but the way you access it is
different as context is now a singleton.
sfContext::getInstance->getRequest()->getParameterHolder();
will work the same way.
or $this->getRequest()->getParamterHolder() from your action.
On Aug 19, 6:58 pm, Nicolas CHARLOT <[EMAIL
Hello,
Have you found a way to make this work ?
I maybe have a solution :
replace with getRequest()->getParameterHolder()-
>has('isicsBreadcrumbs'))
On 20 août, 01:35, Dustin Whittle <[EMAIL PROTECTED]>
wrote:
> Nicolas,
>
> I have run into the same issue and my solution was to extend the vie
Nicolas,
I have run into the same issue and my solution was to extend the view class
and add the data as part of the response content. Also, you can define a
contextual slot (with a cache_key tied to the uri. (which will get cached).
Otherwise, you might be able to store as a user attribute.
- D
