hmm, maybe you need a custom Select Widget for your custom field? Or check out the select widget and see if it's looking for any _meta information on the field that determines how the widget is displayed.
On Tue, Jun 19, 2012 at 8:49 AM, Melvyn Sopacua <[email protected]>wrote: > On 19-6-2012 14:45, Juan Pablo MartÃnez wrote: > > You saw this? > > > > > https://docs.djangoproject.com/en/dev/howto/custom-model-fields/#django.db.models.Field.to_python > > Yes, that's not the issue. I've implemented to_python and get_prep_* and > everything goes ok, until the field gets used as Foreignkey. > In fact, even that goes ok, cause I get the correct related object. It > is *only* the Select widget where things go wrong. > > -- > Melvyn Sopacua > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to [email protected]. > 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. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
