admin for "regular" users - still a bad idea?

2009-11-26 Thread Count László de Almásy
i've seen notes in some django documentation that implies that using / admin/ for non-trusted users is not a good idea. which is unfortunate since it seems like the admin interface is about 95% of what i want for my users to be able to view and manipulate their sales transactions data over the web.

Re: admin for "regular" users - still a bad idea?

2009-11-26 Thread Count László de Almásy
ok, fair enough. does generic views have the machinery to replicate the admin interface? On Nov 26, 7:28 pm, Skylar Saveland wrote: > Yep, still a bad idea.  Permissions are by table not by row.  Use > generic views for basic CRUD. > > Count László de Almásy wrote: > > > &

Re: admin for "regular" users - still a bad idea?

2009-11-27 Thread Count László de Almásy
On Nov 27, 12:30 am, Skylar Saveland wrote: > ha, reading lists on mobile ... I didn't even see that you said that > each user has their own table (still hard to see exactly how this is > efficient/possible/done though).   what do you mean? i just meant that in my database, sales transactions are

Extending result count at bottom of admin pages

2009-12-06 Thread Count László de Almásy
I'm new to django but working hard to come up to speed. I need to make a small change to the admin interface, and am hoping i could get a pointer on how to do this. At the bottom of an admin page, the number of results is displayed in a summary, along with pagination buttons. For example, "1 [2] 7

Re: Extending result count at bottom of admin pages

2009-12-07 Thread Count László de Almásy
On Dec 6, 9:33 am, Kaze wrote: > You can override "changelist_view" function in admin.py for that > model. ok, thanks, that helped me figure out a solution. here's what i added to admin.py within my Sales class. i can then access 'cl.amount_sum' from my pagination.html template. anything wrong wi