Timezone field value always displays as (None) in admin list view about django-timezone-field HOT 6 CLOSED

I've replicated this behavior on django 1.7 as well.

from django-timezone-field.

What's going on here is the django admin is expecting the first argument of the choices list to be of the same type as the value returned by the field. Right now the first argument of the choices list is a string describing a pytz timezone, while the value returned by this field is actually a pytz timezone.

Probably need to specify or at least store choices as (<pytz timezone>, <string>).

from django-timezone-field.

Thanks for looking into this @mfogel

Aha that makes sense. I wonder if there is any way to explicitly tell django what value to use to represent a field for its admin views (like maybe a method that needs to be overridden in the field's class definition or something similar)?

from django-timezone-field.

This is fixed in the 1.3 release I just pushed to pypi a few minutes ago. Give it a try, let me know if it doesn't work for you.

from django-timezone-field.

@mfogel Thanks! I will definitely try it out in the next few hours and let you know if it works 😃

from django-timezone-field.

@mfogel That did the trick 😄 thanks a bunch 👍

from django-timezone-field.