With regards to the history log on models in the admin view.
I am adding instances of models via the db api (model.save())
method. When such a model is opened (but not edited) and then saved
for the first time in the admin model view a history log entry is
created showing ALL elements of the mo
Thanks Karen & Daniel,
I think your overiding approach will work. Thank you.
Implemented a work around. I added extra fields (that persist my
method information) to my model that I update and save when I do a
listing. Price I pay is an extra database update each time the model
is getting list
..and
therefor not visible to the fieldsets field?
Still clear as mud?
On Jan 7, 5:48 pm, Daniel Roseman
wrote:
> On Jan 7, 10:35 am, EagerToUnderstand wrote:
>
> > I am referencing a self defined model method in list_display option of
> > ModelAdmin. I would like to
I am referencing a self defined model method in list_display option of
ModelAdmin. I would like to do the same in the fiedsets option of
ModelAdmin, but I get an error saying my method is missing from the
form when the page is rendered. It seems to me I can only render
model methods with list_di
I would like to change the information/size of the returned HTML page
depending on the User-Agent accessing the content.
(Typically rendering a smaller page for a PDA than for a PC browser.)
I know how to get hold of the User-Agent. It feels to me like this
must be a common requirement, yet I can
5 matches
Mail list logo
