Adrian Holovaty wrote:
Seems like its not possible to access request object in hooks like
pre_save and display methods(those are listed in list_display) ? Is it
supposed to be like this by design ? If so then hardly its very
convinient to use in real applications.
Yes, this is by design. Model
couldn't we do something similar to get_active_site() call on the sites table?
that way people who need the 'request' object could just call it and
it wouldn't impact the api of anything else?
On 11/18/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 11/17/05, plisk <[EMAIL PROTECTED]> wrot
On 11/17/05, plisk <[EMAIL PROTECTED]> wrote:
> Seems like its not possible to access request object in hooks like
> pre_save and display methods(those are listed in list_display) ? Is it
> supposed to be like this by design ? If so then hardly its very
> convinient to use in real applications.
Y
limodou wrote:
> 2005/11/17, plisk <[EMAIL PROTECTED]>:
> >
> > Hi there.
> >
> > Seems like its not possible to access request object in hooks like
> > pre_save and display methods(those are listed in list_display) ? Is it
> > supposed to be like this by design ? If so then hardly its very
> > co
2005/11/17, plisk <[EMAIL PROTECTED]>:
>
> Hi there.
>
> Seems like its not possible to access request object in hooks like
> pre_save and display methods(those are listed in list_display) ? Is it
> supposed to be like this by design ? If so then hardly its very
> convinient to use in real applica
Hi there.
Seems like its not possible to access request object in hooks like
pre_save and display methods(those are listed in list_display) ? Is it
supposed to be like this by design ? If so then hardly its very
convinient to use in real applications. For example, i would like to
get server addre
6 matches
Mail list logo
