The change_messages logged in the admin site's object history use the actual Python model field names. Is there a more or less trivial way to force it to use the fields' verbose_names instead?
This would make history pages more meaningful for non-developers who use the admin site. Additionally, it could then benefit from L10n if used in the project, specifically: if the verbose_name gets translated nicely. At the moment, the worst case is when a non-English speaking user comes across a history entry that is pretty much uninformative as there's no way to guess what that perhaps rather technical field name actually represents. OTOH, for a dev debugging the app, the status quo might be preferable, so not I'm sure about opening a ticket. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
