search

VOKO-Utrecht / voko

Administration and automation for VOKO
4 stars 8 forks source link

Show last order on profile page in admin #301

Closed mgvd closed 11 months ago

mgvd commented 1 year ago

Members come and go. Sometimes it's hard to see when members are still active and ordering at Voko. If the administrator can see when people placed their latest order, they can assess better if that member is still active or is a sleeping member of Voko

bveldkamp commented 11 months ago

Where exactly should this go? I had a look at this:

Adding the last order date to the users overview page (i.e. /admin/acounts/vokouser) requires just a few lines of code, because we are already overriding the default Django admin page here, and adding a single field is straightforward.

Adding it to the userprofiles page (/admin/accounts/userprofile) otoh looks to be a bit more complicated, because it is still uses the default Django admin page. As far as I can see, we would need to override the entire page to be able to add a single field, similar to how the user overview page now works.

Or should this field be added to a user's page, rather than the overview page? ( /admin/accounts/vokouser/1/change or /admin/accounts/userprofile/1/change , both are also still the default Django pages)

mgvd commented 11 months ago

In that case I would suggest adding it to the admin user overview page ( /admin/acounts/vokouser ), only. The goal is that the admin team can see whether a user is active or not by placing orders.

Op ma 11 sep 2023 om 10:55 schreef Berend Veldkamp @.***

:

Where exactly should this go? I had a look at this:

Adding the last order date to the users overview page (i.e. /admin/acounts/vokouser) requires just a few lines of code, because we are already overriding the default Django admin page here, and adding a single field is straightforward.

Adding it to the userprofiles page (/admin/accounts/userprofile) otoh looks to be a bit more complicated, because it is still uses the default Django admin page. As far as I can see, we would need to override the entire page to be able to add a single field, similar to how the user overview page now works.

Or should this field be added to a user's page, rather than the overview page? ( /admin/accounts/vokouser/1/change or /admin/accounts/userprofile/1/change , both are also still the default Django pages)

— Reply to this email directly, view it on GitHub https://github.com/VOKO-Utrecht/voko/issues/301#issuecomment-1713458757, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARKEMWUIAVM2RJJ3SQLNG3XZ3GXNANCNFSM6AAAAAA2AZPBEE . You are receiving this because you authored the thread.Message ID: @.***>